• Прототипи · Figma

A prototype: agreeing the structure while a change costs an hour rather than a week of rework

The most expensive changes are the ones that arrive on a finished site. «Where is our delivery page?», «Why is the calculator right at the bottom?», «But we agreed there would be a comparison» — all of this gets said after the markup is built, when every such sentence means a day or two of work. A prototype moves those conversations to the start: grey rectangles with captions, showing every page and what each is made of. Changing something here means moving a block, not rewriting code.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Focus
sites and stores, mostly OpenCart and Next.js
after a free audit
Price
30
Guarantee

days after project sign-off

sites and stores, mostly OpenCart and Next.js
Focus
5
Timeline

to 20 working days

a free conversation about the task
Start
30
Warranty

days from the date the acceptance act is signed

within 2 hours
Reply
under a written contract
Terms
What's included

Complete list of work and what you get as a result

  • a list of every page with an explanation of why each exists
  • the composition of every page type, block by block, in display order
  • the visitor's path from entry to the target action, with all the branches
  • the prototype for the narrow screen on equal terms with the wide one, not «we will adapt it later»
  • draft texts in place instead of «the text will come later»
  • a list of what you have to prepare: photos, documents, data
  • marked places where a decision has not been made yet — so they do not get lost
  • a written sign-off, from which development is counted
When this service isn't right

What's not included — so there are no surprises at delivery

  • a finished design: the prototype is deliberately without colours, fonts or styling
  • writing the final texts for the pages
  • markup and development — the next job with a separate estimate
  • a guarantee that the structure will not change during development
  • promises about the site's positions in search
Who it's for

Situations where this service delivers results

Scenario 1 of 4

A client building a site for the first time

The most useful case. A prototype shows what a site consists of, and the question «what will be there» turns into a concrete list.

We'll review your situation in a free audit
A free conversation about the task

We establish whether a prototype is needed as a separate step: for simple sites it is redundant.

What we measure

  • How many page types there areA landing page is one type. A store with a catalogue, cards, an account and articles is five or six, and each has to be signed off separately.
  • How many people make the decisionA single owner will settle it with themselves as they go. Three managers will not, and the prototype pays for itself with one avoided rework.
  • Whether there is complex logicA calculator, a multi-step form, a customer account. Such things cannot be agreed in words — they have to be seen step by step.
  • Whether it is clear what you sellThis is the main question, and it is not about the site. If the answer is vague, a prototype will not replace it, but it will expose it well.
  • Whether materials existPhotos, texts, documents, product data. The prototype will show how much of it is really needed, and that is usually an unpleasant surprise.
  • Whether going straight to markup is simplerFor a simple two-page site a prototype is a redundant step. We will say so outright rather than sell a stage for the sake of a stage.

What you get

  • an answer on whether a prototype is needed as a separate step
  • a draft list of pages
  • an estimate of the scope and timeline
  • honest advice to start with development straight away, if that is the case

Timeline: 1 conversation

Why is it free

Half the projects do not need a prototype: the site is simple, one person decides, the structure is obvious. We would rather not sell a stage you can do without.

What's next

You get an understanding of the scope. Then you decide for yourself.

Short form: your contact and site URL

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • European clients

    Among our work — projects for Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

What affects the price

Why two seemingly identical tasks are priced differently

  • Number of page typesThe main driver. Not the number of pages but of types: a hundred product cards are one type, while a catalogue, a card and a cart are three.
  • Complexity of the logicA static page is drawn quickly. A multi-step scenario with branches already means several states per step.
  • Depth of the workSchematic blocks with captions are cheaper. A prototype with draft texts and real sample data is closer to a document.
  • Number of sign-offsOne showing plus corrections is predictable. Sign-off through several managers with different opinions means more rounds.
  • The mobile versionDesigning the narrow screen separately is almost a second prototype. But without it the mobile decisions get made blind during the markup.
  • State of the source dataIf the list of services or products is not in order, it has to be put in order first — and that is often the longest part.
Cases

Tasks and results in numbers — all metrics measured by us

a consulting firm in business structuring and raising finance, a one-page corporate site

