Velosyti

What a clickable first version saves you

Seeing screens you can click through, before a line of real code is written, catches the expensive mistakes while they are still cheap to fix.

· 2 min read · For anyone commissioning a new app

The most expensive mistakes in software are not bugs — they are the right code built for the wrong screen. A form with the wrong fields, a flow that skips a step your staff actually need, a dashboard that shows the wrong numbers first. These are cheap to fix on a screen you are only looking at. They are expensive to fix once real development has already gone into them.

What a clickable first version is

It is a set of screens you can actually click through — tap a button, move to the next screen, fill a form — built to look and feel real, before any of the underlying system is built. Nothing behind it works yet; the value is entirely in letting you and your team react to it as if it were the real thing, together, in one sitting.

What it catches

  • A step your staff would actually skip or find confusing, only visible once you try clicking through it yourself.
  • A screen with too many fields, or the wrong ones, for how the work actually happens.
  • Disagreement inside your own team about how something should work — better surfaced now than after launch.
  • Whether the overall flow matches how your business actually runs, not how it was described in a meeting.

What it does not replace

It is not a test of performance, security, or whether the real system will handle your actual data correctly — those come later, in the real build, once the screens themselves are agreed. Treat it as a fast, cheap way to agree on what to build, not as proof that it is built correctly.

Questions to ask any vendor

  • Can I click through it myself, on my own phone or laptop, not just watch a video of it?
  • How many rounds of changes are included before real development starts?
  • Does my team get to test it with a few real users before we commit to the full build?
  • How closely will the final product actually match this version?

How we can help

Every project we take on starts with a clickable first version, so you are reacting to real screens, not describing them in a meeting room. See how we work, or talk to us to see this on your own idea.

References

  1. Usability testing — overview
  2. web.dev — learn and build for the web