The flows, before the screens
Every path a person can take through the product, written down and agreed. Removing a step at this stage costs a conversation. Removing it after the build costs a rebuild.
Screens and flows designed, reviewed and agreed before development starts — so the booking, the order or the sign-up actually gets finished, and nobody discovers a wrong assumption three weeks into a build you are already paying for.
Every path a person can take through the product, written down and agreed. Removing a step at this stage costs a conversation. Removing it after the build costs a rebuild.
Screens you tap through on your own phone, in your own hand. You approve something you have used, not a picture of it in a slide.
Including the states a demo never shows: empty, loading, error, no connection, and the long names and long Arabic strings that quietly break a layout.
If the product is bilingual, the Arabic layout is designed rather than mirrored — typography, numerals, dates and the direction the eye actually travels.
We start from the job the user is trying to finish, not from a list of screens. A gym member wants to be training on Tuesday evening; a lab customer wants to know whether a case is ready. The screens fall out of that, and the ones that do not serve it get cut before they cost anything.
You see the flows first and say where they are wrong — you know your business and we do not. Then the screens are built up from those flows, reviewed in passes, and assembled into a prototype you can use end to end.
Nothing goes into development until you have signed off what the product is. That signature is what makes a fixed quote possible: the price stops being a guess about scope and becomes a price for a thing that already exists on screen.
Design can be bought on its own. You get the source files and the exported screens, and you own them — any competent developer or agency can implement from them, including one you have not hired yet.
That is deliberate. A design you cannot take anywhere is leverage, not a deliverable, and we would rather win the build because the design was good than because you were locked in.
Daily companion app
Read the case study →
NFC digital business card
Every business, name, price and phone number in these demos is invented. What you enter is saved only in your own browser, for the day, so you can find it on the dashboard — nothing is sent anywhere.
Restaurant · Dubai · English
Table reservations that show what is genuinely free for your party size, online ordering for collection or delivery, and the staff view — the reservation book, the pass and the menu in one place.
Café & roastery · Dubai · English
A 32-item menu with size, milk and extras, order-ahead for pickup or delivery with a time slot, and the bar's ticket board where staff move each order from new to ready.
Yes. You get the design source files and the exported screens, and they are yours — implement them with any team you like. Most clients go on to the build, but nothing in the arrangement requires it.
Yes, and it is a common way to start. Send us what exists and we will tell you honestly what is ready to build and what still needs decisions — usually the empty, error and loading states, which are the ones that get skipped.
Yes, and it is designed rather than mirrored. Arabic layout is not an English screen reversed: the typography, the numerals, the dates and the way a line is scanned all change. Al-Muslim, ICCD Hub and Voicers all ship bilingual interfaces, and this website is another one.
One to three weeks for most products, depending on how many roles and flows there are. A single-audience app sits at the short end; a platform with three different kinds of user at the long end.
That is exactly what this stage is for, and changing your mind here is free. It is the reason design happens before the build rather than during it.
Describe the product and who uses it. You get a scope summary, and a fixed price for the design stage on its own if that is where you want to start.