1. Growth Model
(the transcript is below)
Action Step
Complete this before moving on.
Watch the full overview video above and read through the transcript below. As you go through, pay attention to the four-phase approach (Strategy, Engineering, Enablement, Handoff) and how each function's targets connect back to the revenue goal.
Part 1: Hook / Open
A CRO walks into a board meeting and gets asked "how did you set these targets?"
The honest answer is... a spreadsheet someone on the team put together based on gut feel and a growth rate the board wanted to see.
There's no formula connecting the revenue target to the headcount plan, no math tying marketing budget to pipeline requirements, and no way to tell whether those targets are achievable with the team they have.
That's a pattern we see a lot — the targets exist, but the math behind them doesn't — and the project that fixes it is what we call the Growth Model.
A Growth Model is the infrastructure that reverse-engineers a company's revenue funnel — connecting the ARR target all the way down to headcount, pipeline, marketing budget, and hiring timelines in a single integrated model.
My name is Yasin from LeanScale, and in this video I'm going to break down for you our entire Growth Model Playbook... what it is, the core concepts, how it gets built, and what changes once it's in place.
Part 2: What Growth Model Is
So when we talk about the Growth Model project, what we're actually building under the hood is an integrated planning model that mathematically ties every function's targets together — sales, marketing, customer success, and finance — all working backwards from a single revenue goal.
On the input side, we're pulling in the ARR target, historical conversion rates, sales cycle lengths by segment, quota attainment data, marketing channel efficiency, and CSM capacity ratios.
On the output side, every leader has quarterly targets that are mathematically connected — how many reps to hire and when, the marketing budget by channel tied to SQL targets, CSM headcount tied to new logo projections, and the pipeline that needs to be built one full sales cycle before it's needed.
But here's the thing — once it's built, the tracking is formulaic.
When one number changes — say conversion rate drops or a hire gets delayed — the entire model recalculates and shows exactly where the impact lands.
The way I describe it to clients is that a Growth Model is like a blueprint for a building.
Without it, every contractor is working off their own interpretation of what the building should look like — the plumber and the electrician are making separate plans, and nobody knows if it all fits together until they're already behind schedule.
With it, every function is building off the same set of plans, every dependency is mapped, and when something changes on one floor the team knows exactly what that means for every other floor.
Part 3: Growth Model Pro Tips
Now the Playbooks Library below this video goes deep on the full methodology behind the Growth Model project — but before we get into how it gets built, here are a couple things you really don't want to get wrong when implementing this into a startup.
First — understanding the difference between top-down and bottom-up planning. Almost every company we work with either has a board target with no validation of whether the team can hit it, or a bottom-up plan that's too conservative. The best growth models use what we call the W Method — iterating between executive targets and functional team capacity until both sides align.
Second — pipeline has to be built one full sales cycle before the bookings period it feeds. This is the most missed calculation in growth planning. If the sales cycle is 90 days and the target is Q4 bookings, that pipeline needs to exist in Q3. Companies that figure it out as they go discover mid-year they don't have next quarter's pipeline, and by then it's too late.
Third — headcount math is not capacity math. Saying "we need five reps at a million each to hit five million" ignores the fact that a new rep takes five to seven months to ramp and 30% of sales reps turn over annually. Factor in ramp and attrition, and that fifth rep you hire in Q1 is producing maybe 600K in year one, not a million.
Part 4: The Problem in Context
And the data backs up why this project is so key for startups who are scaling.
According to CB Insights, poor planning is the primary driver of startup failure — not product, not market fit — and 75% of venture-backed companies never return cash to investors.
Gartner found that only 7% of organizations achieve greater than 90% forecast accuracy, and fewer than half of sales leaders trust their own forecasts.
The Salesforce State of Sales Report found that only 30% of B2B reps hit quota in 2024, down from 44% in 2022.
And Demandbase found that sales and marketing misalignment costs companies 10% of annual revenue on average.
So it's not just one team that feels this — sales is missing quota because targets weren't tied to capacity, marketing is spending without knowing which channels produce pipeline at the right cost, finance can't get clean CAC by segment, and the CEO is defending a growth plan to investors that nobody on the team actually believes in.
Part 5: How It Gets Built
So how does a Growth Model project actually get implemented?
At LeanScale, for all of our projects, we follow a four-phase approach — Strategy, Engineering, Enablement, and Handoff.
Strategy
In the Growth Model project, strategy is by far the heaviest phase — it's where about 70% of the work happens.
This is where we work with every stakeholder who touches the revenue plan — the CRO, VP of Sales, CMO, head of CS, finance, and RevOps — and align everyone around a single integrated model.
Before the project even kicks off, our team pulls the company's CRM data — opportunity data, conversion rates by segment, sales cycle lengths, quota attainment history — and assembles a V0 of the growth model based on best practices from having built this for dozens of startups, combined with the unique data from the company we're working with.
We also lean heavily on AI agents throughout this process — agents trained on our playbooks that know how to analyze CRM exports, extract conversion rates, flag data quality issues, and assemble a draft model from intake data and benchmarks. We go deeper into how we use AI in the implementation of this project in the full playbooks in the library.
From there, we walk into the kickoff with a model that's already 70% built — the customer is reacting and correcting, not creating from scratch.
Over seven meetings, we iterate with each stakeholder — locking in revenue targets, validating sales capacity rep by rep with ramp and attrition, confirming marketing SQL targets by channel with pipeline timing offsets, validating CSM capacity, and stress-testing the whole plan with finance.
At the end of that process, four things are locked in: the bookings target tied to ARR, a rep-by-rep hiring plan with quarterly timing, a marketing budget by channel tied to SQL and pipeline requirements, and a CSM capacity plan tied to new logo projections.
Engineering
Phase two is the technical build — and for the Growth Model, this phase is lighter than most of our other projects.
The core deliverable from strategy is the model itself — which powers an interactive dashboard the customer can explore and use for board presentations.
For companies that want ongoing tracking, we configure dashboards that show plan versus actuals, quota tracking by rep, pipeline versus target with timing offsets, and variance alerts when metrics drift.
We've built a Growth Model Agent that uses structured planning frameworks with all of the capacity assumptions, conversion ratios, ramp curves, and segment-level unit economics codified. Using APIs and MCPs, that agent connects directly to the CRM — whether that's Salesforce or HubSpot — and pulls pipeline actuals, rep productivity data, and marketing spend to keep the model calibrated against real performance.
What used to be a 30 to 60 hour manual modeling effort now gets delivered in a fraction of the time because the agents handle the data extraction, the calculations, and the model iterations while our human architects focus on orchestration, the strategic judgment calls and stakeholder alignment.
The full details of the AI agents we use and the model build process are broken down inside the playbook library if you're curious.
Enablement
Phase three is enablement, because the model is useless if the team doesn't know how to use it.
For the growth model:
We train RevOps on the full model mechanics — how to enter monthly actuals, run scenarios, and monitor assumptions.
We train sales leadership on their capacity model and when hiring triggers should fire.
We train marketing on SQL targets by channel and how the pipeline timing offset works.
And we train CS and finance on their respective sections — carry ratios, hiring triggers, board reporting views, and how the whole model ties to the operating budget.
Handoff
From there phase four is the handoff, and this is where maintenance expectations get set.
And this is important — a Growth Model is not a one-time deliverable you build and put on a shelf.
It requires monthly tracking of actuals versus plan, quarterly assumption reviews, and an annual full recalibration with fresh historical data.
And here's why that matters: every time a key hire gets delayed, every time a conversion rate shifts, every time a new channel launches or an assumption proves wrong — someone needs to update the model.
If nobody owns that, what happens is targets stay locked to assumptions from six months ago. Sales is working off a capacity plan that doesn't account for the two reps who left. Marketing is spending against SQL targets based on a conversion rate that's drifted.
Over two quarters, the model becomes a document nobody trusts — and the company is right back to finger-in-the-air planning.
So the handoff isn't just about transferring ownership — it's about making sure after the model is fully built out... someone on the team understands the model deeply enough to keep it accurate and relevant.
Part 6: What It Unlocks + Close
So let's bring this all together to where we started. Once the growth model project is in place, what actually changes?
Every function's targets are mathematically connected to the revenue goal — when the board asks how targets were set, the answer is a formula, not a feeling.
Companies with proper growth planning see 15 to 30% improvement in pipeline production — and research shows companies with strong cross-functional alignment grow 19% faster.
Hiring goes from reactive to proactive — instead of scrambling when capacity feels tight, the model tells leadership exactly how many reps to hire, which quarter, and what each hire will produce accounting for ramp.
And the biggest thing that changes after this project is confidence and certainty.
That CRO can now answer "how did you set these targets?" with actual math — here's the capacity, here's the pipeline, here's the conversion rates, and here's what needs to be true for us to hit the number.
Finance gets a model that ties to the operating plan without manually reconciling spreadsheets, and every functional leader is working off the same blueprint instead of planning in silos.
If you want more detail on any of this — the concepts, the methodology, the full implementation process — the playbooks library has everything laid out for you. Our Advisory Overview Playbook covers the problem, approaches, and strategic understanding behind this project. The Methodology Playbook goes deep on every concept we talked about for this project. And the Implementation walks through the step-by-step build process.
And if you're a revenue leader at a fast growing startup who's feeling good about the planning and forecasting side after watching this — but you're thinking, okay, now how do I make sure the stage definitions and conversion tracking can actually measure against these targets — we have a whole playbook on exactly that called the GTM Lifecycle. It's broken down the same way in our Playbook Library. And while you're there, you'll see we have playbooks on every major GTM project — from Market Map and Attribution to Quote to Cash and more. Feel free to check those out next.
Again, this is Yasin from LeanScale, and I'll see you in the next one!
Comment in Slack
Post your answer in your onboarding channel.
What did you learn? What clicked?
Any questions — or will you have more questions once you actually get into the hands-on trainings? Either is fine. Just capture where you are right now.