Nick QuirkMost agencies obsess over closing the deal and then treat the sales-to-delivery handoff as a Slack message: "New client signed — Acme Industrial, $6k/mo SEO retainer, contract in the drive folder. Can someone set up the project?"
Two weeks later the SEO lead is on a discovery call asking Acme questions the salesperson already asked. The client answers them again, politely, while quietly recalibrating their expectations of your agency. Somewhere in month two you discover sales promised a full site migration audit that was never priced. Margin evaporates. The renewal conversation gets awkward.
The sales-to-delivery handoff is the single highest-leverage 45 minutes in your entire client lifecycle. It costs almost nothing to do properly and it compounds across every account you sign.
What actually gets lost between signature and kickoff
It's rarely the obvious stuff. Nobody loses the contract value or the start date. What evaporates is the context that made the deal close — and the context that will make delivery hard.
1. The real reason they bought
A client signs an SEO retainer because organic traffic is down 30%. That's the stated reason. The actual reason is that the VP of Marketing told the CEO she'd fix it by Q3 and her job depends on showing movement. Sales knows this. Delivery, working from a scope document, does not — so they spend month one on a technical audit instead of shipping three quick-win pages the VP can forward to her boss.
2. Promises made outside the SOW
Every salesperson says yes to something small to get the deal over the line. "Sure, we can look at your Google Business Profiles too." "We'll include a monthly call with your dev team." These never make it into the statement of work and they always surface in month two, when the client references them casually and you have no record.
We tracked this at one 18-person agency: across 22 new accounts in a year, 17 had at least one verbal commitment that never reached the delivery team. Average unbilled cost per occurrence: about 6 hours.
3. The pricing math
A $6,000/month retainer isn't a budget — it's the output of an assumption. Sales priced it assuming 40 hours of delivery, with maybe 8 of those from a senior strategist. If delivery doesn't know the hour envelope or the seniority mix, they'll staff it however feels right and you'll find out the account is at 22% margin during a quarterly review.
4. Red flags sales noticed and didn't mention
The prospect took three weeks to answer a two-line email. Their "marketing team" is one coordinator who also runs events. Legal took a month on the contract. These aren't deal-killers — they're delivery risk, and the person who saw them should name them out loud.
The handoff document: what to actually capture
Keep it to one page. A 12-page internal brief gets written once and never again. Here's the field list that holds up in practice:
- Commercial terms: monthly value, contract length, notice period, invoicing cadence, any ramp or discount structure.
- Hour envelope and staffing assumption: total monthly hours priced, split by role. This is non-negotiable — delivery cannot protect margin they can't see.
- Stated goal vs. real goal: two separate lines. Sales fills in both.
- Success metric and baseline: what number, measured how, from what starting point, by when. "Increase organic traffic" is not a metric. "Non-branded organic sessions from 14,200/mo to 20,000/mo by month nine, measured in GA4" is.
- Every promise made: a bulleted list of things said in calls, emails, or the proposal that aren't explicitly in the SOW. Mark each as included, out of scope, or needs decision.
- Stakeholder map: economic buyer, day-to-day contact, internal champion, likely blocker. Include who has access to what — CMS, GA4, Search Console, the DNS registrar.
- Known constraints: legal review on all published content, a dev team with a six-week sprint queue, a CMS that can't do custom meta descriptions. These shape the whole first quarter.
- Churn risk, named: the three things most likely to lose this account. Force the salesperson to write them.
- Competitive context: who else they pitched, why you won, what the last agency did wrong. "The previous agency sent reports nobody read" tells you exactly what reporting needs to look like.
Run it as a live meeting, not a document drop
A written brief alone fails because the value is in the follow-up questions. Book 45 minutes with sales, the delivery lead, and the person who'll do the actual work. Record it. The recording becomes the reference asset — when a question comes up in month four, someone can scrub to minute 18 instead of guessing.
Structure the meeting in three blocks:
- Sales walks the deal narrative (15 min). Not the scope — the story. How they found you, what they tried before, what objections came up, who pushed back internally.
- Delivery interrogates (20 min). The delivery lead's job is to find gaps, not nod along. Good questions: "What did we say when they asked about timelines?" "Did anyone commit to a number?" "If this goes badly, what's the first thing that breaks?"
- Decisions and owners (10 min). Every needs decision item gets resolved or assigned. Anything out of scope gets a plan for how it'll be communicated to the client — usually on the kickoff call, by the delivery lead, framed as a change order option rather than a refusal.
Do this within 48 business hours of signature and always before the client kickoff. If your kickoff is scheduled for day three, your handoff happens on day one. The order matters: you cannot run a confident kickoff while still discovering what your own company promised. We've covered the kickoff mechanics separately in closing the kickoff gap.
Where the handoff should live
The common failure mode is a handoff that happens correctly and then disappears. A Google Doc in a folder nobody opens. A Slack thread buried after 40 messages. Six months later a new PM inherits the account and starts from the contract alone.
Context has to live where the work lives. The hour envelope should be visible next to time tracking, so you can see at a glance that you priced 40 hours and burned 58. The promise list should sit next to the project phases. The stakeholder map should be attached to the client record, not a shared drive.
This is where generic task tools struggle — most are built around tasks, not clients, so retainer context has nowhere natural to live. PeakKR was built for agency retainers specifically, which means deal context, hour budgets, and phases sit on the same client record. If you're evaluating options, the tool comparison hub is a reasonable starting point.
What good looks like after 90 days
Agencies that fix the handoff report fairly consistent effects. Kickoff calls get shorter — 45 minutes instead of 90 — because you're confirming rather than discovering. First-month margin improves because scope creep is caught at signature instead of invoice. And the client's perception shifts: they feel like they hired one company instead of being passed between two.
There's a downstream effect too. A documented handoff gives you a documented starting point, which makes every quarterly review and eventual offboarding conversation dramatically easier. You can show exactly what was promised and exactly what was delivered.
The other benefit is capacity. Re-discovery is pure waste — it's senior time spent re-learning things your own company already knew. Eliminating it is one of the cheapest ways to scale delivery without adding headcount, because you're reclaiming hours you were already paying for.
Make it unskippable
The handoff only works if it's a gate, not a courtesy. Two rules that hold: no project gets created