Task
Build a turnkey corporate site for B2B consulting: explain four service areas (financial management, corporate structuring, M&A, Government Relations), show the team and the way of working, and lead the visitor to a consultation request.
Solution
A one-page site on Next.js: an animated hero section, sections for the target audience, services, the way of working, the team, and a request form. Navigation by anchors (#services, #process, #audience, #team, #contact), with only one internal link in the HTML. GA4 (G-2ENCYLQ2S1) and gtag connected.
Result
TTFB 0.25 s at 102 KB of HTML — the lightest document among the 16 measured portfolio sites and the second fastest response. GA4 (G-2ENCYLQ2S1) is connected — unlike most of the measured projects, the analytics here actually works. Measured 31.07.2026.

a Ukrainian manufacturer of non-combustible wall panels

Task
Present technical products so that a designer or a tender client finds the specifications without calling a manager.
Solution
A corporate site on Next.js with a product catalogue, a calculator and structured data. Organization markup with the address, country and a search action — so the brand is recognised correctly by search.
Result
164 pages in the sitemap with no duplicates; first server response 208–244 ms, a product page 208 ms; 8 types of structured data (Organization, PostalAddress, Country, QuantitativeValue, SearchAction, WebSite, ImageObject, EntryPoint); a correct robots file with service sections closed; analytics connected.

Did not find your case?

Describe how it works on your side — we will tell you whether “Site prototype before development” fits and what it means in your situation. No brief and no call: one question, one answer.

Process steps

Transparent stages with approval at every step

Total duration:5–20 days

  1. A conversation about the task

    1–2 working days

    We establish what you sell, to whom, and what action the visitor is meant to take. Without an answer to that a prototype becomes a set of pretty rectangles.

  2. The list of pages

    1–3 working days

    We compile a list of pages and types, each with an explanation of what it is for. This is usually where it turns out half of what was planned is not needed.

  3. The composition of the pages

    2–8 working days

    We break each type into blocks in display order. Grey rectangles with captions: no colours, so the conversation stays about content.

  4. The narrow screen

    1–4 working days

    We design the same pages for a phone. The order of blocks here is different, and that has to be decided now rather than during the markup.

  5. Draft texts

    1–3 working days

    We put draft headings and captions in place. «The text will come later» is the most common reason a finished site looks empty.

  6. Sign-off

    1–2 working days

    We go through the prototype together, record the corrections and sign the result off in writing. The scope of development is counted from it.

Technologies & integrations

What we build on and what it connects to

Stack

  • Figma
  • HTML
  • CSS
  • JavaScript
  • TypeScript
  • Next.js
  • React
  • Markdown
  • Git
  • GitHub
  • OpenCart
  • WordPress

Integrations

  • Figma
  • Git
  • Google Docs
  • Telegram
  • Notion
A prototype or straight to design

How this option differs from the alternative

What the sign-off conversation is aboutcomposition and order
Cost of a changemoving a rectangle
The development estimaterests on an agreed list
Overall timelinelonger by the prototype stage
When you can do without a prototyperedundant for a two-page site
What we need from you

We can't start without this — best to prepare in advance

  1. what exactly you sell and to whom
  2. what action the visitor is meant to take on the site
  3. what materials already exist: texts, photographs, documents, product data
  4. examples of sites that make sense to you, and what exactly about them
  5. whether there are constraints: a brand style, a platform, existing hosting
  6. who on your side makes decisions and signs off the result

If something is missing — let us know, we'll help you gather it or do it as a separate task.

FAQ

Most frequently asked questions — with concrete answers

Why is the prototype without colours?

Because colours instantly pull the conversation onto themselves. The moment the brand green appears, the discussion moves from «is this block needed here» to «could the shade be darker». Grey rectangles are unpleasant to look at, and that is exactly what makes them useful: there is nothing to say about them except the substance.

Is this not the same as a technical specification?

Close, but a prototype is more honest. A specification can be read three different ways, and each reader will be sure they understood correctly. A prototype is visible: either a block is on the page or it is not. That is exactly why we sign the result off in writing — the scope of development is counted from it.

How many rounds of corrections are included?

Corrections are the point of the stage, not a problem. We go through the prototype together and change it until the structure suits you. Limiting the number of rounds makes no sense: ten corrections here are cheaper than one after the markup. What genuinely affects the timeline is several people deciding with different opinions.

Do you build the site itself after the prototype?

Yes, and that is the most common order. But the prototype stays yours whether or not you continue with us. That is deliberate: a stage after which you are tied to one contractor is a bad stage, and we do not want to build one.

Do you prototype the mobile version too?

Yes, and we advise against economising here. On a narrow screen the order of blocks is different, and if it is not decided now it will decide itself during the markup — that is, by accident. Half the mobile problems of finished sites come from exactly there.

We have no texts yet. Should we wait?

No, the opposite. The prototype is what will show how many texts are needed and of what length — a far more concrete task than «write something about us». We put draft headings in place, and you or your writer replace them with real ones.

How long does it take?

5 to 20 working days. A landing page is a week. A store or a service with an account and several scenarios is closer to the upper end. The longest part is usually not the drawing but the sign-off, when several people decide.

Do you guarantee the structure will not change later?

No, and promising that would be dishonest. During development something new always comes up — the data turns out different from what was assumed, or a new service appears. A prototype does not abolish changes; it reduces their number and makes each of them cheaper.

Let us work out whether you need a prototype as a separate step

A short conversation about the task — and a draft list of pages. Free of charge, we reply within 2 hours.

From measured casesTTFB 0.25 s at 102 KB of HTML

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.