GRA-3541: devtool/AI-infra investor target list (10) with personal hooks#286
GRA-3541: devtool/AI-infra investor target list (10) with personal hooks#286Gradata wants to merge 1 commit into
Conversation
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
📝 Walkthrough
Note: No breaking changes, security fixes, or public API modifications (documentation-only change) WalkthroughAdds a new documentation file ChangesInvestor Outreach Target Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/fundability/devtool-investor-targets.md`:
- Around line 123-134: The "Outreach priority (by fit x reachability)" section
lists investors in order but provides no documented scoring or weighting
methodology, making future updates subjective and inconsistent. Add a simple
scoring system next to each target entry (for example, numeric scores for "fit"
and "reachability" factors, or a combined priority score) so that the ranking
becomes reproducible and maintainable as the document is updated over time.
- Around line 25-119: Add provenance and verification metadata to each investor
profile (Sarah Guo, Elad Gil, Martin Casado, Astasia Myers, Ed Sim, Guillermo
Rauch, Amjad Masad, Shawn Wang, Jon Sakoda, Tim Chen) to create an auditable
trail and prevent information drift. For each profile, include a source field
documenting where the information came from (e.g., public research, founder
intro, announcement, Twitter activity) and a verified-on date indicating when
the facts were last confirmed. This can be added as a footer line under each
numbered section or as a structured field within each profile block.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 8fb9e2eb-20ca-43cf-a7ed-0adbdf584373
📒 Files selected for processing (1)
docs/fundability/devtool-investor-targets.md
📜 Review details
⏰ Context from checks skipped due to timeout. (6)
- GitHub Check: pytest macos-latest / py3.11
- GitHub Check: pytest macos-latest / py3.12
- GitHub Check: pytest ubuntu-latest / py3.12
- GitHub Check: pytest windows-latest / py3.12
- GitHub Check: pytest ubuntu-latest / py3.11
- GitHub Check: pytest windows-latest / py3.11
🧰 Additional context used
🪛 markdownlint-cli2 (0.22.1)
docs/fundability/devtool-investor-targets.md
[warning] 7-7: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 25-25: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 36-36: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 46-46: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 57-57: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 67-67: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 76-76: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 85-85: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 94-94: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 103-103: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 112-112: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 123-123: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 135-135: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
| ### 1. Sarah Guo — Conviction | ||
| - Stage fit: Pre-seed / seed lead. AI-first fund, explicitly agent-infra. | ||
| - Why us: Conviction's "Software 3.0" thesis is about the new infra layer | ||
| under autonomous agents. Memory/state is the most-cited missing piece. | ||
| - Personal hook: She co-hosts No Priors and repeatedly frames "agent | ||
| memory" as unsolved. Lead with a concrete demo: same correction taught | ||
| once in Claude Code, recalled automatically in Cursor. | ||
| - Intro path: No Priors guest network; YC S26 partner intro; warm via any | ||
| Conviction portfolio founder in dev tooling. | ||
| - Verify: confirm Conviction is actively writing pre-seed checks this cycle. | ||
|
|
||
| ### 2. Elad Gil — solo investor | ||
| - Stage fit: Seed through growth; writes early conviction checks solo. | ||
| - Why us: Has written extensively on AI agent infrastructure gaps and the | ||
| "state/memory layer" being underbuilt. | ||
| - Personal hook: Reference his public posts on agent durability/memory — | ||
| position Gradata as the persistence layer that makes agents compound. | ||
| - Intro path: Founder referral; he is responsive to crisp cold emails with | ||
| a working demo + traction number (WAU). | ||
| - Verify: current check size appetite for pre-seed devtools. | ||
|
|
||
| ### 3. Martin Casado — a16z (infra) | ||
| - Stage fit: Seed/Series A; infra + devtools partner. | ||
| - Why us: His central question is "do AI startups have a durable moat?" | ||
| Gradata's answer: a compounding, user-owned procedural-memory graph that | ||
| improves with every correction — a workflow/data moat, not a model moat. | ||
| - Personal hook: Frame directly against his "no moat" essay — we ARE the | ||
| moat layer that sits above interchangeable models/agents. | ||
| - Intro path: a16z infra scout network; warm intro from a16z portfolio | ||
| devtool founder. | ||
| - Verify: a16z's current early-stage infra mandate / minimum traction bar. | ||
|
|
||
| ### 4. Astasia Myers — Felicis | ||
| - Stage fit: Seed lead; data/AI infra and developer tools focus. | ||
| - Why us: She publishes on the emerging AI memory / agent-infra stack and | ||
| tracks the category closely. | ||
| - Personal hook: Cite her memory/agent-infra market maps; offer Gradata as | ||
| a concrete cross-agent instance of the category she's mapping. | ||
| - Intro path: Her published research threads invite inbound; founder warm | ||
| intro preferred. | ||
| - Verify: confirm she still leads seed at Felicis and category is in-thesis. | ||
|
|
||
| ### 5. Ed Sim — Boldstart Ventures | ||
| - Stage fit: Inception / pre-seed lead. Dev-first, infra-first by design. | ||
| - Why us: Boldstart is the canonical "first check into dev tools" fund; | ||
| bottoms-up, developer-adopted infra is the entire portfolio shape. | ||
| - Personal hook: Gradata is bottoms-up devtool adoption (OSS install, WAU | ||
| growth) — exactly Boldstart's inception pattern. Lead with adoption curve. | ||
| - Intro path: Boldstart founder network; Ed is active on X around dev infra. | ||
| - Verify: current inception check size and OSS-traction expectations. | ||
|
|
||
| ### 6. Guillermo Rauch — Vercel (angel) | ||
| - Stage fit: Angel / pre-seed. | ||
| - Why us: Obsessive about developer experience and AI SDK ergonomics. | ||
| Gradata is a DX upgrade for anyone building or using coding agents. | ||
| - Personal hook: Pitch the DX story — no more hand-maintained CLAUDE.md; | ||
| memory just works across tools. Speaks his language (zero-config, lazy). | ||
| - Intro path: Vercel/Next.js community; AI SDK contributors; X DM with demo. | ||
| - Verify: whether he's actively angel-investing this cycle. | ||
|
|
||
| ### 7. Amjad Masad — Replit (angel) | ||
| - Stage fit: Angel / strategic. | ||
| - Why us: Replit Agent needs durable, portable memory; he understands the | ||
| agent-memory pain at production scale. | ||
| - Personal hook: Position cross-agent procedural memory as the layer Replit | ||
| Agent (and every agent) lacks — portability is the unlock. | ||
| - Intro path: Replit community; X; AI-engineering events. | ||
| - Verify: angel vs strategic-only; potential competitive-overlap concerns. | ||
|
|
||
| ### 8. Shawn "swyx" Wang — Latent Space / smol (angel + distribution) | ||
| - Stage fit: Angel + massive AI-engineering distribution. | ||
| - Why us: Latent Space and the AI Engineer community ARE the early-adopter | ||
| channel for an agent-memory tool. Angel + audience = WAU accelerant. | ||
| - Personal hook: Procedural memory / agent state is a recurring Latent Space | ||
| topic — offer a deep-dive writeup + demo for the pod/newsletter. | ||
| - Intro path: Latent Space Discord; AI Engineer conf; direct DM. | ||
| - Verify: angel check availability; treat primarily as distribution if not. | ||
|
|
||
| ### 9. Jon Sakoda — Decibel Partners | ||
| - Stage fit: Seed / Series A; enterprise dev + infra. | ||
| - Why us: Decibel is built around developer-led, infra-first companies and | ||
| the path from OSS adoption to enterprise. | ||
| - Personal hook: Show the OSS -> team -> enterprise wedge: individual devs | ||
| adopt free, teams want shared/governed procedural memory. | ||
| - Intro path: Decibel founder network; Cisco/enterprise infra alumni. | ||
| - Verify: current seed appetite vs Series A focus. | ||
|
|
||
| ### 10. Tim Chen — Essence VC | ||
| - Stage fit: Pre-seed / seed; open-source infra specialist. | ||
| - Why us: Essence focuses on commercializing open-source infra — Gradata's | ||
| OSS-first, cross-agent core is squarely in thesis. | ||
| - Personal hook: Lead with the OSS adoption metric and the monetization | ||
| path (hosted memory / team governance) — Essence's exact pattern. | ||
| - Intro path: OSS maintainer network; Essence portfolio founder intro. | ||
| - Verify: fund cycle status; current OSS-infra check size. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win
Add per-target provenance and last-verified dates.
The profiles still read like current facts (firm, stage, check size, angel activity) with no source trail. A per-row source/verified-on field would keep this doc from drifting and make the outreach notes auditable.
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 25-25: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 36-36: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 46-46: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 57-57: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 67-67: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 76-76: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 85-85: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 94-94: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 103-103: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 112-112: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/fundability/devtool-investor-targets.md` around lines 25 - 119, Add
provenance and verification metadata to each investor profile (Sarah Guo, Elad
Gil, Martin Casado, Astasia Myers, Ed Sim, Guillermo Rauch, Amjad Masad, Shawn
Wang, Jon Sakoda, Tim Chen) to create an auditable trail and prevent information
drift. For each profile, include a source field documenting where the
information came from (e.g., public research, founder intro, announcement,
Twitter activity) and a verified-on date indicating when the facts were last
confirmed. This can be added as a footer line under each numbered section or as
a structured field within each profile block.
| ## Outreach priority (by fit x reachability) | ||
| 1. Sarah Guo (Conviction) — best thesis fit, clear inbound channel | ||
| 2. Ed Sim (Boldstart) — canonical first-check devtools lead | ||
| 3. Astasia Myers (Felicis) — actively mapping this exact category | ||
| 4. Tim Chen (Essence) — OSS-first monetization fit | ||
| 5. Elad Gil — fast solo conviction, demo-driven | ||
| 6. swyx — distribution first, angel second (compounds all others) | ||
| 7. Martin Casado (a16z) — strongest narrative ("we are the moat") | ||
| 8. Jon Sakoda (Decibel) — OSS->enterprise story | ||
| 9. Guillermo Rauch — DX angel credibility | ||
| 10. Amjad Masad — strategic, watch for competitive overlap | ||
|
|
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win
Make the ranking reproducible.
“Fit x reachability” is the right idea, but the current order is undocumented, so later updates will be subjective. Add a simple score or weighting next to each target so the list can be recomputed consistently.
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 123-123: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/fundability/devtool-investor-targets.md` around lines 123 - 134, The
"Outreach priority (by fit x reachability)" section lists investors in order but
provides no documented scoring or weighting methodology, making future updates
subjective and inconsistent. Add a simple scoring system next to each target
entry (for example, numeric scores for "fit" and "reachability" factors, or a
combined priority score) so that the ranking becomes reproducible and
maintainable as the document is updated over time.
1 participant
Adds docs/fundability/devtool-investor-targets.md — 10 devtool/AI-infra investor targets with personal hooks for outreach.