Nick QuirkThe contract is signed. Everyone's happy. Three weeks later, the client asks why the competitor gap analysis they were promised hasn't started, the PM has never heard of it, and the retainer has already burned 40% of its monthly hours on an audit nobody scoped properly.
This is the sales-to-delivery handoff failing in slow motion. It rarely blows up on day one. It leaks quietly for 60 days and then shows up as a margin problem, a trust problem, or both.
The direct answer: a working handoff is a structured document plus a live 45-minute session, owned by delivery, completed before the client kickoff call, and stored where the project team actually works — not in an email thread or a CRM field nobody opens again.
What actually gets lost between sales and delivery
It's almost never the contract value. That gets transferred fine. What disappears is everything around it:
- Verbal promises. "We'll take a look at your Google Business Profiles too." Said on a Zoom call in week two of the deal. Nowhere in the SOW. Absolutely in the client's memory.
- The real reason they bought. The SOW says "technical SEO and content." The actual driver was that the VP of Marketing has a board review in Q3 and needs organic pipeline numbers to move.
- Who hates the last agency and why. Hugely predictive of what will annoy this client. Sales always knows. Delivery almost never gets told.
- Negotiated exclusions. The client asked for link building, you said no, they accepted. Nobody wrote it down, so three months later it resurfaces as an expectation.
- Technical reality. Headless build, three dev teams, a CMS nobody can push to without a two-week sprint queue. Sales heard it, filed it as "they have a dev team."
Every one of those gaps costs hours. In agencies we've looked at, a weak handoff reliably produces 5 to 15 hours of unbilled rework in the first 60 days of a new engagement — roughly 8-12% of a typical $5K/month retainer's capacity, evaporated before you've delivered anything.
Why "send the proposal to the PM" doesn't work
Most agencies think they have a handoff because the signed proposal gets forwarded to delivery. A proposal is a sales artefact. It's written to persuade, not to brief. It says "comprehensive technical audit" because that sounds valuable; it doesn't say "28,000 URLs, Shopify Plus, no staging environment, and their dev lead is on paternity leave until March."
The second failure is treating the handoff as a file drop. Documents capture facts. They do not capture tone, hesitation, or the thing the salesperson says out loud when asked a direct question: "Honestly? I think they're going to be difficult about reporting." That only comes out in conversation. This is the core argument in our deeper piece on not losing deal context — the written record and the live session do different jobs, and you need both.
The handoff document: six sections, nothing more
Keep it short enough that sales will actually fill it in. Six sections, one page, 20-30 minutes of work.
1. Commercial terms
Monthly fee, contract length, notice period, billing date, PO requirements, who signs off invoices, any discount and what was traded for it. If you gave 15% off for a 12-month commitment, delivery needs to know that your effective hourly rate just dropped and the plan has to reflect it.
2. Scope — in and out
Two columns. Deliverables committed, with quantities and cadence ("4 briefs/month, 1 technical audit in month one, monthly reporting deck"). And explicitly: things discussed and excluded. The exclusion list is the one that saves you money.
3. Promises made outside the SOW
A blank list that sales must either fill or sign off as empty. Anything written here gets a decision before kickoff: honour it as goodwill (and log the hours), or renegotiate now. Never discover it in month two.
4. Client context and politics
Who is the economic buyer, who is the day-to-day contact, who can kill the contract, who is quietly skeptical. What happened with the previous agency. What internal metric your champion is judged on. What they said they hated about past reporting.
5. Technical and access reality
CMS and version, hosting, dev process and release cadence, analytics setup, whether GSC/GA4 access exists and who controls it, known tracking issues, any migration planned in the next six months. A planned replatform the client "forgot" to mention will reshape your entire roadmap.
6. Risks and red flags
One honest paragraph from the salesperson. Deals that were price-sensitive, procurement-heavy, or pushed through by a champion with no internal support behave differently in delivery. Say so.
The live session: 45 minutes, three people
PM, lead strategist, salesperson. The PM runs it and has veto power — if the document is thin, the handoff is rejected and the project doesn't get scheduled. That sounds harsh until you realise it's the only mechanism that makes sales fill the form in properly. Make the consequence land on the person who controls the quality.
Structure the 45 minutes like this: 10 minutes on commercial and scope, 15 on context and stakeholders, 10 on technical constraints, 10 on open questions and who chases them. End with a written list of unknowns and owners. Most handoffs produce 4-8 open questions; they should all be closed before the client kickoff.
Crucially, the salesperson stays on the kickoff call. Not forever — just the first one. Continuity of face matters enormously to a client who bought from a person, and it keeps sales accountable for what they sold in front of both audiences.
A 10-day handoff timeline that works
- Day 0 — signature. Deal marked closed-won. Handoff doc auto-assigned to the salesperson with a 48-hour due date.
- Day 2 — document complete. PM reviews, accepts or rejects.
- Day 3 — handoff session. 45 minutes, three people, open questions logged.
- Day 4-5 — translate to plan. PM converts scope into phases, tasks, and an hours budget per month. This is where most of the value lands; see our walkthrough on turning a signed SEO proposal into a project plan.
- Day 6 — access request sent. Single consolidated email: GA4, GSC, CMS, Ahrefs/Semrush, Looker, server logs, dev contact.
- Day 7-8 — internal pre-kickoff. Delivery team reads the brief, raises concerns, confirms capacity.
- Day 9-10 — client kickoff. PM leads, salesperson attends, agenda circulated 24 hours ahead with the scope summary attached so the client sees the same scope boundaries you do.
Ten working days from signature to kickoff is realistic. Under five is usually a sign you skipped the translation step and will pay for it later.
Make the handoff live in your delivery system
The single biggest structural fix is this: the handoff output should not be a separate document. It should become the project. Scope items become phases with hour budgets. Promises become tasks with owners. Exclusions become a visible scope-boundary note the whole team and the client can see. Risks become flagged items reviewed in month-one retro.
If your handoff notes live in a Google Doc and your work lives somewhere else, the notes will be read exactly once. Agency-oriented tools — compared here — differ a lot in whether they let you attach commercial context (retainer hours, contract dates, sc
