Most design projects fail in the same place. Not in the pixels. In the weeks around them. Scope stays verbal. Direction stays a mood. Screens arrive as a reveal. Engineering inherits a file that looks finished and is not.
A project should run the other way. Scope, users, and success get locked first. Two or three real directions follow, not a board of references. Then every screen and every state, reviewed as they are built. Then a handoff an engineer can build from — or the same studio builds it.
That is how Fluids Design runs the work. Four steps: Frame, Explore, Design, Ship. You see work every week. The sequence lives on the process page because the order carries information. We do not add a fifth phase when a project feels large.
What should be true before anyone opens a file?
A conversation, whatever you already have, and one person who can make decisions. That is the whole brief we need to start. Pricing is quoted after the first call, never before.
What happens in week one?
Scope, users, and success get locked. You leave week one knowing exactly what you are getting and when. Frame is not discovery theatre. It is the week that makes the rest of the work possible.
A Project agrees a fixed scope and a fixed price in this week. If the problem is smaller, a Sprint can start instead: one problem, one week, one outcome. If the work is ongoing, Embedded can start on a monthly cadence, and you can cancel any month.
How do you pick a direction without a mood board?
We make two or three real directions. You pick one. We go deep. A mood board is a pile of other people’s work. A direction is a screen that already has a point of view: type, structure, hierarchy, and the way a task actually moves.
Each direction is something you could ship if you had to. If a direction cannot survive a real task — sign in, empty, error, success — it is decoration, and we do not present it. You pick one. We do not average them into a fourth.
What gets designed — and who sees it?
Every screen. Every state. Reviewed with you as it is built, not at the end. You will know by day four if the direction is wrong, not week six. We revise until it is right — that is built into how we price, not sold as extra rounds.
Tokens, components, and documentation are not an add-on. They are how the product stays consistent when the next screen is drawn. The longer argument is in what a design system is for.
What does a real handoff include?
Tokens, specs, and assets — or the same team builds it. Your call. The file is not the deliverable. The deliverable is something that can be built without a meeting to decode it. That is design that survives the build.
Which engagement is this — and can you start from outside Saudi Arabia?
Sprint is one week. Project is four to six. Embedded is monthly. Most work is remote. We are based in Saudi Arabia and work across the Gulf and beyond. If you have a system, we work inside it, or fix it, or replace it — see the questions we get asked.
Look at the sites we designed, then book a call. Tell us what you are building. You leave with a clear scope — even if the answer is that we are not the right studio.