Idea Validation Sprint

Assign an idea and a validation crew frames it on a lean canvas, researches the market and customers, drafts a landing page and a cheap demand test, and verifies the evidence — gated by your approval — to validate, pivot, or kill it fast.

Saves you ~4.2 h / run

How it works

Trigger
When you start the “Validate idea” workflow.
Job
Frame and research the idea, draft the demand test, verify the evidence.
Outcome
A sourced keep, pivot, or stop recommendation.

What it installs

Agents 4

  • Researcher

    Validates demand with sourced research and surfaces the riskiest assumption.

  • Writer

    Designs the demand test and writes the keep/pivot/kill recommendation.

  • Research Verifier

    Adversarially verifies the validation doc's evidence and flags unsupported claims.

  • Idea Validation Sprint Quality Reviewer

    Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.

Teams 1

  • Validation Crew

    A researcher who finds the signal, a writer who builds the demand test, and a verifier who keeps the evidence honest.

Workflows 1

  • Validate idea

    Frame and research the idea, draft the demand test, verify the evidence, revise, then hand off for a keep/pivot/kill decision.

Skills 4

  • lean-canvas

    Generate a Lean Canvas (Ash Maurya) — problem, customer segments, UVP, solution, channels, revenue, cost structure, key metrics, unfair advantage — specifically and measurably, then surface the riskiest assumptions and the experiments that would test them. Adapted from phuryn/pm-skills/lean-canvas.

  • company-research

    Build a strategic company/competitor profile from public sources — executive quotes, product strategy and launches, transformation and PLG signals — every claim recent (12–24 months) and cited with source and date, going deeper than an 'About Us' scrape. Adapted from deanpeters/product-manager-skills/company-research.

  • customer-research

    Uncover what customers actually think, say, and struggle with — extract JTBD, pains, trigger events, desired outcomes, and verbatim language from transcripts/reviews/tickets and digital watering holes (Reddit, G2, forums), score every insight by confidence, and build personas only from real data. Adapted from coreyhaines31/marketingskills/customer-research.

  • deep-research

    Run skeptical multi-source research that produces a cited report — scope the question, fan out searches across the axes that matter, require a source URL for every claim and 2+ independent sources for critical ones, track confidence, distinguish fact from synthesis, and admit gaps. Adapted from samber/cc-skills/deep-research.

Requirements

  • Web research for market and customers — The crew researches the market, competitors, and customer language on the web to validate demand and verify claims; until you connect it, it works from any research, transcripts, reviews, or survey exports you attach.

Setup guide

How to Validate Product Ideas With a Sprint

A practical guide to validating product ideas with a lean canvas, cited research, a demand test, and a keep/pivot/kill gate.

Read the setup guide

Don't see your workflow? Describe it.

A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.

* What keeps taking time you don't have? *



Takes a minute · no account needed