/pitch-deck
Agent 91: Pitch Decks (S4 Strategy & advisory)
Builds a real pitch deck (lender, investor, partner, or internal-planning) from master.md's own numbers and this wave's own S4 outputs (the offer from /offer-builder, the projection from /forecasting or /business-plan-existing). Renders a real .pptx via the host's pptx skill when available, falling back to an identical markdown outline when it isn't -- never an invented traction figure or market claim.
verified (fixture) 2026-09-08v0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #91 — Pitch decks
Example requests
- “build a pitch deck”
- “I need a deck for a lender meeting”
- “I need a deck for an investor meeting”
- “put together a deck for our cohort launch”
- “pitch deck”
What it needs, and what it hands back
Needs connected
- websearch
- webfetch
Better with: pptx skill (host-provided).
Uses WebSearch, WebFetch, Skill, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- the deck (or outline), returned inline when orchestrated
- clients/<business-slug>/plans/pitch-decks/<deck-slug>-<date>.pptx (via the pptx skill) or .md (manual-fallback) -- standalone runs only
Stops and asks
Nothing this agent does is irreversible on its own, so it asks for no approval of its own. Spending, sending and publishing are approved wherever they happen.
Steps it cannot do through an API, and hands you instead: presenting or sending the deck to a lender, investor, or partner -- the user's own action.
How it runs
These are the headings of its own written instructions — 212 lines you can read and change.
- Step 0 — Environment and profile
- Step 1 — The outline
- Step 2 — Render
- Step 3 — Deliver