Route founders by maturity, not by hype.
The point is not to spray outreach everywhere. The point is to move a founder into the one lane that best matches their score, evidence and deployment reality.
Pilot + money beats money alone
That is especially true for systems, AI infrastructure and TRL 6 / 7 style narratives.
Five practical routes
Keep fund names and contacts as internal data until you have verified relationships.
Cloud / non-dilutive
Best first route for solo founders with early product and credible usage plans.
- Fastest perceived value
- Reduces burn
- Works before equity or debt
Deeptech VC
Use when the technology and deployment story are clear enough to justify a structured capital discussion.
- Best with route to TRL 7
- Needs architecture + pilot logic
- Do not enter without proof pack
Strategic CVC
Strongest when ecosystem fit and deployment leverage matter as much as the cheque.
- Money + deployment leverage
- Tighter stack fit required
- Faster yes / no decisions
Venture debt
Useful when there is already minimal revenue, signed contracts or credible cash visibility.
- Lower dilution
- Numbers matter more than narrative
- Bad fit for zero-revenue experiments
GCC pilot capital
Best positioned as contract or pilot funding rather than generic “grant hunting”.
- Works well for security / edge / sovereign AI
- Deployment story must be crisp
- Route requires strong packaging
Service-led scale
For your own business model, this is the highest-value lane: build from TRL 4 to pilot or qualification as a paid service.
- High-ticket revenue
- Proof already exists on the platform
- Naturally linked to deal room
What each route needs
Use this table for founder education and for your internal reviewer logic.
| Route | Must-have | Nice-to-have | Stop sign |
|---|---|---|---|
| Cloud / perks | Usage plan, architecture, short product summary | Budget forecast | No credible need for infrastructure |
| Deeptech VC | Deployment path, KPI pack, target use case | Pilot target or LOI | No route to external deployment |
| CVC | Stack fit and strategic relevance | Joint deployment logic | Weak ecosystem fit |
| Debt | Revenue or contract visibility | Collections and margin clarity | Pre-revenue with no near-term contracts |
| GCC pilot capital | Deployment narrative + sovereign/edge/security angle | Regional contact and partner map | Generic consumer product story |
Simple rule set for v1
Use this before you add more complex ML-based routing.
Score under 60
Keep the founder in build mode: quests, proof pack, perks prep, no warm intros yet.
Score 60–74
Show pilot and route-prep actions. Prioritise non-dilutive perks and service-led packaging.
Score 75+
Allow curated route suggestions, manual review and deal-room packaging.
Score 85+ with proof
This is where your strongest fast-track narrative can credibly begin.