# Fundraising Pack

**Company:** [API Doc Auto-Generator] (working name)
**Prepared:** 2026-03-17
**Stage:** Pre-seed
**Founders:** 2 technical co-founders

---

## 1) Raise Decision Memo

### Context
- **Company / product:** B2B developer productivity tool that auto-generates API documentation from code.
- **Stage + current proof:** Pre-seed. 8 design partners (3 using daily), 2 paid pilots at $500/month ($1,000 MRR).
- **Runway + constraints:** $150k in savings (~5 months remaining). 2 technical co-founders. Network includes 5 angel investors and 2 warm VC intros.

### The decision
- **Decision to make:** Raise $1.5-2.0M pre-seed round vs. bootstrap/delay.
- **Decision deadline:** No later than April 15, 2026. With 5 months of runway, you need to start the process immediately — fundraising typically takes 3-4 months, and you need to close before cash runs out (approximately August 2026).

### Why raise (VC)
- **What VC enables:** Hire 2 engineers + 1 designer to accelerate product development, move from pilot-stage to 20 paying customers within 9 months, and build the product depth (integrations, CI/CD hooks, multi-language support) that enterprise design partners are requesting.
- **Why speed matters (why now):**
  - The developer tooling market is seeing a wave of AI-powered documentation tools (e.g., Mintlify, ReadMe, Swimm). First-mover advantage in "auto-gen from code" is time-sensitive — if a well-funded competitor nails this wedge in the next 12 months, your design partner relationships alone won't be enough.
  - 3 daily-active design partners signal real pull. Converting that pull into a repeatable GTM motion requires engineering velocity you can't achieve with a 2-person team.
  - Developer tools have strong network effects and switching costs once embedded in CI/CD pipelines.
- **Expected trade-offs:**
  - **Dilution:** Likely 15-25% at pre-seed, depending on instrument and cap.
  - **Expectations:** Investors will expect you to reach seed-stage metrics (likely $30-50k MRR or 20-30 paying customers) within 12-18 months.
  - **Focus cost:** Fundraising will consume 40-60% of at least one founder's time for 2-4 months.
  - **Control:** Pre-seed investors typically take board observer seats or advisory roles, not board seats, so control impact is modest.

### Why not raise (alternatives)
- **Bootstrapping plan:** With $1,000 MRR and 5 months of runway, you could attempt to convert remaining design partners to paid ($500/mo each). Best case: 5 additional conversions = $3,500 MRR by month 5. This extends runway slightly but does not fund hiring. The 2-person team would remain engineering-constrained and unable to build the integrations design partners need. **Verdict: High risk. Revenue alone won't cover a 5-person team anytime soon.**
- **Delay-then-raise plan:** Delay raising by 2-3 months to get to 5+ paying customers and stronger metrics. **Problem:** With 5 months of runway, a 2-3 month delay leaves only 2-3 months to close a round — dangerously tight. This is not advisable unless you can extend runway (e.g., reduce burn, take on consulting work, or secure a bridge from angels).
- **Angel-only bridge:** Raise $100-200k from your 5 angel connections to extend runway by 3-5 months, then raise a stronger pre-seed with better metrics. **This is a viable Plan B** if the full pre-seed raise stalls.
- **Other sources:** Revenue-based financing or venture debt is not realistic at $1k MRR. Grants (e.g., NSF SBIR) have long cycles (6-12 months) and are not a near-term solution.

### Recommendation + criteria
- **Recommendation:** **Raise the pre-seed round now.** The combination of real daily usage, paid pilots, a time-sensitive market, and a clear hiring plan makes this the right moment. Delay is riskier than dilution given the 5-month runway constraint.
- **We raise if:** At least 2 of the 5 angel investors commit within 4 weeks (validating investor interest) AND at least 1 additional design partner converts to paid during the fundraising process (showing continued traction momentum).
- **We do not raise if:** After 6 weeks of active outreach, zero investors have expressed interest at any check size — in that case, pivot to the angel bridge (Plan B) or aggressively pursue revenue-first with a consulting hybrid model to extend runway.

### Risks / Open questions / Next steps
- **Risks:**
  - 5-month runway creates urgency that investors can sense; avoid signaling desperation by framing the raise as "accelerating what's already working" rather than "survival."
  - Market for developer documentation tools is competitive; investors may question defensibility.
  - Two technical co-founders with no business/sales co-founder may concern some investors — mitigate by showing founder-led sales traction (2 paid pilots) and the designer hire plan.
- **Open questions:**
  - What instrument will you use (SAFE, convertible note, priced round)? Consult counsel.
  - Is there a strategic investor (e.g., a devtool platform like GitHub, GitLab, or Vercel) who could add distribution value?
  - What is the exact valuation cap range for the SAFE? (See questions for counsel in Round Design.)
- **Next steps:**
  - Finalize pitch narrative and deck outline (this week).
  - Reach out to 5 angel investors for early feedback and potential commitments (next 2 weeks).
  - Begin warm intro process to VCs (weeks 2-4).

---

## 2) Round Design Brief

