Client portals, booking systems, quoting tools, internal dashboards — the software that runs your operation rather than the website that advertises it. Built around your workflow, hosted in the UK, and yours to own outright.
Most businesses arrive here after the same sequence. A spreadsheet worked, then it grew. Someone added a second spreadsheet. Then a shared inbox, then a tool bought to fix the inbox, then a member of staff whose actual job is copying data between the three. The cost of that arrangement is invisible on any invoice, which is why it survives so long.
A custom web application replaces the copying. One system holds the records, enforces who can see what, and does the routine work automatically. Send us the brief and we will scope it properly before anyone talks about price.
Who This Is For
- You have a process nobody can buy software for, because it is specific to how your business actually works.
- Staff spend hours a week moving data between systems that should be talking to each other.
- Your customers or suppliers need to log in and do something — check a job, book a slot, upload a document, approve a quote.
- You have outgrown a spreadsheet that several people now edit at once, and you have started losing changes.
- You need one reliable version of a number that currently exists in three places with three different values.
Who This Isn’t For
This section is here because a wasted six-figure build helps nobody, and we would rather say this now than in month four.
- If an off-the-shelf product genuinely fits, buy it. If your process is close to standard, a licensed product with a vendor maintaining it will beat a custom build on total cost for years.
- If nobody internally will own it. Custom software needs one person who cares whether the data stays accurate. Without that, the system decays and everyone drifts back to the spreadsheet.
- If the process is still changing weekly. Build after it settles. Encoding an unstable process in software is how you end up paying to rebuild the same feature three times.
- If what you actually need is a website. Marketing sites and applications are different disciplines with different costs. We build both, and we will tell you which one your brief describes.
What’s Included
Every build ships with the following as standard rather than as line items you discover later.
- Role-based access control enforced server-side on every screen and endpoint. Hiding a button is not security.
- An audit trail recording who changed what and when, retained for as long as your policy requires.
- Responsive interfaces that work on the phone your staff actually use on site, not only on the desktop they use in the office.
- A REST API, documented, so the next system you buy can talk to this one.
- UK hosting with automated daily backups and a restore procedure we have actually tested.
- Data import from whatever you are running now, including the de-duplication work, because importing years of duplicates is how new systems lose their users in week one.
- Written handover documentation aimed at a developer who has never met us.
- Training per role, because what your finance team needs to know is not what your field staff need to know.
How We Build
Discovery — half a day. We sit with the people who will use the system, not only the people paying for it. The difference between those two accounts of the process is usually where the real requirements live.
Process mapping — 1 to 2 weeks. We write down how work actually flows, including the exceptions your team handles by habit and has stopped noticing. You keep this document whether or not you proceed.
Prototype — 1 week. Clickable screens, no working code behind them. People who cannot read a specification can always read a screen, and being wrong at this stage costs a conversation instead of a sprint.
Build sprints — 4 to 10 weeks depending on scope. Two-week sprints against a staging site you can log into whenever you like. No black box and no big reveal.
User acceptance testing — 1 to 2 weeks. Your team runs real work through it, including the awkward cases, while we fix what surfaces.
Launch and training — 1 week. Migration, go-live, role-by-role training, documentation handover, and the credentials to everything.
What We Build With
PHP and MySQL on the server, React where the interface genuinely warrants it, and server-rendered pages where it does not. This is deliberately unfashionable, and the reason is straightforward: any competent UK developer can pick up a PHP and MySQL application and be productive in a week. Choosing something more exotic would make us harder to replace, and that is not a feature you should be paying for.
Where you already have systems worth keeping, we integrate rather than replace. A finance system that holds ten years of history does not need rewriting because the workflow around it is wrong. We can build alongside it and talk to it over its API, and defer the replacement question until you know which parts genuinely need to change.
Security, Backups and What Happens If We Disappear
Parameterised database access throughout, password hashing to current standards, session hardening, permission checks on the server rather than in the browser, and file uploads that cannot execute. Hosting is UK-based by default with automated daily backups.
On the last point, which clients ask about less often than they should: at handover you receive the repositories, the hosting account, the domain registrar login and the database. Everything is in your name. If we ceased to exist tomorrow, your system would keep running and any developer you hired could take it over from the documentation. Agencies that keep client systems in agency accounts are protecting their revenue, not your continuity.
What It Costs
We quote a fixed price after a free scoping call rather than publishing a range, because the same one-line brief can differ several-fold once it is pinned down. The things that genuinely move the number:
- The number of distinct user roles. Each role is its own permission set, screens and test cases.
- Integrations. Talking to a modern documented API is routine. Talking to a fifteen-year-old system with no documentation is a project of its own.
- Data migration. Clean exports are quick. Twelve years of inconsistent records are not.
- Whether there is a mobile app alongside the web build, or whether a responsive layout is enough.
You get one figure you can budget against, based on a written process map rather than a guess. If scope changes later, the price changes by agreement and in writing.
Related
If the system you need is specifically a sales or HR platform, that is covered under custom CRM and HRM development. If it needs a phone app alongside it, see mobile app development — and read the note there about sharing one backend between both.
On security, we build to the OWASP Top Ten, which is the industry reference for the vulnerability classes that actually get exploited.
Last reviewed
Guides related to Custom Web App Development
How Much Does a Custom Web Application Cost in the UK?
Portals, booking systems and internal tools: what UK businesses actually pay for custom web applications in 2026, and the questions that turn a vague brief into a fixed quote.
Bespoke Software vs Off-the-Shelf: How to Decide
Build when the process is your advantage, buy when it is not. The test we use in scoping calls, the true five-year costs, and how a "bespoke" quote can quietly become a subscription.
Client Portal Development: What to Build and What It Costs
The features that reduce email, the ones that just look impressive, realistic UK costs, and how to write a portal brief that does not double in size halfway through.
Custom Web App Development FAQs
What counts as a web application rather than a website?
A website mostly shows people information. A web application does work: it holds records, enforces permissions, runs a process and changes state. If your users log in, submit something and expect the system to remember and act on it, you need an application. The distinction matters because the cost and timeline are driven almost entirely by the logic behind the screens, not the number of pages.
Should we build custom or configure something off the shelf?
Configure off the shelf if your process is close to standard and you need it running in weeks. Build custom when you have already paid someone to bend an off-the-shelf tool and it still does not fit, when per-seat licensing has become one of your larger software bills, or when the system has to integrate with something that has no ready-made connector. We will tell you which side you fall on during the scoping call, including when the answer is that you do not need us.
What do you build with?
PHP and MySQL for the server side, React where the interface warrants it, and plain server-rendered pages where it does not. We deliberately use boring, widely-known technology so that any competent UK developer can pick your system up later. Choosing something fashionable would make us harder to replace, which is not a feature you should be paying for.
Can you work with our existing system instead of replacing it?
Often, yes. Where a system holds data you need but blocks the workflow you want, we can build alongside it and talk to it over its API or database rather than replacing it wholesale. Replacement is a decision worth deferring until you know exactly which parts genuinely need to change.
How do you handle security and backups?
Role-based permissions on every screen and endpoint, parameterised database access, password hashing, session hardening and an audit trail of who changed what. Hosting is UK-based by default with automated daily backups and a documented restore procedure — one that we test, because a backup nobody has ever restored is a guess.
Ready to start your project?
Tell us what you are trying to build. We will come back within one working day with an honest view on scope, timeline and cost.