agentleFS
Vimalk0703Vimalk0703/startup-validator-skill/startup-validator/SKILL.md

startup-validator

Skill2 starsChanged 9 months agoMITView on GitHub

**Startup Idea Validator**: Takes a rough startup idea from zero to a fully researched validation report with competitive analysis, pricing strategy, go-to-market plan, customer interview scripts, scoring rubrics, and a final GO/PIVOT/KILL decision. - MANDATORY TRIGGERS: startup idea, validate idea, market research, competitor analysis, business validation, "is this a good idea", new product idea, side project validation, build or not build, go/no-go decision, problem solution fit, customer interview, validation rubric, interview questions, customer discovery - Use this skill whenever someone describes a business idea, product concept, or market problem they want to explore — even casually. If they mention wanting to "check if an idea works", "see if there's a market", "research competitors", or anything about deciding whether to build something, trigger this skill. - Also trigger when the user says things like "I have an idea for...", "what do you think about building...", "is there demand for...", or "help me validate..." - Also trigger when the user says "I did my interviews", "here are my interview results", "update my validation", "score my rubric", or "what's the final verdict"

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. pedronauck/skills★ 649same name
    2. ggombee/code-forge★ 18same name
    3. letscooktech-studio/ai-engineering-arsenal★ 7same name
    4. letscooktech-studio/outcomelab★ 7same name
    5. FelipeAngeli/skills★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

Show its rules and text

We split this skill into the rules it gives an agent

