When people first hear the word pretotyping, they usually ask the same question:
Wait, don’t you mean prototyping?
No. Pretotyping and prototyping answer different questions.
Pretotyping asks: should we build it? It tests whether customers want the idea, will change their behaviour for it, or will put some skin in the game before you invest in building.
Prototyping asks: can we build it? It tests whether the product, service, interface, or technology can work once you already have enough evidence that the idea is worth building.
That order matters. Prototype too early and you can spend months proving that a team can build something customers never wanted.
Pretotyping vs Prototyping: The Short Version
| Question | Pretotyping | Prototyping |
|---|---|---|
| Core question | Should we build it? | Can we build it? |
| Main risk tested | Demand risk | Feasibility and usability risk |
| Best timing | Before committing budget, roadmap, or build capacity | After demand is credible enough to explore the solution |
| Output | A small experiment that measures real behaviour | A rough or functional version of the product |
| Evidence | Clicks, signups, deposits, usage, repeat behaviour, customer action | Technical proof, interaction feedback, usability issues, implementation learning |
| Typical methods | Fake Door, Pinocchio, Mechanical Turk, Facade, YouTube, Provincial | Wireframes, clickable prototypes, coded prototypes, service prototypes |
| Failure mode | The test is too vague to measure real demand | The team builds a polished version of the wrong idea |
If you only remember one thing: pretotyping comes before prototyping when the biggest unknown is whether anyone wants the idea at all.
What Is Pretotyping?
Pretotyping is a way to test whether people want an idea before you build it. A pretotype is the smallest believable version of an offer, product, service, or experience that lets you measure real customer behaviour.
The point is not to ask people if they like the idea. The point is to see what they do when the idea appears to be available, useful, or costly.
Good pretotyping tests measure signals such as:
- Clicking to learn more.
- Joining a waitlist.
- Paying a deposit.
- Booking a call.
- Trying a simulated service.
- Returning to use it again.
- Choosing it over an existing workaround.
Pretotyping was created by Alberto Savoia at Google and is covered in the free book Pretotype It. If you need the broader definition, start with what is pretotyping.
What Is Prototyping?
A prototype is a first or preliminary version of a product, service, interface, or component. It helps a team learn how something might work, feel, or behave before it becomes a finished product.
Prototypes are useful when the team needs to answer questions like:
- Can we build this?
- Will the interaction make sense?
- How might the product work in practice?
- What is technically hard?
- What needs to change before a real launch?
Prototyping is valuable. It just answers a different question. A prototype can tell you whether a thing can be built, but it cannot automatically prove that the thing should be built.
When To Use Pretotyping Before Prototyping
Use pretotyping before prototyping when the biggest risk is demand.
That usually means:
- The idea is new or unproven.
- The business case depends on customers changing behaviour.
- The team is relying on opinions, surveys, or competitor evidence.
- The product will be expensive or slow to build.
- Stakeholders are already attached to the solution before demand has been tested.
- The idea sounds exciting, but no one has put real effort, money, or time behind it.
This is where teams get into trouble. They use prototypes to create momentum, then mistake that momentum for evidence. A beautiful prototype can make a weak idea look stronger than it is.
When To Prototype
Prototype once you have enough demand evidence to justify learning how the solution should work.
That means you have seen signs such as:
- Customers take action when the offer appears real.
- The problem is painful enough to interrupt existing behaviour.
- The value proposition is clear enough for people to respond.
- The target audience is specific.
- The team knows which assumption the prototype needs to test next.
In that sequence, prototyping becomes useful. You are no longer asking whether anyone cares. You are asking how to deliver the value well.
Examples: Pretotyping Before Prototyping
1. Fake Door Before Building A Feature
A team wants to build a new reporting dashboard. Instead of prototyping the whole dashboard, they add a real-looking entry point in the existing product: “Generate board report.”
When users click, the page explains that the report is being tested and asks what they expected to see. The team measures clicks, roles, frequency, and willingness to talk.
If no one clicks, the prototype can wait. If the right users click repeatedly, the team has a stronger reason to prototype the report.
2. Concierge Test Before Building Software
A company wants to launch an AI assistant for procurement teams. Before building the model, they run the experience manually for a small number of users.
Customers submit requests. A human team produces the output quickly behind the scenes. The test measures whether users trust the output, come back, and would pay for the workflow.
If the service creates repeat usage, the prototype can focus on automating the parts that matter.
3. Landing Page Before An AI Prototype
A team has an AI product idea but no proof that customers want it. They launch a simple landing page with the promise, pricing signal, and a call to join a pilot.
The pretotype measures traffic quality, conversion rate, customer language, and whether the right buyers take the next step.
Only then does the team decide whether a prototype is worth building.
Decision Guide
Use this quick sequence:
- If the idea is mostly unproven, pretotype first.
- If people say they like it but have not acted, pretotype first.
- If the team is arguing from opinions, pretotype first.
- If customers have already taken meaningful action, prototype the solution.
- If the technical path is the biggest unknown, prototype.
- If both demand and feasibility are uncertain, run a pretotype to test demand before spending heavily on technical exploration.
The practical rule is simple: test desire before design, then test design before delivery.
Pretotype + Prototype Is The Best Sequence
Pretotyping and prototyping work best together, in order.
Pretotyping gives you Your Own Data, or YODA as Alberto Savoia calls it. It tells you whether the idea deserves more time, budget, and attention.
Prototyping helps you shape the product once the demand signal is strong enough to justify building.
The mistake is treating them as interchangeable. They are not. A prototype without demand evidence can become a very expensive opinion.
Frequently Asked Questions
What is the difference between pretotyping and prototyping?
Pretotyping tests whether customers want an idea before you build it. Prototyping tests whether the product, service, or interface can work once the idea is worth building.
Is an MVP a prototype or a pretotype?
An MVP can behave like either, depending on what it tests. If it measures real customer demand with the smallest possible version of an offer, it is close to a pretotype. If it is mainly a rough build used to test usability or functionality, it is closer to a prototype.
Should you always pretotype before prototyping?
No. If demand is already proven and the biggest risk is technical feasibility or usability, prototype. But if the idea is unproven, expensive, or based mainly on opinion, pretotype first.
What is a pretotype example?
A fake door test is a common pretotype. You present a product, feature, or service as if it is available, then measure whether people click, sign up, pay, or otherwise take action before you build it.
Why does pretotyping matter for AI products?
AI makes building faster, which makes building the wrong thing easier. Pretotyping lets teams test whether customers want the AI-powered outcome before investing in models, data, infrastructure, and integration work.
Where To Go Next
Start with the full pretotyping hub, then choose a method from Pretotyping Methods 101 or study real pretotyping examples.
If your team is deciding whether to build, prototype, or stop an idea, see how Exponentially helps teams apply rapid experimentation or work with me to get evidence before committing budget.