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.
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.
Act as a pragmatic early-stage founder advisor. The task is designing a pricing experiment for an early product. Context: [current price, cost to serve, competitor range, customer segments, monthly signups].
1. Pick the one pricing variable to test and say why.
2. Design the test cells and the minimum sample I need.
3. Write the grandfathering rule for existing customers.
4. Define the metric and the date I will decide.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Have the hard conversation before the hard moment.
Act as a pragmatic early-stage founder advisor. The task is drafting a co-founder expectations discussion guide. Context: [roles as we see them, equity split status, time commitments, decision deadlocks so far].
1. List the ten questions that prevent most founder breakups.
2. Cover equity vesting, exits, salary and what happens if one leaves.
3. Script how to raise a resentment early.
4. End with the three decisions we must write down and sign.
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 planning how to land the first ten customers. Context: [what I sell, where those customers gather, my unfair access, weekly hours available].
1. List five channels ranked by my unfair advantage.
2. Write the exact outreach or pitch for the top two.
3. Define the offer that makes saying yes easy now.
4. Set the weekly activity number that makes ten inevitable.
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 preparing answers for tough pitch Q&A. Context: [my deck contents, weakest metric, toughest competitor, round and ask].
1. Write the twelve hardest questions for this specific deck.
2. Draft 30-second answers that concede the real risk then reframe.
3. Flag which answers need a number I must pull.
4. Script the honest "we do not know yet" line that builds trust.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Stretch the months you have without stalling growth.
Act as a pragmatic early-stage founder advisor. The task is triaging expenses to extend runway. Context: [monthly burn breakdown, current runway months, revenue trend, team size].
1. Sort expenses into cut now, renegotiate, and untouchable with reasons.
2. Estimate months gained per cut so trade-offs are visible.
3. Script the two hardest conversations the cuts require.
4. Define the revenue or funding milestone that ends austerity.
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 planning the first hire for an early startup. Context: [what is breaking without this hire, budget, must-have skills, my management experience].
1. Write the role as outcomes for the first 90 days.
2. Separate must-haves from trainable gaps.
3. Design a paid trial task that mirrors the real work.
4. List what I must personally stop doing once they start.
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 structuring a pivot-or-persist decision. Context: [what we believed, what the data shows, runway left, what the team wants to build].
1. Restate the original hypothesis and the evidence against it.
2. List the three strongest pivot candidates from what we learned.
3. Score each on evidence, founder energy and runway fit.
4. Write the kill criteria so this decision does not reopen weekly.
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 building a launch day runbook. Context: [what is launching, channels planned, rollback options, who is on call].
1. List every asset and owner with a due time, hour by hour.
2. Include the rollback trigger and who can call it.
3. Draft the three messages ready to post or send.
4. Plan the week-after follow-up so launch is a start, not an event.
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.