01 What we build
Web applications built
to be handed over.
Dashboards, SaaS products, internal tools, customer portals and the APIs behind them — written so your own engineers can pick them up later without an apology.
Most agency web apps are built to pass a demo, not to be maintained. The tell is always the same: no tests, no types, one person who understands the deploy, and a README that stops at "npm install". We build the other kind, because we are usually the ones still running it in year three.
What a web application build includes
- React and Next.js front ends, typed end to end
- Node, Python or Go services with documented REST and GraphQL APIs
- PostgreSQL, Redis, queues and background jobs
- Auth, roles, audit trails and multi-tenancy from day one, not bolted on later
- Stripe, HubSpot, Salesforce and custom third-party integrations
- Test coverage and CI that runs on every pull request
- A staging environment that mirrors production, always live
What that looks like in practice
3 days scheduled
Month-end reporting on a multi-tenant analytics portal, before and after
Week 2
When you first click real working software, not a status deck
Questions people actually ask
How long does a custom web application take to build?
Six weeks to eighteen months, and the range is that wide because scope drives it far more than technology does. A focused internal tool with one user role is a few months; a multi-tenant SaaS product with billing, permissions and an audit trail is closer to a year. We give a fixed price with the assumptions written down after a week of scoping, so you are not guessing.
Can our own developers take over the codebase later?
Yes, and it is a design constraint rather than a promise. Typed end to end, documented APIs, tests that run on every pull request, and infrastructure defined in code. We also do the handover properly — a walkthrough, the runbook, and the accounts transferred into your name.
Do you work with an existing codebase, or only greenfield?
Both. Roughly half of what we take on is somebody else’s unfinished build. We start those with a paid assessment so you get a written opinion on what is salvageable before committing to a rebuild.
Who owns the code?
You do, from the first commit. The repository lives in your organisation or is transferred to it at handover, along with the domains, the cloud accounts and the third-party services. There is no hostage infrastructure here.
Ready to talk about Web Applications?
A real technical opinion back within two business days — not a sales call.