SOP — Client Lifecycle Emails | Hardt Web Development

00

Overview

These emails handle the six most common client situations after a prospect replies.

The outreach sequences in SOP-EMAIL-001 get you to the first reply. Everything after that is covered here. Each situation has a sample email you can send with light personalization and a Claude prompt to generate a custom version from your call notes or project details.

Prospect→ Discovery→ Proposal→ Build→ Launch→ Post-launch

Situation	When to send	Goal	Tone
Discovery call follow-up	Within 2 hours of hanging up	Confirm understanding, build momentum toward proposal	Warm, confident, organized
Proposal follow-up	3 business days after sending if no reply	Surface objections or confirm timeline	Low pressure, helpful
Late payment reminder	Day 7 after due date (reminder), Day 14 (pause notice)	Get paid without damaging the relationship	Matter-of-fact, professional
Project pause notice	Day 21 of client non-response	Formally document the pause, protect your schedule	Clear, firm, no blame
Scope creep response	Within 24 hours of out-of-scope request	Acknowledge the request, route to change order process	Positive, professional, clear boundary
30-day post-launch check-in	30 days after DNS transfer	Surface wins, retain relationship, plant retainer seed	Genuine, brief, forward-looking

One rule for all of these Always put the key ask or key information in the first two sentences. Clients skim. The subject line and the first sentence together determine whether this email gets read or deferred. Never bury the point.

01

Discovery call follow-up

Send within 2 hours of the call. Not the same day — within 2 hours.

DISC-1A Post-call summary — proposal incoming Within 2 hours of call

Goal

Confirm scope understanding, set proposal timeline

Tone

Warm, organized, confident

Length

Under 180 words

Subject:Great talking — here's what I heard + next steps

Hi [First Name],

Thanks for your time today — it was helpful to hear more about [org/practice name] and what you're trying to accomplish with the new site.

Here's what I took away from the call:

