UX/UI design
Flows and screens, agreed before any code is written.
- User flows
- Wireframes
- Design system
- Prototypes you can click
What this is for
Settling what a thing looks like and how it moves before it is built. Design is where the expensive questions get answered cheaply: what happens on an empty screen, what somebody sees when an action fails, and which of two ways of doing a task takes fewer steps. Changing a drawing costs a conversation; changing built software costs the build. What comes out is a set of screens and rules precise enough that the front-end has nothing left to guess at.
What it covers
- User flows
Every path through the product traced end to end, including the ones that stop halfway, go wrong, or are taken by somebody without permission.
- Wireframes
Structure and hierarchy settled before colour and type enter the conversation, so layout is judged on its own terms.
- Design system
The components, spacing, type scale and colour that screens are assembled from, so the twentieth screen is consistent with the first.
- Prototypes you can click
A clickable version to try before anything is built. It is where a flow that reads well on paper is found not to work in the hand.
What you end up with
- A flow for every path a user takes
Including empty, loading, error and permission-denied states, which is where most of the gaps in a specification are found.
- Screens for each of them
Drawn at the widths they will actually be used at, rather than at one convenient canvas size.
- A prototype you can click through
Shared as a link, so people who were not in the room can react to the real thing rather than to a description of it.
- A component set the build follows
With measurements and behaviour attached, so the built version matches the design instead of approximating it.
What we need from you
- Who the user is, and what they came to do
A sentence for each kind of person who will use it. Design without that is decoration.
- Anything you have — sketches count
Existing screens, a competitor you think gets it right, a diagram drawn on paper. All of it shortens the first round.
- The constraints that are not negotiable
A system that has to be kept, a brand that cannot change, a rule you are held to. Far better stated at the start than discovered at review.
Who works on it
Each part is done by the specialist for it, in the order the work reaches them.
How it runs
- DiscoveryFirst
We work out what you need, what it has to do, and what it will cost.
- Scope written down
- Fixed quote
- Agreed timeline
- DesignBefore the build
You see the site before it is built, on desktop and phone, and approve it before the build starts.
- Designs to approve
- Mobile and desktop
- Final copy
- BuildThe build
The design is built to its measurements, on a link you can open at any point during the build.
- Live preview link
- Progress you can see
- Content loaded
- LaunchHandover
Domain, hosting and email pointed at the new site. Checked on real devices, handed over in your name.
- Live on your domain
- Accounts in your name
- Support after launch
- SupportAfter launch
Updates, fixes and changes for as long as the site is live.
- Updates and fixes
- Monitoring
- A number to message
Questions people ask first
With a conversation about what you actually need, and then a written scope with a price against it. Nothing is built until you have agreed both, and that scope is what the work is measured against for the rest of it.
Also under Design
Get in touch
Every one of these reaches us directly, and is answered by a person.