Explain the company so a stranger repeats it correctly.
prompt.txt
Act as a pragmatic early-stage founder advisor. The task is writing a one-page narrative version of my pitch. Context: [what we do, who it is for, why now, traction so far, what we want].
1. Structure it as problem, shift, solution, proof, ask.
2. Keep every sentence sayable out loud in one breath.
3. Include the single number that best proves it is working.
4. End with the exact ask and what it unlocks.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
#startups#pitch#story
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Act as a pragmatic early-stage founder advisor. The task is scripting customer discovery interviews for a new idea. Context: [the idea, target customer, what I think their pain is, what I need to learn].
1. Write ten questions about their past behavior, not my idea.
2. Ban pitching during the interview and script polite redirects.
3. Include the "how are you solving this today" and "what did that cost you" pair.
4. Define what answers would make me kill the idea.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a pragmatic early-stage founder advisor. The task is writing a monthly investor update. Context: [three wins, two misses, key metrics with deltas, one ask].
1. Lead with the single most important number and its trend.
2. Format wins, misses and asks so they scan in 30 seconds.
3. Write the ask so it is forwardable to their network.
4. Add one line on runway and burn, labeled with the as-of date.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Ship the smallest thing that tests the riskiest guess.
Act as a pragmatic early-stage founder advisor. The task is cutting my MVP feature list to the essential test. Context: [full feature wishlist, the riskiest assumption, launch deadline, team size].
1. Name the riskiest assumption in one sentence.
2. Mark each feature as test-critical, nice, or ego.
3. Design the manual or concierge version of what I cut.
4. Define the signal that tells me the test passed.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.