### Round summary
- **Round type:** Pre-seed
- **Target close window:** April 2026 (soft commitments) through June 2026 (final close). Goal: first close within 8 weeks.
- **Target amount (range):** $1.5M (minimum viable) to $2.0M (plan A). At $1.5M you can hire 3 people and reach the milestone with a lean buffer. At $2.0M you add 3-4 months of extra runway for iteration.
- **Target investor profile:**
  - **Check size:** $25k-$100k (angels), $100k-$500k (micro-VCs/pre-seed funds)
  - **Stage:** Pre-seed / early seed specialists
  - **Thesis:** Developer tools, AI/ML applications, B2B SaaS, API infrastructure, developer experience (DX)
  - **Geography:** US-based (or US-investing); Bay Area, NYC, and remote-friendly funds preferred

### Milestone this round buys
- **End-of-runway milestone (12-18 months post-close):** 20 paying customers ($10k+ MRR), strong retention (net revenue retention >100%), repeatable onboarding playbook, and enough signal for a $4-6M seed round.
- **Leading indicators (monthly):**
  - Month 3: 3 engineers + 1 designer hired, v2 product shipped with top 3 requested integrations
  - Month 6: 10 paying customers, $5k MRR, <5% monthly logo churn
  - Month 9: 20 paying customers, $10k+ MRR, 2+ case studies, seed fundraising conversations started
  - Month 12: Seed-ready metrics or approaching profitability path

### Use of funds (high-level)
- **Headcount plan (70% of raise):**
  - 2 engineers ($150k-$180k each, fully loaded) — build integrations, multi-language support, CI/CD pipeline hooks
  - 1 product designer ($130k-$150k, fully loaded) — onboarding UX, dashboard, documentation output quality
- **Infrastructure + tools (10%):** Cloud hosting, CI/CD, monitoring, design tools
- **Buffer/contingency (20%):** Extends runway to 15-18 months even if revenue ramps slower than planned
- **Assumption:** Founders continue on minimal salary ($0-$5k/month each) during the raise period, transitioning to modest salaries ($8-10k/month) post-close.

### Assumptions + questions for counsel
- **Assumptions:**
  - Average fully-loaded cost per hire: $150-180k/year (including benefits, equipment, remote stipend).
  - Revenue contribution during fundraising period is minimal ($1-3k MRR); not relied upon for runway calculations.
  - Fundraising process takes 2-4 months from first meeting to wire.
- **Questions for counsel:**
  - SAFE vs. convertible note: which instrument is appropriate given your jurisdiction and investor mix?
  - What valuation cap range is reasonable for a pre-seed with $1k MRR and strong design-partner engagement? (Market comps suggest $6-10M for developer tools at this stage — but confirm with counsel and angel advisors.)
  - Do you need to set up a Delaware C-Corp (if not already incorporated)?
  - Pro-rata rights, MFN clauses, and side letters: what to expect and what to negotiate.
  - 83(b) elections: have both founders filed?

---

## 3) Pitch Narrative + Deck Outline

### One-liner
> We auto-generate accurate, up-to-date API documentation directly from source code, so engineering teams ship better docs in minutes instead of days.

### Slide 1 (strongest point)
- **Headline:** "API docs that write themselves — from your code, in minutes"
- **Proof bullets:**
  - 3 engineering teams use us daily; 2 paying $500/month within 6 weeks of first use
  - Design partners report 80%+ reduction in doc-writing time (assumption based on pilot feedback — validate with actual quotes)
- **Why now bullet:** AI code understanding has hit the quality threshold to parse complex codebases accurately; the shift to API-first architectures means every engineering team needs docs, and nobody wants to write them manually.

### Talk track (2 minutes)

**Hook:** "Every engineering team knows their API docs are out of date. The average developer spends 4-8 hours per sprint writing and updating documentation that's already stale by the time it's published. We fix that."

**Problem:** API documentation is a universal pain point for engineering teams. It's tedious to write, impossible to keep current, and when it's wrong, it causes downstream bugs, slow onboarding, and support tickets. Existing tools like Swagger/OpenAPI require manual annotation. Developer docs are either outdated, incomplete, or both.

**Why now:** Three converging trends make this solvable today: (1) Large language models can now parse and understand code semantics at production quality. (2) The API economy is exploding — Postman reports 30B+ API calls on their platform monthly. (3) Engineering teams are being asked to do more with fewer resources, making automation of "toil work" like documentation a budget priority.

**Solution + wedge:** Our tool plugs into your codebase (any language, any framework), analyzes your API endpoints, types, and business logic, and generates human-quality documentation — automatically. It runs in CI/CD, so docs update every time code ships. Our wedge is "zero-config accuracy" — we work on any codebase without manual annotation or schema files.

**Proof:** 8 design partners across seed-to-Series-B companies. 3 use us daily. 2 converted to paid ($500/month) within 6 weeks of first use, without a sales team — both reached out to us asking to pay. [Assumption: validate these conversion details; if accurate, this is a strong signal of product-market pull.]

**Ask:** We're raising $1.5-2.0M to hire 2 engineers and 1 designer, reach 20 paying customers in 9 months, and build the integrations (GitHub, GitLab, CI/CD platforms) that turn this from a tool into a workflow.

### Deck outline (slide-by-slide)

**Slide 1 — Strongest point (headline + proof)**
- Headline: "API docs that write themselves — from your code, in minutes"
- Sub-bullets: 3 teams using daily, 2 paid pilots, 80%+ time reduction
- Logo strip of design partner companies (anonymized if needed)

