Spot the Zombillion Before It Enters the Model
A zombillion is not a number. It is the word people reach for when a forecast has outgrown its evidence but not its confidence. In a runway model, the tell is a line item labelled with a huge market size, a hockey-stick conversion rate, or a ‘conservative’ churn assumption that still ends in a vertical curve. The problem is not ambition; it is that the number cannot be traced back to a source, a cohort, or a signed contract.
Take a SaaS startup projecting 40% monthly growth for 18 months because the total addressable market is ‘enormous.’ The cause is usually a blend of anchoring on a top-down analyst figure and skipping bottom-up capacity checks. The solution is to rewrite the claim as a testable sentence: ‘We will add 12 paying teams per month from the Southampton pilot, each with a 3-seat minimum.’ That sentence can be checked against sales calls, onboarding time, and support load.
Convert Vague Scale Into Operational Units
When someone says the opportunity is a zombillion dollars, they are not sharing a number; they are sharing anxiety about scale. Replace the adjective with units the team already measures: qualified leads per week, demo-to-close rate, average contract value, and implementation hours per account. If the model needs 5,000 accounts in year one, calculate how many sales reps at 20 demos per month and a 25% close rate would be required. The arithmetic often exposes a hiring plan that nobody has approved.
This conversion also fixes the cause of most zombillion forecasts: a mismatch between market size and operating capacity. A market can be huge while the team can only onboard eight customers a month. The solution is to cap the forecast at the bottleneck, then show what investment would remove that cap.
Keep an Assumption Trail Beside Every Big Number
Write three columns next to any ambitious figure: source, owner, and expiry date. The source might be a pricing sheet, a pilot result, or a public filing. The owner is the person who will defend the number in a review. The expiry date forces a refresh after the next cohort lands. If a line has no source, mark it ‘hypothesis’ and keep it out of the cash runway. This is the simplest way to stop a zombillion from becoming a board-approved fact.
Test the Sentence Aloud Before You Present It
Read the forecast sentence to someone outside the planning team. If it sounds like ‘we will capture a zombillion of a massive market,’ rewrite it until it names a customer type, a price, a channel, and a deadline. The takeaway is not to ban big thinking. It is to make big thinking survive contact with a calendar, a budget, and a customer. A number that cannot be repeated in plain language is not a plan; it is a placeholder waiting to be replaced.
