Nick QuirkThe most expensive twenty minutes in an SEO agency is the gap between "contract signed" and the delivery team finding out what was actually sold. I've seen agencies lose a $7,000/month retainer in month two because the salesperson promised a content calendar the strategist never heard about, and the client spent eight weeks quietly waiting for it.
The sales to SEO handoff is not a meeting. It's a documented transfer of context, commitments, and constraints — and if you don't build it deliberately, your delivery team is reverse-engineering the deal from a Stripe notification and a half-filled CRM field.
Why the sales to SEO handoff fails
It fails for structural reasons, not because your salespeople are careless.
Sales is incentivized to close, not to deliver
Commission pays on signature. Once the deal closes, the salesperson's attention moves to the next pipeline opportunity within hours. Anything they didn't write down in that window is gone. If your commission structure has zero relationship to whether the client stays past month four, you've built a system that guarantees thin handoffs.
The proposal is not the scope
Proposals are persuasion documents. They say things like "comprehensive technical audit" and "ongoing content optimization." Your strategist needs to know: how many pages in the audit? How many optimizations per month? Is that 4 or 12? A proposal that reads beautifully to a prospect is often unbuildable to a delivery team.
Verbal promises never get recorded
This is the killer. Over five or six sales calls, a salesperson makes a dozen small accommodations — "sure, we can look at your PPC landing pages too," "yes, monthly calls with your CMO," "we'll include the Shopify migration review." None of it hits the SOW. All of it lives in the client's memory as a firm commitment.
Nobody owns the moment of transfer
Sales assumes delivery will ask questions. Delivery assumes sales will brief them. The account sits in limbo for a week. Meanwhile the client, who was at peak enthusiasm on signing day, is already cooling.
Build a handoff document that delivery can reject
The single most effective change I've seen agencies make: give the delivery lead veto power over the handoff. If the document is incomplete, delivery sends it back and the account doesn't start. That sounds harsh. It takes about three rejections before sales handoff quality permanently improves.
Here's what a usable handoff document contains:
- Commercial terms — monthly retainer, contract length, notice period, invoicing date, any discounts or ramp pricing. Delivery needs to know if month one is discounted, because that affects how many hours you can burn.
- Deliverable counts with numbers — "technical audit covering up to 5,000 URLs," "4 optimized pages per month," "1 reporting call monthly, 45 minutes." No adjectives.
- Budgeted hours by discipline — e.g. 12 hours strategy, 20 hours content, 8 hours technical, 4 hours account management. This is the number the PM protects.
- The client's actual goal — not "increase organic traffic." The real one. "The founder wants to raise a Series B in 14 months and needs to show a defensible acquisition channel." That changes everything about how you sequence work.
- The metric they'll judge you on — and who reports it internally at their company.
- Every verbal promise — a dedicated section. Sales writes them all down, flagged as in-scope or goodwill.
- Known constraints — dev team availability, CMS limitations, legal review on all published content, a competitor they refuse to be compared against.
- Stakeholder map — who signs off, who blocks, who champions you internally, who was skeptical during sales.
- Access checklist status — GSC, GA4, CMS, Ahrefs/Semrush seat, Slack channel, whatever you need.
Access is the one that quietly destroys month one. Agencies routinely lose two to three weeks waiting on Google Search Console access. Start that request during the sales process, not after signature.
The 72-hour rule
Run the internal handoff meeting within three business days of signature. Not a week. Three days, while the salesperson still has fresh recall.
Attendees: the salesperson, the delivery lead or PM, and the senior SEO who'll own strategy. Sixty minutes. The salesperson presents the handoff doc — they don't just send it, they walk through it — and delivery interrogates.
The questions that earn their keep:
- "What did they say when you quoted the price?" (Reveals budget anxiety, which predicts renewal risk.)
- "Who else did they talk to, and why did they not pick them?"
- "Have they worked with an SEO agency before? What went wrong?" — a client burned by a previous agency needs visible wins in weeks 1-3 or they'll assume it's happening again.
- "What's the one thing that would make them cancel?"
- "What did you promise that isn't in the SOW?"
That last one needs to be asked explicitly and without judgment. If your salesperson fears being punished for it, they'll stay quiet and you'll discover the promise in month three during an uncomfortable call.
Kickoff: sales attends, then exits cleanly
Run the client kickoff within 10 business days of signature. The salesperson attends the first 10 minutes to make the introduction, explicitly transfer ownership, and then leave. That last part matters — a clean handoff signal prevents the client from continuing to route requests through the person who said yes to everything.
Script it: "Priya is now your day-to-day lead. She's got the full picture of everything we discussed. I'll be checking in at the 90-day mark, but Priya owns the work from here."
Then delivery restates the scope out loud to the client. All of it. Including what's not included. This feels awkward and it is the highest-ROI awkwardness in your process — it's where you catch mismatched expectations while they're still cheap to fix. If the client says "wait, I thought link building was included," you'd rather learn that on day 8 than day 68. If it comes up later anyway, you'll need a process for saying no to out-of-scope requests politely.
Where the handoff data has to live
Most handoff processes die because the document lands in a Google Doc that nobody opens after week two. The context needs to sit inside the system where the work happens — attached to the project, visible to whoever picks up a task in month seven.
This is where generic project tools get thin. A card in Trello or a task in Asana holds a to-do fine, but it doesn't natively connect the deliverable to the budgeted hours to the retainer to the original promise. Agencies end up with the SOW in one place, hours in a timesheet tool, client comms in email, and the handoff doc in a Drive folder — the classic agency Franken-system. If you're evaluating what to consolidate onto, the agency PM tool roundup is a reasonable starting point. PeakKR handles this by tying retainer scope, budgeted hours, and phase deliverables to the same project record, so the handoff isn't a separate artifact — it's the project setup.
Track whether the handoff worked
Three numbers tell you if your process is real:
- Days from signature to kickoff. Target under 10 business days. If yours is 21, that's where churn is being manufactured.
- Month-one hour variance. If budgeted month one is 44 hours and you burned 67, the handoff missed something. Consistent 40%+ overruns in month one mean sales is selling a different engagement than delivery is running — and you'll be writing a project recovery plan by month four.
- Scope disputes in the first 60 days. Log every "I thought that was included." More than one per new account means the handoff doc isn't capturing verbal promises.
Review these quarterly with sales in the room. Not as a blame exercise — as a calibration one. When a salesperson sees that the three deals they closed with thin handoffs all overran by 35%, the behaviour changes faster than any policy memo achieves.
One structural fix worth considering
On deals above a certain size — pick a threshold, maybe $5k/month — put an SEO lead on the second sales call. Not to sell. To scope. They'll ask about the CMS, the dev process, the content approval chain, and the 40,000 orphaned URLs the prospect forgot to mention.
It costs you an hour of senior time per qualified deal. It buys you a scope that's actually buildable and a delivery team that met the client before the contract existed. Agencies that do this report noticeably lower month-one overruns, because the person estimating the work is the person doing it.
Handoff checklist
- Handoff document template ex