The main goal: [1-sentence summary of their primary goal — e.g. "increase online donations and make it easier for new donors to find you on Google"]
The main problem: [1-sentence summary of what's broken or missing — e.g. "current site is slow on mobile and the donate button isn't working reliably"]
Timeline: [their deadline or "no hard deadline — aiming to launch before the end of Q3"]

I'll have a proposal to you by [specific date — 48 hours from now]. It will cover scope, timeline, and the 50/25/25 payment schedule we discussed.

If anything above doesn't match what you intended, reply and let me know — better to catch it now than after the proposal.

Charles Hardt
Hardt Web Development · charleshardt.com
charles@charleshardt.com

Why the summary mattersMirroring their words back signals you were listening. It also creates a written record of what was agreed verbally — which protects you if scope disputes arise later. If they correct you, that correction is now on the record too.

Write a discovery call follow-up email from Charles Hardt, WordPress developer at Hardt Web Development (charleshardt.com), to: Client name: [FIRST NAME] Organization / practice name: [NAME] Call date: [DATE] Main goal they described: [THEIR PRIMARY GOAL IN THEIR WORDS] Main problem with current site: [THE SPECIFIC PROBLEM THEY DESCRIBED] Timeline: [THEIR DEADLINE OR "no hard deadline"] Proposal delivery date: [SPECIFIC DATE — 2 days from now] Payment structure discussed: 50% deposit, 25% at staging approval, 25% at launch Instructions: - Open with genuine appreciation — one brief sentence, not gushing - Summarize what you understood in three bullet-style lines: main goal, main problem, timeline - State exactly when the proposal will arrive - Invite them to correct anything you misunderstood - Close warmly but briefly - Tone: organized, warm, confident — not salesy - Length: under 180 words - Sign off: Charles Hardt · Hardt Web Development · charleshardt.com - Output subject line first, then email. No preamble.

02

Proposal follow-up

Send on day 3 if no reply. One follow-up only — then move to dormant.

PROP-1A Proposal follow-up — day 3 Day 3 after sending · No reply

Goal

Surface objection or confirm timeline

Tone

Low pressure, genuinely helpful

Length

Under 80 words

Subject:Re: [original proposal subject]

Hi [First Name],

Just checking this landed safely — Bonsai occasionally ends up in spam filters.

If you've had a chance to review it and have questions, I'm happy to walk through anything. If the timing has shifted or you need more information before deciding, let me know — I can work around your schedule.

No pressure either way.

Charles
charles@charleshardt.com · (757) 555-0100

The spam filter openerStarting with a practical, face-saving reason the proposal might not have been seen removes the awkwardness of following up and gives them an easy out if they simply haven't looked at it yet.

Write a proposal follow-up email from Charles Hardt to a prospect who hasn't replied to a proposal sent 3 days ago. Client name: [FIRST NAME] Project: [BRIEF DESCRIPTION — e.g. "new website for your chiropractic practice"] Proposal sent via: Bonsai Original proposal subject line: [SUBJECT] Instructions: - Open with a brief, practical reason for following up — not apologetic - Mention the spam filter possibility naturally (not as an excuse) - Offer to answer questions or adjust timeline if needed - Zero pressure — no urgency language, no deadline, no discount offer - Close with "No pressure either way" or equivalent - Sign off with first name only and phone number — less formal than the original proposal - Length: under 80 words - Output subject line first (use Re: + original subject), then email. No preamble.

After this email — stop If there is still no reply after the follow-up, move them to Dormant in your Notion CRM and set a 6-month re-check. Two no-replies means they are not ready. Sending a third email damages your positioning. They know where to find you.

03

Late payment

Two emails — a gentle reminder at day 7, a firm pause notice at day 14.

PAY-1A Payment reminder — day 7 Day 7 after due date · No payment received

Goal

Prompt payment, assume good faith

Tone

Matter-of-fact, no blame

Length

Under 80 words

Subject:Invoice [#] — payment due [original due date]

Hi [First Name],

A quick note — invoice [#] for $[amount] was due on [date] and I don't see a payment on my end yet. Likely just slipped through — these things happen.

You can pay via the link in the original Bonsai invoice, or reply here if you'd prefer I resend it.

Charles Hardt
Hardt Web Development · charleshardt.com

Write a late payment reminder email from Charles Hardt to a client whose invoice is 7 days overdue. Client name: [FIRST NAME] Invoice number: [#] Invoice amount: $[AMOUNT] Original due date: [DATE] Payment link: Bonsai invoice (already sent) Instructions: - State the fact plainly in the first sentence: invoice number, amount, due date - Assume it's an oversight — "likely just slipped through" framing - Offer to resend the invoice if needed - No late fee mention yet — that comes in the Day 14 email - No passive aggression, no emotional language - Length: under 80 words - Sign off: Charles Hardt · Hardt Web Development - Output subject line first, then email. No preamble.

PAY-1B Payment pause notice — day 14 Day 14 after due date · Still no payment

Goal

State consequences clearly, prompt immediate action

Tone

Professional, firm, no emotion

Length

Under 120 words

Subject:Invoice [#] — 14 days overdue, project pausing today

Hi [First Name],

Invoice [#] for $[amount] is now 14 days past due. Per our agreement, I will be pausing work on your project today until payment is received. A 1.5% monthly late fee has been applied to the outstanding balance.

Work will resume within 2 business days of confirmed payment. Please use the Bonsai invoice link to pay, or reply here and I'll send a new link.

I want to get your project back on track — this is the only thing in the way of that.

Charles Hardt
Hardt Web Development · charleshardt.com

Do not send this unless you will actually pause work. Empty consequences destroy your leverage in every future payment conversation with this client.

Write a 14-day overdue invoice notice from Charles Hardt that formally notifies the client that work is pausing today. Client name: [FIRST NAME] Invoice number: [#] Invoice amount: $[AMOUNT] Days overdue: 14 Late fee: 1.5% per month applied as of today Resume timeline: work resumes within 2 business days of payment Instructions: - State the facts in sentence one: invoice number, amount, days overdue - State the consequence clearly: work pausing today per the signed agreement - Mention the late fee has been applied - Give the path to resolution: pay via Bonsai or reply for a new link - Close with a brief, genuine statement that you want to get back on track - No anger, no guilt language, no threats beyond what the contract already states - Length: under 120 words - Sign off: Charles Hardt · Hardt Web Development - Output subject line first, then email. No preamble.

04

Project pause notice

Send on day 21 of client non-response. Not a threat — a documented fact.

PAUSE-1A Project pause notification — day 21 Day 21 of no client response

Goal

Create written record, free your schedule

Tone

Clear, professional, no blame

Length

Under 130 words

Subject:[Project name] — project on hold as of today

Hi [First Name],

I've reached out a few times over the past [X] weeks and haven't heard back. I understand things get busy — no problem there.

Per our agreement, I'm placing your project on hold as of today. Your work is saved and nothing has been lost. When you're ready to continue, reach out and I'll get you back on the schedule — timing will depend on my availability at that point, which may be [2–4] weeks out.

If something has changed on your end and you'd like to talk through it, I'm happy to do that too.

Charles Hardt
Hardt Web Development · charleshardt.com
charles@charleshardt.com

Log this in Notion immediately. Date sent, stage moved to Paused, note that the clause was invoked. If there is ever a deposit refund dispute, this email and that Notion log are your evidence.

Write a project pause notification from Charles Hardt to a client who has not responded in 21 days. Client name: [FIRST NAME] Project name: [NAME] Number of unanswered follow-ups: [X] Weeks of silence: [X] Re-scheduling lead time to warn them about: [2–4 weeks] Instructions: - Acknowledge the silence without blame — "I understand things get busy" - State clearly that the project is on hold as of today, per the signed agreement - Reassure them that no work has been lost - Explain the re-scheduling caveat: timing depends on availability when they return - Leave a door open for conversation if something has changed on their end - No passive aggression, no guilt, no deadline ultimatums beyond what the contract already provides - Tone: professional, calm, matter-of-fact - Length: under 130 words - Sign off: Charles Hardt · Hardt Web Development - Output subject line first, then email. No preamble.

05

Scope creep response

Send within 24 hours of receiving an out-of-scope request. Never say yes verbally first.

📐

Pipeline stage: Active client — out-of-scope request received

Positive acknowledgment + change order route

The client is not trying to cheat you. They usually don't know what's in scope. Your job is to say yes to the relationship while routing the request through the correct process. Never refuse flatly. Never say "that's out of scope" as the first thing. Acknowledge the request, confirm you can do it, explain the change order process briefly, and send the quote promptly.

SCOPE-1A Out-of-scope request — change order response Within 24 hours of request

Goal

Acknowledge warmly, route to change order

Tone

Positive, clear, no friction

Length

Under 130 words

Subject:Re: [their request subject or description]

Hi [First Name],

Happy to add [the requested item — e.g. "an events calendar with RSVP functionality"] — that's a great addition for what you're building.

It falls outside the scope we agreed on, so I'll put together a brief change order for your approval before we proceed. Based on what you've described, I'd estimate [X hours / $X–X] — I'll have a formal quote to you by [tomorrow / specific date].

Nothing slows down on the existing scope in the meantime.

Charles Hardt
Hardt Web Development · charleshardt.com

Give a rough estimate immediately. "I'll send a quote" with no number creates anxiety. A ballpark in the same email — even a range — lets them decide whether to proceed before the formal change order arrives.

Write a scope creep response email from Charles Hardt to a client who has requested something outside the agreed scope of work. Client name: [FIRST NAME] What they requested: [DESCRIBE THE REQUEST] Reason it's out of scope: [brief — e.g. "not included in the original page list" or "copywriting was agreed to be client-supplied"] Rough estimate: [X hours or $X–X range] Change order delivery date: [tomorrow or specific date] Instructions: - Open positively — affirm the request is a good addition, not a problem - State briefly that it falls outside the agreed scope — one sentence, no lecture - Say you'll send a change order before proceeding — not "I can't do that without..." - Give a rough estimate immediately - Reassure them that existing scope work is unaffected - Tone: positive, professional, zero defensiveness - Length: under 130 words - Sign off: Charles Hardt · Hardt Web Development - Output subject line first, then email. No preamble.

06

30-day post-launch check-in

Send on day 30 after DNS transfer. Set a Notion reminder the day you launch.

🚀

Pipeline stage: Post-launch

The highest-value email in your business

This single email does more for client retention than any other touchpoint. It shows you care about outcomes, not just delivery. It surfaces early wins you can point to. It plants the seed for a maintenance retainer or referral at the moment the client is most satisfied. Do not skip it and do not send it late — day 30 is when the project is still fresh and goodwill is at its peak.

POST-1A 30-day check-in — how is the site performing? Day 30 after launch

Goal

Retain relationship, surface wins, plant retainer seed

Tone

Genuine, brief, forward-looking

Length

Under 160 words

Subject:One month in — how is the site going?

Hi [First Name],

It's been about a month since [site name] went live — wanted to check in and see how things are feeling.

[Optional: one specific early win if you can see it — e.g. "I noticed your Google Search Console impressions are up 40% in the first three weeks, which is a strong start for a new domain."]

A few things worth knowing from my end:

— Everything looks healthy on the technical side — no errors, no security flags, backups running cleanly.
— [Any quick win or update relevant to them]

If anything has come up that you'd like help with, or if you're thinking about adding something to the site, just reply here.

And if the site is working well, I'd genuinely appreciate a Google review or a word to anyone in your network who might need the same thing done.

Charles Hardt
Hardt Web Development · charleshardt.com

Check Google Search Console before sending. Even a small data point — "impressions up," "ranking for [keyword]," "first contact form submission" — makes this email feel personal and worth reading rather than a form letter.

Write a 30-day post-launch check-in email from Charles Hardt to a client whose website launched one month ago. Client name: [FIRST NAME] Site name / org name: [NAME] Launch date: [DATE] Any data points from Google Search Console or Analytics: [PASTE IF AVAILABLE — or write "none yet"] Any specific wins to mention: [e.g. "first contact form submission received", "ranking page 1 for [keyword]", "donation button working smoothly", or "none yet"] Any minor technical updates made since launch: [OR "none"] Instructions: - Open warmly — acknowledge the month milestone without being over the top - Include one specific data point or observation if available — this is what makes it feel personal - Report briefly on site health: no errors, backups running, security clean - Invite them to reply with questions or requests - End with a soft referral ask — genuine, not transactional - Do NOT pitch the maintenance plan explicitly — mention it only if they ask about ongoing help - Tone: genuine, brief, forward-looking — not salesy - Length: under 160 words - Sign off: Charles Hardt · Hardt Web Development · charleshardt.com - Output subject line first, then email. No preamble.

Set the reminder the day you launch In Notion: open the client CRM row → set Follow-up date to launch date + 30 days → label it "30-day check-in." If you wait until day 29 to remember, you will skip it. The reminder takes 10 seconds to set and the email takes 5 minutes to send.

Client Lifecycle EmailsDiscovery through post-launch — templates & Claude prompts

Overview

Discovery call follow-up

Proposal follow-up

Late payment

Project pause notice

Scope creep response

30-day post-launch check-in

Client Lifecycle Emails
Discovery through post-launch — templates & Claude prompts