Signed SEO Proposal to Project Plan: The Handoff

The deal is signed. The proposal said "comprehensive technical SEO audit, content strategy, and monthly reporting" for $6,500/month. Now someone has to turn that sentence into 160 hours of scheduled work across four people over 90 days — and nobody wrote down that the salesperson promised a competitor gap analysis on the third call.

Converting an SEO proposal to project plan means translating commercial language into countable units of work, each with an owner, an hour budget, and a date — and doing it within 48 hours of signature while sales context is still fresh. Everything below is the mechanics of that translation.

What actually breaks between signature and kickoff

Three failures account for most of the damage we see in agency delivery:

• Undocumented verbal scope. The proposal says "content strategy." The client heard "you'll write the content." That gap surfaces in week six, usually in writing, usually with the word "expected" in it.
• No hour budget per deliverable. The retainer has a price but no internal capacity model, so the audit quietly consumes 34 hours of a 40-hour monthly allocation and month one delivers nothing else.
• Access limbo. You can't start the technical audit without Search Console, GA4, CMS admin, and server log access. If nobody chased those on day one, you lose two to three weeks and the client experiences it as your slowness.

All three are solvable with a forty-five minute meeting and a document. The reason they persist is that nobody owns the handoff — sales considers the deal done at signature, delivery considers it started at kickoff, and the gap between those two moments has no name.

Step 1: Translate every proposal line into a countable unit

Proposal language is deliberately elastic because it has to sell. Project plans need to be rigid. The translation rule: if you can't count it, you can't schedule it, and you can't defend it.

Here's what that looks like in practice for a mid-size ecommerce client:

• "Comprehensive technical SEO audit" → Crawl of up to 50,000 URLs, 94-point checklist, prioritized findings doc, 60-minute walkthrough call. 22 hours.
• "Content strategy" → Keyword map for 6 priority categories, 40-page content gap analysis, 12 briefs delivered across months 2–4. 28 hours total, 9 in month one.
• "Ongoing optimization" → Up to 15 on-page implementations per month, delivered as tickets to client dev. 8 hours/month.
• "Monthly reporting" → One dashboard, one 5-bullet commentary, one 30-minute call. 3 hours/month.
• "Link acquisition" → 4 placements/month, DR 40+, within approved topical relevance list. 10 hours/month.

Notice the caps. "Up to 50,000 URLs." "Up to 15 implementations." Caps are not hostile; they're the only thing that makes a retainer a retainer rather than an all-you-can-eat contract. If the client exceeds them, you have a documented basis for a conversation instead of a resentment.

Make the hours sum to the money

Take the monthly fee, divide by your target blended rate, and you have your capacity ceiling. A $6,500 retainer at a $160 blended rate is roughly 40 hours. Now add up your translated line items. If the monthly recurring work hits 21 hours and the month-one audit adds 22, month one is at 43 hours — over budget before anyone has touched a keyboard.

That's not a reason to panic. It's a reason to front-load the plan correctly: run the audit in month one at reduced optimization output and tell the client that explicitly at kickoff. The failure mode isn't overspending month one; it's overspending month one silently and then discovering in month five that the account has averaged 52 hours against a 40-hour budget.

Step 2: Build phases, not a task list

A flat list of 60 tasks is not a plan. SEO work is dependency-heavy, and clients experience progress in chunks. Four phases across 90 days works for most engagements:

1. Days 1–10 — Access and baseline. All credentials collected, crawl run, baseline rankings and traffic snapshot captured, tracking validated. Deliverable: baseline document.
2. Days 11–30 — Diagnosis. Technical audit, keyword map, content gap, competitor set locked. Deliverable: prioritized roadmap with effort/impact scoring.
3. Days 31–60 — First implementation wave. Highest-impact technical fixes ticketed, first four briefs delivered, internal linking pass started. Deliverable: implementation log.
4. Days 61–90 — Compounding and proof. Content published, links placed, first meaningful movement reported. Deliverable: 90-day review with next-quarter plan.

Each phase gets a named owner and a hard review date. The 90-day review is the single most underused retention tool in agency SEO — it's where you reframe "no rankings yet" as "here's the leading indicator movement and here's what month four looks like." If you're worried about month-three churn specifically, the mechanics of surviving that window are covered in keeping clients past day 30.

Step 3: Run the 45-minute internal handoff meeting

Sales and delivery, in a room, before kickoff. Six things get transferred:

1. The buyer's actual motivation

Not the one in the proposal. "Their head of marketing is new and needs a win before their Q2 board review" changes what you prioritize in month one. Write it down.

2. Every promise made outside the document

Ask directly: "What did you say on calls that isn't in the scope?" Expect two to four items every time. Log them, price them in hours, and decide now whether to absorb or renegotiate. This is the single highest-ROI question in the entire handoff — more detail on it in keeping every pitch promise.

3. The stakeholder map

Who signs off on content? Who controls the CMS? Who's the internal skeptic? Name them. An unnamed skeptic will surface at month four and you'll have no relationship with them.

4. Known constraints

Legal review on all published content. Dev sprints run biweekly and close on Thursdays. No changes during Black Friday. These determine whether your 90-day plan is fiction.

5. The KPI definition

What specific number will this client judge you by, and is it the number in your reporting template? If they care about non-brand organic revenue and your dashboard leads with sessions, you've built a dispute into month three.

6. Red flags

Payment friction during negotiation, three reschedules, heavy price pressure. These predict delivery friction. Flag them so the PM calibrates communication intensity accordingly.

Step 4: Chase access on day one, not kickoff day

Send the access request the day the contract is signed —