Process

Four weeks. Four steps.

You see work every week. Nothing disappears into a black box, and the price agreed in week one is the price at the end.

1. 01 · Week 1

   Frame

   Scope, users, and success locked. You leave week one knowing exactly what you’re getting and when.

2. 02 · Week 1–2

   Explore

   Two or three real directions, not mood boards. You pick one, we go deep.

3. 03 · Week 2–4

   Design

   Every screen, every state. Reviewed with you as it’s built, not at the end.

4. 04 · Week 4+

   Ship

   Handed to engineering with tokens, specs, and assets — or built by us. Your call.

Why fix the scope in week one?

Because an open scope is where design projects go wrong, and it goes wrong quietly. Week one settles what is being designed, who it is for, and what would count as it having worked. Everything after that is execution against a decision you were part of, rather than a negotiation you find yourself in at week five.

The price is agreed then too, and it does not move unless you move the scope. Revisions are inside it — that is what “until it is right” means, and it is priced on the assumption that a project reviewed weekly needs fewer of them than one revealed at the end.

What do you need from us?

A conversation, whatever you already have, and one person on your side who can make decisions. That last one is the whole list, really. A project with three approvers and no decider is the single most reliable way to turn four weeks into ten.

Which engagement fits?

What does handover include?

Every screen at every state, the tokens and components as code rather than only as a Figma library, and the reasoning — what a component is for and when not to use it. If we are building it, handover is to ourselves and you get the same package anyway, because the day you want to move it elsewhere should not be the day you discover it was never written down. More on that in how a design project should run.