Website Redesign Follow Up Email Templates

Outcome Summary

• Keep redesign deals moving with follow-ups that add value (without sounding pushy).
• Use the right “micro-CTA” for each stage: confirm a detail, get a yes/no, or book a short review.
• Reuse a small set of templates that work whether you’re sending a demo link, a proposal, or a final check-in.

What Revamp Actually Does (Truth Block)

Revamp (revamp.dev) is an AI website redesign platform that helps you show a redesign direction fast—so your follow-ups can include something concrete.

✅ Revamp does

• Generate an AI website redesign demo from a website URL.
• Provide a live preview link you can share with a client.
• Let you collect light “design preferences” to steer the output.
• Support code export on paid plans.

❌ Revamp does not

• Guarantee SEO, speed, or conversion outcomes from a generated redesign.
• Replace discovery, content strategy, or stakeholder alignment for real projects.
• Reliably handle every complex web app or specialized component without additional work.

The Core Problem

Most redesign follow-ups fail for predictable reasons:

• Your message doesn’t give the client anything new, so replying feels like “work.”
• The ask is too big (“Thoughts?”), so it’s easy to ignore.
• The wrong person owns the decision, so you’re nudging someone who can’t say yes.
• The client is interested but anxious about scope, risk, timeline, or internal approvals.
• Your follow-up sounds like pressure instead of help—so they delay to avoid the conversation.

Framework

Use this workflow to choose the right follow-up and keep momentum.

Step-by-step workflow

1. Name the stage (first reply, demo sent, quote sent, post-call, stalled).
2. Pick one goal for the email (confirm, unblock, decide, schedule).
3. Add one new asset if possible (demo link, a short loom, a clarified scope note, a “before/after” explanation).
4. Use a micro-CTA that’s easy to answer.
   • Yes/no
   • “Which option fits?”
   • “Who should I loop in?”
   • “Want me to send a draft scope?”
5. Reduce risk in one sentence (what’s included, what’s not, what happens next).
6. Make it skimmable (short lines, one ask, no multi-topic paragraphs).
7. Close the loop (if no response, send a polite final check-in that gives them an off-ramp).

Quick selector (stage → template)

Stage	Primary goal	Best template section below	Micro-CTA idea
After their first reply	Move to demo review	“After first reply”	“Should I tailor the demo toward X or Y?”
After you send a demo link	Get a reaction	“Demo link follow-up”	“Want a quick walkthrough, or prefer notes?”
After you send a quote/proposal	Confirm next step	“Post-quote nudge”	“Should I revise scope, or book a review?”
After a call	Summarize + assign ownership	“Post-call recap”	“Did I capture this correctly?”
Stalled / no response	Create a clean decision point	“Stalled / breakup”	“Close the loop, or pause for now?”

Copy/paste email templates

Use these as-is, then swap in specifics (their site, their goal, their constraints).

Template: After first reply (set direction)

Subject: Quick question before I draft the redesign direction

Hey {{Name}} — thanks for getting back to me.

Before I put together a redesign direction, what matters more for this site right now:
- clearer messaging and positioning, or
- a more modern visual feel?

If you tell me which one is the priority, I’ll tailor the first demo accordingly.

— {{Your name}}

Template: Demo link follow-up (value + simple choice)

Subject: Redesign demo for {{Company}} (quick review?)

Hey {{Name}} — I put together a redesign demo based on your current site:
{{Demo link}}

If you skim just one section, check the {{specific section}} — that’s where the biggest clarity win usually is.

Would you rather:
A) I send a short written walkthrough of what changed, or
B) we do a quick screen-share and decide what to iterate?

— {{Your name}}

Template: “What would you change?” (invite critique safely)

Subject: Anything you’d change in the demo?

Hey {{Name}} — curious what you’d adjust in the redesign demo:
{{Demo link}}

Totally fine if it’s not the direction — a fast “too modern / not modern enough / wrong vibe” is enough for me to iterate.

What feels most off: the layout, the copy, or the visual style?

— {{Your name}}

Template: Proposal sent (remove friction)

Subject: Want me to tailor the proposal around your constraints?

Hey {{Name}} — checking in on the proposal I sent.

If this is stuck in review, tell me what constraint I should optimize for:
- speed to launch
- budget
- minimizing internal approvals
- preserving existing content

I can revise the scope so it’s easier to say yes (or no) without a long back-and-forth.

— {{Your name}}

Template: “Forwardable” internal email (help them sell it internally)

Subject: Summary you can forward internally

Hey {{Name}} — if helpful, here’s a forwardable summary for stakeholders:

