One of the most distinctive challenges of hardware finance is the gap between when you spend money and when you earn it. Software businesses can move from idea to first revenue in weeks. Hardware businesses routinely spend 18–36 months in development before generating meaningful commercial revenue — and every one of those months requires cash to cover engineering, components, testing, certification, and team costs.

Getting the cash model right for this kind of business isn't optional. It's the difference between reaching your first commercial milestone and running out of money six weeks before you get there.

Why standard financial models fail for hardware

Most financial model templates are built around a monthly P&L with a simple cash flow bridge. For a software business that starts generating revenue quickly, this works reasonably well. For a hardware business with a multi-year development cycle, it misses most of what matters.

The critical variables for hardware cash modelling are timing-based: when exactly does each engineering milestone fall, what does it cost, and what triggers each tranche of funding? What are the payment terms with your suppliers, and how do they interact with your customer payment terms? What happens to your cash position if a component lead time extends by 8 weeks? These questions can only be answered with a model that's built explicitly around the hardware development and production cycle — not adapted from a SaaS template.

Milestone-based cash forecasting

The most useful cash models for hardware businesses are milestone-based rather than purely calendar-based. They map spending to development phases — concept, prototype, pilot production, commercial launch — and model the cash implications of hitting or missing each milestone on time. This gives you something more useful than a monthly burn rate: it gives you a conditional view of your cash position that lets you make decisions about pacing, hiring, and fundraising timing based on where you actually are in development.

Milestone-based models are also more useful in investor conversations. A hardware investor who understands the development cycle will want to know your cash position relative to key milestones, not just your monthly burn. Showing up with that kind of model signals that you understand your own business at a level of sophistication that builds confidence.

Scenario planning for hardware

Hardware development almost always takes longer and costs more than the plan. This isn't pessimism — it's the statistical reality of building physical products. A good cash model for hardware builds in explicit scenario analysis: what does the cash position look like if the first pilot production run takes an extra 10 weeks? What if a key supplier changes their minimum order quantity? What if a certification process requires an additional test cycle?

Running these scenarios in advance doesn't prevent problems — but it means you see them coming early enough to respond rather than react. The founders who manage cash best in hardware aren't the ones who forecast most accurately; they're the ones who update their model frequently and respond to deviations quickly.

When to raise, and how much

One of the most important outputs of a good hardware cash model is fundraising timing. Hardware founders frequently either raise too early — before they have enough evidence to command a good valuation — or too late, when they're raising under cash pressure and have less negotiating leverage. A clear cash model that maps your milestone timeline to your funding requirements lets you identify the optimal raise window: after a proof point that justifies a step up in valuation, but far enough ahead of cash need that you're raising from a position of strength.

The rule of thumb for hardware is to raise 12–18 months of runway, not 6–9 as is common in software. Development timelines are less predictable, and the cost of running out of cash mid-development is higher — both financially and in terms of team morale and commercial momentum.