Investor ops
Two-phase investor workflow: (1) build investor materials — pitch decks, one-pagers, memos, financial models, and accelerator applications, all anchored to a single source of truth; (2) write investor outreach — cold emails, warm intro blurbs, follow-ups, and update emails that are short, concrete, and personalized. Incorporates former: investor-materials, investor-outreach.From its SKILL.md
npx -y skills add asong56/skills --skill investor-opsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
5.3 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it
Investor Ops
Two sequential phases. Run Phase 1 to create the materials. Run Phase 2 to deploy them via outreach.
Phase 1 — Investor Materials
Build investor-facing materials that are consistent, credible, and easy to defend.
When to Use
- 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.
- 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
- Inventory the canonical facts.
- Identify missing assumptions.
- Choose the asset type.
- Draft the asset with explicit logic.
- Cross-check every number against the source of truth.
Asset Guidance
Pitch Deck — recommended flow: company + wedge → problem → solution → product/demo → market → business model → traction → team → competition/differentiation → ask → use of funds/milestones → appendix. For web-native decks, pair with frontend-slides.
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 where useful, clean layer-by-layer revenue logic, milestone-linked spending, and 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.
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.
Phase 2 — Investor Outreach
Write investor communication that is short, concrete, and easy to act on.
When to Use
- Writing a cold email to an investor.
- Drafting a warm intro request.
- Sending follow-ups after a meeting or no response.
- Writing investor updates during a process.
- Tailoring outreach based on fund thesis or partner fit.
Core Rules
- Personalize every outbound message.
- Keep the ask low-friction.
- Use proof instead of adjectives.
- Stay concise.
- Never send copy that could go to any investor.
Voice Handling
If the user's voice matters, run brand-voice first and reuse its VOICE PROFILE. This phase keeps investor-specific structure and ask discipline — it does not recreate a parallel voice system.
Hard Bans
Delete and rewrite any of these:
- "I'd love to connect"
- "excited to share"
- Generic thesis praise without a real tie-in
- Vague founder adjectives
- Begging language
- Soft closing questions when a direct ask is clearer
Cold Email Structure
- Subject line: short and specific.
- Opener: why this investor specifically.
- Pitch: what the company does, why now, and what proof matters.
- Ask: one concrete next step.
- Sign-off: name, role, and one credibility anchor if needed.
Personalization Sources
Reference one or more of: relevant portfolio companies; a public thesis, talk, post, or article; a mutual connection; a clear market or product fit. If context is missing, state that the draft still needs personalization.
Follow-Up Cadence
Default:
- Day 0: initial outbound.
- Day 4 or 5: short follow-up with one new data point.
- Day 10–12: final follow-up with a clean close.
Do not keep nudging after that unless the user wants a longer sequence.
Warm Intro Requests
Make life easy for the connector: explain why the intro is a fit; include a forwardable blurb; keep the forwardable blurb under 100 words.
Post-Meeting Updates
Include: the specific thing discussed; the answer or update promised; one new proof point if available; the next step.
Quality Gate
Before delivering: the message is genuinely personalized; the ask is explicit; the proof point is concrete; filler praise and softener language are gone; word count stays tight.
Migration Notes
| Deprecated skill | Replaced by | Phase |
|---|---|---|
investor-materials | investor-ops | Phase 1 |
investor-outreach | investor-ops | Phase 2 |
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.