Readiness packages
The investor, acquisition, and client packages — generated from your recorded evidence, gate-checked, and downloadable.
Packages are the reason the evidence engine exists: the investor deck,
acquisition profile, client report, and their siblings are GENERATED from
your product's recorded evidence — measured figures labeled measured,
declared input labeled declared, and every gap printed as an honest
[bracket] instead of invented prose.
What's in a pack
Every audience has its own generator, all reading the same evidence engine:
- Investor — deck, memo, one-pager, diligence data room, pitch prep, YC application, demo script. Traction sections are measured-only: a slide that must never lie.
- Acquisition — buyer-thesis profile with revenue quality, retention concentration, true unit economics, and a valuation framework (the 2–4× SDE band, labeled a heuristic — never an appraisal). One-time products are valued on their trailing-sales table instead; the fork is explicit.
- Client — the branded report for the people paying you: what we're building and how the results are measured.
- Exit — Sell-My-SaaS listing, M&A CIM skeleton, and the transfer checklists.
How generation works
- Earn the gate. Generating requires the matching readiness gate to be open — the deck can't be ahead of the evidence. The gate card shows exactly which requirements are missing and where to record them.
- Generate. Each render is deterministic (same evidence → same pack) and costs credits — listed on the button before you click. A render that fails after charging auto-refunds through the wallet ledger.
- View & download. Packs render in-app (Markdown → PDF) and download as XLSX financials and PPTX decks where the audience expects files.
- Regenerate as you grow. Every render stores a snapshot of the figures it was built from, so the app can show you what changed since your last pack — readiness, MRR, customers, scorecard. Recipients never see the delta; the pack stays a point-in-time artifact.
Sending to people (v1)
Today's loop is create · view · download. Delivery to people — assigning packs to stakeholders and sending them — is admin-only while the Portal Manager becomes the real delivery surface in a later release. When a metered generation throws, your credits refund automatically; deliberate warnings (like a receipt note on a send) never refund, because the work succeeded.