# Investor Materials

> Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, fundraising materials, and investor outreach (cold emails, warm intro blurbs, follow-ups). Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, outreach or follow-up emails to angels/VCs/accelerators, or materials that must stay internally consistent across multiple fundraising assets.

- Skill: `davie521/investor-materials` (Agent Skill)
- Install (CLI): `npx skillmds@latest add davie521/investor-materials`
- Raw SKILL.md: https://api.skillmd.com/api/skills/davie521/investor-materials/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Davie521 (https://skillmd.com/u/davie521)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/davie521/investor-materials

---


# Investor Materials

Build investor-facing materials that are consistent, credible, and easy to defend.

## When to Activate

- creating or revising a pitch deck
- writing an investor memo or one-pager
- building a financial model, milestone plan, or use-of-funds table
- answering accelerator or incubator application questions
- writing cold emails, warm intro requests, or follow-ups to investors
- aligning multiple fundraising docs around one source of truth

## Golden Rule

All investor materials must agree with each other.

Create or confirm a single source of truth before writing:
- traction metrics
- pricing and revenue assumptions
- raise size and instrument
- use of funds
- team bios and titles
- milestones and timelines

If conflicting numbers appear, stop and resolve them before drafting.

## Core Workflow

1. inventory the canonical facts
2. identify missing assumptions
3. choose the asset type
4. draft the asset with explicit logic
5. cross-check every number against the source of truth

## Asset Guidance

### Pitch Deck
Recommended flow:
1. company + wedge
2. problem
3. solution
4. product / demo
5. market
6. business model
7. traction
8. team
9. competition / differentiation
10. ask
11. use of funds / milestones
12. appendix

If the user wants a web-native deck, build it as a self-contained HTML slide page.

### One-Pager / Memo
- state what the company does in one clean sentence
- show why now
- include traction and proof points early
- make the ask precise
- keep claims easy to verify

### Financial Model
Include:
- explicit assumptions
- bear / base / bull cases when useful
- clean layer-by-layer revenue logic
- milestone-linked spending
- sensitivity analysis where the decision hinges on assumptions

### Accelerator Applications
- answer the exact question asked
- prioritize traction, insight, and team advantage
- avoid puffery
- keep internal metrics consistent with the deck and model

### Outreach
Cold emails, warm intros, and follow-ups reuse the same source of truth. Beyond the obvious (personalize, one concrete ask, proof over adjectives):
- follow-up cadence: day 0 outbound, day 4-5 short follow-up with one new data point, day 10-12 final follow-up with a clean close — then stop unless the user wants a longer sequence
- warm intro requests: include a forwardable blurb, and keep it under 100 words

## Red Flags to Avoid

- unverifiable claims
- fuzzy market sizing without assumptions
- inconsistent team roles or titles
- revenue math that does not sum cleanly
- inflated certainty where assumptions are fragile

## Quality Gate

Before delivering:
- every number matches the current source of truth
- use of funds and revenue layers sum correctly
- assumptions are visible, not buried
- the story is clear without hype language
- the final asset is defensible in a partner meeting