Here’s what most freelancers do when a project ends: send the final deliverable, get the last payment, and move on. The client has the work, the relationship fades to ambient, and four months later the freelancer wonders why that client hasn’t come back.
Here’s what happens without a structured close: the client’s experience of the project compresses. The early scope discussion, the discovery, the strategy, the iteration, the problem-solving, all of it collapses into “we had someone do that.” Without a structured summary, the value of the work becomes its surface. The invoice. The file. The thing.
The 3-slide recap fixes this by creating one more moment of shared reflection where the full value becomes visible, before the client’s attention moves to the next thing.
Why most project closings fail
Project endings have a natural energy drop. Delivery day has momentum. The first week after delivery, the client is implementing, reviewing, showing it to their team. By week two, their attention has moved forward. By week four, the project lives entirely in the past.
If you reach out at week four with a vague “how’s it going?” you’re asking the client to reconstruct an experience that has already compressed. You’re also the eighth thing they need to respond to that day.
The recap changes the timing. It arrives when the energy is still present, within 48 hours of delivery, and it does the work of summarizing value before that energy dissipates. It also creates a specific, documented reason to continue the conversation, which “how’s it going?” does not.
Freelancers who consistently send recaps report two practical effects: first, renewal conversations happen at a rate roughly twice as high as when no recap is sent. Second, the recap often surfaces a second project that the client had been thinking about but hadn’t raised, because the recap created a structured context to raise it.
Slide 1: What we set out to do vs. what we delivered
The first slide anchors the recap in the original purpose of the project. This matters more than it seems: after several weeks of iterating on specific components, clients often lose sight of the original goal and how far the final delivery maps to it.
Structure:
Original goal: [One sentence restating the brief in the client’s own words] What we delivered: [Bullet list of final outputs, specific, named, complete] Coverage: [A simple statement: “Delivered all original scope / Expanded scope in X area with client approval / Scoped back in Y area per client request”]
Example:
Original goal: Redesign the onboarding email sequence to reduce first-week churn among trial users.
What we delivered:
- 7 emails, fully rewritten, with new subject lines and CTAs
- Revised send cadence (Days 1, 3, 7, 14 instead of daily)
- A/B test variants for two subject lines (ready to run)
- Brief for the design team on new image treatments
Coverage: Delivered full original scope. Added A/B variants based on your request in Week 2.
Slide 1 is the reality check. It confirms you did what you said you’d do, documents any scope changes, and reminds the client of what you built together.
Slide 2: What changed, the before/after
Slide 2 is where you name outcomes. If you have metrics, use them. If you don’t yet, because the results will take time, use proxy indicators or process improvements.
Structure:
Before: [Specific baseline, metric, process, or state] After: [Specific change, what’s different now] What to watch: [The metric or outcome that will validate this over the next 30–90 days]
If you have numbers:
Before: Trial-to-paid conversion: 2.1% | First-week cancellation rate: 34% After: New sequence live, full data available at 30 days What to watch: Trial-to-paid conversion (target: 2.8%+) and first-week cancellation rate (target: below 25%)
If you don’t have numbers yet:
Before: Onboarding emails written in 2022, no relationship to current product features, open rates declining for 4 quarters After: Full sequence rewritten to current product, new send logic, A/B variants ready What to watch: Open rate Week 1 (current baseline: 18%), click-through on Days 3 and 7
The “what to watch” line is the most important thing you can include if results aren’t measurable yet. It tells the client exactly what success looks like, sets a specific timeline, and positions you as the person who will naturally check back in when the data is available.
The “what to watch” line on Slide 2 is a soft renewal hook built into the recap structure. You’re not pitching. You’re documenting. But the natural follow-up, “I’ll check back at the 30-day mark to see how these metrics are moving”, creates a future conversation that belongs in the context of the work, not as a sales reach-out.
Slide 3: The natural next step
Slide 3 is where most freelancers get uncomfortable and either go vague or don’t include it. Don’t.
The natural next step is not a proposal. It’s a one-paragraph observation about what logically comes next, based on what you now know about the client’s situation after completing the project.
Structure:
What the work revealed: [Something you learned during the project that points forward] What I’d suggest exploring: [Specific next engagement, framed as a question or observation, not a close]
Example:
What the work revealed: During the sequence audit, we found that email Days 7–14 have the highest engagement but currently lead nowhere, there’s no retention content for users who are still active after two weeks.
What I’d suggest exploring: A retention micro-sequence for Days 14–30 targeting engaged non-converters. That’s a 4-email project, probably 3 weeks, that would address the biggest gap we found in the current program. Worth a conversation if you want to see a scope?
This is not a pitch. It’s a consultant reporting what they saw and naming the implication. The client can say yes, no, or “not now.” All three responses are productive, because even “not now” keeps the conversation open.
Delivery format
Three slides in a Google Slides or PowerPoint file attached to an email is standard. Alternatively, use a one-page PDF with three labeled sections. Keep it under 400 words total.
The subject line: [Project name], recap + what's next
The email body:
Hi [Name],
The [project name] work is wrapped. I put together a quick recap while it’s fresh, three slides covering what we built, where we started vs. where we landed, and one observation about what I’d think about next.
Attached. Lmk if you want to jump on a call to walk through it, or if you want to let it sit and circle back in a few weeks.
, [Your name]
Short, specific, low-pressure close. The recap does the work. The email just opens the door.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
