How Do You Forecast Revenue When You Have No History?

To forecast revenue with no history, build a bottom-up financial model from reachable buyers, expected conversions, selling prices and the timing of delivery. Tie each assumption to evidence you can inspect, such as signed orders, live opportunities, price tests or available delivery capacity. Use separate scenarios for unresolved assumptions, and keep revenue recognition separate from cash collection.

Start with the sale, not the market size

Your addressable market does not tell you what you can sell next month. Neither does a fundraising target divided by your price.

Start with one question: What must happen for a customer to generate revenue?

For a consulting business, that might mean a qualified conversation, a proposal, a signed contract and delivery. For a subscription product, it might mean a signup, activation, paid conversion and continued use.

Write that sequence down before opening a spreadsheet. Your revenue forecast should follow it. If the model jumps straight from marketing spend to revenue, it hides the steps you need to test.

Choose a bottom-up revenue formula

Use a formula that matches how customers buy. Separate revenue streams when their sales process, pricing or delivery requirements differ.

Subscription businesses

Track customers by their expected paid start month:

Ending paid customers = opening paid customers + new paid customers − customers lost

Calculate revenue using the service period and applicable subscription price. Account for partial periods, discounts and different plans where relevant. Do not treat every customer added during a month as a full month of revenue automatically.

Services businesses

Start with work you can sell and deliver:

Billable revenue = delivered billable units × realized price per unit

Check the result against available delivery hours or project slots. Signed work that cannot begin yet belongs in the backlog, not automatically in current-month revenue. Confirm the appropriate recognition treatment for project contracts.

Product businesses

Use:

Product revenue = units sold × net selling price

Define net selling price consistently, including applicable discounts and returns. Check whether inventory availability and fulfillment dates support the sales schedule.

Build an assumption register with evidence

Put assumptions on a dedicated tab in your financial model. For each input, record its source, owner and next review date.

Keep three categories visibly separate:

• Committed inputs: signed orders, agreed prices and contractual start dates.
• Observed inputs: actual inquiries, proposal outcomes, price-test responses and measured delivery time.
• Untested inputs: expected conversion, future channel performance and retention before customers have renewed.

Committed inputs still need scrutiny. A cancellable order or conditional launch date is not unconditional revenue.

When an input has no evidence, label it as an assumption. Do not dress it up as an industry benchmark. Decide what would validate it: a paid pilot, a completed buying process or a renewal decision.

The register makes uncertainty actionable. Instead of debating whether the forecast feels ambitious, you can identify the assumption that needs testing next.

Forecast customer acquisition by channel

Give each acquisition channel its own schedule. Founder referrals, outbound sales and paid acquisition should not share one conversion assumption simply because they lead to the same product.

For a sales-led channel, model:

Reachable prospects × qualification rate × close rate = expected new customers

Define each stage precisely. A prospect on a contact list is not a qualified opportunity. An interested contact is not necessarily someone with budget or purchasing authority.

Then add timing. Prospects contacted this month should close in the month supported by their buying process, not automatically in the same period.

For a small number of active opportunities, forecast account by account. Record the potential contract value, remaining approval steps, expected signature date and delivery start. Avoid turning a few uncertain deals into smooth, supposedly dependable revenue through arbitrary probability weights.

Put capacity limits into the model

A forecast can calculate correctly and still describe an impossible operating plan.

Check who will sell, onboard and deliver. If the founder owns all three, do not allocate the same working hours to each activity. If growth requires another employee, connect added capacity to an achievable hiring and onboarding schedule.

Watch for these mismatches:

• Customer starts exceed onboarding capacity.
• Billable work exceeds available delivery hours.
• Unit sales exceed available stock.
• Sales activity assumes a hire is productive before joining.

When a constraint appears, change the revenue schedule or fund the capacity required. Do not leave the constraint in a footnote while keeping the revenue unchanged.

Separate revenue, bookings and cash

Keep distinct schedules for signed business, recognized revenue, invoicing and collections.

An annual subscription paid upfront does not necessarily become revenue immediately. A deposit can improve cash before work is delivered. An invoice issued after delivery can leave you funding operations while waiting for payment.

For each revenue stream, document contract timing, delivery obligations, billing terms and expected collection timing. Have your accountant confirm the recognition policy rather than using invoice dates as a shortcut.

This separation connects the revenue forecast to runway. It shows whether the operating plan needs financing before customer cash arrives.

Build scenarios around specific uncertainties

Do not create a downside case by cutting every revenue line by an arbitrary percentage. Change the drivers that are genuinely uncertain.

A downside case might move an unsigned contract to a later start date or delay an unproven acquisition channel. An upside case might include additional demand, but only alongside the capacity needed to serve it.

Keep contractual prices and other established inputs unchanged unless there is a reason to change them. Each scenario should explain what happened operationally and what decision follows – such as postponing a hire or reducing a spending commitment.

Replace assumptions as evidence arrives

At each monthly close, compare actual results with the forecast by driver: customer starts, conversion, price, delivery timing and customer losses where applicable.

Separate timing differences from lost demand. A delayed contract needs a revised start date. A rejected offer may require a different price, proposition or acquisition assumption.

Preserve the original forecast so you can see where judgment improved. Update future periods with new evidence rather than rewriting past expectations.

If you need help connecting these drivers to hiring, spending and runway, explore our fractional CFO services. You can also book a free 30-minute CFO diagnostic call to discuss which assumptions your revenue forecast needs to test first.