Validation Presenter Skill
Purpose: Format app research findings for McKinzie's review with clear go/no-go recommendations.
Trigger: After completing app opportunity research.
🎯 Output Goal
One-page summary that lets McKinzie decide in 60 seconds:
- •Is this worth building?
- •What's the evidence?
- •What's the risk?
- •What would she need to see to say yes?
📋 Report Structure
markdown
# 🚀 App Opportunity: [Name] ## ⚡ TL;DR (60-Second Summary) **The Pain:** [One sentence] **The Solution:** [App name] - [One sentence] **Why Now:** [Market timing / gap] **Revenue Potential:** $X Year 1 / $Y Year 2 **Verdict:** [🟢 BUILD / 🟡 MAYBE / 🔴 SKIP] --- ## 📊 Evidence Summary ### Pain Point Validation | Metric | Result | Threshold | Status | |--------|--------|-----------|--------| | Mentions Found | X | 20+ | ✅/❌ | | "Desperate" Language | X% | >30% | ✅/❌ | | Willingness to Pay | X mentions | 5+ | ✅/❌ | | **Total Score** | X/3 | 3/3 = validated | | ### Market Validation | Metric | Result | Threshold | Status | |--------|--------|-----------|--------| | Google Trends | X% YoY | 10%+ | ✅/❌ | | Community Size | X | 100K+ | ✅/❌ | | Competitor Revenue | $X | Any paid | ✅/❌ | | **Total Score** | X/3 | | | ### Strategic Fit | Factor | Score | Why | |--------|-------|-----| | Audience Understanding | X/5 | | | Reachability | X/5 | | | Content Flywheel | X/5 | | | Launch Advantage | X/5 | | | Complexity | X/5 | | | Retention | X/5 | | | **TOTAL** | **X/30** | 25+=strong | --- ## 🎯 The Opportunity ### What Users Are Saying > "[Most compelling quote]" > — Reddit user, r/XXX > "[Second quote showing intensity]" > — App Store review > "[Quote showing willingness to pay]" > — Facebook group **Pattern:** [What do all these have in common?] ### Why Existing Solutions Fail | App | The Problem | Users Say | |-----|-------------|-----------| | [Competitor 1] | Too complex | "Takes 30 min to set up" | | [Competitor 2] | Expensive | "$10/mo for basic features" | | [Competitor 3] | Bad UX | "Confusing interface" | **The Gap:** [What no one is doing well] --- ## 💰 Revenue Projection ### Conservative (Year 1) - Addressable Market: X people - McKinzie's Reach: X × 0.02 = Y people - Free Users: Y - Paid Conversion (3%): Z users - Price: $X/month - **Revenue: $____** ### Optimistic (Year 2) - Growth: 3x reach - Improved conversion: 5% - Higher price tier: $Y/month - **Revenue: $____** ### Break-Even - Dev cost: ~$3K (MVP) - Break-even: X months --- ## ⚖️ Pros & Cons ### ✅ Why Build This 1. [Strong pro with evidence] 2. [Strong pro with evidence] 3. [Strong pro with evidence] ### ❌ Risks & Concerns 1. [Risk + mitigation] 2. [Risk + mitigation] 3. [Risk + mitigation] ### 🎲 Unknowns - [What we don't know yet] - [What would reduce risk] --- ## 🎯 McKinzie's Decision ### If You Say YES: **Next 48 Hours:** - [ ] Dev feasibility check (15 min) - [ ] Landing page mockup - [ ] Domain purchase **Next 2 Weeks:** - [ ] MVP build - [ ] Beta test with 5 users - [ ] Iterate ### If You Say NO: **Alternative Opportunities:** 1. [Other niche to research] 2. [Different angle on same pain] ### If You Say MAYBE: **What would convince you:** - [ ] Landing page test (collect emails) - [ ] Interview 3 potential users - [ ] Competitive teardown - [ ] Technical feasibility deep dive --- ## 📝 MVP Spec (If Approved) ### Core Features (3 Max) 1. [Feature] - [Why this matters] 2. [Feature] - [Why this matters] 3. [Feature] - [Why this matters] ### Tech Stack - Frontend: [X] - Backend: [X] - Auth: [X] - Payment: [X] - Timeline: X weeks ### Design Direction - **Vibe:** [Description] - **Colors:** [Palette] - **Style:** [References] --- ## 🔗 Research Artifacts **Full Data:** - Raw quotes: [Link to file] - Competitor analysis: [Link to file] - Market data: [Link to file] **Quick Access:** - Google Trends: [Link] - Top Reddit Threads: [Links] - Competitor Apps: [Links] --- *Report generated: [Date]* *Research time: X hours* *Sources checked: X Reddit threads, Y App Store reviews, Z Facebook groups*
🎨 Visual Formatting Tips
Use Emojis for Scanability
- •🟢 / 🟡 / 🔴 for status
- •✅ / ❌ for pass/fail
- •⚡ for key insights
- •💰 for money
- •⚠️ for risks
Keep It Short
- •No paragraph longer than 3 lines
- •Use tables for comparisons
- •Use bullet lists for features
- •Bold the key numbers
Make Decisions Easy
- •Default to BUILD / MAYBE / SKIP
- •If MAYBE, say exactly what would change to BUILD
- •Include "If you only read one thing" summary at top
📊 Scoring Rubric
Go / No-Go Decision Tree
code
Pain Validation < 2/3? → SKIP (not enough evidence) Market Validation < 2/3? → SKIP (market not viable) Strategic Fit < 20/30? → MAYBE (need different angle) Revenue Potential < $10K Year 1? → MAYBE (need bigger market or higher price) All checks pass? → BUILD (with confidence level)
Confidence Levels
| Level | Meaning | Next Step |
|---|---|---|
| 🟢 High | 90%+ chance of success | Build MVP immediately |
| 🟡 Medium | 60-70% chance | Landing page test first |
| 🔴 Low | <50% chance | Skip or pivot significantly |
✅ Quality Checklist
Before presenting to McKinzie:
- • Can she understand the opportunity in 60 seconds?
- • Is there clear evidence for every claim?
- • Are risks honestly presented?
- • Is the recommendation clear (BUILD/MAYBE/SKIP)?
- • Are next steps obvious if she says yes?
- • Is there a "what would convince you" for maybes?
🎯 Example Output
See: /projects/app-opportunity-research/findings/[APP-NAME]-REPORT.md
Last updated: Feb 15, 2026 Goal: Clear, fast decisions backed by evidence