rsc-universal 0.1.1

package/skills/investor-materials/SKILL.md

@@ -0,0 +1,175 @@
+---
+name: investor-materials
+description: "Use when packaging, organizing, or circulating the documents an investor reads OUTSIDE the meeting — setting up or cleaning a data room, writing the investor one-pager/teaser that earns the first meeting, or drafting the recurring monthly/quarterly investor update — symptoms include unnamed dump-folder files, no follow-on warmth, or needing the attachment a cold email carries. Triggers: 'set up our data room', 'what docs do investors expect before diligence', 'write our investor one-pager / teaser', 'draft this month's investor update', 'our data room is a mess, rename and reorganize the files', 'set up a reusable monthly update format', 'sala de datos para inversores', 'actualización mensual a inversores', 'sala de dades / resum d'una pàgina per a inversors'. NOT the slide narrative (that is pitch-deck), NOT the projection spreadsheet (that is financial-model), NOT the round strategy and investor pipeline (that is fundraising)."
+tags: [fundraising, data-room, investor-update, one-pager, investor-relations, due-diligence]
+recommends: [pitch-deck, financial-model, fundraising, cold-outreach, unit-economics, grants]
+origin: risco
+---
+
+# Investor Materials — Data Room, One-Pager, Investor Update
+
+*The packaging layer of fundraising. You consume the deck, the model, and the metrics — then you organize, name, and circulate the documents an investor reads on their own time. You do not build the story, the spreadsheet, or the round strategy.*
+
+This skill produces exactly **three artifacts**:
+
+1. **The data room** — the organized, numbered, access-tracked folder of diligence files an investor opens after the meeting.
+2. **The one-pager / teaser** — the single page that earns the first meeting and rides along on a cold email.
+3. **The investor update** — the recurring email that keeps existing backers warm and primed for the follow-on.
+
+One-line route-out: the persuasive **story in slides** is `../pitch-deck/SKILL.md`; the **numbers in a spreadsheet** are `../financial-model/SKILL.md`; the **round strategy and investor pipeline** are `../fundraising/SKILL.md`. You package what they produce.
+
+## Decision table — is it yours?
+
+| The ask | Owned here? | Route to |
+| --- | --- | --- |
+| Set up / clean / rename the data room | **Yes** | — |
+| Write the one-pager / teaser | **Yes** | — |
+| Draft the recurring investor update | **Yes** | — |
+| Build the slide deck / narrative arc | No | `pitch-deck` |
+| Build projections / burn / runway / cap-table math | No | `financial-model` |
+| Investor list, outreach strategy, SAFE vs priced, term sheet | No | `fundraising` |
+| Cold first-touch email to a named VC | No | `cold-outreach` (you supply the one-pager it attaches) |
+| LTV / CAC / payback / contribution-margin deep dive | No | `unit-economics` |
+| Grant / non-dilutive funding narrative | No | `grants` |
+| How the one-pager LOOKS (layout, brand) | No | `brand-identity` / `presentations` |
+
+## Intake gate (run before producing anything)
+
+Two questions decide everything. Ask them, do not assume.
+
+1. **Stage?** pre-seed / seed / Series A — sets data-room size (seed skews 30–40 docs, Series A 55–70) and whether the one-pager leads with team or traction.
+2. **What already exists?** Is there a deck, a model, current metrics? You *consume* these. If they are missing and the real ask is to create them, **STOP and route** — building the deck is `pitch-deck`, building the model is `financial-model`. Producing a one-pager with invented traction or a data room that points at a nonexistent model is the failure this gate prevents.
+
+Rule with a why: **if the request is really the narrative or the numbers, you are the wrong skill — route, do not fake.** A polished package around hollow content wastes the founder's one shot with each investor.
+
+## Data room
+
+A complete startup data room is **~50–70 documents across 8 numbered categories**. Number the folders so an investor (who spends only ~2–3 hours total, and 8–12 minutes on cap table + SAFEs alone) navigates without asking. **68% of failed deals cite disorganized documentation as a primary factor, and organized rooms close ~35% faster** — investors assume you run the company the way you run the deal room. That is the entire reason for the numbering and naming rules below.
+
+The 8 categories (full per-doc checklist with seed vs Series-A inclusion flags → `references/dataroom-checklist.md`):
+
+```text
+01_Corporate        incorporation, bylaws, board minutes, shareholder agreements
+02_Financial        financial model, historical P&L, balance sheet, bank statements
+03_Legal_Contracts  customer/supplier contracts, NDAs, leases, litigation log
+04_IP               trademarks, patents, domains, IP-assignment agreements
+05_Team_HR          org chart, key employment + founder vesting, option plan
+06_Product_Metrics  product overview, roadmap, KPI dashboard, cohort/retention data
+07_CapTable_Equity  cap table, SAFEs/convertibles, prior round docs, 409A
+08_Tax_Compliance   tax filings, registrations, licenses, compliance certificates
+```
+
+**Naming convention — non-negotiable:** `YYYY-MM_Doc-Name_vN.ext`. Date for recency, version so nobody diligences a stale file.
+
+```text
+Bad   final_model(2)(FINAL).xlsx
+Bad   captable_new_updated.xlsx
+Good  2026-03_Financial-Model_v4.xlsx
+Good  2026-03_Cap-Table_v2.xlsx
+Good  07_CapTable_Equity/2026-02_SAFE-AngelRound_v1.pdf
+```
+
+- **Surface the most-scrutinized first.** Cap table, SAFEs/convertibles, and the financial model get the most eyes — put them where they cannot be missed and make sure they are the *current* version. Too many files dilutes focus and signals poor prioritization.
+- **Leave half-baked docs OUT.** A folder with 70 files where 15 are drafts reads worse than 45 clean ones. Omit until ready; an empty-looking "08_Tax" with a placeholder is worse than a note "tax filings available on request."
+- **Share a link per investor and read the analytics.** DocSend-style tooling tracks who opened what, time-per-page, and forwards. Use drop-off to fix the materials and warmth signals to prioritize follow-up. You advise the link-per-investor practice and read the analytics — you do not build the VDR software.
+
+## One-pager / teaser
+
+The one-pager's job is to **GET the meeting**; the deck's job is to **close** it. They are different artifacts — one-pagers get ~2.5x higher response rates than full decks for cold outreach. The one-pager is **7 blocks**:
+
+```text
+1. Headline / one-liner   what you do, for whom, in one sentence
+2. Problem                the pain, sized and concrete
+3. Solution               your product, one line of how it works
+4. Traction               the 3–5 metrics that prove pull (MRR, growth %, logos)
+5. Market                 TAM / SAM / SOM with the SOM you can actually win
+6. Team                   why THIS team wins this market
+7. The ask                specific amount + use of funds
+```
+
+- **Lead order by stage.** Pre-revenue leads with **team** (there is no traction to lead with). Post-traction leads with **traction** (the metrics are the strongest card). Re-order blocks accordingly; do not bury the strongest one at the bottom.
+- **A teaser carries NO confidential financials.** A teaser is 1–5 pages with no detailed P&L, no full cap table, no confidential customer data — those live in the deck and the data room behind an access link. Leaking them into the first-touch attachment is a defect.
+- **The ask is specific.** "Raising $1.5M to extend runway 18 months and hire 4 engineers" — not "raising a round." A vague ask reads as an unprepared founder.
+
+```text
+Bad  (ask)       "We're raising a round to grow the business."
+Good (ask)       "Raising $1.5M seed — 18mo runway: 4 eng hires, 2 GTM, to reach $1M ARR."
+Bad  (headline)  "An AI-powered platform revolutionizing the future of work."
+Good (headline)  "Payroll for restaurant groups — cut weekly close from 6 hours to 20 min."
+```
+
+Fill-in 7-block template + a filled mini-example → `references/update-and-onepager-templates.md`.
+
+## Investor update
+
+The monthly update is **~6 fixed sections in ~250 words**. Top VCs prefer short and consistent over long and sporadic — the format itself signals operational discipline.
+
+```text
+1. Headline       one line: the month in a sentence
+2. Highlights     3–5 bullets, the wins that matter
+3. Metrics table  4–6 KPIs: actual vs target vs prior period
+4. Challenges     2–3, each PAIRED with a solution or learning (never a naked problem)
+5. Asks           specific, named — "intro to the VP Sales at X", not "let me know"
+6. Cash / runway  current cash, monthly burn, months of runway
+```
+
+The metrics table is the spine — same KPIs every month so trend is legible at a glance:
+
+```text
+| Metric        | This month | Target | Last month |
+| ------------- | ---------- | ------ | ---------- |
+| MRR           | $42k       | $45k   | $38k       |
+| New logos     | 7          | 8      | 5          |
+| Net churn     | 1.2%       | <2%    | 1.8%       |
+| Cash runway   | 14 mo      | —      | 15 mo      |
+```
+
+- **Fixed cadence, never broken.** Monthly for early-stage, quarterly for growth-stage. Pick a day (e.g. the 5th) and hold it — consistency is the signal. Only emailing investors when you need money trains them to brace, not to help.
+- **Every challenge is PAIRED with a solution or learning.** A naked problem reads as a founder who is stuck; a problem-with-a-plan reads as a founder who is in control.
+- **Asks are named, not vague.** Vague asks ("let me know if you can help") get ignored; named asks ("intro to the VP Sales at Acme") convert passive backers into active allies.
+
+```text
+Bad  (ask)         "Let me know if you can help with anything."
+Good (ask)         "Need a warm intro to a Head of RevOps at a 200+ Series-B SaaS — who do you know?"
+Bad  (challenge)   "Sales cycle is too long."
+Good (challenge)   "Sales cycle stretched to 70 days — fix: added a security-review pack to the deck, two deals already re-accelerated."
+```
+
+Fill-in 6-section template + a filled mini-example + the vague-ask banlist → `references/update-and-onepager-templates.md`.
+
+## Anti-patterns / rationalizations → STOP
+
+| Rationalization | Reality / Fix |
+| --- | --- |
+| "I'll dump every file in one folder, they'll find it" | Investors spend ~2–3h total; disorganization kills 68% of failed deals. Number the 8 categories, name `YYYY-MM_Doc_vN`. |
+| "`final_v2_FINAL(2)` is fine, I know which is current" | They don't. A stale un-versioned file gets diligenced as truth. Date + version every file. |
+| "Send the full deck for cold outreach" | The deck closes; it doesn't open. Send the one-pager — ~2.5x the response rate — deck stays behind the link. |
+| "Put the P&L and cap table in the teaser so they have everything" | A teaser carries no confidential financials. Those live in the data room behind a per-investor link. |
+| "'Let me know if you can help' covers it" | Vague asks get ignored. Name the intro, the role, the company. |
+| "I'll email investors when I have news / need money" | Sporadic updates train backers to brace. Fixed cadence (monthly/quarterly), never broken. |
+| "List the challenge, they'll appreciate the honesty" | A naked problem reads as stuck. Pair every challenge with a solution or learning. |
+| "I'll write the deck / model in here too" | Out of scope. Route to `pitch-deck` / `financial-model`; package what they produce. |
+| "Pad the room to 70 files so it looks thorough" | Drafts dilute focus and signal poor prioritization. Omit until ready; clean beats padded. |
+
+## Verify + handoffs
+
+After generating `dataroom-index.md`, `one-pager.md`, or `investor-update.md`, run the structural lint:
+
+```bash
+./scripts/verify.sh path/to/one-pager.md     # or dataroom-index.md / investor-update.md
+```
+
+It asserts the 8 numbered categories (data room), the 7 blocks + a numeric ask (one-pager), and the 6 sections incl. a metrics table + runway line (update); and it flags placeholders (`TBD`, `XX`, `[amount]`), vague asks, and confidential financials leaking into a teaser. **Structural lint only** — persuasion, metric selection, and framing are judgement the capability eval scores, not the script.
+
+Handoffs:
+
+- `../pitch-deck/SKILL.md` — the slide narrative and story arc you consume.
+- `../financial-model/SKILL.md` — the projections, burn/runway, cap-table math you reference.
+- `../fundraising/SKILL.md` — the round strategy, investor pipeline, SAFE vs priced.
+- `../cold-outreach/SKILL.md` — the first-touch email your one-pager attaches to.
+- `../unit-economics/SKILL.md` — the LTV/CAC/payback figures you surface in the update and one-pager.
+
+## References
+
+- `references/dataroom-checklist.md` — the full 8-category, ~60-document checklist with per-stage (seed vs Series-A) inclusion flags, the file-naming/versioning convention, and the "surface first" vs "omit until ready" lists.
+- `references/update-and-onepager-templates.md` — fill-in monthly-update template (6 sections + metrics table) and one-pager template (7 blocks), each with a filled mini-example, plus the vague-ask banlist with Bad→Good rewrites.