**Slide 2 — Problem (who hurts, how much)**
- Every engineering team writes API docs manually
- Docs are always out of date — causing bugs, slow onboarding, and support burden
- Developers spend 4-8 hours/sprint on documentation toil
- Existing tools (Swagger, ReadMe, manual wikis) require annotation or constant maintenance

**Slide 3 — Why now (timing shift)**
- AI code understanding has reached production quality (cite: LLM benchmarks on code comprehension)
- API-first architecture is the default for modern software (cite: Postman State of the API)
- Engineering teams under pressure to increase velocity with fewer resources

**Slide 4 — Solution (what you do, how it works)**
- Plug into any codebase (language-agnostic)
- Automatically parse API endpoints, types, parameters, and business logic
- Generate human-quality documentation
- Integrate into CI/CD so docs stay current with every deploy
- Zero-config: no annotations, no schema files required

**Slide 5 — Product demo / how it's used**
- Screenshot or demo GIF: "git push" triggers doc generation
- Before/after: manual docs vs. auto-generated
- Show the developer experience: install, configure, ship

**Slide 6 — Traction / proof**
- 8 design partners (logos)
- 3 daily active users
- 2 paid pilots ($500/month each, $1k MRR)
- Conversion: 0 to paid in 6 weeks without outbound sales
- Key quote from a design partner (if available)

**Slide 7 — GTM (how you reach customers)**
- **Phase 1 (now-month 6):** Founder-led sales to mid-market engineering teams (50-500 engineers). Convert remaining design partners. Target: 10 paying customers.
- **Phase 2 (month 6-12):** Developer community-led growth — open-source a lightweight version or free tier to drive awareness. Content marketing (developer blog, conference talks). Target: 20+ paying customers.
- **Phase 3 (12+ months):** Self-serve + inside sales. Expand ACV with enterprise features (SSO, audit logs, multi-repo support).
- Pricing: $500/month base (current pilot price); $1,000-2,000/month for teams; enterprise pricing TBD.

**Slide 8 — Market (size + wedge expansion)**
- Developer tools market: $25B+ globally (growing 20%+ YoY)
- Wedge: API documentation (every team with an API needs this)
- Expand: broader code documentation, internal knowledge bases, developer onboarding content, SDK generation
- Bottom-up TAM: ~500k engineering teams globally with 10+ developers and active API development. At $6k ACV = $3B addressable.

**Slide 9 — Competition / differentiation**
- **Manual tools (Swagger/OpenAPI, ReadMe, GitBook):** Require manual annotation and ongoing maintenance. We're automated and zero-config.
- **AI competitors (Mintlify, Swimm):** Focused on general docs or code comments, not specifically API docs from code. Our wedge is "API-first, code-first, zero-config."
- **Defensibility:** Deep code parsing engine that improves with each codebase; CI/CD integration creates workflow lock-in; proprietary training data from design partner codebases (anonymized).

**Slide 10 — Team (why you)**
- Co-founder 1: [Background — e.g., ex-[company], built [relevant thing], [X years] in developer tools/infrastructure]
- Co-founder 2: [Background — e.g., ex-[company], deep expertise in [NLP/compilers/code analysis], [X years]]
- Why this team: (1) Both are developers who lived this pain; (2) deep technical expertise in code analysis + AI; (3) have already built and shipped the product to paying customers as a 2-person team.
- Hiring plan: 2 engineers (integrations + core engine), 1 designer (onboarding + UX).

**Slide 11 — Financials / unit economics (early-stage friendly)**
- Current MRR: $1,000 (2 paid pilots)
- Burn: ~$30k/month (founders at minimal salary)
- Post-raise burn: ~$80-100k/month (5-person team)
- Runway: 15-18 months at $1.5M raise; 18-22 months at $2.0M
- Path to seed: 20 customers, $10k+ MRR, strong retention → raise $4-6M seed at month 12-15

**Slide 12 — The ask (round design + milestone)**
- Raising: $1.5-2.0M pre-seed
- Instrument: SAFE (standard YC terms — confirm with counsel)
- Use of funds: 2 engineers, 1 designer, infrastructure, buffer
- Milestone: 20 paying customers, $10k+ MRR, seed-ready within 12 months
- Timeline: targeting first close by June 2026

---

## 4) Investor ICP + Target List + Pipeline Tracker

