The first 90 days — what a GrowthFather pod actually does in a new engagement

Every agency talks about a "smooth onboarding". Most clients have lived through three or four. They've stopped believing the brochure.

So instead of describing how we work, here's the operator playbook. The week-by-week tasks, owners, and decision gates we ship inside every new engagement. If you've ever inherited a stuck account from another agency, you'll recognise the pattern that cleaned it up.

Week 1 — immersion, not strategy

The first week is the worst time to write strategy. Nothing we'd write would be grounded — we don't have access, we don't know your last quarter, we don't know your team's rhythm. So we run an immersion sprint:

• Founder workshop (90 minutes). Goals, constraints, what's been tried, what's been ruled out. We push hard on "why now" — most plans fail because the urgency wasn't real.
• Access provisioning. Ad accounts, GA4/GSC, CMS, Slack/Drive. We never use a shared agency login — every account stays in your name with named user roles.
• Brand voice audit. We pull every existing landing page, ad, social post, and email and tag the patterns. Most accounts have three voices fighting each other; the audit names them.
• Analytics + ad-account health check. Tracking gaps, conversion misfires, audience contamination, broken pixels. We shortlist the silent leaks.
• Competitive landscape scan. Three to five comparable brands. What they're running, what they're ranking for, what they've recently shipped.

No deliverables go out this week. We're listening.

Week 2 — the audit + the 90-day roadmap

This is the deliverable week. By the end of week 2 you have:

1. A written audit (20–40 pages depending on scope). Technical, paid, organic, CRO. Plain language, not jargon. Every finding gets a tag — ship now, ship in 30, ship in 60, or not worth it.
2. A baseline dashboard. One Looker Studio per pillar (paid, organic, CRO, retention). Numbers we'll be measured against in month two.
3. The 90-day roadmap. Prioritised by value-to-effort, not by what's "exciting". Roadmap items have a named owner, a target ship date, and a success metric.
4. A 30-minute readout. Founder + CMO. We walk the audit, fight about priorities, lock the roadmap.

This is the moment we kill scope creep. If a stakeholder wants to add a new channel that wasn't in the SOW, we surface the trade — what gets pushed to make room.

Week 3 — first shipped work

Strategists who don't ship in the first three weeks rarely ship at all. We commit to at least three shipped artefacts by end of week 3:

• One quick win on the paid side — usually a tracking fix, a negative-keyword sweep, or a creative refresh. Visible in the data within 7 days.
• One organic foundation — could be a sitemap fix, internal linking pass, or a single high-priority brief delivered.
• One CRO surface — a landing page audit live, or the first variant of a homepage hero in test.

The point isn't the magnitude. It's the cadence. Clients who've been burned by previous agencies need to see motion before they trust the strategy.

Week 4 — cadence locked

By end of week 4 the operating rhythm is set:

• Weekly working session. 45 minutes, same time every week, your team + ours. We never run "monthly updates" — work happens weekly.
• Monthly readout format. Plain language, written, in your inbox by the 5th. Wins, losses, what's next, what we need from you.
• Slack/WhatsApp channel. Where the actual work happens. Replies in minutes during business hours.
• Escalation path documented. Who to ping when the campaign breaks at 11pm. Names, phone numbers, response SLAs.

The cadence is non-negotiable from here. If a working session gets cancelled twice in a row, we surface it as a relationship signal.

Days 30–60 — compound experiments

Month two is when patient work starts paying. The roadmap items shipped in month one are now generating data, and we run our first cohort of structured experiments:

• Paid: the 30/30/30 creative method kicks in — 30 concepts, 30 days, ₹30k test budget.
• Organic: first 4–6 priority briefs published. Internal anchors set up. AI-search formatting applied.
• CRO: first 2–3 tested variants shipped. We're picky — only tests where the expected lift × probability of winning > the engineering cost.
• Retention: lifecycle email map drawn, top 3 automations live (welcome, post-purchase, win-back).

We don't move into a fourth pillar until the first three are showing weekly compounding signal.

Days 60–90 — handover, scale, or pivot

The end of month three is a deliberate decision gate, not a scheduled review. We sit with you and answer one question: does the engagement deserve to continue at this scope?

Three legitimate outcomes:

1. Scale up. The engagement is working — we expand scope (additional channel, deeper specialist time, new market). Pricing reopens.
2. Stay the course. Working as planned but not yet at compounding scale. We continue at current scope for another quarter, with revised milestones.
3. Wind down or pivot. It's not working — and we'd rather call it than coast. Either we identify what changed (the assumption that turned out wrong) and pivot, or we give you a clean exit.

A small share of engagements end here. Not ideal, but better than the alternative — which is dragging an unhappy retainer for another two quarters because no one wanted to have the conversation.

What this isn't

This playbook isn't generic agency boilerplate. It's specific to how a 5-person GrowthFather pod operates. A few caveats:

• It assumes the brand voice is already real. If we're writing your positioning from scratch, week 1 looks different — we'd add a brand sprint before the audit.
• It assumes you have at least one in-house owner. A founder, marketing lead, or growth manager who can make decisions inside our weekly call. Without that, the cadence stalls.
• It assumes the SOW is honest. If we're scoped for paid ads but the bottleneck is the website, we'll surface it in week 2 and repropose. We don't build SOW dependencies that lock you in.

The thing nobody talks about

Most agency engagements fail in month two — not month one. Month one is honeymoon energy. Month two is when the messy operational stuff hits: a campaign breaks, a hire takes longer than expected, a stakeholder pulls support.

The first 90 days work because the cadence is locked in week 4 — before month two's chaos arrives. By the time something breaks, the channel for handling it already exists. There's a Slack thread, a working session, an escalation path.

That's it. The playbook isn't clever — it's just refusing to skip the boring weeks.

---

If you want this run on your account, book a discovery call. If you want the rest of how we operate, read the pricing page — it's the operator framework with the numbers attached.