package/skills/investor-materials/evals/README.md

@@ -0,0 +1,15 @@
+# Evals — investor-materials
+
+`cases.yaml` is read by the repo's skill-eval harness. `should_trigger` and
+`should_not_trigger` measure routing precision: each `should_trigger` prompt must load
+`investor-materials`, and each `should_not_trigger` prompt must instead route to the named
+sibling (`pitch-deck`, `financial-model`, `fundraising`, `cold-outreach`, `unit-economics`) —
+they encode the boundaries between packaging documents and building the story, the numbers, or
+the round. The `capability` case is a scenario scored by a judge model against its `must_include`
+rubric: it feeds the prompt, lets the skill generate the data-room index / one-pager / update
+bundle, and checks the rubric points are met (8 numbered categories, the dated/versioned naming
+example, the 7 one-pager blocks with a specific ask, the 6 update sections with a metrics table
+and named asks, and correct routing of deck/model work to siblings). Run it through the
+repository's standard eval command (see the repo root). The structural lint in
+`../scripts/verify.sh` is complementary — it checks the generated artifacts mechanically; the
+capability eval judges framing and metric selection, which the script deliberately does not.

package/skills/investor-materials/evals/cases.yaml

@@ -0,0 +1,60 @@
+skill: investor-materials
+
+# Prompts that MUST load `investor-materials`. The skill owns the PACKAGING and
+# CIRCULATION of fundraising documents an investor reads outside the meeting:
+# the data room, the one-pager/teaser, and the recurring investor update. It
+# does NOT own the slide story (pitch-deck), the projections (financial-model),
+# or the round strategy/pipeline (fundraising).
+should_trigger:
+  - prompt: "Set up our data room for the seed round — what folders and documents do investors expect before diligence?"
+    why: "Structuring the data room (8 numbered categories, per-stage doc counts, naming convention) is the skill's core organization job."
+
+  - prompt: "Draft this month's investor update for May."
+    why: "The recurring monthly update (6 sections, metrics table, named asks, runway line) is a primary artifact owned here."
+
+  - prompt: "Write a one-pager we can attach to cold investor emails."
+    why: "The investor one-pager/teaser (7 blocks, specific ask, no confidential financials) is owned here; cold-outreach writes the email, this writes the attachment."
+
+  - prompt: "Our data room is a disorganized mess — rename and reorganize all the files so it's not embarrassing."
+    why: "Non-obvious cleanup/organization trigger: renaming to YYYY-MM_Doc_vN and numbering the 8 categories is exactly the disorganization-is-a-deal-killer problem the skill exists to fix."
+
+  - prompt: "Set up a reusable monthly investor-update format with a metrics table we can fill in every month."
+    why: "Non-obvious: the ask is a repeatable FORMAT/system (fixed sections, fixed cadence), not a one-off email — the skill ships that template."
+
+  - prompt: "Actualización mensual a inversores y sala de datos para la ronda."
+    why: "Spanish trigger naming two core artifacts (monthly investor update + data room) — must route here regardless of language."
+
+# NEAR-MISS prompts that must NOT load `investor-materials`. Each routes to the
+# genuinely correct sibling. The recurring trap: anything about the STORY
+# (pitch-deck), the NUMBERS (financial-model), or the round STRATEGY
+# (fundraising) that merely sounds investor-adjacent.
+should_not_trigger:
+  - prompt: "Build the slide narrative and story arc for our investor pitch meeting."
+    route_to: "pitch-deck"
+    why: "The persuasive slide-by-slide story is pitch-deck; investor-materials only packages the deck it produces, it does not build the narrative."
+
+  - prompt: "Build our 3-year revenue projection and burn/runway spreadsheet with the cap-table math."
+    route_to: "financial-model"
+    why: "The projection spreadsheet and cap-table math are financial-model; investor-materials surfaces the model in the data room but does not author it."
+
+  - prompt: "Help me build my investor target list and decide between a SAFE and a priced round."
+    route_to: "fundraising"
+    why: "Investor pipeline and round mechanics (SAFE vs priced, term sheet) are fundraising strategy, not document packaging."
+
+  - prompt: "Write the cold email to this specific VC partner to get her to take a meeting."
+    route_to: "cold-outreach"
+    why: "The first-touch email to a named investor is cold-outreach; investor-materials produces the one-pager that email attaches, not the email."
+
+  - prompt: "Calculate our LTV/CAC and payback period so I know if the unit economics work."
+    route_to: "unit-economics"
+    why: "LTV/CAC/payback analysis is unit-economics; investor-materials only surfaces the resulting figures in the update or one-pager."
+
+# Capability: a realistic end-to-end task scored by a judge against the rubric.
+capability:
+  - scenario: "A seed-stage SaaS founder already has a pitch deck and a financial model and current metrics ($42k MRR, growing). They ask for a complete data-room index, an investor one-pager for cold outreach, and this month's investor update."
+    must_include:
+      - "A data-room index listing all 8 numbered categories (01 Corporate through 08 Tax) with per-stage doc counts (seed ~30–40)."
+      - "The file-naming/versioning convention shown with a concrete dated, versioned example (e.g. 2026-03_Financial-Model_v4.xlsx)."
+      - "A one-pager with all 7 blocks (headline, problem, solution, traction, market TAM/SAM/SOM, team, ask) and a SPECIFIC funding ask stating amount and use of funds; the teaser version omits confidential P&L / full cap table."
+      - "An investor update with the 6 sections, a metrics table comparing actual vs target vs prior period, each challenge PAIRED with a solution/learning, and NAMED asks (a specific intro/role/company, not 'let me know if you can help'), plus a cash/runway line."
+      - "Correctly routes deck-building to pitch-deck and projection-building to financial-model instead of producing them here."

