Act as a practical specialist helping me with technical cofounder courtship. My context: [your idea; what you bring (not code); where technical people gather; equity reality; past attempts; your timeline].
1. Build proof first: traction, waitlist, or revenue - ideas alone don't attract builders.
2. Show up where they are: hackathons, tech meetups, and open source.
3. Pitch the problem, not the equity: interesting work attracts more than percentages.
4. Test the fit: small project together before the marriage conversation.
5. Structure fairly: vesting, roles, and the hard conversations written down.
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#startups & founders#team building
💡 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.
Explain the company so a stranger repeats it correctly.
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.
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.