Services
Web Apps
The tool your team lives in all day, costing them an hour of it. Designed and built so it stops.
Internal systems, admin platforms, client portals and operational dashboards get judged on nothing a marketing site is judged on. Nobody is persuaded by them. People are issued with them, and then use them for six hours a day for four years.
That changes what good means. Density over whitespace. Keyboard over cursor. Recovery over prevention. A saving of ten seconds in a task someone repeats eighty times a day is worth more than any amount of polish.
Trusted by
Software people are stuck with deserves more care, not less.
Nobody chose this tool. They can’t switch to a competitor, so every friction in it is absorbed rather than reported — which is exactly why it compounds and why nobody realises what it’s costing.
We watch people use it before changing anything. The expensive problems are rarely the ones in the ticket queue; they’re the workarounds people stopped mentioning years ago because they assumed that was just how it worked.
- 22 years designing digital products
- 200+ web applications shipped
- 8 industries worked across
What you get
-
Workflow design
The actual sequence of a real task, start to finish, including the parts that leave the screen — the spreadsheet on the side, the phone call, the paper note. Those are where most of the time goes.
-
Dense data views
Tables, filters, bulk actions, sorting and saved views. A table that shows forty rows well beats one that shows twelve beautifully, for anyone doing this all day.
-
Keyboard and speed
Tab order, shortcuts, focus behaviour and defaults. Power users stop using the mouse within a week; software that assumes a cursor punishes them permanently.
-
Roles and permissions
What each role sees, can do, and is told when they can’t. “You don’t have access” with no route forward generates a support ticket every time.
-
Errors and recovery
Undo, confirmation, partial saves, timeouts. In operational software, recovery matters more than prevention — people work fast and will make mistakes.
-
Front-end build
We can build it as well as design it: production front-end code against your API, or a component library your engineers build from. Either way you get a design system rather than a pile of screens.
How it works
-
01
Discovery
The business process, the roles, and the systems around it. Internal tools never exist alone; they sit between other things.
-
02
Observation
We watch people do the work, in the place they do it. For operational software this is worth more than any number of interviews, because people can’t describe habits they’ve stopped noticing.
-
03
Architecture
Structure, navigation and naming, settled before any screens. In admin systems the naming is the design — people have to find things by guessing.
-
04
Design
Screens and every state: empty, loading, partial, error, no-permission, too-much-data.
-
05
Build or handoff
Front-end built by us, or specs and components handed to your engineers, with support through the build.
Questions
Do you build, or only design?
Both. Front-end we can take to production against your API. Back-end and infrastructure sit with your team or your vendor — we’ll work alongside them.
We have a working system that everyone complains about. Replace or improve?
Usually improve, and the answer comes from watching people use it for a day. Full replacements of working operational software are expensive, slow and disruptive to people who’ve built habits around it. We’ll tell you honestly which situation you’re in, including when the answer is “don’t rebuild this”.
Our users have no choice but to use it. Does UX matter?
It matters more, not less. A consumer who hits friction leaves and you find out from your analytics. An employee absorbs it silently, forever, and it shows up as overtime, errors and turnover instead.
Can you work with our existing design system?
Yes, and we’ll tell you where it’s getting in the way rather than quietly working around it.
What about accessibility?
Built in rather than audited afterwards. For internal tools it’s also a legal and practical requirement — you employ people with a range of abilities, and keyboard-only operation benefits everyone who uses the system all day.
How long and how much?
A focused tool or a redesigned flow, six to ten weeks. A full platform, four to six months. Build is quoted separately once the design scope is clear. A range on the first call. [Add your floor.]
Related work
No case studies published yet.
