Discovery SOP Addition: Concept Brief Output After Transcript Analysis - Create the Concept Brief Once you've identified the lead magnet opportunity from transcripts, create this brief to hand off to the Micro Magnet Generator:
THE CONCEPT BRIEF TEMPLATE Copy and fill this out after discovery: CONCEPT BRIEF FOR MICRO MAGNET
- PROBLEM STATEMENT
- The expensive problem: [Specific issue costing time/money/relationships]
- Pattern frequency: [Seen in X+ clients in past Y timeframe]
- Current approach: [What they're doing now that doesn't work]
- Actual cost: [X hours per incident / $Y per month / Z% of revenue]
- YOUR UNIQUE ANGLE
- The truth they're missing: [One sentence - the insight only you see]
- Your framework name: [The [Number] [Method] Protocol/System/Framework™]
- Why this happens: [Root cause they don't recognize]
- TARGET AUDIENCE
- Who specifically: [B2B service providers/consultants/entrepreneurs]
- Their context: [Team size, service type, delivery model, revenue level]
- Pathway served: [Offer/Time/Pipeline - pick primary]
- SOLUTION PREVIEW
- Core framework: [3-5 steps with names]
- Immediate win: [What they fix in first 24 hours]
- Systematic need: [Why one-off fix isn't enough]
- NATURAL EXTENSIONS
- $7 toolkit potential: [Pick ONE direction, list 2-3 options]
- Option 1: [specific toolkit idea with components]
- Option 2: [different angle toolkit]
- Option 3: [another approach toolkit]
- Workshop angle: [Pick ONE focus for 90 minutes, list 2-3 options]
- Option 1: [specific implementation focus]
- Option 2: [different aspect to workshop]
- Option 3: [another angle to explore]
- Sprint connection: [Which pathway, what transformation] Example Brief (From Feedback Discovery) CONCEPT BRIEF FOR MICRO MAGNET
- PROBLEM STATEMENT
- The expensive problem: Getting useless client feedback (comma edits when need strategic direction)
- Pattern frequency: Seen in 5+ clients this month
- Current approach: Sending work hoping for useful feedback
- Actual cost: 20 hours per project in revision cycles
- YOUR UNIQUE ANGLE
- The truth they're missing: You never asked for specific feedback at specific stages
- Your framework name: The 3-Stage Review Framework™
- Why this happens: Service providers don't take ownership of directing the review process
- TARGET AUDIENCE
- Who specifically: B2B service providers delivering done-for-you work
- Their context: 1-5 person teams, high-touch delivery, $5K+ projects
- Pathway served: Time (efficiency/operations)
- SOLUTION PREVIEW
- Core framework: Direction Check → Structure Check → Polish Pass
- Immediate win: Framework email stops revision chaos on current project
- Systematic need: Every client project needs this process
- NATURAL EXTENSIONS
- $7 toolkit potential: [Pick ONE direction, list 2-3 options]
- Option 1: "Client Feedback Toolkit" - 3 GPTs, templates for 5 project types, tracker
- Option 2: "Revision Prevention Kit" - Advanced prompts, scope creep scripts
- Option 3: [Another specific toolkit angle with components]
- Workshop angle: [Pick ONE focus for 90 minutes, list 2-3 options]
- Option 1: "Implementing 3-Stage Framework with current clients"
- Option 2: "Training your team on staged feedback"
- Option 3: "Migrating resistant clients to new process"
- Sprint connection: Time pathway - complete client management system The Handoff Process In Discovery Project: Analyze transcripts → Identify pattern → Create Concept Brief Copy the filled brief In Micro Magnet Project: Paste brief → Collaborate on angle → Generate guide In $7 Toolkit Project: Paste brief + completed micro magnet → Generate toolkit In Workshop Project: Paste brief + micro magnet + toolkit → Generate workshop In Spring Project: Paste brief + micro magnet + toolkit + workshop → Generate sprint Clean separation: Each level builds on previous, no repeated content Required Inputs for Each Generator: Micro Magnet: Needs Concept Brief only $7 Toolkit: Needs Concept Brief + completed micro magnet Workshop: Needs Concept Brief + micro magnet + toolkit (if exists) Sprint: Needs all previous materials + specific transformation goals What Makes a Strong Brief ✓ Specific numbers - Not "wastes time" but "20 hours per project" ✓ Clear framework - Not "better process" but "3-Stage Review Framework" ✓ Natural extensions - Can see the $7, workshop, and Sprint progression ✓ One core problem - Not trying to solve everything ✓ Pattern validated - Multiple clients mentioned it What to Avoid in Briefs ✗ Vague problems ("communication issues") ✗ Multiple problems bundled together ✗ Solutions without frameworks ✗ Audiences too broad ("all businesses") ✗ Missing the cost/impact BRIEF QUALITY GATES Before moving to Micro Magnet/Toolkit/Workshop/Sprint creation, verify: □ Problem is specific enough to happen TODAY □ Cost has real numbers and calculation method □ Framework has named steps, not just concepts □ You picked ONE toolkit direction (not combining) □ You picked ONE workshop focus (not combining) □ Pathway matches the problem, not the solution □ All sections of brief are complete If any box is unchecked, the brief isn't ready. THE ONE BRIEF RULE During Discovery you might identify multiple great ideas. That's fine. Create multiple briefs if you want Save them for later But only take ONE brief to creation at a time Finish and ship before starting the next No jumping between micro magnets. One brief, one creation, one ship. HANDOFF RULE (For All Creation Components) The brief is a CONTRACT. Once you move to creation: Stick to what's in the brief Don't add new problems Don't combine toolkit/workshop options Don't expand the framework Don't change the target audience If you need to change direction, go back to Discovery and create a new brief. This applies to: Micro Magnet creation $7 Toolkit creation Workshop creation The brief constrains scope to prevent feature creep and ensure completion.
Always create the content brief in a MD artifact. Do not use horizontal lines.