Validate family
Proof before product, market, or GTM commitment. See how this offer relates to the rest of the family. Explore Validate
A market-facing sprint to test demand, ICP, offer, and buyer response before you commit more build or GTM investment.
It is for products ready to test with a market: MVPs that need demand signal, founders choosing between ICPs or offers, and teams that want evidence before further build. The output is a demand readout and a clear next step, not vague excitement.
Use a Demand Validation Sprint when you have something concrete to put in front of a market and need to know whether the right audience responds. It is built to separate real signal from compliments, vanity traffic, and low-intent interest.
Deliverables are shaped by how many audiences, channels, or offer variants you test, but a typical sprint includes:
Semi-fixed scope. A separate paid discovery phase is usually not needed because enough discovery happens inside the sprint; scope depends on how many audiences, channels, or offer variants you test.
For heavier or less certain work, a short paid discovery can define scope before execution. See how discovery works
Four anonymized cases show what a demand test looks like once it meets paid traffic. Each one names the audience and the geography, runs a single channel, and treats cost per qualified response — not the click — as the signal.
Founder acquisition for a startup accelerator, Meta, USA & EU · Investor acquisition for a fractional property app, Meta, UK · Clinic acquisition for a telemedicine platform, Google Ads, EU · Therapist acquisition for a VR therapy app, Meta, USA
This offer sits inside the Validate family. Use these links to see the family context, the flagship offer of this family, and the full catalog.
Proof before product, market, or GTM commitment. See how this offer relates to the rest of the family. Explore Validate
A short proof and decision checkpoint for early ideas, new theses, mature-company initiatives, and partner opportunities. See the Validation Sprint
Compare every Validate, Build, Grow, Scale, and Partner offer in one place. Browse the offer catalog
Whether the right audience actually responds to a concrete thing: an MVP, landing page, offer, workflow, prototype, or proof asset. It is built to separate real signal from compliments, vanity traffic, and low-intent interest, and it ends with a demand readout rather than vague excitement.
A Validation Sprint frames the decision and designs the proof path, and can run before anything exists. A Demand Validation Sprint is market-facing: it needs something concrete to put in front of buyers and measures how they respond to it.
Something concrete enough for a market to react to, and a view of who that market is. The sprint refines the offer, audience, and test assets, but it cannot manufacture a product to test. If nothing exists yet, start with a Validation Sprint.
Semi-fixed scope. A separate paid discovery is usually unnecessary because enough discovery happens inside the sprint. What moves the scope is how many audiences, channels, or offer variants you want tested — each additional variant needs its own audience, assets, and read.
Whether to continue, change ICP, change offer, build an MVP, test pricing, pause, or stop. It reports responses, conversion, call quality, and objections against the demand thesis set at the start, so a weak result is as readable as a strong one.
Tell us where you are, what you are trying to prove, and what would make the next move worth it.
If you would rather talk it through before sending a brief, book a short routing call and we will point you to the right next step.