package/skills/investor-materials/references/dataroom-checklist.md

@@ -0,0 +1,134 @@
+# Data room — the 8-category checklist
+
+The reference list behind the SKILL.md data-room section. A complete room is ~50–70 documents
+across 8 numbered categories. **Seed** rooms skew 30–40 docs; **Series A** rooms 55–70. The
+inclusion flag tells you what to include at each stage so you neither under-build (looks
+unprepared) nor over-build (drafts dilute focus).
+
+- ✅ = include at this stage  · ◐ = include if it exists / if material · — = usually omit at this stage
+
+## File-naming & versioning convention
+
+Every file: `YYYY-MM_Doc-Name_vN.ext`, inside its numbered category folder.
+
+```text
+07_CapTable_Equity/2026-03_Cap-Table_v2.xlsx
+02_Financial/2026-03_Financial-Model_v4.xlsx
+07_CapTable_Equity/2026-02_SAFE-AngelRound_v1.pdf
+```
+
+- **Date** (`YYYY-MM`) so recency is obvious — investors diligence the newest file as truth.
+- **Version** (`vN`) so a superseded draft is never mistaken for current.
+- **Hyphenate** the doc name (no spaces, no `(2)`, no `FINAL_FINAL`).
+- One **current** version visible per doc; archive prior versions in a `_archive/` subfolder, not loose.
+
+## 01 — Corporate
+
+| Document | Seed | Series A |
+| --- | --- | --- |
+| Certificate of incorporation / formation | ✅ | ✅ |
+| Bylaws / operating agreement | ✅ | ✅ |
+| Board consents & minutes | ◐ | ✅ |
+| Shareholder / founder agreements | ✅ | ✅ |
+| Cap table summary (full detail in 07) | ✅ | ✅ |
+| Prior financing docs (SAFE/note/round) | ◐ | ✅ |
+
+## 02 — Financial
+
+| Document | Seed | Series A |
+| --- | --- | --- |
+| Financial model (3-statement projection) | ✅ | ✅ |
+| Historical P&L | ◐ | ✅ |
+| Balance sheet | ◐ | ✅ |
+| Cash-flow statement | — | ✅ |
+| Bank statements (recent 3–6 mo) | ◐ | ✅ |
+| Burn & runway summary | ✅ | ✅ |
+| Budget vs actuals | — | ✅ |
+
+> The financial model is built by `financial-model`; you reference and surface it, you do not author it.
+
+## 03 — Legal & contracts
+
+| Document | Seed | Series A |
+| --- | --- | --- |
+| Customer contracts / key MSAs | ◐ | ✅ |
+| Supplier / vendor agreements | — | ◐ |
+| NDAs & key partnership agreements | ◐ | ✅ |
+| Office / equipment leases | ◐ | ✅ |
+| Litigation log (or "none" attestation) | ✅ | ✅ |
+| Insurance policies | — | ◐ |
+
+## 04 — IP
+
+| Document | Seed | Series A |
+| --- | --- | --- |
+| Trademark registrations / applications | ◐ | ✅ |
+| Patents / provisional filings | ◐ | ◐ |
+| Domain & brand-asset list | ✅ | ✅ |
+| IP-assignment agreements (founders + contractors) | ✅ | ✅ |
+| Open-source / license inventory | — | ◐ |
+
+## 05 — Team & HR
+
+| Document | Seed | Series A |
+| --- | --- | --- |
+| Org chart | ✅ | ✅ |
+| Founder employment & vesting agreements | ✅ | ✅ |
+| Key employment agreements | ◐ | ✅ |
+| Option plan & grant ledger | ◐ | ✅ |
+| Contractor / advisor agreements | ◐ | ✅ |
+| Hiring plan | ✅ | ✅ |
+
+## 06 — Product & metrics
+
+| Document | Seed | Series A |
+| --- | --- | --- |
+| Product overview / one-pager | ✅ | ✅ |
+| Roadmap | ✅ | ✅ |
+| KPI dashboard (current metrics) | ✅ | ✅ |
+| Cohort / retention data | ◐ | ✅ |
+| Pipeline / sales data | ◐ | ✅ |
+| Technical / security overview | — | ◐ |
+
+## 07 — Cap table & equity
+
+| Document | Seed | Series A |
+| --- | --- | --- |
+| Cap table (fully diluted) | ✅ | ✅ |
+| SAFEs / convertible notes | ✅ | ✅ |
+| Prior round legal docs | ◐ | ✅ |
+| Option pool details | ◐ | ✅ |
+| 409A valuation | — | ◐ |
+
+> Investors spend 8–12 minutes here alone. Make the cap table and SAFEs current, clean, and impossible to miss.
+
+## 08 — Tax & compliance
+
+| Document | Seed | Series A |
+| --- | --- | --- |
+| Tax filings / returns | ◐ | ✅ |
+| Business registrations & licenses | ✅ | ✅ |
+| R&D / tax-credit filings | — | ◐ |
+| Regulatory / compliance certificates | — | ◐ |
+| Data-protection / GDPR posture | ◐ | ◐ |
+
+## Surface first vs omit until ready
+
+**Surface first** (most-scrutinized — current version, impossible to miss):
+
+- Cap table (07) and SAFEs / convertibles (07)
+- Financial model (02)
+- KPI dashboard (06)
+
+**Omit until ready** (a draft here is worse than its absence):
+
+- Half-finished contracts, unsigned agreements, placeholder tax folders.
+- A note ("available on request") beats an empty or stub file.
+- Anything you would not want diligenced as final.
+
+## Sharing & analytics
+
+- One **access link per investor** (DocSend-style) — not a public folder.
+- Read the analytics: who opened what, time-per-page, whether it was forwarded.
+- Use drop-off to fix weak materials; use warmth signals to prioritize follow-up.
+- You advise this practice and read the data; building the VDR tooling is out of scope.

