Client onboarding and baseline audits
The first 30 days determine whether the next 12 months go well or poorly. A structured 30-day onboarding sequence covering kickoff, baseline audit, competitor analysis, 90-day plan, and first shipped deliverables.
Why the first 30 days set the engagement
Client onboarding determines whether the next 12 months go well or poorly. The first 30 days establish the baseline against which all progress is measured, the working rhythm between operator and client, and the trust that determines whether the client renews. Operators who treat onboarding as paperwork wind up scrambling 4-6 months in when the client asks "what has changed?" and the operator has no clean baseline to compare against.
This lesson covers a structured 30-day onboarding sequence — what to deliver in each week, how to set expectations correctly, and what baseline audit specifically produces.
Day 0: pre-engagement handoff
Once the SOW is signed but before the engagement formally starts, three things happen:
Welcome email + kickoff scheduling
Same-day email confirming the engagement, the kickoff call date (within 5 business days), and a short list of what you need before kickoff (access credentials, brand guidelines, list of competitors they consider most important). Set the tone: responsive, organized, specific.
Access provisioning
Request access to: Google Analytics, search console, CMS (read-only at minimum for the audit; write access by Day 14 for content shipping), Reffed account creation for the client, any other relevant analytics tools.
Clients vary enormously on access provisioning speed. Aim for all access in hand by end of Day 7. If access drags past Day 14, escalate the priority — your work pace depends on it.
Stakeholder identification
Document the people you'll work with. Three roles need clear names:
- Executive sponsor. The person whose budget pays for the engagement. Typically a VP or above. Quarterly check-in only.
- Day-to-day contact. The marketing manager or content lead you work with weekly. Approves content, schedules calls, escalates blockers.
- Implementation owner. The person who actually ships your work into their CMS or makes technical changes. Often a developer or web producer. Critical because their pace gates your impact.
If any role is missing or unclear, surface that immediately. Engagements without clear ownership stall predictably around Day 45-60.
Week 1: kickoff and immersion
The kickoff call (60-90 minutes)
Three agenda blocks:
- Goals confirmation. Restate the business outcomes from the SOW. Ask the client to confirm and add nuance. "We're targeting top-3 cited brand for [category] within 9 months. What does success look like for you specifically beyond the metric?"
- Brand and product immersion. Client team walks you through their product, ICP, top 3 competitors, top messaging themes. 30-45 minutes. Record the call (with permission) for reference.
- Working rhythm setup. Confirm the monthly review meeting cadence. Set Slack or email as the async channel. Establish response-time expectations both directions (typically 1 business day for non-urgent, same day for urgent).
Documentation review
Request and review: brand guidelines, existing content strategy docs, prior agency reports if any, sales messaging documents, customer personas. Most clients send 5-15 documents totaling 30-100 pages. Block 3-4 hours to read systematically.
Initial Reffed audit
Run a full audit at the end of Week 1. The audit gives you the first numerical view of where the client stands. Save the report — this becomes the baseline for everything to come.
Week 2: deeper baseline and competitor analysis
Manual prompt-level audit
Beyond the automated Reffed audit, run the 8-prompt manual audit (from Foundations Lesson 3) against ChatGPT, Claude, Perplexity, and Google AI Overviews. Document the actual responses for each prompt on each engine. This is the qualitative baseline — what AI engines actually say about the client today, in their own words.
The manual audit takes 4-6 hours but produces the most useful single artifact in onboarding. You'll reference these baseline responses when reporting progress months later.
Competitor deep-dive (top 3)
Apply the methodology from Lesson 4.3 to the client's top 3 competitors. Map each competitor's:
- Wikipedia/Wikidata presence
- Reddit citation surface
- Aggregator standing
- Editorial coverage
- Content portfolio depth and structure
- Schema implementation
The deep-dive surfaces the specific gaps between the client's current position and where their competitors are. Those gaps become the action items for the next 90 days.
Content audit
Inventory the client's existing content. Three categories:
- Citation-active pages: Already appear in AI engine responses for relevant queries. Reinforce and extend these.
- Citation-ready pages: Strong content that hasn't yet earned citations. Usually a structure or schema fix away from working.
- Citation-dead pages: Existing pages that don't and won't earn citations without significant rewrite. Decision: rewrite, redirect, or archive.
Week 3: synthesis and roadmap delivery
The 90-day plan document
The output of weeks 1-2 is a structured 90-day plan covering:
- Where the client stands today. Baseline metrics, manual audit responses, content portfolio summary.
- Where competitors stand. Competitive landscape pattern, deep-dive findings, identified gaps.
- What we'll work on for the next 90 days. Specific deliverables, week by week, mapped to gaps and priorities.
- What success looks like in 90 days. Specific metric movements expected, with conservative estimates.
Length: 8-15 pages. Walk through it with the client live in a 60-minute review meeting. Don't email and hope.
Setting realistic expectations
The most important conversation in the entire engagement happens in this Week 3 review: setting the right expectation for timing of results. Honest framing:
- Entity-signal improvements register within 14-30 days
- Content extractability changes typically surface in citation patterns within 30-60 days
- Third-party authority work (Wikipedia, Reddit, aggregators, editorial) takes 60-180 days
- Meaningful share-of-model gains are 3-6 month outcomes, not 30-day outcomes
Clients who think GEO is a 30-day intervention will be disappointed at Day 30 regardless of how well the work is going. Clients who understand the 90-180 day arc will stay engaged through the early-phase work that doesn't yet show in metrics.
Week 4: execution begins
First shipped deliverables
End of Week 4, ship the first content and technical work. Specific deliverables vary by SOW, but typical first-month outputs:
- 2-3 pillar content pieces produced and submitted for client review
- Schema audit completed; recommended schema updates delivered to implementation owner
- Organization schema sameAs array updated
- llms.txt and modern robots.txt drafted and delivered
- First wave of off-page outreach initiated (5-8 journalist pitches sent, 2-3 Reddit contributions made)
Month 1 report
Deliver the first monthly report at the end of Week 4. Format:
- One-paragraph executive summary
- Baseline metrics (saved for comparison in future reports)
- Activities completed this month
- Next month's planned activities
- One observation or recommendation that goes beyond execution
Length: 3-5 pages. The first report sets the template for every monthly report that follows. Invest in making it sharp.
Common onboarding pitfalls
Five mistakes that recur across GEO engagements:
- Starting content production before completing the baseline audit. Without baseline, you cannot measure progress. Resist the urge to "show productivity" in week 1 by shipping content immediately.
- Skipping the manual prompt-level audit. The automated audit gives you numbers; the manual audit gives you the actual quotes AI engines produce. The qualitative baseline matters more than the numerical one for client conversations.
- Not documenting the implementation owner. If you don't have a clear name for who ships your work into the client's site, your work bottlenecks unpredictably 60 days in.
- Promising too-fast results to win the engagement. Whatever you commit to in the kickoff sets the client's expectation for the entire relationship. Conservative commitments produce better long-term satisfaction than aggressive commitments that miss.
- Not setting a quarterly cadence with the executive sponsor. Day-to-day contacts can champion the work, but renewals are decided by executive sponsors. If the executive sponsor only hears about the engagement at renewal time, you're flying blind on retention.
Implementation: improving your onboarding this month
- Week 1. Document your current onboarding process. Honest assessment: which weeks have explicit deliverables and which are improvised?
- Week 2. Build templates for each onboarding artifact: kickoff agenda, manual audit worksheet, 90-day plan template, first monthly report template.
- Week 3. Apply the new structure to your next new engagement.
- Week 4. Retrospective: where did the new structure produce friction? Iterate.
What comes next
Module 5 is complete. You can now price GEO services, document scope rigorously, and run a 30-day onboarding that sets engagements up for long-term success.
Module 6 — the final module — covers scaling: production workflows when you have 5+ clients, tool stacks for operators, hiring and subcontracting, and the specific transition from 3 to 15 clients which is where most operators either compound or burn out.