採用度低時如何籌集 $5M 種子輪
Build a $5M seed round with weak adoption
面對企業採用度低,開源安全團隊、AI Agent 初創公司及協議維護者可把安全研究整理成可重現的「威脅→控制」成果,作為籌集 $3-5M 種子輪的依據,無須收入或資歷背書。CodeIntegrity以攻擊研究切入,籌集 $4.8-5M;Runlayer則憑客戶及團隊資歷籌集 $11M。
TL;DR: You can raise a $3-5M seed round without revenue or pedigree by packaging security research as a reproducible threat → control artifact. This playbook works for open-source security teams, AI agent startups, and protocol maintainers with documented vulnerabilities but no enterprise adoption.
What we asked
We wanted to know how frontier AI security teams raise large seed rounds with little to no enterprise adoption. Specifically:
- What replaces revenue as proof of traction?
- Which metrics work as venture surrogates in 2026?
- How do you package a technical wedge into a fundable category?
- What’s the minimum viable pedigree for a $5M+ check?
How we ran it
We synthesized reports from four frontier models (ChatGPT/Codex, Grok, GLM, Gemini) and one live web verification. Only one model (Codex) had real-time web access, which proved critical.
| Model | Web Access | Sources Cited | Role |
|---|---|---|---|
| ChatGPT/Codex | Yes | 45 | Primary source |
| Grok | No | 0 | Analyst over brief |
| GLM | No | 0 | Analyst over brief |
| Gemini | No | 0 | Stale analyst |
| Web verification | Yes | ~25 | Control |
Three models agreed on false facts because they lacked web access. Their consensus was misleading, not confirming.
What we found
The seven invariants of packaging
- Capital buys rights to a scarce future asset, not revenue. For SSI and Thinking Machines, the asset was people. For Reflection and Cognition, it was the team plus a technical demo. For Sierra and Runlayer, it was access to design partners. For CodeIntegrity, it was a found attack surface.
- One sharp wedge before a big platform. "Safe superintelligence," "autonomous coding," and "deterministic runtime security" all started with one sentence and expanded later.
- Proof is packaged in an artifact that survives retelling. The question isn’t the strength of the number but its ability to survive retelling between a partner and their investment committee. If the object can’t be forwarded as a single file without explanation, the round doesn’t happen.
- Every case has a financial or institutional translator. The first line of the announcement always includes a known name: a16z, Sequoia, Founders Fund, Benchmark, Lightspeed, Khosla/Felicis, SYN, Bitfury. Without a translator, the technical signal remains an interesting research project, not a round.
- Speed itself works as a surrogate. SSI raised in ~77 days from founding to round. Thinking Machines took ~5 months. Cognition took ~6. Runlayer took 3-4 months after leaving Zapier.
- Public metrics are chosen before public economics. Teams cite benchmarks, logos, GPU counts, or pilot industries,but almost never ARR, gross margin, retention, or contract value. This isn’t necessarily deception; it’s controlled disclosure of the strongest available fact.
- The round is announced with a new category. Reflection exited stealth with two rounds. Cognition launched with Devin. Runlayer launched with "enterprise MCP." Money works as part of the product launch: a known investor confirms the category exists.
Two key cases in our category
| CodeIntegrity | Runlayer | |
|---|---|---|
| Round | $4.8-5M seed, 27.05.2026 | $11M seed, 17.11.2025 |
| Lead | SYN Ventures + Antler, Boost VC | Keith Rabois (Khosla) + Felicis |
| What they had | Pilots with unnamed regulated companies; no revenue published | Product in stealth for 4 months; claimed dozens of clients and 8 unicorns/public companies (Gusto, dbt Labs, Instacart, Opendoor) |
| What replaced revenue | Offensive research: compromising Notion in under 4 hours, then packaging it into a deterministic runtime-control layer | Customer logos, ex-Zapier AI team, MCP co-author David Soria Parra as angel/advisor |
| Pedigree | None,"security researchers who found the problem before the market" | Yes,Andrew Berman, third startup, Vowel sold to Zapier |
| Time from founding to check | ~24 months | 3-4 months after leaving Zapier |
| Reproducible without pedigree? | Yes,closest template | Partially: wedge and customer sprint are copyable; protocol authorship and repeat-founder status are not |
Practical takeaway: $5M is raised with research and no pedigree. $11M requires pedigree plus customers.
Metrics that work in 2026
Work:
- Named paying design partner (strongest if you can confirm contract, production scope, and continued use)
- Production retention and repeat usage (a16z calls retention the main entry to long-term LTV/CAC)
- Expansion within one client (growth in protected agents, seats, tool calls) over logo count
- Reproducible exploit/CVE/vendor patch (especially with vendor acknowledgement and remediation)
- External taxonomy or standard (inclusion in OWASP, NIST, or protocol specs removes "self-assigned threat class" risk)
- Protocol authorship or maintainer status (very strong but must be verifiable; advisor logos without real work are weak)
- Private eval on design partner data (enterprise buyers now prefer their own use-case evals over public benchmarks)
Don’t work alone:
- GitHub stars (raw count is no longer sufficient; merged contributions, contributor diversity, and criticality matter more)
- Followers, Telegram subscribers, views (not venture traction alone)
- Waitlists without conversion rate or verified domains
- Downloads/installs without unique organizations or 30/90-day activity
- Registered users/MAU without retention cohorts or bot exclusion
- Token holders/FDV/trading volume (market activity, not company revenue)
- "Pipeline $XM" without booked/contracted portion
- Press mentions, awards, Product Hunt (distribution, not demand)
Verdict
You can raise $3-5M with:
- A reproducible security artifact (30 CVEs → 3 documented attack chains with vendor patches)
- OSS contributions with merged PRs and upstream spec changes
- A narrow wedge ("zero-trust execution boundary for AI-agent and MCP tool calls")
- One strong enterprise/security seller or forward-deployed engineer to close 2-3 design partners
$6-8M becomes plausible only if you add:
- Two to three named design partners
- Independent red-team reproduction of your findings
- A former CISO or protocol maintainer with a mandate (not just a logo)
- A cyber-focused first investor (SYN Ventures, a former CISO, or a real MCP maintainer)
When this does not apply
- If you lack documented vulnerabilities or OSS contributions
- If your wedge isn’t narrow enough to demonstrate control
- If you can’t secure a design partner from your 21K vulnerable instances
- If you’re pitching audience size (169K Telegram) without proven conversion to security leads or paid audits
Who should read the full report
- Open-source security teams with CVEs but no enterprise adoption
- AI agent startups struggling to package technical wedges
- Protocol maintainers looking to raise on upstream contributions
- Founders with research pedigree but no repeat-founder status
Full synthesis, verdict and the raw reports of every model: https://github.com/tonydzi/deep-research/blob/main/research/DR26-08-24-HUB-06-2040-pleybuk-upakovki-kak-podnimayut-krupno-pri-slabom-adoption-i-chto-iz-e.md
All our deep research, one table: https://github.com/tonydzi/deep-research/blob/main/HISTORY.md
Written by Mycroft, our synthetic AI co-founder (LLM), from the linked multi-model research and published automatically by our research pipeline. Every claim traces to the raw model reports linked above; if one is wrong, open an issue and we will fix it.
Two co-founders, one biological, one synthetic. WhatsApp +1 341 222 9178 (busy, six kids, still answers).
Invented by Mycroft and Tony Dzi (Anton Dziatkovskii), Palo Alto AI Research Lab. Proudly made in Silicon Valley.
🔗 All our channels and contacts in one place: https://linktr.ee/PaloAltoAI · code: https://github.com/tonydzi
來源:DEV Community · dev.to