Prototyping before development

With a visual prototype you can see and test usability before we write a single line of code. Prototyping takes a little time at the start, but it speeds up development itself and helps reduce costly rework.

We prototype every project, so you see the whole workflow and the users' decision logic already in the design.

Let's start your project

Why prototype?

A prototype is a clickable model of the solution. With it, we try out the user journeys together with you before any money goes into development. For you, that means three things.

We find mistakes before development

In the design we make a change in hours; in finished code it takes weeks. User tests show us the weak spots while fixing them is still cheap.

A shared understanding before the first line of code

You, our designers and our developers see the same picture. We make decisions on the prototype, not by interpreting a long requirements document.

A more accurate estimate and timeline

When every view and user journey has been thought through, we can estimate the development scope more accurately and the budget is more predictable.

  • 10+
    years of experience
  • 50+
    prototyped projects
  • 1000+
    development hours saved

How does the prototyping process work?

  1. Client interviews

    We listen to your goals: who the users are, what frustrates them, which decisions are critical. This usually takes 2–3 days.

  2. Wireframe and workflow

    We map out the workflows, either already designed or in a plain functional layout. The goal is to pin down what the user needs at each point.

  3. User testing

    We test the wireframe with 5–8 people and check accessibility at the same time: contrast, keyboard navigation and form logic. If the users reach their goal, we move on to design. If not, we fix it first.

  4. Iterating to improve

    If you want changes, we don't redo the analysis. We make the changes quickly in Figma, test again and document only the parts that changed.

  5. Documenting the analysis

    We write down how the application behaves, every possible user journey and how we tell the user about errors. Our developers use it as their working instructions.

Tools we use:

  • Figma ja FigmaJam
  • Kasutajatestimine
  • Dokumenteerimine

What can you get at the end of prototyping?

The result of prototyping is not just a picture. You get the materials development can start from straight away.

Clickable prototype
A Figma prototype you can show to your team, board or investors.
User test summary
What the testers did, where they got stuck and what we changed as a result.
User journey map
Every role and journey in one picture, error states included.
Analysis document
A description developers can start working from right away.
Development estimate
A scope, timeline and budget estimate based on a thought-through solution, not on guesses.

How long does prototyping take?

The timeline depends on how many workflows and user roles the solution has. The times below are approximate; we give an exact estimate after the kick-off meeting.

FeatureSmall projectMedium projectLarge project
For examplea landing page or a single workflowan online store or a customer portala B2B portal or an information system
Client interviews1–2 days2–3 days1 week
Wireframe and workflow3–5 days1–2 weeks3–4 weeks
User testing and iteration2–3 days, one round1 week, 1–2 rounds2–3 weeks, several rounds
Documenting the analysis1–2 days3–5 days1–2 weeks
Totalabout 2 weeksabout 3–5 weeksabout 7–10 weeks

Prototyping for the further development of an existing project

We also try out new functionality for a live solution as a prototype before development. We start by mapping the existing solution and its user journeys, so the new part fits logically into what already works.

The prototype helps us decide together what to change and what to keep, and shows our developers exactly which existing views the change touches.

Prototyping from an existing design

If you already have a brand book, a design system or a finished design, we don't create the design from scratch. We build the prototype on your existing components and styles, so it looks like the final product from the start.

That way we reach user testing sooner, and the time goes into thinking through workflows and user logic instead of deciding on colours and buttons.

Completed projects

See more

We have extensive experience in developing IT software and e-commerce solutions for businesses, spanning from the financial sector to insurance and pharmaceutical industries. We serve as a long-term partner for both large corporations and rapidly growing startups.

Frequently asked questions

  • How much does a prototype cost?

    The price depends on the size of the solution: how many workflows and user roles it has and how many test rounds are needed. A small project's prototype takes about two weeks, a larger one several weeks. We give an exact estimate after the kick-off meeting.

  • Do we keep the prototype?

    Yes. We hand over the prototype, the user test summary and the analysis document. The exact terms are agreed in the contract.

  • Can we order a prototype if someone else does the development?

    Yes. We write the analysis document so that another development team can work from it too.

  • What is the difference between a wireframe, a prototype and a design?

    A wireframe is a schematic of the page: what goes where and what happens after a click, without colours or images. A prototype is a clickable model you can walk through a user journey with. The design is the final look. Our prototypes can be simple schematics or already designed, depending on what needs testing.

Get in touch

Ready for development built on a thoroughly tested foundation? Write to us, and we'll talk about what prototyping could bring to your project.

Aleksei Latõnin

Aleksei Latõnin

Chief Operating Officer