Craft brand narrative and founder story

Craft brand narrative and founder origin story into usable scripts

Founders and marketing teams who need a coherent narrative and proof strategy for website, pitch, and team alignment — not a full launch campaign.

• · Company/product: what it is + who it's for (1-3 sentences)
• · Primary audience + setting (customers, investors, partners, press)
• · Primary channel(s) (website, deck/pitch, talk, social)
• · Desired perception (3-5 adjectives: trustworthy, modern, scrappy, etc.)
• · Story raw material (key events, constraints, before/after, proof points)
• · Constraints (taboo words, compliance/claims rules, tone/voice)

• · Context snapshot
• · Brand perception target (purpose + positioning + personality)
• · Story brief (type + core message + five-second moment + stakes + CTA)
• · Story scripts (2-minute + 30-second + website paragraph)
• · Narrative beat map + proof bank (claims → proof → emotions → CTA)
• · Build-in-public + distribution plan (pillars, cadence, owners, guardrails)
• · Pithy answers + Q&A bank (top questions + crisp responses)
• · Risks / Open questions / Next steps

• · Company/product description available
• · Primary audience clearly defined
• · Primary channel(s) chosen (at least 1)
• · Desired perception articulated (3-5 adjectives)

• · Story lacks a specific five-second moment (stays generic)
• · Brand perception target is too generic (applies to many brands)
• · Proof points don't connect emotionally to narrative (facts without resonance)
• · Build-in-public plan unsustainable (founder capacity underestimated)
• · Cannot verify claims without research (skill fabricates facts if asked)
• · Compliance/regulated claims made without expert review

• · Intake process asks up to 5 clarifying questions (explicit missing-info strategy)
• · Story anchored to single five-second moment (memorable, specific)
• · Rejects generic claims ('making Web3 easier' not allowed)
• · Proof bank ties specific proof points to narrative claims
• · Q&A bank for fundraising/press/keynotes (pithy, rehearsed responses)
• · Guardrails for build-in-public (what to avoid, when to hold back)