Flows and structure
- User jobs, information architecture, and the empty, error, and success states the product needs.
App and UI/UX design
App and UI/UX designInterface design as its own defined project, before a line of production code.
Order the screens, the flows, and the prototype as a project with a start and an end. Design plus development is a different order. You keep the client. We never contact them.
What the design project is for
A build without agreed screens is how timelines slip. This page locks the product on the page, so engineering has something to price.
- 01
Flows people can finish
The jobs the app must do, drawn as screens, not as a slide of boxes.
- 02
A UI in their look
Type, colour, components, and states, so web or mobile engineering is not inventing the interface.
- 03
A prototype you can show
A clickable path through the core jobs, for a stakeholder review you run.
- 04
A spec engineering can quote
The accepted screens become the brief for Custom Web Applications or Mobile App Development.
- 05
Benefits you can sell
Fewer build surprises, a clearer estimate, and a file your client can react to before they fund engineering.
What sits in the design project
The quote names the platforms and the depth. These are the usual layers.
Interface
- Screens and components in the brand, for the device list in the brief: phone, tablet, desktop.
Prototype
- A click-through of the core path, for the review you run with the client.
How it runs
From the jobs to screens you can hand to engineering
You approve flows before we polish every state. Quality check is done in Europe.
How revision rounds work
Flows, screens, and the prototype inside the quoted rounds, on the jobs you listed.
A new product area, a second platform not in the brief, or visual identity from scratch is a new quote.
What we do, and what we need from you
UI work waits on the jobs and the brand. This is the split.
| Task | Your agency |  |
|---|---|---|
| We map the jobs and design the screens to the brief. | ||
| We prototype the core path for the review you run. | ||
| We hand over files a build team can quote from. | ||
| We never contact your client. | ||
| Who uses it, what they must finish, and on which devices. | ||
| Brand files, or a note that identity is a separate order. | ||
| Any existing product, research, or competitor you want us to see. | ||
| Feedback on the dates we agree, including a clear sign-off of the flows. |
Design is the project. Build is the next one.
Ordering both together is fine. The screens still get signed before production code. Design plus development can sit in one programme, but the UI phase still closes first, so engineering quotes against accepted files rather than a moving sketch.
Why agencies sell this on its own
The client sees the product before they fund engineering. You keep the relationship through that review. A signed prototype is easier to price, easier to refuse extras against, and still yours to present.
A website is a different page
Marketing sites sit on Web Design. This page is product UI: accounts, states, and the jobs people finish in the app. Brochure pages, campaign landers, and CMS templates are not in this quote.
Agencies often add these extra services
From the blog
Notes that sit next to this work. All notes
Web Design & Dev
UX Principles for Client Websites
Core UX principles that make websites easier to use, from clarity and consistency to microinteractions and clear design boundaries.
2 min read
Frequently asked questions
Agencies that want app and product UI as a defined project, under their own name.
Ready to brief the screens?
Tell us the jobs and the devices. We design the interface, and you present it.