# Pretotyping

Pretotyping uses deliberately minimal simulations to collect behavioral evidence about whether people want an idea before the team builds a functioning product.

- Type: method
- Domain: Strategy & discovery
- Level: Intermediate
- Last reviewed: 2026-09-23
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/pretotyping/>)

## What it means

Pretotyping is a family of rapid, low-investment tests designed to answer whether a proposed product is worth pursuing before answering whether it can be built well. A pretotype may simulate an experience, manually deliver a result, expose a nonfunctional choice, or limit an offer to a tiny audience so the team can observe real commitments rather than rely on stated enthusiasm.

## Why it matters

Teams can execute a plausible idea beautifully and still discover that too few people care. Pretotyping moves the riskiest demand assumption ahead of substantial design and engineering investment. It makes weak interest cheaper to discover, sharpens the target customer and promise, and creates evidence that can improve or end an idea without treating sunk effort as a reason to continue.

## When to use it

Use pretotyping when demand, adoption, or repeated use is uncertain and a faithful prototype would take meaningful time or money. It works best when the team can define a concrete behavior that represents interest. Do not use deception that could harm people, collect sensitive information unnecessarily, or imply that an unavailable product is ready for purchase without a clear explanation.

## How it works

1. Name the most consequential assumption about who will take what action and why.
2. Choose an observable commitment stronger than an opinion, such as joining a qualified waitlist, scheduling a trial, submitting relevant data, or accepting a real constraint.
3. Create the smallest ethical simulation that can expose that behavior without building the underlying product.
4. Set the audience, threshold, time box, and decision rule before collecting results.
5. Run the test, examine behavior and context, then stop, revise, or invest in a higher-fidelity experiment.

## A practical example

A startup considering an automated procurement assistant first offers a clearly labeled concierge pilot to ten operations managers. Behind the interface, a founder manually prepares the recommendations. Only two managers return for a second request, and both need audit features the original concept omitted. The team revises the value proposition before automating anything.

## Where it breaks

A pretotype measures behavior within an artificial and usually narrow setting. Manual delivery can create service quality that software will not reproduce, while a rough facade can understate demand for an unfamiliar idea. Small convenience samples, novelty, misleading scarcity, and poorly chosen commitment signals can all produce false confidence.

## Common mistakes

- Building a polished prototype when the core question is whether anyone will make a meaningful commitment.
- Counting clicks or compliments as demand without defining what behavior would justify investment.
- Hiding the simulated nature of an offer in ways that misuse trust or expose customers to financial, privacy, or operational harm.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/pretotyping/#visualization-pretotyping>)

## Sources

1. [Pretotyping Resources](<https://www.pretotyping.org/resources.html>) — Pretotyping.org · Original method resources
2. [Pretotyping Quick Reference](<https://www.pretotyping.org/uploads/1/4/0/9/14099067/pretotyping_quick_reference_ms_e_277_2016.pdf>) — Pretotyping.org · Practitioner guide

## Related topics

- [Minimum Viable Product](<https://wiki.soroush.uk/topic/minimum-viable-product/>)
- [Concept Testing](<https://wiki.soroush.uk/topic/concept-testing/>)
- [Validated Learning](<https://wiki.soroush.uk/topic/validated-learning/>)
