How to Build a SaaS Growth Model

Ask a VP of Marketing which single number, improved by a tenth, would add the most ARR this year. Most cannot answer, and the reason is that nobody has written the arithmetic down. What exists instead is a plan: eighteen initiatives, four channels, a hiring request and a target that came from the board rather than from the business.

A growth model fixes that by forcing the business into one chain of multiplication and subtraction. It is deliberately reductive. The value is not that the forecast lands, because it won’t, but that you can watch each input move every month and see which one is actually holding the company back.

This guide builds one end to end, with a full numeric example for a $4M ARR product at $9,000 average contract value. Copy the structure from the SaaS growth model template if you’d rather not start from a blank sheet.

What separates a growth model from a forecast deck

A forecast states a number. A model states how that number gets produced, which means it can be wrong in a specific, diagnosable way. That falsifiability is the whole test.

Run this check on whatever you currently call a model. Can you name every input? Can each one be measured from a system you already own, monthly, without a special analysis request? When the month closes, does someone paste actuals next to the prediction and explain the gaps? Three yeses and you have a model. Fewer and you have a slide.

The other structural difference is direction of travel. Finance models usually run backwards from a target: we need $6M ending ARR, therefore we need 222 new customers, therefore marketing needs to source 40 percent of them. Growth models run forwards from measured reality and frequently produce an uncomfortable answer. That disagreement is the output you’re paying for.

Which of the four growth archetypes are you actually running?

Most SaaS businesses are dominated by one of four engines, and the archetype decides which inputs deserve a tab of their own. Getting this wrong is expensive: an acquisition-driven team building expansion dashboards wastes a quarter, and a retention-driven team adding paid channels burns cash on a leaking bucket.

Archetype	You are running this if	Dominant input	Typical trap
Acquisition-driven	70 percent or more of new ARR comes from new logos and NRR sits under 105 percent	Qualified traffic multiplied by signup rate	Buying growth that leaks straight back out through churn
Retention-driven	NRR above 115 percent and new logo count roughly flat year over year	Gross revenue retention and expansion rate	Under-investing in new logos until category penetration quietly stalls
Monetisation-driven	ARR grows materially faster than customer count	ACV, packaging, seat and usage expansion	Modelling a one-time repricing gain as a recurring annual rate
Loop-driven	A measurable share of new signups arrive through existing users or user-created artefacts	Loop output per cycle and cycle time	Calling a referral discount a loop when the product has no sharing moment

Most B2B SaaS at $2M to $10M ARR is acquisition-driven and wishes it were loop-driven. Be honest about that. If you want the loop-driven version, the mechanics are specific and mostly structural rather than promotional, which is covered in the growth loop definition and worth reading before you model any referral coefficient.

The archetype also determines how far ahead the model can see. Acquisition-driven models are reliable at 6 to 9 months and guesswork beyond 12. Retention-driven models hold up over 24 months because the base moves slowly. That difference should change how much of the annual plan you’re willing to commit in January.

Building the equation tab by tab

Seven inputs carry almost all the signal. Each gets its own column of monthly actuals and one forecast assumption, and the model multiplies through in order.

Add a referral or loop coefficient only if you can measure it from product data, not from a self-reported survey field. A coefficient you cannot instrument is a wish with a decimal point.

Resist the urge to add more. Every extra input costs you reconciliation time each month, and the practical ceiling is around ten before somebody quietly stops updating the sheet. A model that gets reconciled at seven inputs beats a beautiful one at twenty-two that gets opened once.

A worked model for a $4M ARR product at $9,000 ACV

Here is the full chain for a B2B product with a self-serve trial and a light sales touch on larger accounts. The numbers are illustrative but internally consistent, and they’re close to what a company at this stage typically reports.

On the base of $4M, gross revenue retention runs at 87 percent, which removes $520,000. Expansion runs at 13 percent, which adds $520,000 back. Net revenue retention is therefore exactly 100 percent, the base is flat, and every dollar of growth comes from new logos. Ending ARR lands near $6.03M, or 51 percent growth.

That model already tells you something useful before any experiment runs. This company is acquisition-driven by default, not by choice, and an NRR of 100 percent at $9K ACV means the installed base is doing no work at all.

Why five points of activation beat a 30 percent traffic gain

Take the same model and run two candidate bets for the coming year. One buys 30 percent more qualified traffic. The other lifts week-one activation from 34 percent to 39 percent.

The traffic bet looks bigger on first inspection and isn’t, for one reason: the extra 13,800 sessions do not convert at 1.5 percent. They convert at roughly 0.9 percent, because the highest-intent queries and the best-performing pages were already captured. That gives 814 signups rather than 690, not the 897 a blended rate would predict.

The activation bet moves a number that appears twice in the equation. It multiplies new customer volume, and it improves retention and expansion on everything already in the book, because accounts that reach the core action in week one behave differently for the rest of their life.