- Goal: modernize the site while improving clarity of {{primary message}}
- Deliverable: redesign direction + implementation plan (with review checkpoints)
- Risk control: scope is defined up front; anything out-of-scope gets flagged before build work starts
- Next step: confirm the direction from the demo, then finalize scope

If you tell me who else is involved, I can tailor this summary to their concerns (brand, approvals, timeline).

— {{Your name}}

Template: Post-call recap (assign ownership + next action)

Subject: Recap + next step for the redesign

Hey {{Name}} — great talking.

Here’s what I captured:
- Primary goal: {{goal}}
- Must-keep items: {{must keep}}
- Open questions: {{open question}}

Next step (on my side): {{your next action}}
Next step (on your side): {{their next action}}

Did I capture that correctly? If yes, I’ll proceed.

— {{Your name}}

Template: Stalled / “breakup” email (polite off-ramp)

Subject: Close the loop?

Hey {{Name}} — I don’t want to keep pinging if timing changed.

Do you want to:
- keep moving on the redesign (happy to send a tighter scope), or
- pause for now and revisit later?

Either way is completely fine — just tell me what you prefer and I’ll align.

— {{Your name}}

Where Revamp fits into the workflow (without overpromising)

• If you’re stuck at “can you show me what you mean?”, use Revamp to generate a redesign demo link and include it in the next follow-up.
• If feedback is vague, ask for a preference (style direction, layout feel), then regenerate an updated demo.
• If the client needs internal buy-in, a shareable live preview is easier to forward than static mockups.

If you want a structured proposal draft to pair with your follow-ups, you can also use Revamp’s Website Redesign Quote + Proposal Generator.

Use Cases

Use case: Lead replied, but won’t schedule a call

• Scenario: They say “Sounds interesting,” then go quiet.
• Recommended approach: Send a demo link follow-up with a simple choice (walkthrough vs written notes).
• Common mistake: Asking “Any thoughts?” with no direction—your email becomes homework.

Use case: Proposal is “under review” for too long

• Scenario: They need stakeholder approval and you’re stuck in limbo.
• Recommended approach: Send a forwardable summary + ask who else is involved.
• Common mistake: Sending repeated nudges without giving them a message they can forward.

Use case: They like the demo, but worry about scope risk

• Scenario: They’re excited but hesitant about what’s included.
• Recommended approach: Offer to revise scope around their constraint (speed, budget, approvals, content).
• Common mistake: Defending the proposal instead of making it easier to decide.

Decision Checklist

Use this before you send any follow-up.

• Is the email tied to one stage (demo, quote, recap, stalled) instead of mixing topics?
• Did I include one new piece of value (clarification, demo link, summary, next-step plan)?
• Is my CTA easy to answer without a meeting?
• Did I reduce perceived risk (scope clarity, review checkpoints, what happens next)?
• Am I messaging the decision owner (or explicitly asking who that is)?
• Did I make it skimmable (short lines, no walls of text)?
• If they say “not now,” do I have a graceful off-ramp prepared?

Constraints

• Some clients can’t view external preview links due to company security; offer a written walkthrough instead.
• Complex sites (apps, logged-in flows, specialized components) may need more discovery than a quick demo implies.
• Multiple stakeholders often means conflicting feedback; your follow-up should clarify who owns final approval.
• If you don’t have clear exclusions, follow-ups can turn into scope creep.

Common Mistakes

• Following up with no new information: It reads like pressure, and the client delays to avoid the conversation.
• Asking broad questions (“Thoughts?”): You invite vague feedback that doesn’t move the deal forward.
• Chasing the wrong contact: You burn cycles nudging someone who can’t approve budget or scope.
• Overpromising outcomes: You increase risk perception and create distrust when the client asks for guarantees.
• Sending long emails: Busy stakeholders skim, miss the ask, and your follow-up effectively fails.

FAQ

Should my follow-ups be “checking in” or “adding value”? Adding value tends to work better: a demo link, a clarified scope option, a recap, or a forwardable summary.

What if they haven’t looked at the demo link? Assume they’re busy, not avoiding you. Offer a lightweight alternative: a short written walkthrough or a quick screen-share.

How do I follow up without discounting? Don’t negotiate against silence. First, reduce scope risk (revise around constraints) or clarify what’s included/excluded.

What if they say the demo isn’t the right direction? That’s usable signal. Ask what feels off (layout, copy, style) and offer an iteration based on their preference.

When do I send a “breakup” email? When repeated nudges aren’t getting a response and you want a clear decision point—without burning goodwill.

Can I use these templates if I’m in-house (not an agency)? Yes—swap “proposal” language for “internal plan,” and use the forwardable summary to align stakeholders.