package/skills/investor-materials/references/update-and-onepager-templates.md

@@ -0,0 +1,152 @@
+# Templates — investor update & one-pager
+
+Fill-in templates with filled mini-examples, plus the vague-ask banlist. Keep the structure;
+replace the bracketed content. Strip every bracket before shipping — `scripts/verify.sh` flags
+leftover placeholders.
+
+## Monthly investor update (6 sections, ~250 words)
+
+```text
+Subject: [Company] Investor Update — [Month Year]
+
+Hi all,
+
+HEADLINE
+[One sentence: the month in a line — the single thing that mattered.]
+
+HIGHLIGHTS
+- [Win 1 — specific, with a number]
+- [Win 2]
+- [Win 3]
+(3–5 bullets max)
+
+METRICS
+| Metric        | This month | Target | Last month |
+| ------------- | ---------- | ------ | ---------- |
+| [KPI 1]       | [actual]   | [tgt]  | [prior]    |
+| [KPI 2]       | [actual]   | [tgt]  | [prior]    |
+| [KPI 3]       | [actual]   | [tgt]  | [prior]    |
+| Cash runway   | [N] mo     | —      | [N] mo     |
+
+CHALLENGES
+- [Challenge 1] — fix: [what you're doing about it]
+- [Challenge 2] — learning: [what it taught you]
+(each challenge PAIRED with a solution or learning — never naked)
+
+ASKS
+- [Named, specific: "intro to a [role] at [company type]" — not "let me know"]
+- [Hiring/partnership ask if any]
+
+CASH / RUNWAY
+Cash: $[X]. Monthly burn: $[Y]. Runway: [N] months.
+
+Thanks,
+[Founder]
+```
+
+### Filled mini-example
+
+```text
+Subject: Tabl Investor Update — May 2026
+
+Hi all,
+
+HEADLINE
+Crossed $42k MRR and signed our first two restaurant groups — both upsells from single-location pilots.
+
+HIGHLIGHTS
+- MRR $38k → $42k (+11%); two multi-location upgrades drove it.
+- Shipped the payroll-export integration; cut customer onboarding from 9 days to 3.
+- Hired our first AE, starting June.
+
+METRICS
+| Metric        | This month | Target | Last month |
+| ------------- | ---------- | ------ | ---------- |
+| MRR           | $42k       | $45k   | $38k       |
+| New logos     | 7          | 8      | 5          |
+| Net churn     | 1.2%       | <2%    | 1.8%       |
+| Cash runway   | 14 mo      | —      | 15 mo      |
+
+CHALLENGES
+- Sales cycle stretched to 70 days — fix: added a security-review pack to the deck; two stalled deals re-accelerated.
+- Support load spiked with the new integration — learning: shipped 6 help-center articles, ticket volume already down 30%.
+
+ASKS
+- Warm intro to a Head of RevOps at a 200+ seat Series-B SaaS — building our outbound playbook.
+- Know a senior backend eng open to seed-stage? Hiring our second engineer in Q3.
+
+CASH / RUNWAY
+Cash: $580k. Monthly burn: $41k. Runway: 14 months.
+
+Thanks,
+Mara
+```
+
+## Investor one-pager (7 blocks)
+
+```text
+[COMPANY] — [one-line: what you do, for whom]
+
+PROBLEM
+[The pain, sized and concrete — who suffers it and how much it costs them.]
+
+SOLUTION
+[Your product in one or two lines — what it is and how it works.]
+
+TRACTION
+- [Metric 1 — MRR / ARR]
+- [Metric 2 — growth %]
+- [Metric 3 — logos / users / retention]
+
+MARKET
+TAM [$X] · SAM [$Y] · SOM [$Z you can realistically win]
+
+TEAM
+[Why THIS team wins THIS market — the unfair advantage, prior wins, domain depth.]
+
+THE ASK
+Raising [$amount] [round] — [use of funds + milestone it buys].
+```
+
+- **Pre-revenue:** move **TEAM** above **TRACTION** — lead with the strongest card.
+- **Post-traction:** keep **TRACTION** near the top.
+- **Teaser variant:** identical blocks, but NO confidential P&L, full cap table, or named customer financials — those live behind the data-room link.
+
+### Filled mini-example
+
+```text
+TABL — Payroll & scheduling for multi-location restaurant groups
+
+PROBLEM
+Restaurant groups run payroll across 5–50 locations on spreadsheets and 3 disconnected tools;
+weekly close takes a manager 6+ hours and errors trigger compliance penalties.
+
+SOLUTION
+Tabl unifies scheduling, time-tracking, and payroll into one system; weekly close drops to 20 minutes.
+
+TRACTION
+- $42k MRR, +11% MoM, $500k ARR run-rate
+- 38 restaurant groups, 1.2% net monthly churn
+- 3-day onboarding (down from 9)
+
+MARKET
+TAM $14B (US restaurant payroll) · SAM $3.1B (multi-location groups) · SOM $180M (target segments, 3yr)
+
+TEAM
+Founders ran payroll ops for a 120-location franchise; CTO built scheduling at [prior co], 2 prior exits between them.
+
+THE ASK
+Raising $1.5M seed — 18-month runway: 4 engineering hires, 2 GTM hires, to reach $1M ARR.
+```
+
+## Vague-ask banlist (Bad → Good)
+
+Vague asks get ignored; named asks convert passive backers to active allies. Never ship the left column.
+
+| Bad (vague) | Good (named, specific) |
+| --- | --- |
+| "Let me know if you can help with anything." | "Warm intro to a Head of RevOps at a 200+ seat Series-B SaaS." |
+| "Any introductions appreciated." | "Intro to the VP Sales at Acme — we're a fit for their Q3 vendor review." |
+| "We're hiring, spread the word." | "Hiring a senior backend eng (Go/Postgres) — who do you rate and would intro?" |
+| "Feedback welcome." | "Would value 20 min on our pricing-tier change before we ship it June 15." |
+| "Help us grow!" | "Two enterprise logos would unlock our Series A story — who do you know at [segment]?" |