What this prompt does
This prompt assigns the AI a senior startup operator role and makes it write an investor one-pager tight enough to send, with honest numbers and zero hype. You provide the [company], [stage], [key_metrics], and [the_ask]. It returns a two-sentence problem and solution, a market size with sourced TAM, SAM, and SOM and the method behind each, traction drawn from your metrics, product differentiation stated as what only you can do, team highlights tied to why this team wins, and the raise with a use-of-funds breakdown — under 600 words.
The structure works because it forces specificity where vagueness loses investors. By pulling traction directly from [key_metrics] — MRR, growth, retention, CAC, LTV — and asking for the method behind each market-size number, the prompt produces figures an operator can defend. [stage] calibrates expectations for the round, and [the_ask] anchors the use-of-funds. The regulator-clean tone keeps it from drifting into the pitch-deck superlatives investors discount.
When to use it
- You need a one-pager that reads like an operator wrote it, not a hype deck.
- You are raising and want traction metrics stated honestly and specifically.
- You want TAM, SAM, and SOM with the method behind each, not a hand-waved number.
- You need differentiation framed as what only you can do.
- You want a use-of-funds breakdown tied to the actual raise.
- You want the whole thing tight, under 600 words, and regulator-clean in tone.
Example output
You get a single document under 600 words: a two-sentence problem and solution, a sourced TAM/SAM/SOM with each method shown, traction from your metrics (MRR, growth, retention, CAC, LTV), differentiation stated as what only you can do, team highlights tied to why this team wins, and the raise with a use-of-funds breakdown — in a tight, regulator-clean tone.
Pro tips
- Make
[key_metrics]specific or leave them out; investors forgive small numbers but not vague ones, and the traction section leans entirely on these. - Set
[stage]accurately so the expectations and the depth of the ask match the round you are actually raising. - Tie
[the_ask]to a real use-of-funds plan, since a number with no allocation reads as guesswork. - Keep the differentiation concrete — "what only you can do" beats a list of features anyone could claim.
- Verify the TAM/SAM/SOM method the model proposes; sourced reasoning is the point, and an unsupported figure undercuts the rest of the page.
- Tie the team highlights to why this specific team wins, rather than listing titles, since investors back the people as much as the numbers.
- Trim toward the 600-word cap so the page stays scannable and an investor can read it in one sitting without losing the thread.
