Which assumptions belong in a simple GTM math model?
Start with operational truth, not spreadsheet theatre

What is a simple GTM math model actually for?

Most GTM models fail because they try to explain the whole business. That is not the job. A simple model should help you answer a narrow set of operator questions. How much pipeline do we need. Which channel deserves more budget. Is this campaign healthy enough to scale. Are we short on volume, conversion, or sales capacity.

If your sheet cannot change a real decision, it is not a model. It is reporting with formulas. Founders and heads of growth do not need a grand unified theory. They need a decision tool that can survive messy data, weekly review pressure, and shifting channel performance.

That means your first version should be embarrassingly simple. Revenue target on one side. Required pipeline on the other. Between them, only the assumptions that matter enough to move resourcing or spend.

Which assumptions are essential from day one?

There are seven assumptions I would include before anything else. These are the ones that usually change action.

• Pipeline target, because every other input rolls up to required coverage
• Sales cycle length, because timing changes how much coverage you need now versus later
• Stage conversion rates, because weak conversion can make healthy top of funnel look broken
• Show rate, because booked meetings are not pipeline if calendar discipline is poor
• Channel capacity, because every channel has practical delivery and execution limits
• Ramp assumptions, because new programs do not produce like mature ones
• Kill and scale gates, because the model must tell you when to stop, iterate, or push harder

This is enough to run a serious weekly review. It is also enough to catch the most common mistake, teams adding volume to a system with poor downstream conversion or poor attendance.

Which assumptions should sit at the top of the model?

Put commercial assumptions first, not channel metrics. Too many sheets begin with sends, clicks, or reply rates. That reverses the logic. Start with the output the company needs, then solve backward.

• Target revenue or pipeline outcome
• Average deal path in plain language, not fantasy precision
• Expected timing to convert pipeline into revenue
• Current capacity to run and close opportunities

Once those are in place, you can map the minimum flow needed to support the target. This keeps the conversation commercial. Otherwise teams spend an hour debating micro metrics that never reach pipeline.

A simple model should also separate lagging assumptions from leading assumptions. Closed revenue is lagging. Meetings held, opportunities created, and pipeline generated are closer to the present. If your cycle is long, a weekly model should lean more heavily on leading indicators or you will steer too late.

How should you handle outbound assumptions without lying to yourself?

Use thresholds, not optimism. In outbound, one of the cleanest verified gates is this, under 0.5% positive on sends is a kill, 0.5 to 1% is iterate, 1% and above is scale, 2% and above is pour. Those thresholds belong in a simple model because they force action.

Notice what this does not mean. It does not mean every account, segment, or offer should hit the same outcome at the same speed. It means your model needs predefined decision bands so a team cannot explain away weak performance forever.

The fleet baseline positive rate we use as a reference point is 0.05%. That matters because it reminds operators how far from useful a low baseline can sit. A model that assumes early outbound will naturally work is usually a model built by someone who has not had to defend spend in a review.

You also need to separate reply activity from business progress. We have one verified week on the largest account with 44,649 emails, 377 replies, and a 0.84% reply rate. Useful operationally, yes. But not enough to infer positive performance. A clean model keeps reply assumptions and positive assumptions distinct.

What should your model assume about ramp and timing?

This is where founders usually get too aggressive. If you are standing up outbound or changing channel mix, your model should reflect setup drag. Onboarding is about 21 days. Warm up takes 4 to 6 weeks. If you leave that out, quarter one plans get written as if production starts immediately. It does not.

Ramp assumptions matter beyond launch. They affect hiring timing, spend pacing, and whether a bad early week should trigger panic. A simple model should have a clear state marker for each program, not live, onboarding, warming, or stable enough to judge.

If you run a managed motion or an internal team at scale, churn also belongs in your planning layer. The verified range is 3 to 5% monthly. That is not a channel performance assumption. It is an operating assumption. It matters because retained execution capacity is part of GTM math, especially if your pipeline plan depends on continuity.

Why does show rate belong in even a simple model?

Because booked meetings flatter weak systems. Where calendar discipline is broken, booked meetings die at roughly a 50% show rate. That single assumption can change your budget decision faster than almost any top of funnel metric.

If your team counts bookings as success but half do not attend, the model should expose that failure immediately. Otherwise marketing, SDR, and founder all believe pipeline is coming while sales sees empty calendar slots and blames lead quality.

I would rather run a plain model with a tough show rate assumption than a sophisticated one that pretends all meetings happen. Honest friction is more valuable than fake precision.

Which assumptions should stay out of the first version?

Leave out anything that does not create a decision. Vanity detail is the enemy of use. Here is what I would usually exclude from version one.

• Tiny stage variations that are not stable enough to trust
• Persona level assumptions if sample sizes are thin
• Creative level assumptions unless you are actively choosing between offers
• Attribution debates across every touchpoint
• Tool level workflow metrics that never change budget or headcount decisions

This is also where I defer to sibling sites. Deep channel execution detail, like cold email mechanics or LinkedIn step design, belongs elsewhere in the Outbound Pros group. Here, the only question is whether a channel deserves more room in the model and more budget in the mix.

How often should assumptions change?

Less often than most teams think. Your operating assumptions should be reviewed weekly, but not rewritten every time performance wiggles. If the model changes with every wobble, it stops being a management tool and becomes an excuse generator.

I prefer fixed review windows. Weekly for campaign health. Monthly for conversion and show rate assumptions. Quarterly for structural assumptions like sales cycle, capacity, and channel role in the mix. That gives you enough responsiveness without destroying comparability.

The exception is kill or scale gates. Those should be active at all times. If a campaign falls under 0.5% positive on sends, you do not need another month of storytelling. You need a decision.

Where does this advice fail?

This advice fails when the business model itself is unstable. If you are changing pricing, packaging, ICP, and sales process at the same time, a simple GTM model can only tell you that everything is moving. It cannot isolate causality well.

It also fails for teams that do not enforce data definitions. If sales calls one thing pipeline, marketing calls another thing qualified, and finance trusts neither, no model will save you. The spreadsheet is not the fix. Operational alignment is.

And if you are very early, with almost no repeatable motion yet, your first model should be directional, not authoritative. You still need assumptions, but you should hold them lightly and update fast as reality arrives.

Who should not follow this rigidly. Teams running complex enterprise motions across many segments and geographies. They usually need a layered model, one simple operating model for weekly decisions, then deeper scenario models underneath. Also, pure brand or demand creation teams should not force every activity into direct response math just to make the sheet feel serious.

What does a good simple model look like in practice?

It fits on one screen. It can be explained in five minutes. Every assumption has an owner. Every owner knows what action follows when a number moves. That is the standard.

• Top section, commercial target and timing
• Middle section, conversion path and show rate reality
• Bottom section, channel capacity and kill or scale gates
• Side notes, ramp status and known constraints
• Weekly note, what changed and what action follows

A model like this does not impress analysts. Good. It is not meant to. It is meant to keep operators from funding bad channels, overtrusting weak bookings, and ignoring ramp drag.