Repeat client proposal: what to cut and what to keep from last time
Writing a new proposal for a client you already worked with? Cut repeated proof and bios; keep scope, pricing, and what changed since last project.
A repeat client is one of the best leads you will get. They already know how you communicate, how you handle surprises, and whether you finish. Yet freelancers often send the same long proposal they use for strangers: full bio, full portfolio tour, full manifesto on process. That reads like you forgot you worked together, or like you are a vendor who sends boilerplate to everyone.
Repeat proposals should be shorter, more specific, and forward-looking. They should answer: what is different this time, what will you deliver next, and what do you need from them to start.
This guide covers what to cut, what to keep, and how to handle awkward cases (scope creep, new stakeholders, new platform). For invite-style warmth on Upwork, see invitation-only Upwork: shorter proposal structure. For not sounding cloned when you reuse blocks, see reuse proposal across similar jobs.
What repeat clients already know (so you stop re-selling it)
They often already know:
- Your general skill level and role
- That you respond within a reasonable window
- How you handle revisions (even if they want tweaks this time)
- Whether you are reliable on deadlines
They usually still need:
- Scope for this engagement (not last project)
- Price for this engagement (rates change, scope changes)
- Timeline and dependencies (their team changed, their launch moved)
- What changed since last time (stack, brand, stakeholders, compliance)
Your proposal should read like chapter two, not the series recap.
What to cut from last time’s proposal
Cut the long introduction and credential stack
No “I am a passionate professional with ten years…” unless you are reintroducing yourself to a new stakeholder on their side. If a new marketing manager joined, one short line of context is enough:
For context, I worked with [Name/team] on [project] in [month/year], delivering [outcome].
Cut repeated portfolio links they already saw
Point to new work since last project, or one link that is directly analogous to this brief. See reference past work without dumping ten links.
Cut re-explaining your entire process
Unless they asked for a change, assume the process worked. Mention only what is different: async vs calls, new tool, stricter QA.
Cut defensive reminders of how great last time was
One honest line can help. A paragraph of nostalgia does not.
Cut re-negotiating trust they already gave
Repeat clients hire again because trust exists. Over-explaining “communication skills” sounds like you regressed.
Cut copying the old proposal without updating numbers
Stale rates and old milestones are how repeat relationships break. Update everything.
What to keep (or add more of)
Keep a clear scope box for this job
Even retainers need boundaries.
This engagement covers: [list]. Out of scope: [list]. First deliverable by [date].
For scope protection language, borrow from posts about milestones and boundaries. Propose milestones when the client never mentioned milestones still applies when they send a vague “same as before.”
Keep explicit pricing and what moves it
Repeat clients appreciate directness. If rates went up, say so with a reason tied to value or market, not guilt.
My rate for this phase is [$X/hour or fixed $Y] based on [scope]. If we add [extra], I will quote change-order style before work starts.
See fixed-price project proposal pricing when the new job is fixed bid.
Keep a short “what changed since last project” section
Three bullets max:
- New goal or KPI
- New tools or team on their side
- New risks you see (legal, performance, seasonality)
That section signals you are not on autopilot.
Keep one next step tuned to history
If you want me to start Tuesday, approve milestone 1 here and I will reuse the same Figma structure as last time so your team recognizes the handoff.
Familiarity is a feature when you name it.
Three repeat-client proposal shapes
Shape A: Same client, new project (most common)
Length: short to medium.
Opening: reference last project in one line.
Body: scope box, timeline, price.
Close: kickoff action you both already understand.
Example skeleton:
Following [last project], you want [new outcome]. I would scope milestone 1 as [deliverable] by [date] for [$Z], assuming [access]. Out of scope for this phase: [items]. If that matches, [platform action] and I will send the same kickoff checklist we used last time, updated for [new detail].
Shape B: Retainer continuation
Length: short.
Focus on hours, channels, response window, and what is not included. Clients often try to add work without adding budget. A calm “out of scope” line saves you. Compare tone to maintenance-style thinking in your niche; keep it practical, not legalistic.
Shape C: Repeat client, new stakeholder reading the proposal
Length: medium.
One paragraph of context for the new person, then the same scope and price discipline as Shape A. Do not force the new stakeholder to dig through old threads.
When last time did not go perfectly
You can still win repeat work if you handled problems professionally.
Do: acknowledge process fix briefly (“Last time revisions ballooned; this phase includes two structured rounds with written feedback between.”)
Do not: rehash disputes, blame, or passive-aggressive reminders.
If last time ended badly, a full new proposal may not be the right tool. A direct conversation might come first. This article assumes they reached out again or posted a new job openly.
Reusing old proposal text without sounding lazy
Reuse structure, not paragraphs.
Checklist:
- Every date, rate, and deliverable is updated
- At least three sentences reference this brief only
- Links point to relevant new proof
- Stakeholder names are current
Run the proposal checklist like any other send.
Platform notes
Upwork: repeat clients may use Invite to Job or a new contract. Shorter letters win. Do not paste your profile overview.
Email / direct: repeat clients still need scope in writing. “Same as last time” is not a scope.
Fiverr: repeat orders sometimes skip long messages. When a custom offer is required, still state deliverables and revisions.
FAQ
Should I discount because they are loyal?
Optional, not required. Many freelancers give priority scheduling or a small bundle value instead of cutting rate. If you discount, tie it to something (faster payment, longer retainer), not guilt.
They said “just do it like before.”
Reply with a short written scope: “Last time that meant A, B, C. This time I will deliver A and B by [date] for [$X]. Confirm?”
They want a new free test even though we worked together.
Treat as a yellow flag. Offer a paid small task or skip. See unpaid test task requests.
Can I skip the proposal and start in chat?
For tiny tasks, sometimes. For anything non-trivial, put scope in writing on-platform. Repeat clients deserve the same protection you deserve.
Before you send
- Did I cut bio and portfolio noise?
- Did I add “what changed” since last project?
- Are price and milestone 1 current?
- Would this make sense to a new stakeholder on their team?
- Did I run the proposal checklist?
Bottom line: repeat client proposals should feel like continuing a book, not reselling the series. Cut the reintroduction, keep scope and numbers sharp, and show you understand what is new this time.
Win repeat work with proposals that respect shared history
Save your experience, wins, and positioning once in Lervos. For each new lead, paste the job post. Our curated proposal AI builds a structured draft that sounds like you, not a generic template. Edit what you want, send when you are ready.