THE VALIDATION LABORATORY — HOW WE WORK BEFORE WE BUILD
Not a product.A practice.
The Validation Laboratory is the practice every Wabbit engagement draws on before the first line of code gets written. It exists because a product can be executed beautifully and still fail — because the problem it solves isn’t painful enough for anyone to pay to solve. It’s how we reach the early verdict: what the evidence says, before you commit to the build.
Roughly half of new businesses don’t survive five years; two-thirds are gone by ten. Those numbers don’t say why — but they say something simpler: surviving long enough to learn the expensive way isn’t guaranteed. The why has its own data. In CB Insights’ post-mortem analysis of 431 failed startups, the single most common cause of death — 43% — was poor product-market fit: building for demand that wasn’t there. That one is preventable.
Sources BLS, 2024CB Insights, 2024
The most common cause of death is the one you can test for.
Most of this work is invisible. That is the point.
Six steps. Roughly five weeks, depending on the question.
The Lab isn’t one exercise. It’s a sequence — each step’s output is the next step’s raw material, and every name on the list is something we’ll point at by name during your engagement. The first five steps exist so the sixth one tests the right thing: they extract and sharpen what the founder knows until it’s fit to put in front of strangers, and the Field Test then measures whether strangers pay. How much of the Lab an engagement needs depends on the size and the shape of the bet — more on that below.
Mining and Refining.
The Vault.

The Proclamation.
The Frame.
The Hook.
The Field Test.
That’s the Lab. Six steps. Real outcomes at every step. Most of the value isn’t in the final answer — it’s that every step produces something the founder keeps using for the lifetime of the business.
You are not paying for the Lab. You are paying for the right answer about what to build — even when that answer is not yet.
When the engagement is a site or a launch, the Lab runs fast inside the project itself: Mining-and-Refining, a working Proclamation, a Hook, and a positioning experiment that informs the site.
When the bet is platform-scale, the Lab becomes the engagement’s spine: the Architecture Sprint does the extraction and designs the first test, and then the build runs as a sequence of tests — each phase ships something real, puts it in front of the market, and the next phase commits only on what held.
Either way, the Lab is how we make sure it’s the right one to build.
See the build offer →Does the Lab actually produce results?
Different industries, different scales, different-sized bets. The same discipline every time — adapted to the question — including the file where the honest answer was don’t build.
The audience never materialized. He found out for $3,850, not a year of his life.
From a single $250 test, before a dollar went into the build.
The test came before the build; the best month came after.
The other kind of bet — payback, not demand: outgrown tools, rebuilt without breaking.
Where the discipline comes from — four years of sales before Wabbit existed, every offer taken.
Honest about who this is for.
- You’re about to build, and want to be sure it’s the right thing
- You’d rather decide on real market behavior than a gut feeling
- You want the thinking to outlive the project — the Vault and the writing stay yours
- You can give the process a few weeks before committing the budget
- You just want a good-looking website, fast — that’s Launch, and we sell it happily
- You already have a proven, profitable model and the question is machinery, not demand — start at the Architecture Sprint instead
- You need immediate revenue and can’t invest the weeks
- You want certainty guaranteed — the Lab reduces risk, not removes it
Not sure how much of it you need? That’s the Architecture Sprint’s first job: it does the Lab’s extraction work and comes back with the verdict on the build, the plan for it, and the first test.
We tried productizing the Lab. We stopped.
- E.01
- Attempt
- For a few years we sold the Validation Laboratory as a standalone offer — a defined-scope engagement with a price tag, a deployment timeline, and a monthly fee.
- E.02
- Outcome
- The methodology worked when we ran it. A clear answer; a clear next step.
- E.03
- Failure mode
- Productized, separated from the build it was meant to inform, it kept producing the same outcome: the founder left holding a validated idea and a search for someone to build it. The documents survived the handoff; the momentum and the context didn’t — a builder who wasn’t in the room starts over on understanding.
- E.04
- What we do now
- The Lab and the build are most powerful when they’re the same engagement. So now they are.
Before you ask.
- Q.01
How quickly will I know if the idea is valid?
Two to four weeks after the Field Test goes live — once real behavior (not stated intent) has had time to register.
- Q.02
How is this different from a landing page or a survey?
It measures real behavior and real spend, not stated intent. A survey tells you what people say. The Field Test tells you what they do when their wallet is involved.
- Q.03
What if the idea doesn’t validate?
You’ve saved a season and a budget. You keep every artifact — the Vault, the Proclamation, the Frame, the Hook — and you can re-aim with them intact.
- Q.04
Do I keep what the Lab produces?
Yes. You own the Vault, Proclamation, Frame, and Hook outright. They’re designed to keep producing value long after the engagement closes.
- Q.05
How does the Lab fit into a full build?
It doesn’t sit in front of the build; it runs through it. At platform scale, the Architecture Sprint does the extraction work and designs the first test; then the build proceeds in phases, and every phase ends the same way — something real goes in front of the market, and the next phase commits only on what held. An MVP before the full build; an MVP of a feature before the feature. When the bet is the machinery under a working business, the same discipline runs with payback as the test instead of demand.
From the Brainforest · The lantern before the build
Every Wabbit keeps a lantern lit before it builds.
We don’t guess our way through the dark. We map it first.
The Lab is that lantern — the light you cast on a dark idea before you commit a season to it. (The Brainforest? Where wabbits come from — and no, we’re not explaining it here; the Library will.)


