How much does custom web app development cost?

For a small or medium business, a focused first version typically lands between £15,000 and £60,000 depending on the number of user roles, integrations and how much of the process is being replaced. Discovery is usually priced separately and small, so you can size the build before committing to it.

How long does it take to build a custom web application?

A well-scoped first release usually takes 8 to 16 weeks: one to three weeks of discovery, two to three weeks of design, and six to twelve weeks of build and hardening running partly in parallel. Anything quoted at under four weeks is usually a prototype, not a production system.

Custom web app or off-the-shelf software?

Buy off the shelf when your process is genuinely standard. Build custom when the process is the thing that makes you money, when you are paying people to bridge two tools by hand, or when per-seat licensing is growing faster than your team.

Who owns the code and the data?

You should. Ask any web application development service to confirm in writing that you own the repository, the hosting accounts and the database, and that you can take the whole thing elsewhere without a rebuild.

What happens after launch?

Real usage changes the roadmap. Budget for ongoing maintenance — dependency and security updates, monitoring, backups and a steady trickle of improvements — typically 15 to 20 percent of the original build cost per year.

Custom web app development: a complete guide for small and medium businesses

Most businesses do not start out wanting software. They start out with a process that works — until it doesn't. This guide walks through how custom web app development actually runs end to end: discovery, design, development, launch and maintenance, plus what it costs, how long it takes, and what to ask any web application development service before you sign anything.

When a custom web app is the right answer

Custom software is not automatically better than something you can buy. It is better when the process in question is specific to how you make money, when the tools you have only cover part of it, and when people are being paid to move data between systems by hand. Those are the signals worth acting on:

A spreadsheet has become the system of record and more than one person edits it
Staff re-key the same information into two or more tools every day
Per-seat licence costs are rising faster than the headcount using them
Your customers get a worse experience than your competitors' because the tooling can't do it
Reporting takes a person a day a week to assemble

If none of those apply, buy something off the shelf and get on with your day. An honest development partner will tell you that.

The four stages of the development process

Every credible web application development service runs some version of these four stages. The names differ; the sequence rarely does.

Stage 01

Discovery — Map the real process, not the tidy version

Discovery is where most of the money is saved or wasted. The goal is not a specification document — it is a shared, honest picture of how work actually happens today, including the spreadsheet nobody admits to and the WhatsApp group where the real decisions get made.

A good discovery phase produces four things: a process map with the current pain points marked, a list of user roles and what each one needs to do in a day, a prioritised scope for a first release you could genuinely launch, and a rough sizing of cost and timeline you can take to whoever signs it off.

Stakeholder interviews with the people doing the work, not only the people buying the software
Process mapping: current state, bottlenecks, manual re-keying, and what breaks at volume
Data audit — what exists, where it lives, how clean it is, and what has to migrate
Integration inventory: payments, accounting, email, calendars, existing systems
A ruthless first-release scope, with a written list of what is deliberately not in it

Stage 02

Design — Prove the flow before anyone writes code

Design in a business web app is mostly about sequence and clarity, not decoration. The question is whether a user can complete their most common task in the fewest possible decisions, and whether the screen tells them the truth about the state of the work.

Working through clickable prototypes with real users is dramatically cheaper than discovering the same problems in built software. Expect two or three rounds; expect the scope to shrink as things become clearer.

Information architecture and navigation that matches how people think about their work
Wireframes for the three or four screens where the business actually happens
Clickable prototype tested with real users on real scenarios
A small, consistent component set so later screens are quick to add
Accessibility built in from the start — contrast, keyboard flow, sensible labels

Stage 03

Development — Ship in slices, in front of real people

Modern custom web app development is iterative. Work is broken into thin vertical slices — one complete piece of usable functionality at a time — and delivered to a staging environment every week or two so stakeholders can react to something real.

Under the hood you want boring, well-supported foundations: a typed codebase, a relational database with proper constraints, authentication and role-based permissions handled by a maintained service rather than hand-rolled, automated tests around the rules that would cost money if they broke, and continuous deployment so releasing is unremarkable.

Two-week increments with a working demo at the end of each
Environments: local, staging, production — with production-like data volumes
Automated tests on business-critical logic; manual testing on the edges
Security basics: least-privilege access, row-level rules, audit trails, encrypted transport
Performance budgets, because a slow internal tool quietly stops being used

Stage 04

Launch & maintenance — The first release is the beginning of the project

Launch is a process, not a date. Data migration gets rehearsed, a pilot group runs in parallel with the old way for a couple of weeks, and there is a written rollback plan. Training is short and task-shaped rather than a two-hour walkthrough nobody remembers.

After that, the work becomes maintenance and iteration: watching how the app is actually used, keeping dependencies patched, monitoring errors and uptime, and spending a small, regular budget on improvements informed by real usage instead of guesses made at the start.

Rehearsed data migration with reconciliation checks
Pilot rollout, then phased adoption across the team
Monitoring, error alerting, automated backups and a tested restore
Security and dependency updates on a schedule, not on incident
A living roadmap fed by usage data and user feedback

Timeline and budget, roughly

Numbers vary enormously with scope, but for a first production release used by a real team, this is the shape of it:

Typical duration and share of budget by development stage
Stage	Typical duration	Share of budget
Discovery	1–3 weeks	5–10%
Design	2–3 weeks	10–15%
Development	6–12 weeks	60–70%
Launch & handover	1–2 weeks	5–10%
Maintenance	Ongoing	15–20% per year

Questions to ask before you hire anyone

Who owns the code, the hosting accounts and the data? (The answer should be: you.)
What does the first release contain, and what has been deliberately left out?
How often will we see working software, and in what environment?
What happens if we want to stop after discovery?
Who maintains this in year two, and what does that cost?
How are security, backups and access control handled?

Frequently asked questions

How much does custom web app development cost?: For a small or medium business, a focused first version typically lands between £15,000 and £60,000 depending on the number of user roles, integrations and how much of the process is being replaced. Discovery is usually priced separately and small, so you can size the build before committing to it.
How long does it take to build a custom web application?: A well-scoped first release usually takes 8 to 16 weeks: one to three weeks of discovery, two to three weeks of design, and six to twelve weeks of build and hardening running partly in parallel. Anything quoted at under four weeks is usually a prototype, not a production system.
Custom web app or off-the-shelf software?: Buy off the shelf when your process is genuinely standard. Build custom when the process is the thing that makes you money, when you are paying people to bridge two tools by hand, or when per-seat licensing is growing faster than your team.
Who owns the code and the data?: You should. Ask any web application development service to confirm in writing that you own the repository, the hosting accounts and the database, and that you can take the whole thing elsewhere without a rebuild.
What happens after launch?: Real usage changes the roadmap. Budget for ongoing maintenance — dependency and security updates, monitoring, backups and a steady trickle of improvements — typically 15 to 20 percent of the original build cost per year.

Thinking about building something?

We're ♯Thinking — a technically creative studio building web apps for small and medium businesses. See our work or tell us about the process that's outgrown its spreadsheet.

Start a conversation