← Back to articles

How to Model Pre-Revenue Startups



Author: Yanni Papoutsi - Fractional VP of Finance and Strategy for early-stage startups - Author, Raise Ready Reading time: ~10 min

What Investors Are Actually Evaluating

When a VC opens a pre-revenue financial model, they are not trying to assess the accuracy of the revenue forecast. They know the numbers will be wrong. Every early-stage investor knows this. What they are assessing is the quality of the thinking. Specifically, they are asking:

Does this founder know what it costs to build the product they are describing? Does the timeline to first revenue reflect how long product development actually takes, or does it assume everything goes to plan? Have they talked to real customers, or are the pricing and conversion assumptions pulled from a blog post? Do they understand which assumptions drive the most variance in outcomes? Have they thought about what happens if the plan is wrong? A pre-revenue model that answers those questions earns credibility. One that does not answers them by omission.

The Three-Section Structure

Pre-revenue models work best when organized into three distinct sections: the cost model, the revenue model, and the milestone and runway output. These sections serve different purposes and should be built in this order. Section 1: The Cost Model

Build costs first. This is the most reliable section of any pre-revenue model because costs are largely within the founder's control. Costs also represent the strongest evidence of operational realism. A founder who has thought carefully about what it costs to build and run the business they are describing is demonstrating operational literacy. The cost model should include every category of spend with sufficient detail to be credible. Headcount is the most important line item. Build it role by role. List each hire, their planned start date, their gross salary, and the associated employer costs (national insurance, benefits, payroll taxes, and any Employer of Record fees if hiring internationally). A Romanian developer hired through an EOR carries roughly 8 to 12% employer overhead. A French employee carries 40 to 47%. A US employee varies significantly by state. These differences matter at small team sizes. Include the timing lag between the decision to hire and the point at which the person is productive. For a senior engineer, the hiring process alone typically takes eight to twelve weeks. An experienced enterprise sales hire may take three to four months to close and another three to four months to reach full productivity. Your headcount plan needs to reflect this, or your revenue ramp will be optimistic. Infrastructure and tooling costs are often underestimated. List the specific services you depend on: cloud hosting, monitoring, analytics, CRM, security tooling, product analytics. Price each one at the scale you expect to reach by the end of the forecast period, not at the current free tier. Professional services tend to surprise founders who have not raised before. Legal costs for incorporation, shareholder agreements, and option plan documentation typically run GBP 8,000 to GBP 20,000 depending on complexity and jurisdiction. Annual accounting and audit costs start at GBP 5,000 to GBP 8,000 for early-stage companies and increase with transaction volume. Go-to-market costs need a timeline. When do you start spending on sales and marketing? What are the channels? What are the expected conversion rates at each stage of the funnel? If you cannot answer these questions, the go-to-market cost section is not ready. Section 2: The Revenue Model

Revenue in a pre-revenue model is a hypothesis, and it should be labelled as one. The job of this section is not to predict revenue accurately. It is to document the specific assumptions you are making about how revenue will develop, why those assumptions are reasonable, and what the key drivers are. For a B2B SaaS company, the revenue model typically flows through a small number of connected assumptions: how many leads enter the pipeline per month, what is the conversion rate from lead to qualified opportunity, what is the conversion rate from qualified opportunity to closed deal, and what is the average contract value. Each of those four numbers should have a note explaining where it comes from. "Conversion rate from qualified opportunity to close: 25% based on conversations with two enterprise sales leads who have operated in this market, adjusted downward from a typical 30% benchmark to reflect our early-stage positioning" is a model assumption. "Conversion rate: 25%" is a placeholder. Churn and expansion should both be present even at pre-revenue stage, at minimum as flagged assumptions. You will not know your actual churn rate yet. But stating that you are assuming annual churn of 8% because comparable B2B SaaS products at this price point typically see 5 to 12% annual churn shows you have thought about it. Not modelling churn at all is a signal. If you are a marketplace business, you need to model both sides of the market. The supply-side assumptions (number of service providers, activation rate, utilization rate) drive the supply economics. The demand-side assumptions (number of customers, booking frequency, average transaction value) drive the revenue. The balance between supply and demand is the most important assumption in any marketplace model and the one most often oversimplified. Section 3: Runway and Milestones