Bet	New ARR gain, 12 months	Base effect	Total ARR gain	Cost and lag
Traffic plus 30 percent	+$362,000	None	+$362,000	$130K to $180K of extra content and paid spend, 6 to 9 month lag
Activation plus 5 points	+$295,000	+$240,000 from 4 points of GRR and 4 points of expansion	+$535,000	Two engineers for a quarter, first signal in about 3 weeks

The broader point survives the caveat. Inputs that appear more than once in the chain carry more weight than inputs that appear once, and activation sits at the junction between acquisition and retention in almost every SaaS model. That’s also why it shows up as the first lever in most strategies that compound rather than plateau.

Running sensitivity to find the binding constraint

Improve each input by 10 percent relative, one at a time, hold everything else fixed, and record the 12 month ARR change. Then put an honest effort estimate next to each. The ratio, not the raw number, names your constraint.

Two things stand out. Retention produces the second-largest number and is by some distance the hardest 10 percent to obtain, which is why it belongs in the annual plan rather than the quarterly one. And qualified traffic, the input almost every marketing plan leads with, sits last on ratio because of the marginal conversion decay.

Rerun this table every quarter. Constraints move. Once activation is fixed, activated-to-paid usually becomes the bottleneck, and the same sensitivity run will say so without anyone arguing about it in a meeting.

Calibrating the model against actuals every month

On close day, paste the month’s actuals into the actuals column and compute variance per input. Write one sentence for every variance above 10 percent. The whole exercise takes about 40 minutes and it is the single behaviour that separates models that survive from models that get archived.

Three variance patterns are worth naming because they recur:

• Volume up, conversion down, ARR flat. You bought lower-intent traffic. Expected, and fine, provided the model’s marginal rate was set honestly in advance.
• Activation up, paid conversion down. Your activation definition has drifted toward something easy that does not predict payment. Retest the definition against the paid cohort.
• Everything on plan, ARR short. Churn or contraction moved, and the acquisition tabs hid it. Check GRR before you blame the funnel.

Version the model each quarter and keep the old files. When someone asks in October why the July forecast was 30 percent high, the answer should take four minutes to find, not a week. This discipline is the same one that keeps a SaaS marketing model honest at the channel level, and the two documents should share their input definitions exactly.

We ran the model for three months before anyone believed it. Month four it predicted our trial volume within 4 percent and missed paid conversion by 20, which is how we found out sales had quietly stopped calling self-serve trials.

The failure mode: a model built in a deck and never reconciled

The most common way a growth model dies is not error, it is abandonment. Somebody builds a beautiful version for a board meeting in January, presents it, and never opens it again. By April the input definitions have drifted, by July nobody remembers what activation meant, and the model is quietly replaced with a revenue target and a list of campaigns.

Three defences, in order of importance. Give the model a named owner who is measured on reconciliation, not on forecast accuracy. Put the monthly reconciliation on a recurring calendar invite with the finance close. And keep the model in a shared sheet that operators can open, rather than inside a BI tool that requires a ticket.

The other frequent failure is over-engineering. A model with 40 inputs, a Monte Carlo tab and three scenario toggles feels more serious and is far more fragile. If the person who built it leaves, an over-engineered model dies the same week. Seven inputs on a shared spreadsheet outlive most reorganisations.

There’s a cost nobody mentions either. A working model will occasionally tell you to stop doing something a team is emotionally invested in, and if leadership won’t act on that output, the model becomes theatre within two quarters. Decide in advance whether you actually want the answer.

What changes as you scale past this model

At $4M ARR one model tab per input is enough. Past roughly $15M, segment the whole chain by motion, because self-serve and sales-assisted have different conversion rates, different ACVs and different retention, and blending them hides everything worth knowing. The stage-by-stage version of that progression is set out in the scaling growth after product market fit playbook.

Cost inputs also deserve their own tab once headcount decisions depend on the model. Cost per qualified session, fully loaded cost per published asset and cost per activated account turn the growth model into a budgeting instrument rather than a forecasting one. The agency versus in-house cost calculator is the fastest way to get defensible numbers for that tab if you’re comparing delivery options.

Two segmentations are worth adding early because they change decisions: motion, and ACV band. Almost nothing else pays for the complexity it adds at this stage.

Do this in the next five days

Open a blank sheet. Put the seven inputs in column A and pull the last six months of actuals for each from the systems you already have. If you cannot find one of them in under an hour, that missing instrument is your first project, not the model.

Then build the single-month chain, extend it twelve months, and run the sensitivity table. You will have an answer to the question at the top of this page by Friday, and it is frequently not the input the current plan is built around. If the answer looks like a demand problem rather than a conversion problem, the B2B SaaS growth levers guide maps each symptom to the right diagnostic, and the growth experiment brief template turns the winning input into something a team can actually run. Broader context on where a model sits inside the wider function lives in the SaaS growth marketing hub.