Nick QuirkThe deal closed on a Thursday. By the following Tuesday, the strategist assigned to the account is on a kickoff call asking the client what their business goals are — a question the client already answered in detail, twice, during the sales process.
That's a sales-to-delivery handoff failure, and it's the most expensive five minutes in agency operations. Not because of the five minutes, but because of what it signals: the money the client just spent bought them a fresh start with strangers.
Why context evaporates between the pitch and the first sprint
The root cause isn't laziness. It's that sales and delivery store information in incompatible formats.
Sales stores context as narrative. The CMO is new and needs a win by Q3 board review. The previous agency burned them on reporting. The CEO's nephew built the current site and nobody can say that out loud. This is the stuff that actually determines whether an engagement succeeds, and almost none of it survives contact with a CRM field.
Delivery stores context as tasks. Technical audit, keyword map, content calendar. Structured, assignable, trackable — and completely silent on why any of it matters to this particular client.
The handoff is the translation layer. Most agencies treat it as a 20-minute call and a link to the proposal PDF, which is roughly like handing someone a restaurant menu and expecting them to cook the meal.
What it actually costs you
Across agencies I've worked with, poor handoffs show up in four places:
- Scope leakage. Verbal promises from the pitch ("we'll take a look at your Shopify migration") that never hit the SOW. The client treats them as scope; delivery treats them as surprise work. On a $6,000/month retainer, two of these can eat 15–20% of your margin.
- Delayed start. If delivery has to re-interview the client, you lose 10–14 days of a 90-day proving window. For a retainer that renews at month six, that's a meaningful chunk of your evidence base.
- Trust decay. Clients read repeated questions as disorganization. The first 30 days set the tone for whether they treat you as a partner or a vendor to be managed.
- Churn risk concentrated in months 2–4. This is when the gap between what was sold and what's being delivered becomes visible. Most "we didn't see results" churn is actually "we didn't get what we thought we bought."
The three artifacts that make a handoff real
A handoff isn't a meeting. It's a meeting plus three documents that exist before and after it. If you only build one thing from this article, build the first.
1. The Deal Context Brief (written by sales, before the meeting)
One page. Non-negotiable sections:
- Why they're buying now. Not "they want more traffic." The actual trigger: funding round, new CMO, lost organic rankings after a redesign, competitor outranking them on a bottom-funnel term the CEO googles weekly.
- What success looks like to the person who signs the invoice. Often different from what the marketing manager cares about. Write both.
- Everything we said we'd do that isn't in the SOW. This is the single highest-value field. Sales must list verbal commitments explicitly, even if the answer is "nothing." Especially if the answer is "nothing," because then you can hold them to it later.
- Known constraints. Dev resources, CMS limitations, legal review on all content, a single stakeholder who's out on leave for six weeks.
- Political map. Who's the champion, who's the skeptic, who's never in the room but kills things anyway.
- Pricing logic. What was discounted, what was bundled, what the client pushed back on. Delivery needs to know if the margin is thin before they're generous with scope.
If sales resists writing this, the fix is structural: no handoff meeting is scheduled until the brief exists, and the commission milestone ties to handoff completion rather than signature. Agencies that make this change see brief quality improve within one quarter.
2. The Assumptions Log (written during the meeting)
Every engagement is built on assumptions that nobody stated. "We assumed they have Google Search Console access." "We assumed the dev team can ship template changes." "We priced 8 pieces of content assuming 1,200 words each."
During the handoff, the delivery lead's only job is to surface and record these. Each assumption gets an owner and a verification deadline — usually the kickoff call. This is where you catch the $4,000 misunderstanding before it becomes a $4,000 write-off.
3. The First 30 Days Plan (written after the meeting, shared with the client)
A dated list of what happens, who does it, and what the agency needs from the client to make it happen. This becomes the agenda for the client kickoff, which turns that call from a discovery session into a confirmation session. Clients consistently rate this as the moment they decide the agency is competent.
The 40-minute handoff meeting agenda
Attendees: salesperson, delivery lead, account manager, and whoever will be the primary executor (strategist or senior SEO). Four people maximum. Anyone else reads the brief.
- 0–10 min — Sales narrates the deal. Not reading the brief aloud; everyone pre-read it. Sales tells the story: how the conversation evolved, what the client got animated about, where they hesitated.
- 10–25 min — Delivery interrogates. The delivery lead asks every uncomfortable question now, while sales still remembers. "When you said we'd handle the migration, what did they think that included?" "Did anyone mention a competitor by name?"
- 25–35 min — Assumptions and risks. Build the log. Assign verification owners.
- 35–40 min — Confirm the first 30 days and who sends the kickoff invite. Sales makes the introduction email personally; delivery leads the call. The client should see a baton pass, not a disappearance.
Then — and this matters — sales attends the client kickoff call and says nothing after the first two minutes. Their presence signals continuity. Their silence signals that delivery is in charge now.
Where the handoff should live
The brief and assumptions log need to live where the work lives, not in a CRM the delivery team never opens and not in a Google Doc that gets orphaned in someone's Drive.
The practical test: six weeks in, when a strategist asks "why are we doing monthly exec reporting on a $4k retainer?", can they find the answer in under 30 seconds without asking anyone? If the answer lives in Slack history or a salesperson's head, your handoff process isn't a process.
Most general-purpose tools handle this poorly because they have no native concept of a client engagement that spans sales and delivery — you end up bolting a "context" doc onto a project board and hoping people read it. If you're evaluating options, it's worth comparing how different platforms handle agency-specific project structures rather than generic task management. In PeakKR, the deal brief attaches to the client record and surfaces on every project under that client, which is the behaviour you want regardless of which tool you pick.
Measuring whether your handoff is working
Three metrics, all cheap to track:
- Days from signature to first client deliverable. Target: under 14. If it's 25+, context loss is almost always part of the cause.
- Unbilled scope in months 1–3. Track hours logged against work that wasn't in the SOW. If it exceeds 10% of contracted hours, your briefs aren't capturing verbal promises.
- Repeat questions at kickoff. Have the account manager tally how many questions the client has already answered during sales. Anything above two is a red flag; zero is achievable within a quarter.
Agencies that fix the handoff usually find it also fixes two adjacent problems: white-label partner briefing gets sharper because you already have a format for transferring context, and offboarding gets easier because the original success criteria are documented and you can show exactly what you delivered against them.
Your sales-to-delivery handoff checklist
- Deal Context Brief written by sales within 2 business days of signature — including a mandatory list of all verbal promises not in the SOW
- Handoff meeting scheduled before the client kickoff, never after
- Four attendees max: sales, delivery lead, AM, primary executor
- Everyone pre-reads the brief; the meeting is for interrogation, not recitation
- Assumptions log created live, with an owner and verification date per line
- Pricing logic and margin position disclosed to
