The conversation every developer avoids sounds like this: "I should probably pitch Client A on more work. But I don't know what to say."
You've delivered. The project closed well. The client sent the happy-wrap-up message. And you're sitting on the obvious move -- there's a $1,997 engagement scope that fits this client exactly, and they don't know it exists.
That's not a sales problem. It's a copy problem. I said at the end of the 3-Product Ladder post that I'd give you the upgrade email. Here it is.
- Three reasons developers don't send this email (and the fix for each)
- Three subject line variants, ready to copy
- A complete email body you can send within 48 hours of project close
- A guard-rail list: who this email works for and who it doesn't
- What to do if they say no (spoiler: nothing bad happens)
Why You Haven't Sent It Yet
Three things keep developers from making this move. None of them are about confidence.
Price anchoring. You've billed this client at $120/hour. Your brain calculates $1,997 as "about 17 hours at my rate." Their brain doesn't do that math. They calculate it as "a full operational AI system, built and running in 30 days, with someone else responsible for it working." Those are not the same purchase. The moment you anchor to your hourly rate in your head, you've already undersold the tier before writing a word.
The wrong ask. "Would you like more work?" is not a pitch. It's a fishing expedition. You put all the framing work on the client: they have to invent the next scope, estimate what it might cost, compare it mentally against their budget, and decide whether it's worth a conversation -- all without enough information. That's a lot of work. Most people default to "we'll reach out if something comes up." The email below does that framing work for them.
No copy. This one's fixable in the next five minutes. Here's the draft.
The Email
Three subject lines, a body, a timing note, and one rule about what not to add.
Subject line options (use one; test two if you have volume):
- A: About the [Project Name] work
- B: One more thing before we close out [Project Name]
- C: Quick question -- re: [Project Name]
Option A performs best with clients who search their inbox by project. Option C performs best with mobile-first clients who scan subject lines fast. Option B works when the project had a natural endpoint that both sides acknowledged.
Hi [Name],
Really happy with how [Project Name] came out -- [one sentence on the specific result, e.g., "the Stripe webhook is processing cleanly, no retry failures in 72 hours."]
Quick thing I wanted to put in front of you while it's still fresh.
I work with clients at three levels:
| Tier | What it is | Price |
|---|---|---|
| Hourly | Specific pieces, you direct the scope (what we just did) | Your rate |
| Blueprint | Full implementation guide for the workflow, your team replicates it | $297 one-time |
| Concierge | I take the whole thing end-to-end: production deploy, documentation, one revision round, 30-day fix-or-refund SLA | $1,997 |
The Concierge tier is best for clients with an active AI or automation project that needs to go from "we tried a thing" to "it's actually running in production." Based on what we built together, I think [Project Name or the workflow behind it] qualifies.
Worth 30 minutes to scope it out? I have time [next week / this Thursday].
Cheers,
[Your name]
Timing note: Send within 48 hours of project close. The client is at peak positive sentiment right after delivery. Waiting two weeks means starting re-engagement from cold. The email earns the most traction when the project result is still fresh and concrete.
What not to add: Don't attach a proposal. Don't include a full pricing table beyond the three-tier comparison. Don't write "let me know if you have questions about the tiers" -- that's friction dressed as helpfulness. The email asks one yes-or-no question: worth a scoping call? Keep it there.
Who NOT to Send This To
This email has a specific use case. It breaks down outside of it.
Skip it if:
- This was a first engagement. You haven't built the "I know your stack" credibility yet. Pitch the Blueprint tier instead -- lower commitment, lets you demonstrate process before asking for $1,997.
- The client pushed back on your hourly rate during the project. That's a signal about their price ceiling, not a reason to try harder. Respect it and move on.
- There were scope or communication issues. If the client was frustrated at any point or you had to re-negotiate the brief mid-project, repair the relationship first. This email lands wrong when trust has a hole in it.
Send it if:
- This was the second or third engagement with this client
- They asked "what else can you do?" during or after the project
- They have an active AI or automation initiative that's stalled at the proof-of-concept stage and needs full production deployment
The Concierge tier is a full operational AI build. The client should have a real project in mind, not a vague interest in "doing something with AI." The email pre-qualifies that -- the three-tier table lets them self-select.
What Happens After You Send It
Two outcomes, both fine.
If they say yes to the scoping call: you run 30 minutes of discovery, confirm the scope fits the Concierge tier, and send the Stripe link. Use the Concierge page as your reference during the call -- the scope, deliverables, and SLA are all there so you're not ad-libbing the commitment.
If they say no or don't reply: you haven't burned anything. You've told them a tier exists and what it includes. Many clients who eventually buy the Concierge tier do so six to twelve months after first hearing about it. The seed is planted. The next time their AI project stalls, they know who handles the full deployment.
The only bad outcome is never sending the email. That leaves $1,997 on the table for a client who already trusts you -- which is the hardest kind of trust to build.
For the full email series, upsell templates, and 30+ implementation guides: the Annual Library is $497/year. It's where the email above lives alongside the upgrade sequence, objection handlers, and the 30-day cadence for new Concierge clients.
Next post: how to write the common failures section -- the part of a $297 implementation guide that makes buyers think "this is worth twice the price." Related: What's inside the AI Visibility Operations Library V2.