
≈ 8 min read
article · 21 November 2026 · ux / design
Website prototype: why map out the pages before design begins.
How a prototype differs from a mockup, which types of wireframes exist, how to approve them without endless edits, and which projects truly save time and money at this stage.
Most disputes about a website are not about button colours. They happen because the client and the contractor pictured the page differently. One expected a detailed catalogue with filters, the other drew a showcase of three blocks. This usually surfaces on the finished mockup, when redoing it already costs money and weeks. A prototype exists precisely so that such gaps show up earlier, while the page is still a set of grey rectangles.

Most disputes about a website are not about button colours. They happen because the client and the contractor pictured the page differently. One expected a detailed catalogue with filters, the other drew a showcase of three blocks. This usually surfaces on the finished mockup, when redoing it already costs money and weeks. A prototype exists precisely so that such gaps show up earlier, while the page is still a set of grey rectangles.
Below we look at how a prototype differs from a mockup, which types exist, how to approve one and in which projects it really cuts the budget.
What a prototype is and how it differs from a mockup
A prototype is a page diagram: which blocks it contains, in what order, what they say and where each button leads. Colours, fonts and photos are deliberately left out at this stage so that the discussion is about meaning rather than taste. The mockup comes later and answers a different question: how it will all look. In building terms, a prototype is the floor plan of a flat, and the mockup is the interior design with finishes and furniture.
The distinction seems like a formality until you face the reverse order of work. When the mockup is drawn as final right away, every change in meaning breaks the composition: add a pricing block and the grid shifts, remove the reviews and the gap needs filling. The client pays for redrawing even though it was the logic that changed, not the styling.
A wireframe rests on the project goals and the section structure. If the brief is not ready yet, start there: we covered how to put it together in our article on writing a website specification.

