Build a path to revenue, not a target growth curve
A top-down market estimate tells you how much demand might exist. A bottom-up model asks what your team can launch, reach and serve in each month. Use the market estimate as a plausibility check, then build revenue from actions, customer behavior and capacity. A serviceable obtainable market expressed as customers or sales is not automatically the same thing as your forecast revenue; align geography, time horizon, units and price before comparing them.
Your roadmap supplies the timing: product ready, sales channel live, new region entered, team hired. Each event can switch on costs, capacity, acquisition or revenue. Moving one event should update all the dependent rows. That is what makes the financial model flexible.
Roadmap event → operating capacity and spending → customer activity → billings and revenue → costs → cash balance
Give inputs, calculations and outputs distinct jobs
The original Google Sheets model has Settings, Roadmap, Payroll, Projections, Monthly Forecast, P&L | Cash Flow | Balance, Data for Charts and Charts tabs. The same structure works in Excel. Keep dates, rates and prices in input sheets; calculate each month once in the forecast; link summary statements and charts to those calculated rows. Avoid typing a forecast value again in a report or chart.
| Part | Decision or calculation |
|---|---|
| Settings and roadmap | Currency, planning period, applicable taxes, funding dates and dated milestones |
| Payroll and projections | Roles, start events, fully loaded cost, acquisition inputs, prices and other expenses |
| Monthly forecast | Customer and revenue drivers, direct costs, payroll, operating spend and investment by month |
| Statements and charts | Profit, cash and balance checks; linked views of decisions and constraints |
Keep units and timing visible in every assumption: dollars per month, customers acquired per month, conversion per visit and cash collected in a given month. A model that mixes monthly spend with annual conversion, or orders with customers, may look precise while being wrong.
1. Turn milestones into dates other sheets can use
List each event once, give it a date and name the rows that depend on it. In the original Roadmap tab, the seed round is a reference event and later dates can be offset by a number of months. A dropdown connects those events to start dates in Payroll and Projections. EDATE can shift a base date by whole months; use a consistent month convention throughout the forecast.
Roadmap model · original workbook extract
Event date = EDATE(reference date, months after reference)
Monthly cost = IF(forecast month ≥ start month, monthly amount, 0)
If the launch slips from October to December, product revenue and launch-dependent marketing should move together. Some costs may not move: an already hired team and committed development spending can continue during the delay. Mark each row as delayed, continuing or one-time; otherwise a postponement can accidentally make the cash forecast look better.
2. Make hiring and investment follow the operating plan
For each role, record the salary, employer costs, hiring event and any later step-up. The old Payroll tab links start dates to events rather than requiring dates to be typed twice. Check the exact payroll-tax base and country rules separately; a displayed percentage does not establish the correct fully loaded employer cost for every jurisdiction.
Roadmap model · original workbook extract
In Projections, connect direct delivery costs, marketing, contractors and capital purchases to the events that cause them. Keep recurring spend separate from one-off outlays. For instance, buying a computer is a cash outflow when purchased; if it qualifies as a capital asset under your reporting rules, depreciation is a later noncash expense. Do not count both as the same month's operating expense.
3. Forecast customers from channels, conversion and price
For an app, organic and paid installs can feed activation and paid conversion; for a website, start with qualified visits; for direct sales, use leads, capacity and the sales-cycle lag. The original article uses a subscription app as its illustration. Do not treat an install or site visit as a paying customer.
Paid visits = active campaign spend ÷ cost per qualified visit
New customers = eligible visits × visit-to-paid conversion
Monthly billings = billable customers × price per customer
Separate organic activity from paid acquisition and record the work needed to earn it. If a product has recurring revenue, roll forward the opening customer base, new subscriptions and cancellations; billable customer timing must match the actual offer. Acquisition cost depends on the customers won, not just the visits or installs bought.
A planned price, conversion rate or cost per acquisition is a testable input, not evidence. Start with a range, run a small campaign or sales test, and replace the assumption with observed cohorts when you have them.
4. Connect a launch month to its cash consequence
Suppose a small subscription product spends $8,000 on development in September, launches in October, receives 1,200 qualified visits that month and converts 5% of them into 60 new paying customers. At $50 per customer, assume it both bills and collects $3,000 in October. These are illustrative inputs chosen to show the links; they are not the figures in the historical screenshots.
| Driver or cash item | September | October |
|---|---|---|
| Qualified visits / new customers | — | 1,200 / 60 |
| Customer receipts (60 × $50) | $0 | $3,000 |
| Development payment | ($8,000) | $0 |
| Delivery costs | $0 | ($600) |
| Acquisition spend | $0 | ($1,500) |
| Payroll and other operating spend | $0 | ($4,500) |
| Net monthly cash flow | ($8,000) | ($3,600) |
| Cumulative cash before funding | ($8,000) | ($11,600) |
October customers = 1,200 visits × 5% = 60
October cash flow = $3,000 − $600 − $1,500 − $4,500 = −$3,600
Cumulative cash need by October = $8,000 + $3,600 = $11,600
Here receipts and billings coincide only by assumption. A free trial, annual prepayment, delayed settlement or unpaid invoice changes cash timing and may change the period in which revenue is recognized. Model customer retention and renewals after launch instead of repeating 60 new customers forever.
5. Read profit, cash and the balance sheet separately
The Monthly Forecast should feed a management P&L, a cash-flow statement and a balance sheet. The P&L shows whether the period's recognized revenue covers its expenses. Cash flow shows when money actually arrives and leaves; financing is shown separately from operating performance. The balance sheet should reconcile assets with liabilities plus equity, with an explicit check row.
Operating cash flow is not always net income plus depreciation. Add back relevant noncash charges and adjust for receivables, payables, inventory, deferred revenue and other working-capital movements when they matter. Show capital purchases in investing cash flow and actual funding receipts in financing cash flow. Configure tax, capitalization and revenue rules for the business and jurisdiction before treating the statements as accounting outputs.
6. Test what happens when a milestone moves
Now move launch from October to December while the $8,000 development payment remains in September and the $4,500 monthly team and overhead costs continue in October and November. If the $1,500 acquisition campaign and $600 delivery costs start only at launch, there are no customer receipts during the two delayed months. The cash deficit grows by $4,500 in each month before December even begins.
Cash need at end of November = $8,000 September development + $4,500 October fixed spend + $4,500 November fixed spend = $17,000
That $17,000 is a pre-launch funding requirement under these simplified assumptions, not the total required to reach break-even. December may add another deficit. This is why a funding event should not automatically switch off existing costs. Test a slower conversion rate, a higher acquisition cost and a later cash receipt as separate scenarios, then decide what to validate or defer.
Keep charts linked to the forecast, including month labels. Show customer acquisition, revenue against operating costs and the cash low point. A chart is useful when a changed assumption visibly changes the decision, not merely when it makes the model look polished.
Use the model to choose the next milestone
A good roadmap model answers three concrete questions: which event unlocks demand or capacity; which spending must happen before that event; and how much cash is needed if it is delayed. Start with those links, test the most uncertain acquisition and retention inputs, and update the forecast with actual results every month. The useful output is a decision about sequencing, spending and funding—not a single attractive break-even date.