Hardware Series A rounds are larger because the money buys the ability to build repeatedly. Vatn Systems' record — $76.5M raised with a $60M Series A — shows how to size a capital-intensive round around physical milestones rather than calendar months.
Key takeaways
- Software Series A benchmarks understate what a hardware round must fund.
- Size the round around the next physical milestone plus one extra build-test loop.
- Working capital and certification are real budget lines, not footnotes.
- Separate capex from opex when presenting the ask.
- Map non-dilutive sources before setting the equity number.
Most published Series A benchmarks are drawn from software companies, where the round funds a team and a go-to-market motion. If you are building physical systems, the round has to fund tooling, materials, test cycles and a factory floor before revenue exists.
Rather than arguing the point abstractly, this works through it using a documented record: Nelson Mills of Vatn Systems (Portsmouth, Rhode Island), an autonomous underwater vehicle manufacturer.
| | | |---|---| | Founder | Nelson Mills | | Company | Vatn Systems (Portsmouth, RI) | | Total raised | $76.5M | | Latest round | Series A — $60M | | Round date | July 2026 | | Named backer on record | BVVC |
The Series A is roughly four fifths of everything raised to date. That is the signature of a hardware company: the seed proves the concept, the Series A pays for the ability to build repeatedly.
Unit economics arrive late. You cannot iterate your way to margin in a week; each learning cycle costs materials and time.
Working capital is real. Inventory, long-lead components and supplier deposits consume cash that never appears in a software plan.
Certification and testing. In defence, medical and marine systems, qualification programmes are budget lines, not footnotes.
1. Cost the next physical milestone, not the next 18 months. Hardware timelines slip; milestones are more honest than calendars. 2. Add a build-cycle buffer. Assume at least one full design-build-test loop more than your plan shows. 3. Separate capex from opex explicitly when you present. Investors underwrite them differently, and blending them makes the ask look inflated.
Raising a software-sized Series A into a hardware plan is the most common way capital-intensive companies end up bridging at bad terms.
Non-dilutive sources — government programmes, customer prepayments, equipment finance — should be mapped before you set the equity number, not after.
The record above is what is publicly documented: totals, stage, amount, date and named participants. Valuation, terms and board composition are not part of it.
Frequently asked questions
- Why are hardware Series A rounds bigger?
- Because each learning cycle costs materials and time, and inventory, long-lead components and qualification programmes consume cash long before revenue.
- How should I size the round?
- Cost the next physical milestone, add a full extra design-build-test loop as buffer, and present capex separately from opex.
- What is the most common mistake?
- Raising a software-sized round into a hardware plan, then bridging at poor terms when the first build cycle slips.
- Should I use non-dilutive funding?
- Map government programmes, customer prepayments and equipment finance before you fix the equity number — they change how much you need to sell.
- Where do the figures in this article come from?
- From the structured founder funding records we maintain: total raised, round stage, round amount, round date and named participants. They exclude valuation, deal terms and board composition.
