How do I support assumptions in a pre-revenue startup financial model?

Separate signed commitments from unvalidated expectations. Label pricing, conversion and sales-cycle assumptions clearly, identify the tests that could validate them, and show how cash needs change if those assumptions fail.

What sanity checks should I run before sharing an investor model?

Check revenue against sales and delivery capacity, reconcile opening and closing cash, verify payment timing, and test whether changing major assumptions updates every affected schedule. Inspect any output that stays unchanged when its underlying driver moves.

How should I build a downside scenario?

Change specific operating inputs such as conversion, sales-cycle length, collection timing or delivery costs. Follow the impact through revenue, expenses and cash, then identify what action you would take and when.

What Makes a Financial Model Credible to Investors?

Q: What makes a financial model credible to investors?

Traceable assumptions, driver-based forecasts and reconciled cash calculations make a model easier to evaluate. Show the evidence behind each material input, label uncertainty and connect downside outcomes to specific operating decisions.

A financial model is credible to investors when its forecasts follow from identifiable business drivers, its assumptions have supporting evidence, and its cash calculations reconcile. Build revenue from customers, pricing and retention rather than a growth target, then test whether sales capacity, hiring and funding can support the result. Where evidence is missing, label the assumption and show what changes if it is wrong.

Start with assumptions someone else can inspect

Your investor model should let a reader move backward from an output to its cause. If revenue increases, which input changed: lead volume, conversion, price, retention or sales capacity?

Create an assumptions tab with a source, owner and last-updated date for each material input. Separate observed results from signed commitments and untested expectations. A signed contract and a founder's pricing hypothesis should not carry the same label.

Use your accounting records, CRM, customer contracts, payroll and collection history where available. If the business is pre-revenue, mark commercial assumptions as unvalidated and identify the test that could validate them. Do not turn an ambition into an apparent historical fact.

Build revenue from the way customers actually buy

Choose a revenue equation that matches your business. For a subscription company, reconcile opening recurring revenue with new business, expansion, contraction and churn. For a services business, connect revenue to billable capacity, utilization and realized rates.

For a sales-led startup financial model, make the acquisition chain explicit:

Qualified opportunities × win rate = expected wins, adjusted for the time needed to close.

Then connect wins to contract start dates, pricing and revenue recognition. Keep bookings, recognized revenue and cash receipts separate. Signing an annual contract does not automatically mean recognizing all its revenue or receiving its cash that month.

Check that the inputs use consistent definitions. A win rate calculated from qualified opportunities cannot be applied to every inbound lead. A forecast becomes harder to defend when the spreadsheet quietly changes the denominator.

Check growth against the capacity to deliver it

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

Connect sales hiring to start dates and ramp assumptions. Do not give a new hire full productivity before your plan expects them to reach it. If founders currently close deals, distinguish founder-led selling from the process you expect hired sellers to repeat.

Apply the same discipline after the sale. Check implementation workloads, support needs, inventory availability or delivery hours, depending on the business. Identify which constraint would force another hire or delay revenue.

The useful output is not just a higher expense line. It is a visible decision: hire earlier, limit sales commitments, change delivery or accept slower growth.

Make margin improvements explainable

Do not improve gross margin simply by typing a better percentage into a future year.

Connect direct costs to their underlying drivers: delivery hours, payment processing, product usage, hosting, materials or other costs required to serve customers. Use a consistent classification so moving an expense between categories does not masquerade as an operating improvement.

If the model assumes lower delivery costs, name the mechanism. Does onboarding require fewer hours? Does a supplier agreement change unit costs? Does pricing increase while service requirements stay unchanged?

Keep unsupported improvements visible as assumptions. Show the result without them so the funding plan does not depend on an unexplained margin gain.

Reconcile profit with cash

A profitable month and a cash-positive month are not interchangeable. Build a cash bridge that starts with opening cash, adds receipts and funding, subtracts payments, and arrives at closing cash.

Model customer payment timing separately from revenue. Include payroll dates, supplier terms, capital spending, debt payments and applicable tax payments. For businesses holding inventory, show when purchases consume cash relative to customer collections.

Run these checks before sharing the model:

Opening cash matches the previous month's closing cash.
The historical starting position reconciles to accounting records and bank balances, with differences explained.
The balance sheet balances if the model includes integrated statements.
Financing appears only on its assumed receipt date.
The model flags when cash falls below the minimum operating buffer you have explicitly chosen.

Show the cash position without the proposed raise as well. Otherwise, the funding input can conceal the shortfall you need to explain.

Stress the assumptions that change the decision

Build downside cases by changing operating drivers, not by applying an arbitrary discount to total revenue.

Test slower sales cycles, weaker conversion, delayed collections or higher delivery costs. Where inputs are connected, let the consequences flow through. A delayed customer launch can postpone revenue while implementation payroll continues.

Compare scenarios using the outputs that govern action: lowest cash balance, timing of the shortfall, funding required and milestones reached before cash becomes constrained.

Attach a response to each material downside. Which hire would you defer? Which spending commitment is already locked in? When would you need to act? A scenario becomes useful when it changes a decision rather than just a chart.

Make the investor version easy to challenge

Keep the summary focused on revenue drivers, margins, headcount, cash and funding needs. Link those outputs to the detailed schedules instead of rebuilding them manually in a presentation tab.

Before sending the financial model investors will review, change each major assumption and follow the effect. If pricing changes but receipts do not, inspect the formulas. If hiring shifts but payroll stays fixed, find the disconnected schedule. Remove unexplained hardcodes from forecast calculations.

After each close, compare actual results with the forecast at the driver level. Explain whether a miss came from volume, timing, price or cost. Update the relevant input rather than spreading the variance across future months to preserve the original target.

The goal is a model you can defend and use to make the next operating decision. If you want help identifying weak assumptions or disconnected cash logic, explore our fractional CFO services, or book a free 30-minute CFO diagnostic call to discuss where your model needs attention.