Skip to content

founder-brief.template.md

Latest commit

 

History

History
81 lines (54 loc) · 3.09 KB

founder-brief.template.md

File metadata and controls

81 lines (54 loc) · 3.09 KB
Raw

Founder brief

Your agent reads this before every GTM skill, so its advice is about your actual business, not a textbook. Copy this file to docs/gtm-cofounder/founder-brief.md in your project (or let the start-here skill fill it in by interviewing you).

Answer the core five to begin. That is enough to get a diagnosis and a roadmap. The "Go deeper" questions are optional: fill them in over time, or let each skill ask for the ones it needs. Tag each answer [validated] (a real user who is not a friend told you) or [assumption] (your best guess for now). Assumptions are fine to start with. Send them to the talk-to-users skill to make them real.

Core five (answer these first)

  1. In one plain sentence, no jargon, what does it do?

  2. Who exactly is it for? (role, company size and shape, technical context)

    [validated | assumption]

  3. What do they use today instead, and why you over that?

    [validated | assumption]

  4. Stage and traction: how many users, and do they come back?

  5. Your single strongest asset: the most powerful, provable thing you have (a marquee logo, a hard number, a real user quote, a live demand signal).

Go deeper (optional, answer anytime)

Skip these to start. Each question notes what answering it unlocks, so you only invest where you want the payoff.

Positioning and story

  • What painful problem does it kill, in the user's own words? (becomes your homepage headline and the stakes in your story)

    [validated | assumption]

  • What trend is making that pain worse right now? (this is your villain, what gives your positioning urgency)

    [validated | assumption]

  • What does your homepage or repo description say today? (paste the actual line, not a paraphrase) (lets the agent sharpen what you have instead of guessing it)

Buyers and pricing

  • Who pays, if that is a different person from who adopts? (lets the agent design pricing and a sales motion aimed at the real buyer)

    [validated | assumption]

  • Who is it clearly NOT for? (a sharp "not for" makes your ICP believable)

  • The job they hire it for: When [situation], I want to [motivation], so I can [outcome]. (becomes your value proposition)

    [validated | assumption]

Distribution and motion

  • Motion: open source / PLG / inbound / sales-led / unsure? (picks which channels and tactics fit you)

  • Where do your users already hang out and discover tools? (tells us where to launch and find your first users)

Focus

  • What are you deliberately saying no to right now? (the roadmap you're protecting, the requests you turn down) (keeps the agent from recommending work you've ruled out)

Evidence (be honest, this is the whole point)

  • Which known companies or notable developers already use it, that you can name? (your strongest proof)

  • How many real users have you interviewed who are not friends? (tells the agent how much is validated versus guessed)

  • Which answers above are still assumptions? List them, then run talk-to-users. (routes the guesses to real evidence)