How Much Does a Custom Customer Portal Cost in the UK? (2026 Guide)

If you are pricing a custom customer portal in the UK, you have probably found that most quotes are useless. They range from a few thousand pounds for a glorified login page to six-figure bespoke development projects, with no explanation of what moves the number. This guide breaks down the real cost drivers, explains why a fixed price is possible at all, and puts a number on the thing most buyers ignore: the cost of not building.

Throughout, we mean a portal in the operational sense: a system your customers, members or partners run themselves, integrated with your CRM and the rest of your stack, with the CRM as the single source of truth. We do not mean a support-ticket widget or an ecommerce storefront. For the full picture of what that looks like for a mid-market operator, start with the pillar guide on customer portals for mid-market B2B.

What actually drives the cost of a custom portal

Six factors do most of the work. When a vendor quote swings wildly, it is almost always one of these moving underneath.

1. Number of journeys

A journey is a complete job your customer can do without emailing your team: check the status of an order, upload a document, renew a membership, view an invoice, raise and track a request. Each journey carries its own screens, validation, permissions and notifications. The number of journeys is the single largest driver of scope, which is why a portal that does one job costs far less than one that does ten. Be ruthless here. Most teams need three journeys to remove the bulk of the chasing, not fifteen.

2. Integration complexity

A portal is only useful if it shows live, accurate data, which means it has to talk to your systems: your CRM, finance system, project tool, ERP or bespoke database. A clean, well-documented API with the data you need is cheap to connect. A legacy system with no API, or data spread across spreadsheets and three disconnected tools, is expensive because someone has to build and maintain the plumbing. If your stack is messy, that complexity shows up in the quote. Tidying it first with a deliberate data engineering exercise, or wiring up the right integrations, often lowers the total bill.

3. The state of your data

Portals expose your data to your customers, so the quality of that data stops being an internal problem and becomes a public one. Duplicate records, missing fields and inconsistent formats that your team quietly works around will surface the moment a customer logs in. If the data needs migrating or cleaning before it can be trusted, that is a project in its own right. A focused data migration can be the difference between a portal that builds confidence and one that erodes it.

4. Security and compliance needs

Authentication, access control and audit trails are table stakes. Beyond that, the cost climbs with your obligations: single sign-on, role-based permissions across customer types, data residency rules, and any sector compliance you carry. A B2B services firm with standard requirements sits at the low end. A business handling regulated or highly sensitive data sits higher because more has to be designed, tested and documented.

5. User volume and concurrency

A portal serving a few hundred named customers is a different engineering problem from one serving tens of thousands of concurrent users. For most mid-market B2B businesses, volume is not the cost driver people fear it is, because the user base is known and bounded. If you genuinely need 5,000-plus users active on day one, you are in a different and more expensive bracket, and you should price accordingly.

6. Ongoing hosting and support

The build is a one-off. Hosting, monitoring, security updates and support are recurring. Treat the portal as live software with a running cost, not a website you launch and forget. A sensible budget separates the build cost from the monthly operating cost so you can compare vendors honestly.

Why a fixed price is possible at all

Most custom software is quoted by the day because the scope is open-ended, which is exactly why those projects overrun. A fixed price becomes possible when the scope is productised: the vendor is not starting from a blank page every time.

At SpotDev, a custom customer portal is fixed-price from £15,000 and launched in 30 days from contract signing, with working software typically within around two weeks. That is achievable because the build starts from established portal foundations, reusable journey patterns and an in-house engineering team that does this operational software repeatedly. You pick proven journeys, usually three, and they are adapted to your brand, systems, data, fields, permissions, notifications and integrations. It is a productised scope on a genuinely custom build, not a generic template you fight to bend into shape.

The timeline depends on three things being true: a fixed scope, fast access to the systems the portal needs to read from, and prompt feedback from your side. Commercially, it is £5,000 on contract signing with the balance before launch, and hosting on a recurring payment. Additional journeys are £2,000 each and add roughly two days; larger extras move the build up a tier.

There is also a written guarantee: miss the agreed launch date and SpotDev refunds the first payment in full, and you keep everything built. No clauses, no exclusions. That only works when scope is controlled, which is the whole point of productising it.

What is not in the fixed price

Being clear about exclusions is part of a credible quote. The fixed price does not cover open-ended product development, complex legacy-system rebuilds, bespoke mobile-app functionality, data-cleansing projects, or unlimited integrations. If your situation needs one of those, it is not that a portal is wrong for you; it is that the work splits into a build plus a separate, scoped piece. Knowing which bucket you are in before you sign is what keeps a project on budget.

The cost of not building: the hidden human-API tax

The number that never appears on a quote is the one you are already paying. When customers cannot self-serve, your team becomes the API. Every status request, document re-send, invoice query and "can you just confirm" email is a human call into your systems, answered manually.

Put rough figures on it. If two people each spend two hours a day fielding requests that a portal would answer automatically, that is twenty hours a week, close to a full-time role, spent on a system job done by humans. Add the slower response times, the errors from manual handling, and the senior people pulled into chasing rather than building the business. Over a year, that recurring drain comfortably exceeds the one-off cost of a portal, and unlike the portal it never stops or scales down.

This is the framing that matters for a mid-market B2B business turning over £3m to £50m with 30 to 500 employees: a portal is not a cost line, it is a way to stop spending headcount on work that should be automated. We dig into this in the sibling piece on how to stop chasing customers for documents and status.

How to decide what to budget

Once you understand the drivers, the budgeting question becomes concrete. Count the journeys that would remove the most manual work. Audit your integrations and the state of the data behind them. Be honest about your security and compliance obligations and your real user volume. Then separate the one-off build from the ongoing operating cost.

The next decision is whether to build custom at all or take something off the shelf. That trade-off, and where each option breaks down for a mid-market operator, is covered in the cluster keystone on build versus buy for a customer portal. If you have already outgrown an off-the-shelf tool, the piece on what to do when you have outgrown an off-the-shelf portal is the more relevant read.

When you are ready to put a real number against your specific journeys, integrations and data, the fastest route is to scope it directly. See your price and explore the proven journeys on the customer portals page, where the build, timeline and guarantee are laid out in full.

Frequently asked questions

How much does a custom customer portal cost in the UK?

Costs vary with the number of journeys, integration complexity, the state of your data, security and compliance needs, user volume and ongoing hosting. A productised custom build, such as SpotDev's, is fixed-price from £15,000 and launched in 30 days, which gives you a firm figure rather than an open-ended day-rate estimate.

Why can some portals be sold at a fixed price when most software cannot?

Because the scope is productised. The build starts from established portal foundations and reusable journey patterns rather than a blank page, so the vendor can commit to a price and a 30-day timeline, provided scope is fixed, system access is fast and feedback is prompt.

What is not included in a fixed-price portal?

Open-ended product development, complex legacy-system rebuilds, bespoke mobile-app functionality, data-cleansing projects and unlimited integrations sit outside the fixed price. These are scoped separately, which is what keeps the core build on time and on budget.

What does it cost to add more functionality later?

With SpotDev, additional journeys are £2,000 each and add roughly two days to the build. Larger additions move the project up a tier. Treat the portal as live software with an ongoing hosting and support cost, not a one-off website.

Is a custom portal worth it for a mid-market business?

For a B2B services business whose customers, members or partners constantly chase the team for updates, usually yes. The recurring cost of staff manually answering those requests typically exceeds the one-off build cost within a year. It is a poor fit only if you need 5,000-plus portal users on day one, which is a different and larger bracket.