Which prototypes a web design studio uses
Several formats hide behind one word, and they should be chosen for the task rather than out of the contractor's habit. They differ in detail, effort and how closely they show the future result.
Here are the four formats that come up most often:
| Format | What it shows | Where it fits |
|---|---|---|
| Hand sketch or whiteboard drawing | The main idea and the order of blocks | A first meeting, discussing the structure |
| Diagram in a design tool | Grey blocks, real headings, button labels | The main working format for most projects |
| Clickable prototype | Transitions between pages and the path to an enquiry | Catalogues, customer accounts, calculators |
| Detailed prototype with copy | Content volume and complex elements | Large sites with many sections |
When a diagram is enough and when you need a clickable version
For a small service website of five to seven pages, a diagram of the home page and one typical inner page is usually enough. The rest follow the same rules. A clickable version is overkill here: the visitor's path is short and easy to talk through.
Things are different when you are building an online store, a customer account or a price calculator. The user goes through several steps, picks options, goes back, and a mistake on one screen drags the others along. A clickable prototype lets you send a link to five colleagues or friendly clients and watch where they get stuck. Such a small test often reveals more than a two-hour meeting.
The mobile version of the prototype
It is worth drawing the phone view separately, at least for the home page and the key landing page. On a narrow screen, blocks line up in a single column, and you immediately see that the enquiry form has slid down to the sixth screen and the pricing table does not fit the width. Fixing this in a diagram is far cheaper than after the layout is coded.
For many companies most visitors arrive from smartphones, so a desktop-only prototype gives a false sense of readiness. We covered typical losses on small screens in our piece on the mobile version of a website.
How to approve a prototype without endless revisions
Approval is the most vulnerable stage. The client is shown grey blocks, nods, and a month later, seeing the colour mockup, realises they wanted something else. To avoid this, the prototype should not simply be sent as a link but walked through together: explain why each block is there, which visitor question it answers and what the person should do next.
A workable approval process usually looks like this:
- The company appoints one person who makes decisions and collects colleagues' comments.
- The contractor presents the diagram at a meeting and explains the purpose of each block.
- Edits arrive as a single list rather than scattered messages from the director, the marketer and the sales team.
- After revision the approved version is fixed, and any further structural changes are discussed separately.
What to check before sign-off
Approve the diagram only once it answers a few simple questions:
- is it clear from the first screen what the company offers and to whom;
- does the page answer the client's main objections;
- is it obvious where to click to leave an enquiry or call;
- are there blocks that are only decorative and explain nothing;
- does the company have enough material to fill everything drawn.
Also make sure the diagram contains real headings and at least draft paragraphs rather than meaningless Latin filler. Real wording changes the prototype itself: it turns out the company has three advantages, not six, or that an honest explanation of the price needs a block with sample calculations. At the diagram stage such discoveries are almost free; after coding they become rework.
How a prototype saves the design budget
Direct savings are hard to express in a single number, but the mechanism is clear. An hour on a diagram costs noticeably less than an hour on a mockup, let alone on coding, so every change moved from a late stage to an early one becomes many times cheaper. On mid-sized projects prototyping usually takes from a few days to two weeks and spares you repeated design rounds. For a business in Moscow, where a launch is often tied to a season or a trade show, this predictability is especially valuable.
An approved diagram becomes a reference for everyone involved: the copywriter sees the volume of text, the developer sees the complex elements, the SEO specialist sees where headings for search queries belong. Design work moves faster because the designer solves only visual tasks and does not invent the structure on the fly. This is how we work as a web design studio too; see our design and branding page for details.
When you can do without a prototype
Not every project needs a separate stage. If the site is built on a ready-made template with a rigid structure, the block layout is essentially predefined, and redrawing it makes no sense. The same goes for small changes to a live site, where one block changes rather than the logic of the page.
Sometimes the stage is skipped because the company has a detailed brief and examples of sites it wants to resemble. This works, with a caveat: someone else's site solves someone else's problems, and copying its structure without understanding why each block is there leads to the same disputes, only later and at a higher cost. The more complex the project, the more expensive the shortcut: a corporate website with dozens of sections built without a diagram almost always ends up in rework.
The prototype as the foundation of UX/UI design
In professional terms, a prototype belongs to interface design: how a person uses an interface and how that interface looks. The first half is about the convenience of the path, the second about appearance. A wireframe covers convenience: the sequence of screens, clear navigation, the number of steps to the goal. If this foundation is well thought out, good styling reinforces it instead of masking flaws. So before ordering a website design, ask the contractor whether a prototype is included.
Visitors usually do not notice a convenient interface: they simply find what they need and leave with a result. We have a separate article on invisible website usability, and well-planned UX/UI design starts with exactly this kind of diagram.
If you are planning a company website or a full relaunch, start with diagrams of the key pages. The epic name. team builds turnkey websites from prototype to launch and will help you approve the structure without extra rounds of revisions; details are on our website development page.
articles
More equally interesting articles.

marketing
Media coverage for business
Which formats to choose, where to find a story, how to write a pitch and a press release, what to know about paid placements and how to make use of a published piece.
read the article21 November 2026tools
Choosing a targeting specialist
We explain how to choose a targeting specialist and check their work: what to ask at the meeting, which access to keep, what reports should contain and which signs show it is time to change contractors.
read the article20 November 2026breakdowns
Behavioural factors
What a search engine learns from how people behave in the results and on your site, why Yandex treats faked behaviour as search spam and how to improve it honestly.
read the article20 November 2026FAQ
FAQ.
Yes, we offer full-cycle social media promotion: strategy, content creation, targeted advertising and results analytics.
We give you access to trello/asana where you can see every stage of the work. We also hold regular calls and send progress reports.
Yes, we work with staged payments. You pay for each completed stage according to the approved plan.
Timing depends on the project's complexity. On average a website takes 2 to 6 weeks. We always give exact deadlines before the work starts.
We can work with your content or offer our copywriters to create unique texts and select images.
The price is made up of the scope of work, functionality complexity, design and additional services (content, crm integration, etc.). We provide a detailed estimate broken down by stages.
With an audit: we study the business, the audience and the goals and shape a clear strategy. Then we fix the terms in a contract, agree on the details and start. Results are shown in numbers, and we build the project's growth on them.
You can leave a request at any time - our operators will call you back within a day. The office works on weekdays from 10:00 to 19:00 moscow time.
Still have questions? We may already know the answer
we'll get back to you within one business day

we help businesses grow
Ready to grow?
Leave a request and our managers will get back to you within one business day