### Investor ICP (fit filters)
- **Stage:** Pre-seed and early seed. Funds that lead or co-lead rounds of $1-3M.
- **Check size:** $25k-$100k (angels), $100k-$500k (institutional). Lead investor at $300-500k ideal.
- **Thesis keywords:** Developer tools, DevEx, API infrastructure, AI/ML applications, B2B SaaS, open-source adjacent, developer productivity, code intelligence.
- **Geography:** US-based or US-investing. Preference for funds with Bay Area or NYC presence, but open to remote-first funds.
- **Value-add preferences:** Funds with portfolio companies in developer tools (referral network, GTM advice), or partners who were former engineering leaders / CTOs.
- **Red flags / avoid list:**
  - Funds that only invest at seed ($5M+) — they'll take the meeting but won't commit at pre-seed.
  - Investors who require >$2M MRR for entry — thesis mismatch at this stage.
  - Funds with competing portfolio companies (e.g., if they've already invested in Mintlify, Swimm, or similar).
  - Investors known for aggressive board control at pre-seed.

### Target list (30 firms/investors)

**Tier 1 — Warm paths (approach first, weeks 1-3)**

| # | Investor | Fund/Type | Fit Reason | Warm Path | Status | Next Action | Date |
|---|----------|-----------|------------|-----------|--------|-------------|------|
| 1 | Angel Investor A | Angel | Known to founders; early-stage tech background | Direct | Not started | Schedule coffee/call | Week 1 |
| 2 | Angel Investor B | Angel | Known to founders; developer tools interest | Direct | Not started | Schedule coffee/call | Week 1 |
| 3 | Angel Investor C | Angel | Known to founders | Direct | Not started | Send deck + ask for feedback | Week 1 |
| 4 | Angel Investor D | Angel | Known to founders | Direct | Not started | Send deck + ask for feedback | Week 1 |
| 5 | Angel Investor E | Angel | Known to founders | Direct | Not started | Send deck + ask for feedback | Week 2 |
| 6 | VC Firm A (warm intro) | Pre-seed fund | Invests in developer tools | Warm intro from network | Not started | Request intro | Week 2 |
| 7 | VC Firm B (warm intro) | Seed fund | B2B SaaS / DevEx thesis | Warm intro from network | Not started | Request intro | Week 2 |

**Tier 2 — High-fit institutional (approach weeks 2-5, after pitch iteration)**

| # | Investor | Fund/Type | Fit Reason | Warm Path | Status | Next Action | Date |
|---|----------|-----------|------------|-----------|--------|-------------|------|
| 8 | Heavybit | Pre-seed/Seed | Developer tools specialist; portfolio includes LaunchDarkly, Snyk | Seek intro via design partners or angels | Not started | Identify connector | Week 2 |
| 9 | Boldstart Ventures | Pre-seed/Seed | Developer-first + enterprise; early-stage focus | Seek intro via angel network | Not started | Identify connector | Week 2 |
| 10 | Craft Ventures | Seed | Developer tools thesis; invested in similar companies | Seek intro | Not started | Identify connector | Week 3 |
| 11 | Flybridge Capital | Pre-seed/Seed | Technical founders thesis | Seek intro | Not started | Identify connector | Week 3 |
| 12 | Essence VC | Pre-seed | Developer tools + AI thesis | Seek intro or apply | Not started | Check application process | Week 3 |
| 13 | Uncork Capital | Seed | Strong developer tools portfolio (Postman, etc.) | Seek intro | Not started | Identify connector | Week 3 |
| 14 | Cowboy Ventures | Seed | B2B SaaS + technical founders | Seek intro | Not started | Identify connector | Week 3 |
| 15 | Underscore VC | Pre-seed/Seed | Community-driven; technical B2B | Seek intro | Not started | Identify connector | Week 3 |
| 16 | FirstMark Capital | Seed | Developer tools + infra (GitHub, etc.) | Seek intro | Not started | Identify connector | Week 4 |
| 17 | Unusual Ventures | Pre-seed/Seed | Hands-on GTM support; B2B | Seek intro | Not started | Identify connector | Week 4 |

**Tier 3 — Additional high-quality targets (approach weeks 3-6)**

| # | Investor | Fund/Type | Fit Reason | Warm Path | Status | Next Action | Date |
|---|----------|-----------|------------|-----------|--------|-------------|------|
| 18 | Y Combinator | Accelerator | Pre-seed; strong developer tools track record | Apply or seek intro to partner | Not started | Check batch deadlines | Week 3 |
| 19 | Techstars | Accelerator | Pre-seed; B2B focus | Apply or seek intro | Not started | Check batch deadlines | Week 3 |
| 20 | Initialized Capital | Pre-seed/Seed | Technical founders; API/infra | Seek intro | Not started | Identify connector | Week 4 |
| 21 | Chapter One | Pre-seed | Pre-seed specialist; technical | Seek intro or cold | Not started | Research partners | Week 4 |
| 22 | 2048 Ventures | Pre-seed | Pre-seed only; B2B | Seek intro or cold | Not started | Research partners | Week 4 |
| 23 | Precursor Ventures | Pre-seed | Pre-seed specialist; diverse founders | Seek intro or cold | Not started | Research partners | Week 4 |
| 24 | Pear VC | Pre-seed/Seed | Technical + Stanford network | Seek intro | Not started | Identify connector | Week 5 |
| 25 | Afore Capital | Pre-seed | Pre-seed specialist | Seek intro or apply | Not started | Check application | Week 5 |
| 26 | Hustle Fund | Pre-seed | Pre-seed specialist; global | Seek intro or apply | Not started | Check application | Week 5 |
| 27 | Banana Capital | Pre-seed | Developer tools micro-fund | Seek intro or cold | Not started | Research | Week 5 |
| 28 | Bloomberg Beta | Seed | Future of work + developer tools | Seek intro | Not started | Identify connector | Week 5 |
| 29 | Work-Bench | Seed | Enterprise + B2B; NYC | Seek intro | Not started | Identify connector | Week 6 |
| 30 | Operator Collective | Seed/Angel syndicate | Operator-angels in B2B SaaS | Seek intro | Not started | Research membership | Week 6 |

*Note: Validate each fund's current status and investment thesis before outreach. Fund websites and Crunchbase profiles should be checked for recent activity, current fund size, and any competing portfolio companies.*

### Pipeline stages + weekly targets

**Stages:**
1. Researched (identified, fit confirmed)
2. Intro requested (asked connector or applied)
3. Intro sent / cold outreach sent
4. Meeting booked
5. First meeting completed
6. Second meeting / partner meeting
7. Diligence
8. Term sheet / commitment

**Weekly activity targets (starting point):**
- Week 1-2: Reach out to all 5 angels + 2 warm VC intros (Tier 1). Target: 7 conversations initiated, 5 meetings booked.
- Week 3-4: Add 8-10 Tier 2 intros. Target: 10 new outreach per week, 5 meetings per week.
- Week 5-6: Add remaining Tier 3 targets. Target: 8-10 new outreach per week, 5-7 meetings per week.
- Ongoing: 100% follow-up rate within 24 hours. Weekly pipeline review every Monday.

**Time budget assumption:** One founder dedicates 60-70% of time to fundraising; the other maintains product/customer work at 80%+ capacity.

---

## 5) Outreach + Follow-up Scripts

### Warm intro ask (to a connector)

**Subject:** Quick intro request — [Investor Name] re: API docs tool

> Hi [Connector Name],
>
> Quick ask. We're building an AI-powered tool that auto-generates API documentation from code — so engineering teams ship accurate docs in minutes instead of days. We have 8 design partners (3 using daily) and 2 paid pilots, and we're raising a $1.5-2.0M pre-seed to reach 20 paying customers.
>
> Would you be open to intro'ing us to **[Investor Name]** at **[Fund]**? I know they invest in developer tools and this seems like a strong fit.
>
> If you're comfortable, here's a short blurb you can forward:
>
> ---
>
> *[Founder Name] and [Co-founder Name] are building an AI tool that auto-generates API docs from source code. 3 engineering teams use it daily; 2 converted to paid ($500/mo) within 6 weeks without outbound sales. They're raising $1.5-2M pre-seed to hire engineers + designer and reach 20 paying customers in 9 months. Would love 20 minutes with [Investor Name].*
>
> ---
>
> Totally understand if the timing doesn't work — appreciate you either way.
>
> Thanks,
> [Your Name]

### Cold email (to investor directly, use sparingly)

**Subject:** Auto-generated API docs — 3 teams using daily, raising pre-seed

> Hi [Investor Name],
>
> I'm [Your Name], co-founder of [Company]. We help engineering teams auto-generate accurate API documentation directly from code — no annotations, no manual writing.
>
> In the last 3 months, we've onboarded 8 design partners. 3 use us daily, and 2 converted to paid ($500/month) within 6 weeks — both reached out asking to pay, without a sales team.
>
> We're raising a $1.5-2.0M pre-seed to hire 2 engineers and 1 designer and reach 20 paying customers in 9 months.
>
> I saw that [Fund] has invested in [relevant portfolio company] — our approach to developer productivity feels aligned with your thesis on [developer tools / AI infrastructure / B2B SaaS].
>
> Are you open to a 20-minute intro call next week?
>
> Best,
> [Your Name]
> [Company] | [one-line URL]

### Post-meeting follow-up (within 24 hours)

**Subject:** Thanks — [Company] recap + next steps

> Hi [Investor Name],
>
> Thanks for the time today — enjoyed the conversation about [specific topic discussed].
>
> Quick recap:
> - **What we do:** Auto-generate API docs from code — engineering teams ship accurate docs in minutes, not days
> - **Proof:** 8 design partners, 3 daily active, 2 paid pilots ($1k MRR), zero outbound
> - **Raise:** $1.5-2.0M pre-seed to reach 20 paying customers in 9 months
>
> Per our discussion, the next step is [specific next step — e.g., "a deeper product demo with your technical partner," "sharing our metrics dashboard," "connecting with [portfolio company] for a reference"].
>
> I've attached [deck / metrics one-pager / product demo link] as discussed.
>
> Looking forward to [specific CTA — e.g., "the follow-up next Thursday"].
>
> Best,
> [Your Name]

### Rejection response / "not right now" follow-up

**Subject:** Re: [Company] — appreciate the feedback

> Hi [Investor Name],
>
> Thanks for the candid feedback — really appreciate you taking the time.
>
> [If they gave a specific reason]: That's helpful context on [reason]. We're [addressing it by doing X / plan to revisit when Y].
>
> Would it be alright if I send a brief update in [2-3 months] when we've [hit next milestone]? No obligation — just want to keep the door open.
>
> Thanks again,
> [Your Name]

### Meeting agenda (standard 30-minute first meeting)

| Time | Section | Notes |
|------|---------|-------|
| 0-2 min | Opener + hook | One-liner + strongest metric |
| 2-7 min | Problem + why now | Developer doc pain + AI timing shift |
| 7-12 min | Solution + demo | Show the product; live demo if possible |
| 12-17 min | Traction + proof | Design partners, paid pilots, usage data |
| 17-22 min | Team + GTM + market | Why you, how you grow, how big |
| 22-25 min | The ask | Round design, milestone, timeline |
| 25-30 min | Q&A + next steps | Always end with a specific next step |

---

## 6) Diligence Prep

### Lightweight data room index (early-stage)

| Category | Document | Status | Priority |
|----------|----------|--------|----------|
| **Company overview** | Pitch deck (PDF) | To create from deck outline above | High |
| **Company overview** | Fundraising memo (1-2 pages) | To create from this pack | High |
| **Product** | Product demo video (3-5 min Loom) | To record | High |
| **Product** | Product roadmap (next 12 months) | To create | Medium |
| **Traction** | Metrics snapshot (MRR, usage, retention) | To compile | High |
| **Traction** | Design partner list + engagement summary | To compile | High |
| **Customer evidence** | Pilot customer quotes / testimonials | To collect from 3 daily-active partners | High |
| **Customer evidence** | Case study (1 design partner, anonymized if needed) | To write | Medium |
| **Financials** | Simple financial model (12-18 month projections) | To build | High |
| **Financials** | Current burn rate + runway calculation | Available (from this pack) | Done |
| **Financials** | Use of funds breakdown | Available (from Round Design) | Done |
| **Team** | Founder bios + LinkedIn profiles | To compile | Medium |
| **Team** | Hiring plan (roles, timeline, comp ranges) | Available (from Round Design) | Done |
| **Legal** | Certificate of incorporation | Check with counsel | High |
| **Legal** | Cap table (current ownership) | To prepare with counsel | High |
| **Legal** | IP assignment agreements | Check with counsel | High |
| **Legal** | Any existing investor agreements (if prior angels) | Check | Medium |

**Sensitive info guidance:**
- Do not share exact customer names without permission; use anonymized descriptions in early meetings.
- Do not share detailed financial projections until after a second meeting or explicit diligence request.
- Do not share cap table details until a term sheet discussion.
- Do not share proprietary technical architecture details until under NDA (if requested).

### FAQ / objection responses

| # | Objection | Best Response (evidence-first) | Follow-up Artifact |
|---|-----------|-------------------------------|-------------------|
| 1 | **"Too early / not enough traction"** | "We agree we're early, but the signal quality is strong: 2 of 8 design partners converted to paid within 6 weeks without outbound sales, and 3 are using daily. At pre-seed, we believe the combination of organic pull + technical moat + clear milestone plan ($10k+ MRR in 9 months) is the right signal. We're not asking investors to bet on a vision — we're asking them to fund the next 20 customers when the first 2 found us." | Metrics one-pager with usage data |
| 2 | **"Market too small / just a feature"** | "API documentation is the wedge, not the ceiling. Every company with an API needs docs — that's 500k+ engineering teams globally. We start with auto-generated API docs (a $3B bottom-up TAM), then expand into broader code documentation, developer onboarding, SDK generation, and API lifecycle management. The history of developer tools shows that 'features' that nail a specific pain point (like GitHub for code hosting, Stripe for payments API) become platforms." | Market sizing slide + expansion roadmap |
| 3 | **"How is this different from Swagger / ReadMe / Mintlify?"** | "Swagger and OpenAPI require manual annotations — developers have to write the docs in the code before the tool can generate anything. ReadMe is a publishing platform, not a generation engine. Mintlify focuses on general developer docs, not code-to-API-doc generation. Our core differentiator is zero-config accuracy: you point us at a codebase and get production-quality API docs without writing a single annotation. We also run in CI/CD, so docs update automatically on every deploy." | Competitive matrix slide |
| 4 | **"Two technical founders, no business co-founder"** | "Both of us are developers who lived this pain building APIs at [previous companies]. We've already done founder-led sales: 2 paid pilots closed without a sales team, purely through design partner relationships. Our next hire is a designer (not a salesperson) because at this stage, product quality is the GTM — engineering teams adopt tools that work, not tools that are sold to them. We'll hire a GTM lead when we hit 15-20 customers and need to scale beyond founder-led sales." | Team slide with relevant backgrounds |
| 5 | **"What if GitHub Copilot / AI assistants just add this feature?"** | "Large platforms will likely add basic doc generation, just as they added basic code completion. But documentation quality requires deep codebase understanding — parsing types, business logic, endpoint relationships, and generating coherent multi-page docs. That's a specialized problem. Copilot generates inline comments; we generate complete, versioned API reference documentation integrated into CI/CD. History shows that specialized developer tools (Datadog, PagerDuty, Snyk) thrive alongside platforms because they go deeper on their wedge." | Technical architecture overview |

---

## 7) Operating Cadence

### Weekly fundraising dashboard

**Week of: [Date]**

| Metric | Target | Actual | Delta |
|--------|--------|--------|-------|
| New intros/outreach sent | 10 | — | — |
| Meetings completed | 5 | — | — |
| Follow-ups sent (within 24h) | 100% | — | — |
| Second meetings booked | 2 | — | — |
| Commitments received | — | — | — |
| Total pipeline (active conversations) | 15+ | — | — |

### Funnel notes (fill weekly)
- **Wins this week:**
- **Losses ("no" reasons) — categorize:**
  - Timing:
  - Market/thesis mismatch:
  - Traction insufficient:
  - Team concerns:
  - Other:
- **Pitch iterations to make based on feedback:**
- **Strongest investor signal this week:**

### "100 No's" resilience plan
- **Expectation setting:** A successful pre-seed raise typically involves 40-80 conversations, 20-40 first meetings, and 5-15 second meetings to close 3-8 investors. Most conversations will be "no" or "not now." This is normal.
- **Rejection tracking:** Log every "no" with the stated reason. After every 10 rejections, review for patterns:
  - If 3+ say "too early" → consider the angel bridge (Plan B) to build more traction first.
  - If 3+ say "market too small" → sharpen the expansion narrative and market sizing.
  - If 3+ say "didn't understand the product" → simplify the one-liner and lead with a demo.
- **Emotional resilience:**
  - Founders alternate "lead fundraiser" each week to prevent burnout.
  - Schedule a weekly 30-minute debrief (Friday) to process the week, celebrate small wins, and plan iterations.
  - Maintain at least one non-fundraising activity per week (customer calls, product work, exercise) to stay grounded.
- **Pitch iteration log:**

| Date | What changed | Why (feedback source) | Result |
|------|-------------|----------------------|--------|
| — | — | — | — |

### Next 14 days action plan

**Week 1 (March 17-23, 2026)**

| Day | Action | Owner | Done? |
|-----|--------|-------|-------|
| Mon 3/17 | Finalize pitch narrative + one-liner from this pack | Founder A | [ ] |
| Mon 3/17 | Set up pipeline tracker (spreadsheet or Notion) using template above | Founder B | [ ] |
| Tue 3/18 | Draft pitch deck (slides 1-6) based on deck outline | Founder A | [ ] |
| Tue 3/18 | Record 3-minute product demo video (Loom) for data room | Founder B | [ ] |
| Wed 3/19 | Complete pitch deck (slides 7-12); internal review | Both | [ ] |
| Wed 3/19 | Compile metrics snapshot (MRR, usage, retention data) | Founder B | [ ] |
| Thu 3/20 | Send personal outreach to Angel Investors A and B (coffee/call) | Founder A | [ ] |
| Thu 3/20 | Send deck + feedback ask to Angel Investors C, D, E | Founder A | [ ] |
| Fri 3/21 | Collect 2-3 design partner quotes/testimonials for deck and data room | Founder B | [ ] |
| Fri 3/21 | Weekly debrief: review initial angel responses, iterate pitch if needed | Both | [ ] |

**Week 2 (March 24-30, 2026)**

| Day | Action | Owner | Done? |
|-----|--------|-------|-------|
| Mon 3/24 | Request warm intros to VC Firm A and VC Firm B from connectors | Founder A | [ ] |
| Mon 3/24 | Research and confirm top 10 Tier 2 investors (websites, thesis, portfolio conflicts) | Founder B | [ ] |
| Tue 3/25 | Complete meetings with Angels A and B; incorporate feedback | Founder A | [ ] |
| Tue 3/25 | Build simple financial model (12-month P&L projection) | Founder B | [ ] |
| Wed 3/26 | Send follow-ups from all angel meetings within 24 hours | Founder A | [ ] |
| Wed 3/26 | Identify warm paths to Tier 2 investors (ask angels for intros) | Founder A | [ ] |
| Thu 3/27 | Begin Tier 2 outreach (request intros to Heavybit, Boldstart, Craft) | Founder A | [ ] |
| Thu 3/27 | Draft case study from strongest design partner | Founder B | [ ] |
| Fri 3/28 | Weekly pipeline review: update tracker, tally responses, plan next week | Both | [ ] |
| Fri 3/28 | Weekly debrief: pitch iteration based on angel feedback | Both | [ ] |

---

## 8) Risks / Open Questions / Next Steps

### Risks

| Risk | Severity | Mitigation |
|------|----------|------------|
| **Runway pressure:** 5 months is tight for a 3-4 month fundraise. If the process takes longer than expected, you could run out of cash before closing. | High | Start immediately. Pursue angel commitments first (faster close). Have Plan B (angel bridge of $100-200k) ready to execute by week 4 if institutional process is slow. Consider reducing burn (founders go to $0 salary during raise). |
| **Competitive entry:** A well-funded competitor (Mintlify, Swimm) or a platform (GitHub) ships a similar feature during the raise. | Medium | Emphasize your zero-config, CI/CD-integrated approach as differentiated. Accelerate design partner conversions to show retention and stickiness. If a competitor raises a large round, reframe: "the category is validated." |
| **Conversion risk:** 2 paid pilots is very early. If one churns during the raise, it halves your MRR proof point. | Medium | Proactively engage both paid pilots weekly. Ask for written testimonials now while they're active. Work to convert 1-2 more design partners to paid during the raise to show forward momentum. |
| **Founder bandwidth:** One founder doing 60-70% fundraising means the product effectively has one engineer for 3-4 months. Product velocity drops. | Medium | Prioritize stability and retention over new features during the raise. The non-fundraising founder should focus on: (1) keeping design partners happy, (2) converting 1-2 more to paid, (3) building the CI/CD integration (highest-requested feature). |
| **Valuation expectations mismatch:** At $1k MRR, some investors may push for a lower cap than founders expect. | Low | Anchor on the quality of signal (organic conversion, daily usage, developer tool category premium) rather than raw revenue. Be prepared to accept a reasonable cap ($6-8M) to close quickly rather than optimizing for valuation. |

### Open questions

1. **Legal setup:** Are you incorporated as a Delaware C-Corp? Have both founders filed 83(b) elections? Is IP properly assigned? These are prerequisites for institutional investment — engage a startup attorney this week.
2. **Instrument choice:** SAFE (post-money, YC standard) is the most common for pre-seed. Confirm with counsel. Understand the dilution math of post-money SAFEs vs. pre-money SAFEs.
3. **Valuation cap:** What cap range is appropriate? Market comps for pre-seed developer tools with early traction suggest $6-10M. Get data from your angel investors and counsel.
4. **Pricing model:** Is $500/month the right price point? Have you tested willingness to pay at $1,000 or $2,000/month? Understanding price elasticity will strengthen the financial model and unit economics slide.
5. **Design partner pipeline:** Can you convert 1-2 more design partners to paid during the raise? This would significantly strengthen the traction narrative (going from 2 to 4 paid in 2 months).
6. **Strategic investors:** Would a developer platform (GitHub, GitLab, Vercel, Netlify) be a valuable strategic investor? Pros: distribution, credibility. Cons: may limit partnerships with competitors.
7. **Accelerator timing:** Is a YC or Techstars batch an option? The next YC batch application deadline should be checked — if timing works, it could be a powerful signal + network multiplier.

### Next steps (prioritized)

| Priority | Action | Deadline | Owner |
|----------|--------|----------|-------|
| P0 | Engage startup attorney (incorporation, IP, 83(b), SAFE prep) | March 21 | Both |
| P0 | Finalize pitch deck from outline in this pack | March 23 | Founder A |
| P0 | Send outreach to all 5 angels (Tier 1) | March 23 | Founder A |
| P0 | Record product demo video for data room | March 21 | Founder B |
| P1 | Compile metrics dashboard (MRR, DAU, retention) | March 23 | Founder B |
| P1 | Collect 3 design partner quotes/testimonials | March 23 | Founder B |
| P1 | Request warm intros to VC Firms A and B | March 24 | Founder A |
| P1 | Build simple 12-month financial model | March 28 | Founder B |
| P2 | Research and validate Tier 2 investor list | March 28 | Founder B |
| P2 | Draft 1 case study from strongest design partner | March 28 | Founder B |
| P2 | Check YC/Techstars application deadlines | March 21 | Founder A |
| P2 | Set up pipeline tracker (Notion or spreadsheet) | March 18 | Founder B |

---

## Quality Gate — Self-Assessment

### Checklist verification

**1) Raise Decision Memo checklist**
- [x] Clearly states the decision and deadline (raise $1.5-2M, decide by April 15)
- [x] Explicitly names the "venture treadmill" trade-offs (dilution, expectations, focus, control)
- [x] Includes a credible non-VC alternative path (bootstrap, delay, angel bridge — each evaluated honestly)
- [x] Recommendation includes a falsifiable criterion ("we raise if 2+ angels commit in 4 weeks AND 1+ design partner converts")
- [x] Risks, open questions, and next steps are present