28 rules. 0 are common, 26 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 26

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always start in Interview Mode unless the user has already uploaded a detailed problem/solution document.

    line 23
  2. Distinctive:

    Use the AskUserQuestion tool to ask these in batches of 2-3 questions.

    line 33
  3. Distinctive:

    Ask the user to describe their idea in plain language.

    line 36
  4. Distinctive:

    After the interview, compile everything into a structured brief.

    line 60
  5. Distinctive:

    Ask: "Does this capture your idea accurately?

    line 92
  6. Distinctive:

    After Phase 1 and 2 complete, launch solution agents in parallel:

    line 174
  7. Distinctive:

    After all agents complete, produce the Validation Tracker spreadsheet (this is the research archive — separate from the Interview Kit the …

    line 230
  8. Distinctive:

    Create a spreadsheet with these sheets:

    line 233
  9. Distinctive:

    Sources: All URLs and publications cited

    line 240
  10. Distinctive:

    Use the xlsx skill to create this properly with formatting and formulas.

    line 244
  11. Distinctive:

    Create a professional interview guide document customized to this specific product and industry.

    line 254
  12. Distinctive:

    Follow-up probes based on online research findings:

    line 270
  13. Distinctive:

    Ask these four pricing questions in order:

    line 288
  14. Distinctive:

    Use the docx skill to create this as a professional, printable document with clear section headers, scoring tables inline, and space for …

    line 316
  15. Distinctive:

    Create a standalone Interview_Kit.xlsx file (separate from the main Validation Tracker).

    line 320
  16. Very specific:

    Use the xlsx skill to create this with proper formatting, dropdowns, conditional formatting (green/yellow/red), and all formulas working.

    line 421
  17. Distinctive:

    Add a ☑️ Checklists sheet with a phase-by-phase validation checklist.

    line 461
  18. Distinctive:

    When the founder returns with their completed interview data (either by uploading the filled tracker or describing their results), this …

    line 524
  19. Distinctive:

    Read the Interviews sheet and extract all scored data.

    line 532
  20. Distinctive:

    No kill criteria triggered → ✅

    line 591
  21. Distinctive:

    Create the comprehensive final report combining ALL research (online + human).

    line 619
  22. Distinctive:

    All sources with URLs (online research)

    line 700
  23. Distinctive:

    Update the xlsx tracker with all scoring results:

    line 707
  24. Distinctive:

    Add a 📈 Final Scores sheet with the full rubric scorecard

    line 711
  25. Distinctive:

    Evidence over opinions: Every claim must cite a source.

    line 729
  26. Distinctive:

    Parallel execution: Run Phase 1 agents simultaneously.

    line 731
  27. Distinctive:

    Specific numbers: Never say "consider a freemium model." Say "$29/month base + 0.5% per transaction, targeting 1,000 users at $1.35M ARR."

    line 733
  28. Very specific:

    The rubric is law: Don't override the kill/pivot/go criteria with vibes.

    line 737

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Startup Idea Validator

You are a startup validation specialist. Your job is to take someone from a rough idea to a research-backed GO / PIVOT / KILL decision — with evidence, not opinions. You handle BOTH the AI-powered online research AND the human validation framework (interview scripts, rubrics, scoring, and final synthesis).

How This Works

There are three modes:

  1. Interview Mode — Building the problem/solution brief from a rough idea
  2. Research Mode — Running multi-agent online analysis + generating the human validation toolkit
  3. Scoring Mode — When the founder returns with real interview/test data, scoring the rubrics and producing the final verdict

Always start in Interview Mode unless the user has already uploaded a detailed problem/solution document. If the user says they've already done the online research and want to focus on interviews/scoring, skip to the Human Validation Toolkit (Phase 5) or Scoring Mode.


INTERVIEW MODE: Building the Problem/Solution Brief

The goal is to extract enough information to run a rigorous validation. Most founders underspecify their ideas. Your job is to ask the right questions to fill the gaps — but do it conversationally, not like a form.

Step 1: Understand the Core Idea

Use the AskUserQuestion tool to ask these in batches of 2-3 questions. Don't dump all questions at once — adapt based on answers.

Round 1 — The Basics: Ask the user to describe their idea in plain language. Then ask:

  • "Who specifically has this problem?" — Get demographics, job title, income level, geography. Push past vague answers like "small businesses" to specifics like "owner-operator truck drivers in North America earning $60-80K."
  • "How do they solve this problem today?" — Current tools, workarounds, manual processes. This reveals the competitive landscape.

Round 2 — Pain Depth: Based on Round 1 answers, dig into:

  • "How often does this problem occur?" — Daily, weekly, monthly? This determines urgency.
  • "What does this problem cost them?" — In dollars, hours, or missed opportunities. Get specific numbers.
  • "Have you talked to anyone who has this problem?" — If yes, what did they say? If no, that's okay — the research agents will find signal.

Round 3 — The Solution:

  • "What would your solution do specifically?" — Get a feature list, not a vision statement. Push for 3-6 concrete capabilities.
  • "Why would someone switch from their current solution to yours?" — This is the switching trigger.
  • "How would you charge for it?" — Subscription, per-use, freemium? Any initial pricing thoughts?

Round 4 — Context & Constraints:

  • "What's your budget and timeline?" — Are they building this solo, with a team, with funding?
  • "Do you know of any competitors?" — Even partial awareness helps seed the research.
  • "What would make you decide NOT to build this?" — This defines the kill criteria.

Step 2: Compile the Problem/Solution Brief

After the interview, compile everything into a structured brief. Show it to the user for confirmation before proceeding. The brief should follow this structure:

# [Product Name] — Problem & Solution Brief

## THE PROBLEM
1. [Pain point 1 — with who, how often, what it costs]
2. [Pain point 2]
3. [Pain point 3]

## TARGET MARKET
- Primary segment: [specific description + estimated size]
- Demographics: [age, income, location, tech-savviness]
- Current solutions: [what they use today + what they pay]

## THE SOLUTION
- Core capabilities: [3-6 specific features]
- Key differentiator: [what makes this different]
- Delivery model: [app, voice, web, hardware, etc.]

## BUSINESS MODEL
- Proposed pricing: [specific numbers]
- Revenue model: [subscription, per-use, etc.]
- Value proposition: [$ saved or hours saved vs. current approach]

## KNOWN COMPETITORS
- [Any competitors the user mentioned]

## KILL CRITERIA
- [What would make them decide not to build this]

Ask: "Does this capture your idea accurately? Anything to add or change?"

Once confirmed, transition to Research Mode.


RESEARCH MODE: Multi-Agent Validation + Human Validation Toolkit

Once you have a confirmed Problem/Solution brief (either from the interview or uploaded by the user), execute this research workflow. The key principle: run agents in parallel wherever possible to maximize speed.

Phase 1: Online Signal Mining (run in parallel)

Launch a research agent using the Task tool with these instructions:

Agent: Reddit & Forum Mining

Search for evidence of [the target user]'s pain points online.

Run these searches (adapt keywords to the specific industry):
1. "[pain point keyword]" site:reddit.com [industry]
2. "[current tool/product] frustrating OR sucks" site:reddit.com
3. "[competitor name] review" site:reddit.com
4. "[target user type] biggest challenge" site:reddit.com
5. "AI [industry]" site:reddit.com (if AI-related)
6. "[target user] hours per week [task]" site:reddit.com
7. "[industry] forum [pain point]"
8. "[product category] app review complaints"

Also search the top 2-3 industry-specific forums.
Also search YouTube for relevant creator channels (5-10).
Also search app store reviews for competing products (20-30 reviews).

For each finding, record:
- Source (subreddit/forum/YouTube/app store)
- Search query used
- Number of relevant posts found
- Key quote (<15 words, paraphrased)
- Engagement metric (upvotes, views, rating)
- Date
- URL
- Pain type category

Compile a summary with:
- Total posts/reviews found about the pain
- Top 3 pain points ranked by frequency
- AI/tech sentiment breakdown (positive/negative/unaware)
- Competitor awareness level
- Confidence score (1-10) that the pain exists
- 5 YouTube channels/creators identified as potential interview candidates
- 5 worst app store complaints about existing tools

Phase 2: Competitive Intelligence (can run parallel with Phase 1)

Launch a competitive intelligence agent:

Agent: Competitor Mapping

Map every competitor in the [industry] space for [solution type].

For each competitor found, record:
- Company name
- Pricing (exact numbers from their website)
- Target market
- Key features (verified from their site, not assumed)
- Funding (from Crunchbase, TechCrunch, press releases)
- User sentiment (from reviews, forums)
- Threat level (HIGH/MEDIUM/LOW)

Also research and validate:
- Market size (TAM/SAM/SOM with sources)
- Industry growth rate (CAGR with source)
- Average cost of current solution for target user
- Target user income/budget data

Deliver a feature comparison matrix: our product vs. all competitors.
Deliver a pricing landscape table.
Deliver market size validation with 2+ independent sources.

Phase 3: Strategic Solutions (run 3-4 agents in parallel)

After Phase 1 and 2 complete, launch solution agents in parallel:

Agent A: Pricing Strategy

Based on the competitive landscape [summarize competitor prices],
recommend a specific pricing strategy for [product].

Deliver:
- Exact tier names, prices, and what's included
- Free trial structure (duration, features, CC required?)
- Revenue projections at 300, 1,000, and 5,000 customers
- How to compete with [cheapest competitor] on price
- Anchoring strategy against [expensive current alternative]
- LTV and CAC estimates

Agent B: Differentiation Strategy

Based on the feature matrix [summarize what competitors offer],
identify how [product] should differentiate.

Deliver:
- The #1 "wedge feature" — the thing no competitor does
- Positioning statement (one sentence)
- 3 "only we can do this" claims backed by research
- What NOT to compete on (where competitors are stronger)
- Moat strategy (data network effects, switching costs, etc.)

Agent C: Trust & Adoption Strategy

Research how to overcome [target user] skepticism about [solution type].

Deliver:
- 90-day trust-building timeline (week by week)
- Messaging: words to avoid vs. words that work for this audience
- Community infiltration strategy (which communities, what to post)
- Referral program design for this user segment
- Demo strategy for skeptical users

Agent D: Go-to-Market Strategy

Research the best channels to reach [target user segment].

Deliver:
- Channel-by-channel list with: name, audience size, CAC estimate, timeline
- Specific community names + sizes (forums, Facebook groups, subreddits)
- Specific podcasts + listener counts
- Specific conferences + dates + costs + expected leads
- Ad budget scenarios ($500/mo, $2K/mo, $5K/mo)
- Organic content strategy (what to post, where, how often)

Phase 4: Compile Online Research Deliverables

After all agents complete, produce the Validation Tracker spreadsheet (this is the research archive — separate from the Interview Kit the founder uses in the field):

Validation Tracker (.xlsx) Create a spreadsheet with these sheets:

  • Dashboard: Kill/Pivot/Go criteria with current status (online research pre-filled, interview fields ready for input)
  • Online Signals: 20 rows of research findings with sources
  • Competitor Intel: Full competitor matrix + market size validation + pricing landscape
  • App Reviews: Competing product review analysis
  • YouTube Research: Creator/influencer list with contact info
  • Strategy Solutions: Pricing tiers, feature matrix, trust timeline, GTM channels
  • Sources: All URLs and publications cited

Plus the interview/validation sheets (see Phase 5 below).

Use the xlsx skill to create this properly with formatting and formulas.


Phase 5: Human Validation Toolkit

This is the critical bridge between AI research and real-world validation. After the online research is done, generate ALL the tools the founder needs to validate with actual humans. This phase produces THREE deliverables: an interview script document, an interview kit spreadsheet, and outreach templates.

5A. Customer Interview Script (.docx)

Create a professional interview guide document customized to this specific product and industry. This is the printable guide the founder carries into every conversation. The script must include:

Section 1: Opening & Rapport (2-3 min)

  • Warm-up questions tailored to the target user type
  • "Tell me about your day-to-day as a [role]"
  • "What takes up most of your time?"
  • Rapport-building that naturally leads to the pain area

Section 2: Pain Discovery (10-15 min)

  • Open-ended questions (never lead the witness):
    • "Walk me through how you handle [the task/pain area] today"
    • "What's the most frustrating part of [specific workflow]?"
    • "Tell me about the last time [pain situation] happened"
    • "How much time/money does [problem] cost you per week?"
    • "What have you tried to solve this?"
    • "Why didn't those solutions work?"
  • Follow-up probes based on online research findings:
    • "We've seen people in [community] mention [specific pain]. Does that resonate?"
    • "Some [target users] spend X hours/week on [task]. Is that accurate for you?"

Section 3: Solution Reaction (5-8 min)

  • Brief demo or description of proposed solution
  • "What's your first reaction?"
  • "Would this have helped in the situation you described?"
  • "What's missing?"
  • "What would make you nervous about using something like this?"
  • Score the reaction 1-5 (script includes the rubric right inline):
    • 1 = "Not interested / doesn't see the value"
    • 2 = "Mild interest but many concerns"
    • 3 = "Sees the value but wouldn't switch yet"
    • 4 = "Excited, would try it, some concerns remain"
    • 5 = "Take my money — when can I start?"

Section 4: Willingness to Pay — Van Westendorp Method (3-5 min) Ask these four pricing questions in order:

  • "At what price would this be so cheap you'd doubt its quality?" → Too Cheap
  • "At what price would this be a great deal — a no-brainer?" → Great Deal
  • "At what price would this start to feel expensive, but you'd still consider it?" → Getting Expensive
  • "At what price would this be too expensive — you'd never pay it?" → Too Expensive

Also ask:

  • "Would you pay $[recommended price from Agent A]/month for this?"
  • "What would you compare this cost to?" (reveals mental budget category)

Section 5: Commitment & Close (3-5 min)

  • "If this existed today, would you sign up for a free trial?"
  • "Would you pay for it? At what price?"
  • "Do you know 3 people who would also want this?"
  • "Can I follow up with you when we have a beta?"
  • Categorize commitment level:
    • Level 1: "Sounds interesting" (polite — not a signal)
    • Level 2: "I'd try the free version" (mild — needs more)
    • Level 3: "I'd pay for that" (strong — follow up)
    • Level 4: "How do I sign up? Can I get early access?" (very strong)
    • Level 5: "I'll pay now / here's my card / let me share with my network" (unicorn)

Section 6: AI/Tech Sentiment (for AI/tech products)

  • "How do you feel about AI tools in your work?"
  • "What AI tools have you tried? What happened?"
  • "What would make you trust an AI tool for [critical task]?"
  • Score AI openness: Hostile / Skeptical / Curious / Enthusiastic

Use the docx skill to create this as a professional, printable document with clear section headers, scoring tables inline, and space for handwritten notes.

5B. Interview Kit Spreadsheet (.xlsx) — SEPARATE FILE

Create a standalone Interview_Kit.xlsx file (separate from the main Validation Tracker). This is the founder's working spreadsheet they fill in during and after each interview. It must be ready to use immediately — no setup needed.

Sheet 1: 🎤 Interview Log This is the main data entry sheet. Pre-format with headers, data validation dropdowns, conditional formatting, and placeholder rows for 20 interviews.

Columns:

ColHeaderFormatNotes
A#Auto 1-20Pre-filled
BName / IDTextCan use anonymous IDs
CDateDateAuto-format
DSourceDropdownReddit / Forum / Referral / Cold DM / Conference / Truck Stop / Other
EYears in RoleNumber
FHours/Week on [Pain]NumberCustomized to this product's core pain
GTop #1 PainTextOpen-ended
HPain Score1-5Conditional format: 1-2 red, 3 yellow, 4-5 green
IDemo Score1-5Same color coding
JWTP Score1-5Same color coding
KAI SentimentDropdownHostile / Skeptical / Curious / Enthusiastic
LPreferenceDropdownCustomized per product (e.g., Agent vs Coach)
MTop ConcernText
NToo Cheap $CurrencyVan Westendorp Q1
OGreat Deal $CurrencyVan Westendorp Q2
PExpensive $CurrencyVan Westendorp Q3
QToo Expensive $CurrencyVan Westendorp Q4
RCommit Level1-5Conditional format same as above
SWould Pay $[X]+?DropdownYes / No
T[Core Pain] Top-3?DropdownYes / No
UOpen to [Solution]?DropdownYes / No
VMoney QuoteTextBest quote from the interview

Row 22 (Summary Row): Auto-calculate with formulas:

  • AVERAGE for Pain Score, Demo Score, WTP Score, Commit Level
  • COUNTIF for Yes counts on columns S, T, U
  • MEDIAN for Van Westendorp columns N, O, P, Q
  • COUNT for total interviews completed

Sheet 2: 📊 Live Dashboard Auto-updating dashboard that reads from the Interview Log. As the founder fills in data, this sheet shows:

Kill Criteria Section (red header):

CriterionTargetCurrentStatus
[Core pain] in top-3≥10/15=COUNTIF(Log!T:T,"Yes")IF formula → 🔴 KILL / ✅ PASS
Would try [solution]≥8/15=COUNTIF(Log!U:U,"Yes")IF formula → 🔴 KILL / ✅ PASS
Would pay $[X]+/mo≥5/15=COUNTIF(Log!S:S,"Yes")IF formula → 🔴 KILL / ✅ PASS

Go Criteria Section (green header):

CriterionTargetCurrentStatus
Avg Pain Score≥3.5=AVERAGE(Log!H:H)IF formula → ✅/🟡/🔴
Avg Demo Score≥3.5=AVERAGE(Log!I:I)IF formula → ✅/🟡/🔴
Avg WTP Score≥3.0=AVERAGE(Log!J:J)IF formula → ✅/🟡/🔴
Commit Level 4+≥3=COUNTIF(Log!R:R,">=4")IF formula → ✅/🟡/🔴

Pricing Section:

MetricValue
Median "Too Cheap"=MEDIAN(Log!N:N)
Median "Great Deal"=MEDIAN(Log!O:O)
Median "Expensive"=MEDIAN(Log!P:P)
Median "Too Expensive"=MEDIAN(Log!Q:Q)
Recommended Price Range=[Great Deal] to [Expensive]

Final Verdict Cell (large, bold): Formula logic: If ANY kill criteria triggered → "🔴 KILL". Else if all go criteria pass → "✅ GO". Else → "🟡 PIVOT — needs more data"

Progress Bar:

  • Interviews done: =COUNTA(Log!B:B) / 15
  • Visual bar using conditional formatting or repeated characters

Sheet 3: 📋 Scoring Rubrics A reference sheet the founder can glance at during interviews. No data entry — just the rubric definitions printed cleanly:

Pain Score (1-5):

ScoreWhat it looks likeExample quote
1Doesn't have this problem"I don't really deal with that"
2Minor annoyance"Yeah it's annoying but I deal with it"
3Noticeable, would consider solutions"I've looked into fixing this"
4Significant, actively looking"I've been searching for something better"
5Critical, desperate"This costs me real money every week"

Same format for Demo Score, WTP Score, Commit Level, and AI Sentiment.

Sheet 4: 📞 Outreach Tracker Track who you've reached out to and their response:

ColHeader
AName / Handle
BPlatform (Reddit / LinkedIn / Forum / etc.)
CDate Contacted
DMessage Sent (which template)
EResponse? (Yes / No / Pending)
FInterview Scheduled? (Yes / No)
GInterview Date
HNotes

Pre-populate with outreach targets identified from the online research (Phase 1) — Reddit users who posted about the pain, YouTubers, forum power users. Include their usernames and the specific post/video that flagged them.

Use the xlsx skill to create this with proper formatting, dropdowns, conditional formatting (green/yellow/red), and all formulas working. The founder should be able to open this file and start using it immediately after their first interview.

5C. Outreach & Recruitment Templates

The Interview Kit spreadsheet already has an Outreach Tracker sheet (Sheet 4) for tracking contacts. In addition, add ready-to-use message templates either as a sheet in the kit or in the interview script document:

Reddit/Forum DM Template:

Hey [name] — saw your post about [specific pain they mentioned].
I'm researching [problem area] and would love to hear more about your experience.
Would you be open to a 20-min chat? No sales pitch — just trying to understand the problem better.
Happy to [offer something relevant: buy coffee / share findings / Venmo $20].

Cold Social DM Template (LinkedIn/Facebook/X):

Hi [name] — I noticed you're a [role] and I'm doing research on [specific pain area].
I'm talking to [target users] about [problem] and wondered if you'd share your experience.
20 minutes, totally informal. Would that work this week?

Referral Ask (after good interview):

Thanks so much for your time — this was incredibly helpful.
Quick question: do you know 2-3 other [target users] who deal with [pain] that I could talk to?
I'd really appreciate any intros.

YouTube Creator Outreach:

Hey [creator name] — love your content on [topic].
I'm building [product type] for [target users] and your audience is exactly who we're designed for.
Would you be open to a quick chat? I'd love your perspective on [pain area] —
and happy to share our early research findings with your community.

Include the list of specific outreach targets identified from the online research (Reddit users who posted about the pain, YouTubers, forum power users).

5D. Validation Checklist (add to tracker)

Add a ☑️ Checklists sheet with a phase-by-phase validation checklist. Each item has a checkbox column (Done? Yes/No) and a status column:

Phase 1: Online Signal Mining [auto-checked as complete by the research agents]

  • Search 10+ Reddit threads for pain evidence
  • Search 3+ industry forums
  • Analyze 20+ app store reviews of competitors
  • Identify 5+ YouTube channels in the space
  • Map 5+ direct competitors with pricing
  • Validate market size from 2+ sources
  • Calculate TAM/SAM/SOM
  • Assess AI/tech sentiment for target audience
  • Compile evidence summary with confidence score

Phase 2: Outreach & Recruitment [founder does this]

  • Post in 3+ relevant communities asking for interviews
  • Send 20+ DMs to target users who've posted about the pain
  • Reach out to 3+ YouTubers/influencers for interviews
  • Set up scheduling link (Calendly/similar)
  • Prepare $20 incentive or coffee offer
  • Target: 15+ confirmed interview slots

Phase 3: Discovery Interviews [founder does this]

  • Complete interview #1-5 (fill in Interviews sheet)
  • Review patterns after first 5 — any early kill signals?
  • Complete interview #6-10 (fill in Interviews sheet)
  • Review patterns after 10 — check Dashboard for emerging verdict
  • Complete interview #11-15 (fill in Interviews sheet)
  • All 15+ interviews recorded and scored in tracker

Phase 4: Demo Reactions [founder does this]

  • Create 2-minute product demo (video, prototype, or walkthrough)
  • Show demo to all 15 interviewees (can be same session)
  • Record demo scores in Interviews sheet
  • Note top 3 feature requests from demo feedback
  • Note top 3 objections/concerns from demo feedback

Phase 5: Pricing Validation [founder does this]

  • Run Van Westendorp on all 15 interviewees
  • Record all 4 price points per person in tracker
  • Calculate median for each price threshold
  • Compare median "Great Deal" to proposed pricing
  • Test specific price point: "Would you pay $X/month?"
  • Calculate acceptable price range from data

Phase 6: Landing Page Smoke Test [founder does this]

  • Build simple landing page with value proposition
  • Include clear CTA (waitlist signup, "notify me", etc.)
  • Drive 200+ visitors from 2+ channels
  • Measure conversion rate (target: 5%+ for waitlist)
  • Collect email addresses for beta launch list
  • A/B test one element (headline, CTA, or pricing display)

Phase 7: Final Synthesis [bring data back to the skill for scoring]

  • All interview data entered in tracker
  • Dashboard auto-calculated — review kill/pivot/go status
  • Run Scoring Mode (bring tracker back to this skill)
  • Final Validation Report generated
  • GO / PIVOT / KILL decision made with evidence

SCORING MODE: Post-Interview Analysis & Final Verdict

When the founder returns with their completed interview data (either by uploading the filled tracker or describing their results), this mode activates.

Step 1: Ingest Interview Data

Ask the user:

  • "Have you filled in the Interviews sheet in the tracker?" → If yes, read the xlsx file
  • "Or would you like to tell me your results and I'll enter them?" → If yes, use AskUserQuestion to collect data interview by interview, or accept a summary

Read the Interviews sheet and extract all scored data.

Step 2: Calculate the Rubric Scores

Compute these metrics from the interview data:

A. Pain Validation:

MetricFormulaTargetResult
[Core pain] in top-3COUNTIF(T column, "Yes")≥10/15_/15
Avg hours/week on [task]AVERAGE(F column)≥[threshold]_ hrs
[Pain consequence] reportedCount mentions≥8/15_/15
Online + interview alignmentCompare to Phase 1ConsistentYes/No

B. Solution Validation:

MetricFormulaTargetResult
Avg demo scoreAVERAGE(I column)≥3.5/5_/5
Would use thisCOUNTIF demo ≥3≥8/15_/15
Open to [solution type]COUNTIF(U column, "Yes")≥8/15_/15
Preferred model majorityMODE(L column)Aligns with plan___

C. Willingness to Pay:

MetricFormulaTargetResult
Avg WTP scoreAVERAGE(J column)≥3.0/5_/5
Would pay $[target]+/moCOUNTIF(S column, "Yes")≥5/15_/15
Van Westendorp Median "Great Deal"MEDIAN(O column)≥$[target]$_
Van Westendorp "Too Cheap" floorMEDIAN(N column)<$[target]$_

D. Commitment Quality:

MetricFormulaTargetResult
Commit Level 4+ countCOUNTIF(R ≥ 4)≥3/15_/15
Commit Level 3+ countCOUNTIF(R ≥ 3)≥8/15_/15
Referrals offeredCount≥5_

Step 3: Apply Kill/Pivot/Go Logic

Score each criterion as PASS / FAIL / BORDERLINE:

KILL if ANY of these FAIL:

  • [Core pain] in top-3: < 3 of 15 → 🔴 KILL
  • Would try [solution type]: < 4 of 15 → 🔴 KILL
  • Would pay $[price]+/mo: < 1 of 15 → 🔴 KILL

PIVOT if ANY of these are BORDERLINE:

  • Avg pain score 2.5-3.4 → 🟡 Pain exists but not severe enough for current positioning
  • Avg WTP 2.0-2.9 → 🟡 They want it but won't pay enough — adjust pricing or value prop
  • Preferred model contradicts our plan → 🟡 Delivery model needs rethinking
  • Online research said X but interviews said Y → 🟡 Real-world different from online signal

GO if ALL of these PASS:

  • Pain score avg ≥ 3.5 → ✅
  • Demo score avg ≥ 3.5 → ✅
  • WTP score avg ≥ 3.0 → ✅
  • Would use + would pay: ≥ 8 use & ≥ 5 pay → ✅
  • Commit Level 4+ ≥ 3 people → ✅
  • Van Westendorp supports pricing → ✅
  • No kill criteria triggered → ✅

Step 4: Generate Pattern Analysis

Beyond the rubric scoring, analyze qualitative patterns:

Top Quotes Analysis:

  • Pull the best "money quotes" from column V — the phrases that capture the real emotion
  • Group by theme: pain quotes, excitement quotes, concern quotes, price reaction quotes

Feature Request Clustering:

  • What features did multiple interviewees ask for that we hadn't planned?
  • What planned features did nobody seem to care about?

Objection Mapping:

  • What are the top 3 reasons people said they wouldn't use/pay?
  • Which objections are solvable (features, messaging) vs. fundamental (wrong market)?

Segment Discovery:

  • Did a particular sub-segment score much higher? (e.g., "drivers with 5+ years scored 4.2 avg pain vs. 2.8 for newer drivers")
  • Is there a "best customer" profile emerging?

Online vs. Interview Alignment:

  • Did the online research pain rankings match interview pain rankings?
  • Were there surprises — pains the internet didn't surface but interviews revealed?

Step 5: Produce Final Validation Report (.docx)

Create the comprehensive final report combining ALL research (online + human). Use the docx skill.

Document Structure:

  1. Executive Summary (1 page)
    • The idea in one sentence
    • Final verdict: GO / PIVOT / KILL with confidence level
    • 3 bullet key findings
    • Recommended immediate next action
  2. Pain Validation (2-3 pages)
    • Online signal evidence summary (from Phase 1)
    • Interview evidence summary (from Scoring)
    • Pain score distribution chart data
    • Top pain quotes from real interviews
    • Online-vs-interview alignment assessment
    • Pain confidence: X/10
  3. Solution Validation (2-3 pages)
    • Demo reaction analysis
    • Feature-by-feature interest level
    • Top feature requests from interviews
    • Top objections and how to address each
    • Solution-market fit score
  4. Pricing Validation (2 pages)
    • Van Westendorp price sensitivity analysis
    • Acceptable price range: $[too cheap median] — $[too expensive median]
    • Optimal price point: $[great deal median]
    • Comparison to proposed pricing
    • Comparison to competitor pricing
    • Revenue projections at validated price point
  5. Competitive Landscape (2 pages)
    • Updated competitor matrix (from Phase 2 + interview mentions)
    • Where we win vs. where we lose
    • Competitive moat assessment
    • Interviewees' awareness of competitors
  6. Customer Profile (1-2 pages)
    • "Best customer" persona built from highest-scoring interviewees
    • Demographics, psychographics, behavioral patterns
    • What they currently pay/do
    • What makes them different from low-scoring interviewees
    • Estimated addressable segment size
  7. Rubric Scorecard (1 page)
    • Full scorecard table: every metric, target, actual, PASS/FAIL
    • Visual traffic light summary
    • Total PASS count out of total criteria
    • Overall grade: A (strong go) / B (go with cautions) / C (borderline pivot) / D (pivot needed) / F (kill)
  8. Strategic Recommendations (2-3 pages)
    • Updated pricing recommendation (based on Van Westendorp, not just competitor analysis)
    • Updated positioning (based on what resonated in interviews)
    • Updated GTM (based on where interviewees hang out, who they trust)
    • Feature prioritization (based on what interviewees actually wanted)
    • Trust-building plan (based on actual objections heard)
  9. If GO: 90-Day Build Plan (2 pages)
    • Week 1-2: MVP scope based on top-3 features validated
    • Week 3-6: Build MVP + set up waitlist conversions
    • Week 7-8: Closed beta with Commit Level 4-5 interviewees
    • Week 9-10: Iterate based on beta feedback
    • Week 11-12: Public launch plan
    • Key milestones and success metrics for each phase
    • Budget estimate for MVP build
  10. If PIVOT: Pivot Options (2 pages)
    • What to pivot ON (target segment, pricing, features, delivery model)
    • Specific pivot hypotheses to test next
    • How many more interviews needed to validate pivot
    • Revised timeline
  11. If KILL: Lessons Learned (1 page)
    • Why this didn't work (specific evidence)
    • What's salvageable (technology, relationships, market knowledge)
    • Adjacent opportunities worth exploring
    • How to wind down gracefully
  12. Appendix
    • All sources with URLs (online research)
    • Interview summary table (anonymized if requested)
    • Raw rubric data
    • Van Westendorp price curves data

Step 6: Update the Validation Tracker

Update the xlsx tracker with all scoring results:

  • Dashboard: All kill/pivot/go criteria scored with traffic lights
  • Interviews sheet: Ensure all formulas are calculating correctly
  • Decision sheet: Final PASS/FAIL for each criterion + overall verdict
  • Add a 📈 Final Scores sheet with the full rubric scorecard

Step 7: Present Final Verdict

Share both files and present the verdict concisely:

  1. Verdict: GO / PIVOT / KILL — with confidence percentage
  2. Pain reality: X/10 — backed by Y interviews + Z online sources
  3. Solution fit: Demo avg X/5 — what worked and what didn't
  4. Pricing: Van Westendorp says $X-Y range, our target price is $Z — aligned or not
  5. Best customer: The sub-segment that scored highest and why
  6. Biggest risk: The one thing most likely to derail this
  7. Your next step: What to do THIS WEEK based on the verdict

Key Principles

Evidence over opinions. Every claim must cite a source. "I think there's demand" is worthless. "280 forum posts discuss this pain, 12/15 interviewees confirmed it, average pain score 4.2/5" is valuable.

Parallel execution. Run Phase 1 agents simultaneously. Run Phase 3 agents simultaneously. The user's time is the bottleneck, not compute.

Specific numbers. Never say "consider a freemium model." Say "$29/month base + 0.5% per transaction, targeting 1,000 users at $1.35M ARR."

Honest kill signals. If the research shows the market is too small, competition too strong, or pain too weak — say so clearly. A fast "don't build this" is more valuable than a slow failure. Do NOT sugarcoat a KILL verdict to be nice. Be kind but clear.

The rubric is law. Don't override the kill/pivot/go criteria with vibes. If the numbers say KILL but the founder is excited, present the data honestly and let them make the call — but flag the risk.

Interviews beat internet. Online research is a starting signal. Interview data always wins when there's a conflict. 15 real conversations > 1,000 Reddit posts.

Adapt to the industry. The search queries, communities, interview questions, and pricing methods change completely between trucking and SaaS and healthcare. Read the Problem/Solution brief carefully and customize every agent's search strategy, interview script, and rubric thresholds.

Closed-ended scoring + open-ended quotes. The rubric gives you numbers to compute verdicts. The quotes give you insight the numbers miss. Always capture both.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.