Draft an investor narrative with disciplined assumptions
Use only information supplied in the conversation and this skill text. Do not browse, call tools, inspect files, execute code, create artifacts, or take external actions. Return the work directly in chat. Attribute material claims to supplied source labels or quotations; a pasted URL is a source label, not evidence that its contents were checked. Distinguish supplied facts, reasonable interpretations, proposals, and unknowns.
Inputs and scope: Identify the requested format, audience, fundraising stage, company proposition, customer evidence, business model, traction, team facts, funding ask, use of proceeds, and supplied assumptions or metrics. If a decision-changing input is absent, ask the smallest useful question and complete the portions supported by available material. State assumptions explicitly; do not manufacture facts, approvals, dates, or completion evidence.
Method 1. Define the investment argument in plain language: what problem matters, why this approach could win, and what evidence supports the next stage. Separate a compelling narrative from claims of inevitability. 2. Build a source-backed fact sheet before drafting. Preserve dates, metric definitions, cohorts, revenue versus bookings, paid versus free customers, and historical actuals versus forecasts. 3. Resolve material inconsistencies or keep them visible. Do not choose the larger growth number for rhetorical effect, merge incompatible recurring-revenue measures, or turn a target into achieved traction. 4. Construct the narrative in an order suited to the format: problem, customer, solution, evidence, market context supplied, business model, competitive position, team, plan, and ask. Omit unsupported sections or label evidence gaps instead of inventing market facts. 5. Translate the narrative into concise slide copy, memo prose, or direct application answers. Use small in-chat assumption tables for price, volume, cost, runway basis, or milestones; no rendered deck or financial workbook is produced. 6. Connect the funding request to specific proposed uses and milestones, including dependencies and uncertainty. Finish with investor questions the current evidence may invite and the few revisions that would most improve credibility.
Output: Return the requested narrative or slide-by-slide copy, a claims-and-assumptions table, unresolved metric conflicts, and anticipated investor questions.
Quality checks: Check arithmetic on small supplied figures, consistent periods, credible milestones, permission-sensitive customer references, and whether each strong claim has support. Distinguish ambition from forecast and evidence from advocacy.
Worked example: A company reports $20,000 monthly recurring revenue in June and $300,000 annual bookings, including setup fees. Present them separately; do not call bookings ARR. If the ask is $500,000 for hiring and expansion but no cost breakdown exists, draft the use-of-proceeds narrative as a proposal with missing allocation, not a calculated runway claim.