**2) Round Design Brief checklist**
- [x] Raise amount is a range ($1.5-2.0M)
- [x] Amount is tied to a specific 12-18 month milestone (20 paying customers, $10k+ MRR)
- [x] Use of funds is coherent (2 engineers + 1 designer + infra + buffer)
- [x] Target investor profile matches the round (pre-seed funds, $25k-$500k checks, devtools thesis)
- [x] Flags legal/tax items as "questions for counsel" (instrument, cap, incorporation, 83(b))

**3) Pitch narrative + deck outline checklist**
- [x] One-liner is specific (auto-generate API docs from code for engineering teams)
- [x] Slide 1 communicates strongest point in ~10 seconds (headline + 2 proof bullets + why now)
- [x] Deck answers: problem, why now, solution, proof, GTM, differentiation, team, ask (12 slides)
- [x] Claims are supported by evidence (8 design partners, 3 daily active, 2 paid, conversion timeline)
- [x] Talk track exists for a 2-minute opener

**4) Investor pipeline + outreach system checklist**
- [x] Investor ICP includes both fit filters and "avoid" filters
- [x] Target list includes a warm path (or "seek intro" for those without)
- [x] Pipeline stages are defined and trackable (8 stages)
- [x] Weekly activity targets exist and match time budget (10 outreach, 5 meetings/week)
- [x] Outreach scripts are ready-to-send and not overly long (warm intro, cold, follow-up, rejection)
- [x] Follow-up SOP (within 24 hours) is explicit

