Turn a technical milestone into a commercial forecast by mapping the dependencies from evidence to customer acceptance, contracting, delivery, invoicing and cash collection. Each dependency needs an owner, a completion test, a timing range and a financial consequence. Technical success reduces one category of risk; it does not by itself prove demand, scalable economics or the timing of revenue.
Key conclusions
- Define exactly what the technical result proves and what it does not.
- Map customer, regulatory, supply-chain, production and financing dependencies through to cash.
- Forecast revenue only when delivery and acceptance conditions can be supported.
- Model delays as connected operational scenarios, including continued cost and working-capital effects.
Technical success and commercial readiness are different
A pilot may demonstrate that a process works under controlled conditions. The next customer may require a different feedstock, duty cycle, site integration, certification, warranty or throughput. Production may require suppliers and quality systems that did not exist for the pilot.
The error is to place a “launch” date in the model and begin a smooth revenue curve immediately afterwards. The commercial forecast needs to show the sequence by which evidence becomes an accepted product or service and then becomes cash.
Build the evidence-to-cash chain
Validate
Define performance, scale, duration and operating conditions.
Qualify
Complete customer, regulatory, safety and site requirements.
Monetise
Contract, deliver, obtain acceptance, invoice and collect.
Technical evidence
Record the test protocol, target, observed result and limitation. “Pilot complete” is not sufficient if the commercial unit requires a different scale or environment.
Customer adoption
Map the decision-maker, budget cycle, procurement steps, site work, acceptance test and contract conditions. A letter of intent and a signed purchase order carry different timing and cash implications.
Delivery capability
Translate bills of material, supplier lead times, labour, yield, rework, warranty and capacity into unit economics. Early units often cost more and take longer than the steady-state case.
Cash conversion
Identify deposits, milestone payments, retention, acceptance and debtor terms. Revenue recognition and cash receipt may occur in different months.
Illustrative dependency map
| Dependency | Evidence required | Forecast consequence if late |
|---|---|---|
| Extended-duration test | 1,000 hours at target throughput | Engineering cost continues; qualification starts later |
| Customer site approval | Signed integration and safety acceptance | Delivery and deposit move |
| Critical component | Supplier slot and verified lead time | Inventory payment may precede revenue by more months |
| Performance acceptance | Contractual test passed | Final invoice and cash collection deferred |
The dependencies should enter the financial model as dates and decision rules. If the extended test is late, the model should continue relevant costs, delay downstream activities and show whether management stages hiring or orders.
Use ranges and gates
Where evidence is incomplete, use a timing range and a gated commitment. Management might authorise long-lead deposits after a defined technical result but defer production hiring until customer site approval. This makes the capital plan responsive without pretending uncertainty has disappeared.
The forecast should show the critical path: the dependency whose movement has the greatest effect on first repeatable cash. That is often more valuable than adding detail to later years.
Common mistakes
- Equating technical readiness with customer willingness to buy.
- Using the demonstration unit’s cost as the mature production cost.
- Ignoring certification, integration, procurement and acceptance periods.
- Forecasting invoiced revenue as cash without payment terms or retention.
- Assuming multiple customer projects can use the same scarce technical team simultaneously.
- Moving revenue in a downside case while leaving costs and working capital unchanged.
Management checklist
- State what each technical milestone proves and its limitations.
- Map qualification, procurement, contracting and acceptance.
- Validate supplier lead times, capacity, yield and early-unit cost.
- Connect revenue recognition to invoicing and cash collection.
- Identify the critical path and timing range.
- Gate irreversible spending to evidence.
- Model an integrated delay scenario and management response.
Related questions
What is the difference between technical and commercial readiness?
Technical readiness concerns whether the technology performs under defined conditions. Commercial readiness also requires customer acceptance, delivery capability, viable economics and a financeable route to repeatable sales.
When should forecast revenue begin?
When the model can support the sequence from customer commitment through delivery and acceptance to invoicing. A product launch date alone is not enough.
How should pilot revenue be treated?
Separate one-off funded trials or engineering income from repeatable product revenue where the economics, acceptance conditions or delivery model differ.
Why can growth increase the funding requirement?
Production deposits, inventory, labour and receivables may consume cash before customers pay. Faster orders can therefore increase working-capital needs.
Sources and scope
- Set up a cash flow statement — business.gov.au (reviewed 23 August 2026).
- Create a budget — business.gov.au (reviewed 23 August 2026).
Sources support the general principles identified above. The analysis, framework and illustrative examples are Sentinel Capital’s professional judgement.
General information only. This article does not take account of any organisation’s circumstances and is not legal, tax, investment or financial-product advice. Obtain advice from appropriately qualified advisers before acting on a financing, valuation or governance matter.