Methodology
Our Product Marketing & RevOps Methodology
We don't invent frameworks to sound proprietary. Every engagement runs on seven established, industry-standard models from product marketing, RevOps, and engineering leadership — explained in full below, with exactly how each one shows up in our services.
The Operating Framework
How these frameworks get applied, engagement to engagement.
- 1
Growth Audit
We review your product analytics, funnel, pricing, and current acquisition channels to find the highest-leverage bottleneck — usually completed within the first week.
- 2
Architecture
We design the specific engine (funnel, media plan, or GTM strategy) needed to fix that bottleneck, with clear success metrics agreed upfront.
- 3
Deployment
Our team executes and ships — in your ad accounts, CRM, and lifecycle tools — with weekly checkpoints so nothing launches into a black box.
- 4
Scale & Compound
We double down on what's working using cohort data, cut what isn't, and expand into the next growth lever on your roadmap.
Pirate Metrics (AARRR)
Originated by Dave McClure, 500 Startups
AARRR splits the user journey into five measurable stages — Acquisition, Activation, Retention, Referral, and Revenue — so a single 'conversion rate' can't hide where a funnel actually breaks.
Most teams have decent Acquisition and Revenue data because ad platforms and billing systems report them automatically. Activation and Retention are where instrumentation usually falls apart, and where the highest-leverage fixes live.
How we apply it
Every Growth Audit starts by mapping your funnel to these five stages before we touch a single channel or campaign — it's how we find the real bottleneck instead of guessing.
The North Star Metric Framework
Popularized by Sean Ellis; formalized by Amplitude
A North Star Metric is the single measure that best captures the value your product delivers to customers — not revenue, which is a lagging output, but a leading indicator like 'weekly active teams' or 'documents processed.'
The framework's real power is in the input metrics beneath it: 2-4 metrics your team can directly influence that ladder up to the North Star. Without that decomposition, a North Star Metric is just a vanity dashboard number.
How we apply it
We define your North Star and its input metrics in week one of any engagement, so every service — from a lifecycle campaign to a paid channel — is judged against the same number your whole company should care about.
The Lead-to-Revenue Waterfall
Standard RevOps pipeline model (Leads → MQL → SQL → SQO → Closed-Won)
The waterfall tracks conversion rate at every pipeline stage, not just top-of-funnel volume and bottom-line revenue. A 60% MQL-to-SQL rate with a 5% SQL-to-Closed-Won rate tells a completely different story than the reverse — even if total revenue looks identical.
Stage-by-stage conversion data is what lets RevOps and marketing agree on where budget or process changes will actually move the needle, instead of arguing from anecdote.
How we apply it
Our Lead Generation engagements instrument this waterfall explicitly, with weekly MQL → SQL → closed-won reporting so you can see exactly which stage improved after each change we ship.
RICE / Impact–Effort Prioritization
RICE scoring popularized by Intercom; Impact-Effort matrix a common PM tool
RICE scores initiatives on Reach, Impact, Confidence, and Effort to produce a comparable priority score — useful when a backlog has more good ideas than a team has capacity to ship. The simplified Impact–Effort matrix plots the same trade-off visually: high-impact, low-effort work goes first.
The framework's value isn't the math — it's forcing an explicit conversation about effort and confidence before committing execution time, instead of prioritizing by whoever asked most recently.
How we apply it
Every roadmap item we propose — a landing page rebuild, a pricing change, a new campaign — gets scored this way before it enters the plan, so you always know why something is being executed now versus next quarter.
The Growth Flywheel
Inbound flywheel model, popularized by HubSpot
The flywheel model replaces the linear funnel (which treats customers as an output) with a loop: Attract, Convert, Close, and Delight feed back into each other, with delighted customers becoming a source of Attract-stage momentum through referrals and reviews.
The practical implication is that 'Delight' — onboarding quality, support, retention — isn't a cost center bolted onto the end of a funnel. It's the stage that determines how much friction (or acceleration) the whole flywheel has going forward.
How we apply it
Fractional CMO engagements are built around keeping this flywheel spinning — pricing, onboarding, and retention decisions are made together, not by separate teams optimizing different stages in isolation.
Cohort-Based LTV:CAC Modeling
Standard SaaS unit-economics methodology
Blended LTV:CAC hides enormous variance between acquisition channels and signup months. Cohort-based modeling groups users by signup period and tracks cumulative revenue against acquisition cost for that specific group — revealing which channels are actually profitable and how long payback really takes.
This is the difference between a channel that looks efficient on last-click ROAS and one that's genuinely compounding: the cohort curve either bends up toward profitability or flattens out, and only cohort data shows you which.
How we apply it
Every Performance Marketing engagement reports cohort LTV:CAC weekly, not platform-reported ROAS — it's the only view that tells you whether spend today will still look good in six months.
Team Topologies
Matthew Skelton & Manuel Pais, Team Topologies (2019)
Team Topologies defines four fundamental team types — stream-aligned, platform, enabling, and complicated-subsystem — and argues most engineering org charts fail because they mix these responsibilities inside one team instead of designing clear boundaries between them.
A stream-aligned team owns a single product or user journey end-to-end. Platform and enabling teams exist to reduce that team's cognitive load, not to accumulate their own empire — the moment a 'platform team' starts dictating roadmap instead of removing friction, the topology has broken.
How we apply it
Every Fractional CTO engagement starts by mapping your current team against these four types — most technical debt and cross-team conflict traces back to a team shaped wrong for what it's actually responsible for.
Keep Exploring
See these frameworks in named form.
Free Growth Audit
Want these frameworks run on your product?
A Growth Audit maps your funnel, pipeline, and cohorts against every model above — then tells you exactly which one to fix first.