// Web applications
Applicationspeople keep using
Dashboards, SaaS products, customer portals and back-office tools. The kind of software where the second month of use matters more than the first demo.
From
£12k, fixed after discovery
Timeline
6 to 12 weeks
You get
Product design, front end, API
Ownership
Your repo from commit one
An application is not a set of pages. It is a set of states, and most of the ones that go wrong are the ones nobody drew: empty, loading, partially loaded, offline, permission denied, and the record that was deleted while somebody had it open.
We design and build the whole surface, including the parts that only appear when something has gone wrong, because those are the screens that decide whether people trust the thing.
What the work covers
SaaS front ends and design systems
A component library with real states, not a page mockup. Built so the tenth screen costs less than the second rather than more.
Auth, billing and multi-tenancy
Roles, permissions and tenant isolation designed at the data layer, where they hold, rather than in the interface, where they are a suggestion.
Admin panels and back-office tooling
The screens your own team lives in. Usually the highest return work in a product and usually the last thing anyone budgets for.
APIs, data models and integrations
The schema decided before the screens, because a data model that does not fit the domain surfaces as a hundred small interface compromises.
Real-time and background work
Queues, jobs, webhooks and live updates, with the retry and failure paths written rather than assumed.
Instrumentation and error tracking
Logging and error reporting wired in from the start, so the first production bug is something you can read rather than reproduce.
What goes wrong with application projects
Not a list of things other people do badly. These are the ones worth checking before anybody quotes you.
- 01Permissions enforced only in the interface. Hiding a button hides nothing: the endpoint behind it is still reachable by anyone who knows the id. Every write has to re-check on the server.
- 02A data model designed around the first screen. Every later screen then needs a workaround, and by month three the workarounds are the architecture.
- 03No empty states. The product is demonstrated with seed data and meets its first real user with a blank page and no explanation.
- 04Loading states bolted on late, which is how an application ends up feeling slower than it is. Perceived speed is mostly about what happens in the first 200 milliseconds.
- 05A prototype promoted to production. It ships without tests, without error handling and without anyone deciding that it had been promoted.
Questions we get asked
Often, yes. It starts with a read of the codebase and an honest report: what is worth keeping, what has to be replaced, and what it will cost either way. Sometimes that report says do not rebuild, and we will say so.
Often paired with
Your next product starts here.
Tell us what you're building, right here. Attach a brief if you have one — no commitment, no pressure, just a real reply.