Skip to main content
Mobius
Intermediate

What is a prototype

Also known as: prototyping

Definition

A prototype is a cheap, early stand in for a product or service, built to show people and learn what to fix before paying to build the real thing.

Why it matters

Changing an idea on paper takes an afternoon, changing it after it is built means paying to build it again.

Common mistakes

Polishing an early prototype until it looks finished, so testers stop criticising and the team stops wanting to change it.

Related terms

Worked exampleIllustration

Paper prototype with test notes

Illustrative: a fictional cosmetics clinic that takes bookings on WhatsApp, no real business. Its new online booking form is drawn on paper and shown to 5 clients at the reception desk, with one task: "book a facial for Friday".

  1. Note 1

    Most testers looked for the time before anything else.

    3 of 5

  2. Note 2

    Some did not know whether to pay now or at the visit.

    2 of 5

  3. Note 3

    One client asked to get the confirmation on WhatsApp.

    1 of 5

  4. Changes

    The time moves to the top, one line explains payment, and the confirmation comes on WhatsApp.

Three changes found in one afternoon, before a single line of code.

Illustration

The fidelity ladder

What do you need to learn?

  1. Step 1

    Paper sketch

    Takes: an afternoon

    Answers: Do people understand the order of the steps?

    Cheapest step that answers it

    The clinic's test: 5 clients at the desk

  2. Step 2

    Clickable screens

    Takes: a few days

    Answers: Can people finish a booking without help?

  3. Step 3

    Working pilot

    Takes: weeks

    Answers: Do real clients book and come?

Cost of one change: Paper, Screens, Pilot, Live product. You are here: Paper⁨Cost of one change⁩⁨Paper⁩⁨Screens⁩⁨Pilot⁩⁨Live⁩⁨product⁩⁨You are here⁩

Paper sketch is the cheapest step that can answer this question. Paper is the cheapest place to be wrong: the clinic found three changes in one afternoon, before any code.

Illustrative: the steps a fictional clinic can take before it builds a booking form for real. Each step up takes longer and answers a different question.

The later the change, the more it costs

Cost of one change: Paper, Screens, Pilot, Live product. Cheapest here⁨Cost of one change⁩⁨Paper⁩⁨Screens⁩⁨Pilot⁩⁨Live⁩⁨product⁩⁨Cheapest here⁩

Source for the direction, not for a number: Jakob Nielsen, "Paper Prototyping: Getting User Data Before You Code", NN/g, 2003.

A shape, not a measurement: the same change costs more at each step from paper to a live product. No numbers are drawn, because the popular multipliers have no solid source.

Definition

A prototype is an early, cheap version of a product or service made to be shown and tested, not sold. It can be a paper sketch of a booking form, a few screens you can click through, a sample dish or a trial class. Nielsen Norman Group describes a prototype's fidelity as how closely it matches the look and feel of the final system. Low fidelity, such as paper, is quick to make and easy to change. High fidelity looks like live software and suits later tests. A prototype answers whether people understand the idea and want it. An MVP goes one step further and tests whether they use it or pay for it.

Why it matters

Jakob Nielsen put it plainly in 2003: it is much cheaper to change a product early in the development process than later. A prototype also shows where people hesitate before anyone writes a line of code. Its real risk is polite feedback, because people praise what they are shown.

Directly related: MVP, UX, UI.

Improvement tips

  • Start on paper or with simple screens, and move to a working pilot only when the cheaper version stops teaching you anything new.
  • Give each tester one task, such as "book a facial for Friday", and watch where they hesitate.
  • Test with real or likely customers, not friends, and write down what they do rather than what they say.

Common mistakes

  • Asking "do you like it?" instead of giving a task and watching.
  • Treating praise from a prototype test as proof that people will pay.
MVP vs Prototype

Related terms

StartupsBeginner

MVP

An MVP (minimum viable product) is the smallest version of a product real customers can use, built to learn whether they want it before you build all of it.

ProductIntermediate

UX

