How I Operate & Build Applied Growth Systems
A connected engine of acquisition, activation, retention, and revenue — built on a structured operating system, powered by AI, and applied across every stage of the funnel.
Growth Compounds When It's Treated as a System
The difference between companies that plateau and companies that compound isn't budget or headcount. It's structure.
Each month starts from zero
Each cycle builds on the last
Channels operate in silos
Inputs, experiments, outputs connect
Urgency drives the roadmap
Impact scores drive the roadmap
Coined the growth loop model — test rapidly, kill what doesn't work, double what does
Built the systems-over-tactics framework — growth is an engine, not a campaign
Defined activation-first growth — find the aha moment, build your whole system around it
“The principles haven't changed. The stack has.”
How I Operate: The Growth OS
Five stages that run on every engagement, every sprint, every decision.
Clarify
Define the actual business outcome before optimizing anything.
"Not 'more traffic' — 'reduce CAC below $40 by Q3'"
Diagnose
Find the real constraint — not the assumed one.
"Traffic is fine. The page converts at 1.2%. That's the lever."
Prioritize
Score opportunities by impact, confidence, and ease.
RICE scoring — every initiative ranked, nothing random
Experiment
Run controlled tests before committing to full execution.
Two-week sprints, hypothesis-driven, kill fast / scale fast
Scale
Turn validated wins into systems: SOPs, automation, dashboards.
So wins don't live in one person's head
Where It Gets Applied: The AARRR Model
The OS runs across every stage of the funnel — not just acquisition.
Metrics
Focus
Primary Lever
Diagnose → ExperimentMetrics
Focus
Primary Lever
Clarify → ExperimentMetrics
Focus
Primary Lever
Scale → DiagnoseMetrics
Focus
Primary Lever
Prioritize → ScaleMetrics
Focus
Primary Lever
Experiment → ScaleaiOS: The Intelligence Layer That Multiplies the System
AI doesn't replace the system. It runs inside it — accelerating every step, eliminating manual overhead, and making the whole engine faster.
Karpathy-Style Memory
Retains every experiment, result, and pattern — the system gets smarter with every cycle.
Obsidian Vault
Connects strategy, briefs, audits, and frameworks into one searchable operating layer.
ACE Framework
Atlas tracks what's known, Calendar sequences what's next, Efforts drives what's in motion.
“Andrew Chen called it 'the growth team's unfair advantage' — proprietary systems that competitors can't copy because they're built around your specific data, customers, and context. aiOS is that layer.”
Every Skill Has a Place in the System
Capabilities without a system are just a list. Here's where each one fires.
Acquisition Engine
- ·Paid Digital & Programmatic/CTV
- ·SEO, AEO, & content
- ·Attribution modeling
- ·OOH/Traditional channel strategy
Conversion Layer
- ·Landing pages
- ·CRO & A/B testing
- ·Offer structuring
- ·Form optimization
Retention + Lifecycle
- ·CRM workflows
- ·Email / SMS sequences
- ·Lifecycle automation
- ·Re-engagement
Analytics + Measurement
- ·GA4 & GTM
- ·BigQuery & Looker
- ·Custom dashboards
- ·ROAS modeling
AI + Automation Systems
- ·n8n · Make · Claude API
- ·aiOS execution layer
- ·Obsidian · Codex · Agents
- ·Wiki systems
Product + Engineering Collab
- ·Next.js & Supabase
- ·Vercel & Railway
- ·Sprint coordination
- ·Data pipelines
Full tech stack available on the homepage — 73 tools across 12 categories.
What You Get When the System Is Running
Not deliverables. Outcomes.
Faster Experiment Velocity
Two-week sprint cycles replace reactive execution. Every test has a hypothesis, a measure, and a kill switch.
Gustaf Alströmer's Airbnb growth team ran 50+ experiments/week. Velocity is the variable most teams underestimate.
Unified Revenue Visibility
Every channel, every funnel stage, every dollar — connected into one reporting layer that tells the business story.
Gokul Rajaram's framework: if you can't measure it across the full funnel, you don't own it.
Compounding Systems
Wins don't live in one person's head. Every validated result becomes an SOP, an automation, or a dashboard.
Brian Balfour's core thesis: the team that systematizes fastest wins the compounding game.
Audit, diagnose, establish baseline metrics and sprint rhythm
First experiments live, reporting unified, quick wins documented
System operational, compounding cycle running, roadmap prioritized by RICE
I'm strongest where growth is treated as infrastructure, not a department.
Ready to Build the System?
Let's talk about what a growth operating system looks like inside your company.