Every few months a founder asks me some version of the same question: if you joined on day one and had to build an AI-native growth function from nothing, what would you actually do first? Not a vision deck. The real sequence, week by week, with the tools and the hires in the order they pay for themselves.
This is that plan. I'm writing it as the memo I'd hand a hiring manager before the offer, not after. It's grounded in the stack I actually run day to day, Astro, n8n, Claude Routines, GA4, IndexNow, not a vendor-neutral framework that sounds good in a meeting and falls apart on contact with a real backlog.
Why "growth function," not "growth hire"
Most companies still budget for growth like it's 2019: hire a marketer, give them a few tools, hope the pipeline compounds. That model assumes the bottleneck is headcount. In 2026 the bottleneck is usually architecture, how the tools talk to each other, what runs without a human clicking a button, and what gets measured automatically instead of in a Friday spreadsheet.
A growth function is the system, not the person. One generalist with the right stack can do what used to take three specialists, an SEO lead, a marketing ops hire, and a data analyst, because the judgment work and the repetitive work finally run on separate tracks. I cover the actual split between those two tracks in Claude Routines vs n8n: when to use which, the short version here is that deterministic pipeline work goes to n8n and anything needing judgment goes to an agent. The 90-day plan below is built on top of that split.
Not a growth marketer. Not a performance ads specialist. A generalist who can write production code, wire an n8n workflow, and prompt an agent well enough to trust it with judgment calls. That combination is rare and it's the entire reason a one-person growth function can outperform a five-person team still working off spreadsheets and manual QA.
The 90-day plan
I'd split it into three 30-day phases: foundation, build, and prove. Each phase has one job. Skipping ahead to "build" without finishing "foundation" is the single most common failure mode I've seen, teams wire automations on top of tracking they can't trust, then spend month four debugging numbers instead of shipping.
| Phase | Job | You'll know it worked when |
|---|---|---|
| Days 1โ30 | Foundation: measurement and audit | Every channel reports to one dashboard, no manual exports |
| Days 31โ60 | Build: automate the repeatable, encode the judgment | Two routines and one n8n pipeline run unattended for a week straight |
| Days 61โ90 | Prove: tie output to pipeline or revenue | A number a CFO would accept, not a vanity metric |
Days 1โ30: foundation
- Audit what already exists. Most companies have GA4 half-configured and a Search Console nobody's opened in months. Fix the tracking before touching the content or the ads.
- Stand up a GA4 channel group that separates AI referral traffic (chatgpt.com, perplexity.ai, gemini.google.com) from classic organic. I walked through the exact setup in Claude Routines vs n8n and the posts it links to, without this split you're flying blind on the fastest-growing channel.
- Get IndexNow wired to the deploy pipeline. A single API call on every publish, cheap to set up, immediately shortens the gap between "we shipped it" and "it's indexed."
- Pick the Astro-or-equivalent stack if the current site is slow to ship on. Static-first with a real build step beats a page builder the moment you need to template dozens of pages without hand-editing each one.
- Write the standard before automating anything. A checklist for what "good" looks like, schema present, answer-first structure, internal links, freshness dates. Automations only enforce a standard that already exists on paper.
Days 31โ60: build
- Ship the first Claude routine: a pre-merge content gate. It reviews every page against the checklist from phase one and comments instead of silently merging. Report-only first, always, until you trust its judgment on real edge cases.
- Stand up an n8n pipeline for the deterministic fan-out work, turning one topic brief into a draft, schema, and image generation without a human touching each step. This is the track that should never involve an agent making a judgment call, it's the same shape every time.
- Add a scheduled routine for a weekly audit catching broken links, stale freshness dates, and orphan pages, the kind of rot that compounds quietly if nobody's watching for it.
- Connect deploy-triggered IndexNow so URL submission stops being a manual step someone forgets during a busy week.
Days 61โ90: prove it
- Pull the first real report. AI referral sessions, organic sessions, and whatever the business actually sells, tied together in one view, not three separate exports.
- Kill whatever didn't work. Something from phase two will be a dud. Cut it before month four instead of defending the sunk cost.
- Document the playbook. Everything built in the first 60 days should be reproducible by the next hire without three Slack threads of tribal knowledge.
- Decide the next hire, if any. By day 90 you'll know whether the gap is more engineering, more content, or more paid acquisition. Don't guess that on day one.
If the company's data is scattered across five tools with no shared identifier (a customer ID, a UTM convention, anything), phase one takes longer than 30 days and that's fine. Shipping automations on top of broken tracking just automates the confusion faster. I'd rather report "foundation took 45 days" on day 45 than ship a dashboard nobody trusts.
The tool stack, and why each piece earns its spot
| Layer | Tool | Job |
|---|---|---|
| Site | Astro + a fast host | Static-first, no framework tax on pages that don't need client-side state |
| Deterministic pipelines | n8n | Content fan-out, feed syncs, anything with a fixed, repeatable shape |
| Judgment work | Claude Routines | PR review, audits, anything where the right steps depend on what gets found |
| Measurement | GA4 + Search Console | Separate AI referral traffic from classic organic, track citations, not just clicks |
| Crawl + indexing | IndexNow | Cuts the lag between publish and indexed, free and a single API call |
Nothing on that list is exotic, and that's deliberate. I run the full breakdown of what's actually in production, ranked by impact, in my AI agent portfolio. The advantage isn't in any single tool, it's in keeping the deterministic and the judgment-based work on separate tracks instead of forcing one tool to do both badly.
Team shape, not headcount
I'd resist adding a second full-time hire until the generalist from month one is genuinely bottlenecked, not busy, bottlenecked. Busy is normal in month two. Bottlenecked means a specific, recurring task that a specialist would do measurably better and more often than the generalist can get to it.
When that happens, the second hire is almost never another generalist. It's someone who covers the one gap the audit actually revealed, paid acquisition, lifecycle email, or deeper engineering for a product the growth system now depends on. Hiring a second generalist before that gap is clear just duplicates coverage instead of extending it.
Key takeaways
- Build the function, not the headcount. One generalist with the right stack replaces work that used to take a team, because deterministic and judgment-based tasks finally run on separate tracks.
- Foundation before build, always. Automating on top of untrusted tracking just produces confusion faster.
- Report-only automations first. A pre-merge gate or a weekly audit earns trust by flagging issues before it ever gets permission to fix them directly.
- The 90-day output isn't a dashboard, it's a number a CFO would accept and a playbook the next hire can run without you.
- Don't hire the second person until the audit names the specific gap. A second generalist rarely is the right next hire.
What I'll do next
I'm turning this into an actual working template, the checklist from phase one, the two routine prompts from phase two, and the report structure from phase three, as a single repo a hiring manager could hand to day-one me. I've already written the individual pieces, the routine-versus-pipeline split in Claude Routines vs n8n and the full automation inventory in my AI agent portfolio, what's missing is stitching them into one onboarding document instead of scattered posts.
FAQ
What's the very first thing you'd do on day one? +
Would you hire a full growth team on day one?
How do you decide what goes in n8n versus a Claude routine?
What should the 90-day review actually measure?
What's the biggest mistake companies make building this?
Want this built for your team?
I design AI agents and growth automation that run without babysitting. If that sounds useful, let's talk.
Get in touch โ