UX, user experience, is everything a person goes through with your business, from the first search to the follow up, and above all where they get stuck.

ProductBeginner

UI

UI, user interface, is what a person sees and taps on a screen, the buttons, text, menus and their layout, and it tells the eye where to look first.

ProductBeginner

User Story

A user story is one short sentence that says who needs something, what they want to do and why, so the person building it understands the goal.

From the blog

The MVP Trap: Build an Experiment, Not a Product

Why founders overbuild MVPs, how to choose the riskiest assumption, and how to test demand before months of product work.

Quick check

A clinic wants to know whether clients understand its new booking form. What is the cheapest useful first step?

Choose an answer

Frequently asked questions

Do I need a prototype before I start my business?
Not necessarily a software one. Any cheap way to show the idea before paying for it counts: a drawing of the order form, a sample product, one trial session. If showing it to five customers could change your plan, it is worth doing.
When does a prototype first become useful?
The moment you are about to pay someone to build something: a website, an app, a new service. A prototype shown first costs little and often changes the brief.
How do I build a prototype with no budget?
Draw the screens on paper, one sheet per screen, and swap the sheets as the tester "taps". For a service, run it once by hand for a few customers before you set it up properly.
Can a prototype help me raise money?
It can make an idea easier to understand, and investors see that you tested it. It does not prove demand: what people do with a real offer does, and that is the job of an MVP.
Why does prototyping matter for a business already running?
Before a new website, a new booking flow or a new service, a prototype shows customers the change before you pay for it, so the fixes happen on paper.
What goes wrong when a business skips the prototype?
The problems show up after the build, when every fix costs a new round of work. Features that confuse customers stay, because changing them now is expensive.
How do I use prototypes without slowing down?
Keep them small: one screen or one step of the service, one task, five people, one afternoon. The UX page explains why a handful of testers is usually enough.
How do I get useful feedback on a prototype?
Give one task, then stay quiet. Note where people hesitate and what they ask. Do not explain the screen: if it needs explaining, that is the finding.
What does prototype mean in plain words?
A rough draft of a product or service that you can show to people. It looks enough like the real thing to test, and it is cheap enough to throw away.
Is building a prototype risky?
It is cheap, but not free of risk. The main risk is polite, falsely positive feedback: people praise what they are shown. Watch what testers do, not what they say.
Do I need to code to build a prototype?
No. Paper, a presentation with linked slides or a simple design tool is enough. Code comes later, when the cheaper versions stop teaching you anything new.
What is the difference between a prototype and an MVP?
A prototype tests whether people understand the idea and want it. An MVP is a real, working first version that tests whether they use it or pay for it. The comparison page on this site sets the two side by side.

Sources: Kara Pernice, "UX Prototypes: Low Fidelity vs. High Fidelity" (nngroup.com, 2016), Jakob Nielsen, "Paper Prototyping: Getting User Data Before You Code" (nngroup.com, 2003)

Last reviewed: 2026-09-24

I have worked with

What Clients Say

From different fields, at different stages of business

Dan Manto

Eclipse Capital

Real Estate Investment and Finance, USA

Arty McLabin

GameReady

Game Development Education and Outsourcing, International

Anna, Beautician

Anna

Beautician

After I finished a cosmetology course at a leading company, I was confused. I didn't know how to open a business, what to sell from home, or how to bring in clients. Since I reached out to Mobius, everything has changed. We built an organized plan with clear steps and no unnecessary risks. Today I see results, and I'm growing and developing every month.

Mark, Massage therapist, Gan Yavne

Mark

Massage therapist, Gan Yavne

When I finished a massage course, I imagined a different world. I found out it's a hard field, and financial stability isn't easy to find. When I came to Mobius, something changed. We started an organized process and built a business plan. Without Mobius? I probably would have given up. Today I believe in myself and in my own path.

Building a product and unsure of the next step?

Alex helps Israeli teams turn product ideas into something that ships and sells. The first call is free.

+972 055-248-6151. Better on WhatsApp: I am in meetings most of the day and answer as soon as I am free.