Why web app development cost UK estimates have no honest average
There is no dependable market-wide answer to “web app development cost UK”. Apps with similar screens can require radically different permissions, integrations, data migration, security controls and exception handling.
A credible budget starts with delivery roles × days × applicable rates, then adds discovery, testing, project management, migration, deployment, launch support and an explicit allowance for identified uncertainty. That is more defensible than assigning a portal or SaaS product to a broad price band.
Many published ranges are agency-authored planning figures, not independent market data. They can indicate order of magnitude, but they do not answer what your custom web application will cost without showing the assumptions underneath.
We quote custom web application development individually and provide a fixed written quote before work starts. Complex projects commonly take three to six months, but duration alone is not a price. The fictional GBP estimate later in this article excludes 20% VAT; supplier charges remain in their stated currencies.
Website, web app or native app: price the right product
A content-led website mainly publishes information. A web app authenticates users, stores structured data and lets people perform actions governed by permissions and business rules.
Browser-based apps usually avoid separate iOS and Android releases, app-store review processes and native distribution accounts. For comparison, Apple lists its developer membership at US$99 per membership year or the available local-currency equivalent.
That does not make every web app cheaper than a native product. Offline operation, deep device access or genuinely different mobile experiences can create substantial browser engineering or justify native applications.
Page counts are a poor estimating unit. We need to know each screen’s states, user roles, validation rules and failure behaviour. A single payment screen can include failed cards, duplicate submissions, refunds, abandoned sessions and delayed confirmation from a provider.
Scope portals, booking systems, internal tools and SaaS separately
The product label is only a starting point. These categories contain different workflows and cost drivers.
| Product | Core workflow | Likely cost drivers | Sensible deferrals |
|---|---|---|---|
| Customer portal | Sign in, view account data and documents, complete one customer action | Payments, SSO, CRM synchronisation, delegated permissions | Advanced reporting, multiple customer actions, self-service branding |
| Booking system | Find availability, reserve, change or cancel | Availability rules, reminders, payments, refunds, calendar synchronisation | Waiting lists, complex pricing, multiple calendar providers |
| Internal tool or dashboard | Search data, update records and approve work | Data quality, imports, exports, approvals and spreadsheet synchronisation | Polished analytics, broad automation, rarely used reports |
| SaaS MVP | Onboard an organisation and complete the product’s main job | Tenant separation, subscriptions, account administration, usage limits, support tooling | Multiple plans, extensive customisation, secondary workflows |
Customer portal development cost rises when “view my documents” becomes “pay invoices, invite colleagues and synchronise every change with the CRM”. Booking rules need the same precision: rescheduling and refunds are separate behaviours, not finishing touches.
An internal tool development cost also depends on whether it replaces spreadsheets or remains synchronised with them. For a SaaS MVP development cost UK estimate, tenant isolation and support administration matter even when the visible interface looks small.
The requirements that make a simple portal expensive
The expensive work is often hidden behind a short feature name.
| Requirement | Work that sits underneath it |
|---|---|
| User roles | Permission matrix, restricted queries and role-specific testing |
| SSO or MFA | Identity-provider setup, recovery paths and session handling |
| Document uploads | Validation, access control, storage and failed uploads |
| Payments | Webhooks, failed payments, refunds and reconciliation |
| CRM or accounting integration | Authentication, field mapping, retries and conflict handling |
| Audit logs | Event design, retention, search and restricted access |
| Historical-data migration | Cleaning, mapping, rehearsal and verification |
| Administrator tooling | Overrides, support access and correction workflows |
We call this the “except when” problem. The ordinary route may be simple, but real operations contain partial approvals, duplicate records, manual overrides, cancellations and systems that disagree.
Every external integration adds investigation, authentication, error handling, rate limits and test-environment work. The quote should also say what happens when the third party is unavailable and who owns diagnosis when its undocumented behaviour differs from expectations.
Non-visible work includes security controls, backups, monitoring, accessibility, performance testing and recovery procedures. Hosting data in the UK does not create automatic GDPR compliance. Where an organisation must pay the ICO data-protection fee, current tiers run from £52 to £3,763, with exemptions available.
The incident process must support the ICO’s 72-hour deadline for breaches that must be reported. Public-sector buyers should also account for testing against the Department for Education guidance specifying WCAG 2.2 Level AA for public-sector websites and mobile applications.
Build the quote from roles, days, rates and risk
A proper breakdown covers discovery, UX and interface design, technical design, engineering, QA, project management, deployment, migration and launch support.
For an external benchmark, IT Jobs Watch reported a £550 median advertised Software Engineer contract rate for the six months ending 21 October 2026, based on 487 quoted daily rates. That is contract-vacancy data, not an agency price list or a recommended rate.
The following fictional estimate applies that single rate mechanically so the arithmetic is visible. It is not a typical project, market range or ZeroPixel quote.
| Work | Assumed days | Illustrative rate | Subtotal |
|---|---|---|---|
| Discovery | 5 | £550 | £2,750 |
| UX and interface design | 8 | £550 | £4,400 |
| Technical design | 4 | £550 | £2,200 |
| Engineering | 50 | £550 | £27,500 |
| QA | 10 | £550 | £5,500 |
| Project management | 8 | £550 | £4,400 |
| Deployment | 3 | £550 | £1,650 |
| Data migration | 6 | £550 | £3,300 |
| Launch support | 4 | £550 | £2,200 |
| Identified integration uncertainty | 5 | £550 | £2,750 |
| Illustrative total excluding VAT | 103 | £56,650 |
Real quotes may use different role rates. What matters is that each rate, day count and responsibility is visible rather than hidden inside “development”.
Test the quote by changing an assumption. Adding SSO should move discovery, technical design, engineering and QA. A legacy import should affect discovery, engineering, migration, QA and launch support. A second integration should expose additional mapping, error-handling and testing work.
Contingency should pay for named uncertainty, such as incomplete integration documentation. An unexplained percentage added at the bottom tells the buyer nothing.
What it costs to run a web app after launch
Build cost and web app maintenance cost UK budgets should be separate. Running costs combine fixed subscriptions, usage charges and human support.
| Cost | Charging basis to record |
|---|---|
| Application hosting | Current Vercel or alternative plan, included usage and overages |
| Database and authentication | Current Supabase or alternative plan, usage limits and overages |
| Transactional email | Resend Pro is US$20 per month for 50,000 emails, then US$0.90 per additional 1,000 |
| File storage | Cloudflare’s 1 October 2026 R2 table lists US$0.015 per GB-month for standard storage and free internet egress |
| Payments | Stripe UK lists 1.5% plus 20p for a successful standard UK-card payment, with no setup or monthly fee; other payment types differ |
| Monitoring and backups | Subscription, retention, alert volume and recovery testing |
| Support and maintenance | Agreed response time, updates, fixes and improvement capacity |
A quote should snapshot the chosen Vercel and Supabase plan names, prices, included limits and overages when it is issued. Free-tier inactivity or pause rules must also be checked rather than treated as a production guarantee.
Supabase invoices in US dollars and applies VAT or other indirect taxes according to the billing address. Its USD list price is therefore not automatically the final amount on a UK invoice. Usage assumptions should cover active users, emails, stored files, bandwidth, transactions and log retention.
Fixed quote or day rate: compare who carries the risk
Fixed-price work suits a sufficiently defined outcome. Day-rate delivery can suit discovery, uncertain integrations or a product expected to change materially during development.
Neither model is automatically cheaper or more flexible. The lowest fixed quote may simply use the narrowest interpretation of the requirement, whilst an open-ended day rate can move uncertainty entirely onto the buyer.
Compare quotes against the same checklist:
- acceptance criteria and evidence required for approval;
- assumptions, exclusions and third-party costs;
- discovery, design, testing, migration and launch scope;
- change control and progress reporting;
- responsibility for supplier-caused rework;
- treatment of undocumented integration behaviour;
- intellectual-property and source-code ownership;
- warranty, support and handover arrangements.
Ask who pays when an integration behaves differently from its documentation. “Integration included” is not enough if the quote excludes retries, error states and reconciliation.
Reduce the cost before asking for a quote
Build one complete, valuable workflow before commissioning shallow versions of every planned feature. A customer who can sign in, find the right document and complete one useful action is a stronger first release than a broad portal full of unfinished routes.
Established services can reduce bespoke work for payments, email, authentication and storage when their constraints and ongoing costs are acceptable. Our technology stack reflects tools we use to ship and maintain real products, rather than choosing technology for novelty.
No-code can suit a temporary, low-risk internal workflow. Custom software becomes easier to justify when ownership, complex permissions, security, integrations or long-term change matter. Sometimes targeted workflow automation is enough without building a standalone product.
Give each supplier the same briefing checklist:
- users and roles;
- primary workflow and acceptance criteria;
- exception and failure cases;
- required integrations and responsible system owners;
- existing data and its condition;
- security, accessibility and compliance needs;
- target date and budget constraints;
- features that can wait until a later phase.
Do not accept a total until every material assumption is visible and changing an assumption visibly changes the quote.
Bring that checklist to a project discussion, and we will scope an individually quoted build around the workflow that matters first.