This is the output section that investors spend the most time on. It should answer three questions directly. How long does the capital being raised last under the base case? Under the conservative case? Under the worst case? What specific milestones will be reached with this capital? Not vague descriptors ("build product," "acquire customers"), but specific and measurable outcomes: ship the core product to ten pilot customers by month eight, reach GBP 50k MRR by month fourteen, close two enterprise contracts by month sixteen. What metrics, achieved by when, create the conditions for the next fundraise? The milestone section is where founders most often underdeliver. Milestones should be tied to the cost model (these are what the capital funds) and the revenue model (these are the commercial outcomes those costs are designed to produce). A milestone document that is disconnected from the financial model is not a financial model output. It is a slide deck.

The Most Important Pre-Revenue Assumption

Time to first revenue is the single assumption that drives more variance than any other in a pre-revenue model. It determines when cash starts coming in, how long the company is fully burning without offset, and how much runway remains when the company becomes commercially active. Most pre-revenue models underestimate time to first revenue. The most common reasons are: product development takes longer than planned (software almost always does), the sales cycle is longer than assumed because the product is not yet proven, onboarding and integration for the first customers takes time that the model did not account for, and pricing conversations take longer than expected once a real dollar figure is on the table. A useful rule: take your estimated time to first revenue, apply a 30 to 40% buffer, and check whether the round you are raising still provides enough runway in that scenario. If it does not, you either need to raise more capital or run leaner until first revenue arrives.

Scenario Modeling for Pre-Revenue Companies

Every pre-revenue model needs at least three scenarios, and they need to be built from different assumption sets rather than from multiplying a single revenue number up or down. Base case: assumptions as modelled. Time to first revenue at the planned date. Hiring plan as specified. Revenue ramp as per the model. Conservative case: first revenue delayed by three to six months. Two key hires delayed or replaced with more junior alternatives. Revenue in year one at 50 to 60% of the base case. Capital efficiency case: focused on extending runway. Minimum viable headcount. Aggressive prioritization of only the activities required to reach the milestone that unlocks the next round. This scenario answers the question: if everything takes longer and costs more than planned, how long can the company survive on this capital? The question investors are asking when they look at the conservative and capital efficiency cases is not whether the business fails in those scenarios. It is whether the founder has thought about them. A founder who has only modelled the base case has only thought about the best case.

What Not to Model

Do not model revenue starting in month one unless the product already exists and customers are in active conversations. Investors who have funded pre-revenue companies know what the first six months look like. Immediate revenue signals either that the timeline is wrong or that the founder has not been honest about the current state of the product. Do not present a single revenue scenario as a forecast. At pre-revenue stage, anyone claiming precision in revenue forecasting is either not being honest or does not understand the uncertainty inherent in the exercise. Do not model headcount productivity at 100% from day one. Build in a ramp: a new sales hire who starts in month three typically contributes meaningful revenue by month six or seven, not month four. A new engineer who joins mid-sprint contributes full velocity after three to four weeks of context.

FAQ

How detailed should a pre-revenue model be?

Detailed enough to answer the core questions without false precision. A 50-row model with honest assumptions and clear notes is more fundable than a 200-row model built on inputs that cannot be defended. Build the level of detail you can actually explain and defend in a 30-minute investor conversation. Should pre-revenue models include a P&L?

Yes. Even with zero revenue, the P&L shows the cost structure and the trajectory toward breakeven. It also forces you to think about gross margin, which becomes an important assumption as soon as revenue appears in the model. How should a pre-revenue model handle taxes?

At early stage, most pre-revenue companies carry accumulated losses that fully offset any future tax liability for years. Include a tax line, assume zero tax liability for the forecast period given the accumulated deficit, and note the assumption.