Why prototype when you can just design the pages
A common scenario: the client receives a good-looking mockup, and only during approval does it turn out there is no pricing section, the lead form is buried at the bottom, and there is no room for the Uzbek version, whose text often runs longer than Russian. Fixing that in a finished design, or worse in a coded site, costs time and money.
A prototype answers a different question than a design does. Design shows how the site looks; a prototype shows how it works: which path a visitor takes, how many steps lie between landing and enquiry, what happens when someone taps Order. That is why it is easy to discuss with your sales team, not only with the director.
The stages of Figma prototyping
Good prototyping doesn't start in Figma. First you need to understand the business and the audience, and only then open the design tool. A typical sequence looks like this:
- The site's goal: leads, calls, Telegram chats, online payment or a simple service showcase.
- Page and section structure, a sitemap on paper or in a spreadsheet.
- Low-detail screen layouts (wireframes): blocks, placeholder headings, button positions.
- Links between screens: menus, clicks, pop-ups, form steps.
- Testing with real people: colleagues, managers, a few friendly customers.
- Revisions and locking the approved version before visual design starts.
What to account for in the Uzbek market
Most visitors arrive on a phone, from Instagram, Telegram channels, Meta and Google ads. So the phone screen is drawn first and the desktop layout adapts afterwards. Do it the other way round and the mobile version ends up as a stripped-down copy.
Languages deserve their own attention. A Russian and Uzbek switcher should be visible on the first screen, and blocks should survive different text lengths. Payments and contacts matter too: where the Click or Payme choice appears, whether there is a Telegram chat button, what the order confirmation page looks like. It is far easier to build these into a prototype than to bolt them on later.
How to approve a prototype without dragging the timeline
The main rule is a single decision-maker. If five people review the mockup and each sends separate edits, work stalls. Appoint one person who collects every comment into a single list.
Phrase feedback as a task rather than a taste: “customers can't tell what delivery costs” or “the sales manager needs a call button higher up”. Comments like these turn into changes quickly. Also separate must-haves from wishes for later, otherwise version one never ships.
What drives the cost of prototyping
Price is set by the amount of thinking, not by the software. It depends on the number of unique screens and scenarios, the complexity of the logic (a calculator, a personal account, a filtered catalogue), the number of language versions, how interactive the prototype needs to be and how many revision rounds you go through. A one-scenario landing page and an online store with a cart are very different jobs, so an honest estimate is only possible after a conversation about goals.
Who does the work matters as well. A designer who doesn't know how the site will be built may draw something expensive or impossible to implement. It is better when the prototype is handled by people who understand both development and marketing.
Common mistakes
The first is skipping the prototype to save time: the time is then spent on rework. The second is making it too detailed, with final colours and photos, so that discussion drifts into styling. The third is forgetting analytics: if goals and events aren't planned up front, you won't be able to tell later which buttons and forms bring in enquiries.
How it connects to turnkey website development
A prototype is the foundation for the estimate, the timeline and the technical brief. Once the structure is approved, the developer knows the scope and you know what you are paying for. At markdev we start website development from goals and a prototype, not from picking a template. If you'd like to talk about how this would work for your business in Tashkent or the regions, send us a request and we will go through the task with you.
FAQ
How is a prototype different from a website design?
A prototype shows structure and logic: which blocks exist and how a visitor moves between screens toward an enquiry. Design adds colours, fonts, photos and brand style. The prototype is approved first, then the design is drawn.
Do I need a prototype for a small landing page?
Yes, but it can be simple: a sketch of the blocks and the path to the lead form. A one-page site needs a short approval round, while a store or a site with a personal account needs a more detailed prototype.
Can I use Figma for free?
Figma has a free plan with limitations, which is often enough for small projects. Plan terms change, so check the current limits on the service's official website.
Who should approve the prototype on the client side?
Ideally one person who gathers opinions from the director, marketer and sales managers and passes on a single list of edits. That cuts down the number of approval rounds.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.