Deeptech funding stages should be planned around technical maturity, evidence, and adoption risk, not only round names like pre-seed, seed, and Series A. A useful roadmap maps each milestone to the right mix of grants, SBIR/STTR, pilots, strategic customers, EIC-style funding, and VC.
Software funding stages often follow product and revenue growth. Deeptech funding stages follow risk reduction: can the science work, can it be engineered, can it be demonstrated, can customers adopt it, and can the company scale it?
This roadmap connects the grant search process in how to find startup grants with the funding choice logic in non-dilutive funding vs VC.
Not just rounds
A deeptech founder should ask: what risk does the next dollar retire? If the answer is technical risk, a grant may fit. If the answer is market speed, VC may fit. If the answer is deployment proof, a pilot or strategic partner may fit.
This is where generic startup funding advice breaks. A software company may be able to move from prototype to traction with a small team and cloud infrastructure. A deeptech company may need lab access, specialist materials, certification, safety testing, hardware iterations, clinical or field validation, manufacturing partners, or regulated deployment before revenue becomes meaningful.
That does not mean deeptech companies should avoid VC. It means VC should be timed against evidence. If equity money is used before technical risk is reduced, founders may give up too much ownership for a milestone that grant or customer funding could have supported. If grants are used after the market window is open, the company may move too slowly.
The roadmap should therefore start with risk, not with round labels. Pre-seed, seed, and Series A mean different things in different markets. A robotics company at seed may still be proving field reliability. A biology tools company at seed may be validating reproducibility. An AI infrastructure company at seed may already be selling. Round names are shorthand; evidence is the operating reality.
This is also why copying another company's funding path is dangerous. Two companies can both be "deeptech" and still require completely different capital sequences. One may need university translational funding and STTR before it can incorporate the right IP. Another may need a paid pilot before any grant makes sense. Another may need VC early because the market is moving faster than public funding cycles.
Roadmap
| Stage | Typical evidence | Useful funding |
|---|---|---|
| Lab proof | Scientific principle, early data, founder expertise. | Research grants, STTR, university translation funding. |
| Prototype | Working prototype, early test plan, technical risk map. | SBIR/STTR, NSF Seed Fund, feasibility grants. |
| Validation | Benchmarks, user or customer feedback, regulatory path, pilot design. | Demonstration grants, EIC-style funding, customer pilots. |
| First deployment | Operational proof, partner commitment, deployment economics. | Strategic customers, contracts, blended finance, seed/Series A. |
| Scale | Repeatable production, sales motion, margins, quality systems. | VC, debt, project finance, scale-up grants. |
The roadmap should be built backwards from the next fundable milestone. A fundable milestone is not a vague achievement like "improve prototype." It is a specific evidence point: demonstrate continuous operation for 100 hours, validate sensitivity against a benchmark, complete a pilot with a named partner, achieve a regulatory pre-submission step, reduce unit cost below a target, or prove manufacturability in a relevant environment.
A good roadmap also shows the company what not to fund yet. If the current bottleneck is technical validation, money spent on broad sales hiring may be premature. If the bottleneck is customer adoption, another lab-only experiment may not change the story. If the bottleneck is manufacturability, a beautiful prototype may not be enough. The roadmap should force those tradeoffs into the open.
Evidence milestones
Every funding stage should produce evidence that makes the next funding source easier to secure.
| Evidence type | What it proves | Who cares |
|---|---|---|
| Bench data | The core mechanism works under controlled conditions. | Grant reviewers, technical advisors, early investors. |
| Relevant-environment test | The technology survives conditions closer to real use. | Demonstration funders, customers, strategic partners. |
| Pilot result | The system can create value in a customer or field setting. | Customers, VC, procurement teams, scale-up funders. |
| Regulatory or standards evidence | The path to approval or compliance is credible. | Health, energy, aerospace, climate, and industrial buyers. |
| Manufacturing evidence | The technology can be produced repeatedly and economically. | VC, strategic partners, project finance, scale-up grants. |
A strong roadmap does not treat all evidence equally. Early technical data may unlock a feasibility grant, but it may not unlock a growth round. A pilot letter may impress investors, but it may not satisfy a funder that needs a clear R&D work plan. The roadmap should show which evidence matters to which capital source.
Founders should describe each milestone in the language of the next audience. A grant reviewer may care that the experiment reduces uncertainty against a public funding priority. A customer may care that the result proves uptime, accuracy, safety, or integration effort. An investor may care that the milestone changes valuation, speed, or defensibility. The same technical result can support all three stories, but only if it is captured intentionally.
This is where many roadmaps break. Teams run good technical work but do not collect the evidence future funders need. They test a prototype but fail to document conditions. They run a pilot but do not capture customer workflow data. They speak to buyers but do not turn that into letters, quotes, or adoption criteria. A funding roadmap should define the evidence artifact, not only the activity.
Funding by stage
| Funding type | Best stage | Why |
|---|---|---|
| SBIR/STTR | Prototype and R&D validation | Designed for small business R&D and technical risk reduction. |
| NSF Seed Fund | Early-stage deep technology | Supports startup R&D and takes zero equity. |
| EIC Accelerator | Higher-maturity innovation and scale-up | Targets startups and SMEs developing and scaling innovations, often around TRL 6-8. |
| Pilots and contracts | Validation and first deployment | Creates customer evidence and real-world constraints. |
| VC | Scale and market capture | Funds speed, hiring, commercial expansion, and larger capital needs. |
TRL is one way to describe technical maturity. For a deeper guide, use the TRL levels for founders article.
Do not force a company into one funding lane. A climate hardware startup, for example, might use an early R&D grant for lab validation, a customer pilot for field data, a strategic partner for manufacturing access, and VC for team growth after the adoption story is credible. A biotech tools company might need SBIR-style R&D support, regulatory planning, and specialist investors in a different order.
Each funding type should have a job. Grants should not be used as a generic runway substitute unless the funded work is truly aligned. Pilots should not be treated as sales proof unless they include success criteria, customer commitment, and a path to follow-on adoption. VC should not be used to brute-force a technical milestone that would be better solved through focused R&D funding. The roadmap should explain why each source belongs.
Geography
Funding roadmaps are geographic. The same technology may have a US SBIR path, a UK Innovate UK path, an EU EIC path, and an international Eurostars path, but the eligibility and timing will differ.
This matters for companies with distributed founders, subsidiaries, university origins, or cross-border pilots. A grant may require the applicant to be incorporated in a specific country, perform work locally, include an SME, or build a consortium. A funding roadmap should list where the company can legally apply today and what entity or partner structure would be needed later.
| Geography question | Why it matters | Roadmap action |
|---|---|---|
| Where is the applicant registered? | Many grants require a local company or eligible SME. | Map eligible jurisdictions before searching calls. |
| Where will the work happen? | Some funders require project activity, spending, or impact in-region. | Separate technical work location from customer location. |
| Do you need partners? | Collaborative R&D schemes may require consortium structure. | Start partner development before the call deadline. |
| Can grant and VC entities coexist? | Investors may fund one entity while grants require another. | Clarify IP, transfer, and contracting assumptions early. |
Geography can also affect sequencing. A US company eligible for SBIR may have a different path from a European SME eligible for EIC or national innovation grants. A UK company may need to think about Innovate UK categories and collaboration rules. A company with a US parent and European subsidiary may have to decide which entity owns the funded work, IP, and customer contracts before applying.
The practical move is to add an entity column to the roadmap. For each funding option, state which legal entity can apply, where the work must happen, whether partners are required, and whether IP or revenue assumptions create conflicts. That prevents the team from finding a perfect-looking call that the company cannot actually use.
Bad timing
| Mistake | What happens | Better move |
|---|---|---|
| Raising VC before technical risk is reduced | Dilution is high and investor conviction may be low. | Use non-dilutive funding to generate evidence first. |
| Applying for scale-up grants too early | Reviewers expect readiness you cannot show. | Target feasibility or prototype funding. |
| Using grants for commercial gaps | The project may be outside eligible R&D scope. | Use customers, strategic partners, or VC for market execution. |
| Ignoring budget realism | The roadmap looks disconnected from actual work. | Use the grant budget template when costs become the blocker. |
Bad timing is not always obvious in the moment. A founder may feel productive because applications are being submitted, investor calls are happening, or pilots are being discussed. The test is whether each activity improves the next strategic decision. If an activity consumes focus without changing evidence, runway, adoption, or financing terms, it may be motion rather than progress.
A roadmap should include kill criteria. If a call requires a partner that cannot commit, reject it. If a VC round would close on terms that prevent the next technical milestone from being funded properly, reconsider timing. If a pilot would monopolize engineering time without generating reusable evidence, renegotiate scope. Strategy includes saying no early enough to protect the real path.
Build roadmap
- Write the current TRL and the next evidence milestone.
- List the technical, regulatory, market, and team risks.
- Match each risk to a funding type.
- Sequence grants, pilots, and VC so each one improves the next ask.
- Review the roadmap monthly as calls, evidence, and runway change.
The roadmap should be a working operating document, not a fundraising slide. Add dates, owners, dependencies, expected cost, likely funders, and evidence outputs. If a milestone does not change the next funding conversation, it may be a task rather than a strategic milestone.
A useful test: after each planned funding step, write the sentence you hope to be able to say. For example, "we validated performance in a relevant environment," "we completed a paid pilot," or "we reduced manufacturing cost by 40%." If the sentence is not stronger than what you can say today, the roadmap needs work.
Examples
A roadmap becomes useful when it is specific to the company type. The same pre-seed label can mean completely different things for a bio platform, a climate hardware company, an AI infrastructure company, or an advanced materials spinout. Each has a different evidence bottleneck.
| Company | Early roadmap | Later roadmap |
|---|---|---|
| Bio tools startup | Research grant or SBIR for assay validation, then pilot with a lab or clinical partner. | Specialist seed/Series A after reproducibility, workflow fit, and regulatory path are clearer. |
| Climate hardware company | Prototype grant, materials testing, field-relevant validation, and customer discovery. | Demonstration funding, strategic industrial partner, then scale capital. |
| AI infrastructure startup | Smaller non-dilutive support may help with benchmarks or public-sector pilots. | VC often matters earlier if the market is moving quickly and technical capex is lower. |
| Advanced materials spinout | STTR or translational grant for lab-to-prototype movement and IP de-risking. | Pilot manufacturing partner and strategic capital after repeatability is proven. |
| Dual-use robotics company | SBIR/DOD-style topic fit, prototype testing, and mission-owner feedback. | Contracts, pilots, and VC once deployment use cases are validated. |
The roadmap should also show what the company will not do yet. A founder may decide not to raise institutional VC until a prototype reaches a relevant environment. Another may decide not to pursue a large consortium grant until partner roles are clear. These negative decisions are part of the strategy; they prevent the team from chasing every source of capital at once.
In practice, the roadmap should sit next to the company operating plan. If the technical team changes a validation milestone, the funding plan should change. If a customer pilot appears earlier than expected, the grant shortlist should be re-ranked. If runway shortens, the team may need a faster but more dilutive option. Funding strategy is not separate from company building.
Operating cadence
A funding roadmap should be reviewed on a cadence, not only when cash is running out.
The best time to prepare for a grant, pilot, or financing round is usually before the opportunity is urgent. Grant calls have deadlines. Investors need evidence. Strategic partners need internal alignment. If the company waits until runway is short, every option becomes worse: the team writes weaker grants, accepts poorer investment terms, or chooses pilots that do not support the long-term roadmap.
| Cadence | Roadmap review | Decision output |
|---|---|---|
| Weekly | Check active grant deadlines, partner dependencies, and work-package progress. | Immediate actions: submit, reject, ask funder, chase partner, adjust scope. |
| Monthly | Re-rank funding options against evidence, runway, TRL, and commercial signals. | Updated top 3 funding moves. |
| Quarterly | Review whether the company is still pursuing the right capital sequence. | Roadmap reset: grant-first, pilot-first, VC-first, or hybrid. |
| After each technical result | Ask which funding conversations become easier or harder. | New claims, new evidence gaps, and changed investor/funder narrative. |
The cadence keeps the roadmap honest. A grant that looked perfect three months ago may become irrelevant after a pilot opportunity appears. A VC round that looked premature may become realistic after a validation result. A technical delay may mean the next grant should fund risk reduction rather than scale-up.
This is also how the roadmap becomes useful to the team. Engineers can see why a test matters. Business leads can see which customer evidence changes the funding story. Founders can explain to investors why they are taking non-dilutive funding now without looking like they are avoiding commercial discipline.
For board or advisor discussions, keep the roadmap to one page but keep the underlying detail alive. The top page should show current maturity, next evidence milestone, top funding options, deadline windows, and decision gates. The detail underneath should include call notes, partner status, budget assumptions, and evidence gaps. That gives leadership a clear view without turning funding strategy into a spreadsheet nobody reads.
The roadmap should become more selective over time. Early on, a wide scan is useful because the company is learning what funders value. Later, the best teams narrow their focus to the few funding paths that match their evidence, geography, and market timing. The goal is not to apply everywhere. The goal is to make each funding step make the next one easier.