Research and workflow mapping
Time with the people who will use the software, to learn what they do today, where they get stuck, and what they work around.
UI and UX design
Screens people understand the first time, designed before a line of code.
Overview
Good design in business software is mostly about removing steps. We watch people do the job, sketch the flow, and test clickable prototypes with real users before the build starts, so the expensive changes happen on paper.
What you get
- User research and workflow mapping
- Clickable prototypes in Figma
- Design systems your developers can reuse
- Usability testing with real users
What we offer
UI and UX design, in detail
Pick the parts you need. We scope them together, quote a fixed price, and build in two-week steps.
Wireframes and prototypes
Clickable Figma prototypes you can try on your own phone and share with your team before any code is written.
Visual design
Interfaces that match your brand and stay readable in a bright warehouse or on a cheap phone.
Design systems
A shared library of components and rules, so new screens stay consistent and are faster to build.
Accessibility
Contrast, text size, keyboard use, and screen reader support checked against WCAG 2.1 AA.
UX audits
A review of an existing product with a prioritised list of what to fix first and why.
Where it fits
Typical projects
- Redesigning an internal tool staff have learned to avoid
- Designing a new product before raising funds or starting the build
- Making a consumer app simpler for first-time smartphone users
- Creating a design system for a growing product team
Technology
What we use
Well-supported tools with a long runway, chosen for the project rather than for novelty.
- Figma
- FigJam
- Design tokens
- Storybook
- Maze
Where AI fits in
AI helps us move faster in the early stages: drafting copy variants, summarising interview notes, and generating first-pass layouts we then refine by hand. Final designs are always decided by people.
How it works
From first call to production
Every engagement follows the same shape, so you always know what happens next and what you will see.
- 01 · Week 1
Scope
We sit with the people who will use the thing. You get a written scope, a fixed estimate, and an honest note about what we would cut first.
- 02 · Weeks 2 to 10
Build
Two-week iterations against a shared board. You see working software every fortnight, not a status deck.
- 03 · Launch week
Launch
Staged rollout, real monitoring, and a rehearsed way back. We stay on the call until the graphs go flat.
- 04 · Ongoing
Run
Patching, alerts, and a monthly review of cost and reliability. Leave with your code and your documentation whenever you want.
Questions
Frequently asked questions
Can we hire you only for design?
Yes. Some clients take our designs to their own developers. We hand over Figma files, a component library, and notes on behaviour.
How long does design take?
Research and prototypes for a focused product usually take two to four weeks, depending on how many user groups are involved.
Do you test the designs?
Yes. We test prototypes with a handful of real users before the build. It is the cheapest point to find a problem.
Related
More from Build
Have a project like this in mind?
Send a paragraph about what you need. An engineer replies within one working day, and you get a written scope with a fixed price within a week.