Optimize · Re-engagement & Win-Back
Write a "We've Improved" Win-Back Email
Turn an internal improvement (process, team, pricing) into a credible reason to reach back out.
foundermanagerIntermediate⏱ 20 min per email
When to use
Use when your agency has made a real, specific operational change (new senior hire, new reporting system, productized retainer, dropped a service) that directly addresses why a cohort of past prospects or clients said no. Avoid for vague improvements like 'we're better at communication now'.
The prompt
You are an agency operator who knows that 'we've improved' is the most boring sentence in sales — and you write the version that actually earns a reply. Agency: [AGENCY_NAME] — [SERVICES] | Recipient: [RECIPIENT_NAME] at [RECIPIENT_COMPANY], type: [PAST_CLIENT or LOST_PROSPECT] | The specific thing that's changed: [WHAT_CHANGED] | The prior objection this change addresses: [PRIOR_OBJECTION] | Proof the change is real: [PROOF_OF_CHANGE] Write a single email that converts [WHAT_CHANGED] into a credible reason to reopen the conversation, tied directly to [PRIOR_OBJECTION]. - Do not use the phrases 'we've improved', 'we've grown', or 'we've evolved' - Lead with the specific change, then the specific objection it fixes — in that order - Include [PROOF_OF_CHANGE] (a metric, a hire's name, a new SLA, a client outcome) - Soft CTA: 'worth a look?' not 'let's hop on a call' - Max 140 words Subject line + email body.
Variables
- [AGENCY_NAME] — Your agency
- [SERVICES] — What you sell
- [RECIPIENT_NAME] — Their first name
- [RECIPIENT_COMPANY] — Their company
- [PAST_CLIENT or LOST_PROSPECT] — Which one applies
- [WHAT_CHANGED] — The specific operational change
- [PRIOR_OBJECTION] — The objection this change fixes
- [PROOF_OF_CHANGE] — Evidence the change is real and working
Example input
AGENCY_NAME=Branchwork, SERVICES=Webflow design + dev for B2B, RECIPIENT_NAME=Priya, RECIPIENT_COMPANY=Foldstack, PAST_CLIENT or LOST_PROSPECT=LOST_PROSPECT, WHAT_CHANGED=we now offer a 6-week fixed-scope MVP package at $24k instead of only ongoing retainers, PRIOR_OBJECTION=they didn't want to commit to a 6-month retainer for a first project, PROOF_OF_CHANGE=shipped 9 of these MVPs in the last 4 months with avg 38 days from kickoff to launch
Example output
Subject: A version of Branchwork that would've fit Foldstack last time Priya — when we talked in October, the dealbreaker was that we only sold ongoing Webflow retainers and you wanted a single defined project to start. Fair point, and we changed it. We now run 6-week fixed-scope MVP builds at $24k flat. Nine shipped in the last four months, average 38 days from kickoff to live site, then clients decide if they want anything ongoing — no pressure either way. That structure would have matched what Foldstack actually needed. If the project's still on the list, worth a look at how it'd map? And if Foldstack already shipped it or scope changed, just tell me and I'll get out of your inbox.
Pro tips
- If you can't name a specific objection it fixes, the change isn't sharp enough to lead with — pick a different angle
- Front-load the proof (number of projects, named hire, SLA) — vague proof reads like spin
- This email outperforms case-study sends when the prior objection was process, not results
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS callRelated prompts