Proposals for existing clients should feel different from first-time proposals — because they are different. The credibility work is done. The client already trusts your quality, your communication style, and your follow-through. Your proposal can start from that foundation instead of building it from scratch.
What changes in an existing-client proposal
Shorter overall. You don’t need to build the full case. Skip the bio section or shrink it to one sentence. Cut the “why hire us” positioning. The relationship does that work.
Lead with the relationship. Reference the previous engagement in your opening. What did you deliver? What did it produce? This reinforces why they should continue working with you before you even describe the new scope.
More direct tone. You’ve emailed back and forth. You’ve been on calls. The proposal can sound like you — not like a formal document from a stranger. Don’t overcorrect and become too casual, but drop the “we are pleased to present” formality.
Same core structure. Even though the document is shorter and the tone is warmer, the structure stays: project summary, deliverables, timeline, price, next step. The client still needs to know what they’re approving.
Sample proposal for an existing client
Here’s a complete example. Context: a freelance developer writing a proposal for a client they completed a website project with six months ago. The new work: adding an e-commerce store section.
Proposal: E-Commerce Integration Prepared for: Marta Solis / Bloom Ceramics Date: May 27, 2026 Proposal: 2026-019
Project summary
Following the website launch in November, Bloom Ceramics has a strong online presence and is now ready to add direct-to-consumer sales. This proposal covers the integration of an e-commerce module — product pages, cart, and checkout — using your existing Webflow site as the foundation.
What I’ll deliver
- Product listing page template (built once, reusable for all products)
- Individual product page template with image gallery, description, sizing, and Add to Cart
- Cart and checkout flow using Stripe via Webflow Commerce
- Order confirmation and email notification setup
- Mobile-optimized across all new pages
- 2 rounds of revisions
- 30-minute walkthrough call + written documentation for adding new products
Timeline
| Phase | Description | Duration |
|---|---|---|
| 1. Setup | Stripe connection, product structure, architecture | Days 1–2 |
| 2. Templates | Product listing + individual product pages | Days 3–7 |
| 3. Checkout | Cart, checkout, confirmation flow | Days 8–11 |
| 4. Revisions | Two rounds based on your feedback | Days 12–16 |
| 5. Launch | QA, handoff, walkthrough | Day 17–18 |
Total: approximately 3.5 weeks from kickoff. Timeline assumes your product images and copy are ready at kickoff.
Investment
$4,200 — 50% on signing ($2,100), 50% on final delivery ($2,100)
Included: all above, up to 2 revision rounds Not included: product photography, copywriting, additional pages beyond scope above
Next step
Reply to confirm and I’ll send the contract + first invoice today.
That proposal is 270 words. It took about 20 minutes to write. The client knows the developer, trusts the developer, and just needs to see scope and price to say yes.
Notice the opening: it acknowledges the previous project and connects the new work to it. “Following the website launch in November” signals continuity. The client feels like this proposal is part of an ongoing relationship, not a sales pitch from a vendor.
What to reference from previous work
The more specific the better. Don’t just say “our previous engagement.” Say what you delivered and, if you have it, what the result was.
“The email nurture sequence we built in Q1 is now converting at 3.4% — ahead of the 2% benchmark you set.”
“The brand identity guidelines I delivered in March are now being used by your internal team and three contractors without any handoff calls.”
“Since the site redesign, your organic sessions are up 41% month-over-month.”
You don’t need a full case study. One sentence with a real result is enough to remind the client why they should continue working with you.
When to use this format vs. a longer proposal
Use the shorter existing-client format when:
- The client knows your work well (more than one project together)
- The scope is contained and clear
- You’re extending existing work or adding to an established system
Use a more complete proposal format when:
- The new scope is significantly larger or different from past work
- There’s a new decision-maker or stakeholder involved
- The engagement represents a major shift in the relationship (first retainer, much higher value)
In the second case, the proposal needs to re-establish context for anyone reading who doesn’t know your history with the client.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
