← All insights

Why you approve the UI before we write code

Changing a design takes minutes. Changing finished code takes days. Here is why sign-off comes first.

On every app and website we build, there is a point where we stop and ask you to sign off the design. Only after that do we start writing code. Some clients find this a bit slow at first. Here is why we do it.

Changes are cheap on screen and expensive in code

Moving a button, renaming a menu or adding a step to a form takes a few minutes in a design file. Once that screen has been built, connected to a database and tested, the same change can take a day or more. Catching it early saves you money.

You see the real thing, not a description

A written brief can mean different things to different people. A clickable prototype cannot. You tap through the screens on your own phone and see exactly how it will work. If something feels wrong, you will notice it straight away.

You can test it with real people

Before any development starts, you can show the prototype to a few customers or staff members and watch them use it. If they get stuck, we fix the design, not the code.

It keeps the quote honest

Once the design is approved, we both know exactly what is being built. That makes the timeline and the price far more reliable, and it gives us a clear reference if questions come up later.

What sign-off looks like

We share the designs with you, walk you through them and collect your feedback. We usually go through one or two rounds of changes. When you are happy, you approve it in writing and we start building. Changes after that are still possible, they are just quoted separately so there are no surprises.

Want to see how this would work for your project? Get in touch.

More insights