What Is Pretotyping? Definition + Examples
Pretotyping is a fast, cheap way to test whether people actually want a product before you build it. Coined by Alberto Savoia in The Right It, it swaps expensive development for simple experiments — fake doors, manual stand-ins, wooden mock-ups — that generate real demand data, so you validate the idea instead of your own optimism.
Quick Answer: Pretotyping tests demand for an idea before you invest in building it, using quick, low-cost experiments that produce real market data ("would people actually use this?") rather than opinions. A prototype tests how to build something; a pretotype tests whether you should build it at all.
How pretotyping works: test "the right it" before building it right
Pretotyping works by answering one question before you spend real money: if you build this, will anyone actually use it? Alberto Savoia, a longtime engineer and Google's former self-described "Innovation Agitator," built the method around a blunt observation he calls the Law of Market Failure — most new products fail even when they are competently built. The usual culprit is not weak execution. It is building something the market never wanted.
His fix is a mindset shift: make sure you are building "the right it" before you build "it" right. "Building it right" is engineering, design, and polish. "The right it" is the more basic question of whether the product deserves to exist at all. Pretotyping attacks that second question first, while it is still cheap to be wrong.
The evidence you collect has to be your own. Savoia warns against "Thoughtland" — the comfortable place where ideas get judged by opinions, forecasts, and encouraging nods from friends. Opinions do not count. Instead he wants YODA: Your Own DAta, gathered from real people making real choices about your specific idea.
And data only counts when it carries "skin in the game." A verbal "sure, I'd buy that" costs nothing and predicts nothing. A click on a buy button, an email signup, a small pre-order, or a person handing over time or money — those are commitments, and commitments are what pretotyping measures. For a wider walk-through of turning a raw idea into testable evidence, see the complete guide to startup idea validation.
The main pretotype techniques for early-stage founders
Savoia catalogs several pretotyping techniques; four surface most often for early-stage founders. Each one simulates the product experience while building as little as possible.
The Pinocchio pretotype: a lifeless mock you carry around
The Pinocchio is a non-working, lifeless version of a product that you carry around to see whether you would really use it. Its name comes from the wooden puppet who longed to become a real boy. Savoia's favorite example is Jeff Hawkins, who whittled a block of wood the size of a pocket organizer and carried it for weeks — "checking" it with a chopstick stylus — before committing to build the PalmPilot. If you would not use even a fake, you will not use the real one. See what a Pinocchio pretotype is for a full teardown.
The fake-door (façade) pretotype: sell it before it exists
The fake-door, or façade, pretotype puts up the entrance to a product that does not exist yet and counts how many people try to walk through it. That "door" might be a landing page, a pricing button, or an ad; anyone who clicks simply meets a polite "coming soon." Because it uses real strangers spending real attention, a fake door produces exactly the skin-in-the-game demand signal Savoia prizes.
The Mechanical Turk pretotype: humans behind the curtain
The Mechanical Turk hides human effort behind what looks like a finished, automated product. It is named after the 18th-century chess-playing "machine" that secretly concealed a human operator. Rather than building expensive technology up front, you deliver the result by hand — manually producing the "algorithm's" output, for instance — to learn whether people value it at all before you engineer it.
The one-night-stand pretotype: deliver the full experience once
The one-night stand delivers the complete product experience, but only once and mostly by hand. Instead of building a lasting system, you run the full service a single time for real customers — cooking the meal, driving the route, doing the work manually — and watch whether they show up, pay, and ask for more. It is the fastest way to test a service idea end to end.
Pretotype vs prototype vs MVP: what each one tests
These three tools get muddled constantly, yet each answers a different question and demands a different level of investment. The table below lines them up.
| Approach | Core question it answers | What you actually build | Type of data it returns |
|---|---|---|---|
| Pretotype | "Should this exist — will people want it?" | Little to nothing; you fake, simulate, or hand-deliver the experience | Real demand signals with skin in the game |
| Prototype | "Can we build it, and will it work as designed?" | A rough but functioning version of the real thing | Technical feasibility and usability feedback |
| MVP | "What is the smallest real product people will pay for?" | A genuine, minimal, shippable product | Behavior of real, paying early adopters |
Takeaway: A prototype and an MVP both assume the idea is worth building and focus on how to build it. A pretotype challenges that assumption first, for a fraction of the effort — which is why it belongs earliest in the sequence. For a closer split of the first two, see the difference between a pretotype and a prototype.
When pretotyping beats building anything
Pretotype whenever building the real thing would be slow, costly, or hard to reverse — and especially when you feel certain the idea is brilliant. Conviction is exactly the moment founders skip validation and lose the most, pouring months into a product no one asked for.
Start by writing down a falsifiable hypothesis. Savoia frames it as an XYZ hypothesis: "at least X% of Y will Z." Naming the audience and the action you expect turns a vague hope into a number you can test with a fake door or a Mechanical Turk this week. At Edmired we treat that sequence as the default: buy your data before you buy your build.
Pretotyping is not a fit for every case. If something is trivially cheap to build, sometimes the fastest test is simply shipping it. And a pretotype measures interest, not whether you can deliver quality at scale — that is the job of prototypes and MVPs later. The discipline is one of sequence: spend a little to learn whether you are chasing the right it, then invest fully once the data has earned it.
Key Takeaways
- Pretotyping tests demand, not feasibility: it answers "will people actually want this?" before you spend real money building it.
- The method comes from Alberto Savoia's The Right It: make sure you are building "the right it" before you build "it" right.
- Collect YODA — Your Own DAta: run your own experiments on real people instead of trusting opinions, forecasts, or "Thoughtland."
- Insist on skin in the game: a click, signup, or pre-order counts as evidence; a friendly "I'd buy that" does not.
- Learn the four core techniques: the Pinocchio, the fake-door/façade, the Mechanical Turk, and the one-night stand each fake the product cheaply.
- A pretotype comes before the prototype and the MVP: it challenges whether an idea should exist before you invest in how to build it.
- Pretotype hardest when you feel most certain: strong conviction is when founders most often skip the test and build the wrong thing.
Frequently Asked Questions
What does the word "pretotyping" mean?
Pretotyping is a blend of "pretend" and "prototype." You pretend the finished product already exists and test how real people respond, without actually building it. Alberto Savoia coined the term to name a stage that comes even before prototyping: instead of building a rough version to see whether it works, you simulate the experience to see whether anyone wants it in the first place.
Who invented pretotyping?
Alberto Savoia invented pretotyping. An engineer and former self-styled "Innovation Agitator" at Google, he introduced the concept in his 2011 ebook Pretotype It and expanded it into the 2019 book The Right It. His central claim, drawn from watching countless products fail, is that most failures come from building something the market never wanted — not from building it poorly.
Is pretotyping the same as building an MVP?
No. An MVP is a real, minimal product you build and ship to paying users, so it still requires genuine engineering. A pretotype usually involves building little or nothing — you fake the product with a landing page or deliver it by hand. Pretotyping comes first and far more cheaply; an MVP makes sense only after your data says the idea is worth building.
How is pretotyping different from prototyping?
A pretotype tests whether you should build something; a prototype tests how to build it. Prototyping answers "can we make it work?" through a rough but functional version. Pretotyping answers the earlier, more fundamental question — "if we build it, will people use it?" — using simulations and manual stand-ins. Savoia's rule: confirm you have the right it before you build it right.