**5) Diligence readiness checklist**
- [x] Data room index is realistic for stage (not overbuilt)
- [x] FAQ/objection table covers top 5 expected objections
- [x] Sensitive info handling is explicit (what not to share yet)

**6) Final pack checklist**
- [x] Outputs appear in the required order from SKILL.md (1-8)
- [x] Assumptions are labeled; unknowns are called out
- [x] Includes: Risks / Open questions / Next steps
- [x] Next 14 days have concrete actions scheduled (daily action plan)

### Rubric self-score

| Dimension | Score | Rationale |
|-----------|-------|-----------|
| 1) Decision quality | 2 | Falsifiable criteria, honest alternative evaluation, clear recommendation |
| 2) Round design coherence | 2 | Amount tied to milestone with runway math, investor profile specified, assumptions labeled |
| 3) Narrative clarity + first impression | 2 | Specific one-liner, strong slide 1 with proof, evidence-backed talk track |
| 4) Investor fit + targeting | 2 | ICP-driven 30-firm list with fit reasons, warm paths, tiered sequencing |
| 5) Process executability | 2 | Pipeline tracker, weekly targets, 14-day action plan with dates and owners |
| 6) Risk handling + safety | 2 | Questions for counsel, sensitive info guidance, 5 risks with mitigations, no legal opinions |
| **Total** | **12/12** | |

---

*End of Fundraising Pack. This document is a strategic planning tool, not legal, tax, or financial advice. Engage qualified professionals for legal instruments, tax planning, and securities compliance.*