Nick QuirkThe deal closes on a Thursday. The salesperson posts a 🎉 in Slack, moves the opportunity to Closed Won, and starts chasing next month's pipeline. Three weeks later the client asks why nobody has mentioned the competitor gap analysis they were promised on slide 14, and the strategist running the account says the words that kill renewals: "I wasn't aware we'd committed to that."
The sales-to-delivery handoff is the structured transfer of everything known about a client — goals, promises, constraints, personalities, and pricing assumptions — from the person who sold the work to the team that will do it. It should take one written artifact and one 30-minute meeting. Most agencies do neither, and pay for it in month-three churn.
What actually gets lost in a bad handoff
Context loss isn't abstract. In agencies I've audited, it shows up as four measurable costs:
- Re-discovery time. A delivery lead who starts cold spends 4–8 hours over the first fortnight asking questions the salesperson already had answers to. On a £3,000/month retainer with a 40-hour budget, that's 10–20% of month one burned on archaeology.
- Scope leakage. Promises made verbally in the pitch — "we'll do a content refresh audit in month two," "you'll get a named strategist on the monthly call" — get delivered anyway when the client surfaces them, but they were never priced. Three un-scoped promises at 5 hours each is 15 hours of unbilled work per account.
- Trust decay. Clients read a disconnected kickoff call as a sign the agency is disorganised. They're not wrong. First impressions in month one determine whether the client defends your invoice internally in month six.
- Churn. Agencies that lose clients at month 3–4 almost never lose them on results — SEO hasn't had time to produce results. They lose them on the gap between the pitch experience and the delivery experience.
The context package: what the salesperson must write down
Everything below should live in one place attached to the project, not scattered across CRM notes, a proposal PDF, and someone's inbox. If your team has to open four tools to assemble the picture, the handoff will decay the moment the salesperson is busy.
1. Commercial reality
Monthly fee, contract length, notice period, invoicing cadence, and — critically — the hours the deal was priced at. If you sold a £4,000/month retainer assuming 45 hours of blended delivery, write that number down. The delivery lead needs it to say no later.
Also record what was discounted and why. "We took 15% off because they signed a 12-month term" is a different conversation from "we took 15% off because the buyer pushed hard and we wanted the logo."
2. The promise register
This is the single highest-value section and the one most commonly missing. List every commitment made during the sales process, with a source: proposal section, pitch deck slide, or "said on the call on 14 March." Typical entries:
- Technical audit delivered within 21 days of kickoff
- Monthly reporting call with the CMO, not just the marketing manager
- Competitor gap analysis covering four named competitors
- Slack channel access, not just email
- Content briefs reviewed by a senior editor before delivery
Each one becomes a task or a recurring commitment in the project plan. Nothing in the register is allowed to stay as prose. We covered the mechanics of converting commitments into a schedule in signed SEO proposal to project plan.
3. Why they bought
Not the surface answer ("they want more organic traffic"). The real one. A SaaS company buying SEO because their paid CAC has doubled needs different early wins than a local services business whose owner just watched a competitor outrank them. Write the actual trigger, the internal champion's personal stake, and what success looks like to the person signing the invoice.
4. People and politics
Who is the champion, who is the economic buyer, who is the sceptic? One field that pays for itself repeatedly: who internally will try to kill this contract and why. If the in-house SEO manager felt threatened during the sales process, your delivery team needs to know before the first call, not after the first passive-aggressive email.
5. Known landmines
Legacy agency relationships, a developer team with a six-week ticket queue, a CMS that can't do server-side redirects, a legal review process for every published page. These constraints determine whether your 90-day plan is realistic. Sales almost always knows at least two of them and almost never writes them down.
6. Assets and access
What's already been shared, what's promised, and what hasn't been asked for yet: GA4, Search Console, CMS, server logs, ad accounts, brand guidelines, previous audits. List each with an owner and a target date.
The 30-minute handoff meeting
The document does most of the work. The meeting exists for the things people won't write down. Run it within 48 hours of signature, before the client kickoff, with the salesperson, the delivery lead, and whoever will be the day-to-day contact.
- Minutes 0–10: Salesperson walks the promise register. Delivery lead flags anything that can't be delivered in the priced hours. This conversation happens now or it happens in front of the client later.
- Minutes 10–20: People, politics, and tone. How formal are they? Do they want weekly contact or do they hate meetings? What did the buyer say that made you think they'd churn?
- Minutes 20–30: First 30 days. Agree the kickoff agenda, the first deliverable and its date, and who sends the access request email.
One rule makes this stick: the delivery lead formally accepts or rejects the handoff. If the context package is incomplete, it goes back. Without an acceptance step, handoffs quietly degrade into a forwarded proposal PDF within a quarter.
Where the tooling breaks
Most agencies keep sales context in a CRM and delivery context in a project tool, with a chasm between them. The proposal lives in one system, the project plan in another, and the promises live in a human's memory. General-purpose boards make this worse because they have no concept of a retainer, priced hours, or a client-facing commitment — you end up rebuilding the structure by hand for every new account. If you're evaluating options, the practical differences are laid out in our roundup of PM tools for agencies and the tool-by-tool comparisons.
What you want, whatever you use: the signed scope, the promise register, the hour budget, and the phase plan attached to a single client project record that the delivery team opens on day one. In PeakKR this is the project itself — phases, retainer hours, and commitments live together so nothing has to be re-typed from a proposal.
Measure the handoff, not just the project
Three numbers tell you whether your process works:
- Time from signature to kickoff call. Target under 7 days. Beyond 10, the client's buying enthusiasm has cooled measurably.
- Month-one hour variance. Actual hours versus priced hours. Consistent 20%+ overruns in month one usually mean promises weren't captured, not that the team is slow.
- Promise completion rate at day 60. Count the register entries delivered or scheduled. Below 80% and you have a structural handoff problem, not a capacity problem.
Agencies that get this right also tend to have cleaner exits, because the same discipline applies at the other end of the lifecycle — see the
