What Does It Cost to Build a Customer Portal?
A customer portal usually costs between SEK 600,000 and SEK 2.5 million. The price is driven mainly by the number of integrations with business systems, plus login and security such as BankID or SSO. A portal pays for itself through fewer support tickets and self-service – often faster than you'd expect once you calculate the cost per ticket.
A customer portal – “my pages” – is one of the investments that pays for itself most easily, because it trades expensive support tickets for cheap self-service. But the price varies widely, and it comes down to almost one thing: how many systems the portal needs to talk to. Here’s the price picture, the cost items to watch, and a simple model for calculating the payback.
Price range by scope
| Scope | Typical cost |
|---|---|
| Simple portal (1 integration) | SEK 600,000–1,000,000 |
| Portal with multiple integrations | SEK 1,000,000–1,800,000 |
| Extensive portal | SEK 1,800,000–2,500,000+ |
The number of integrations is the single most important price factor. A portal that only shows data from one system is relatively cheap. One that pulls together tickets, invoices, contracts and orders from several business systems requires considerably more work – and that’s where the cost grows.
Why do integrations weigh so heavily? Because a portal without real data isn’t worth much. The point is that the customer no longer has to call and ask, and that requires the portal to show the same information an employee would otherwise look up. Each such system has its own way of handing over data, and fetching it securely, keeping it current, and displaying it clearly is its own work per connection. The more systems, the more logic – and the greater the value once it works.
The cost items to watch
Three items deserve special attention:
- Integrations with business systems. Each connection that pulls real data is its own sub-project with development, testing and error handling. This is usually the heaviest item.
- Login and security. BankID and SSO are separate cost items, both in development and in the ongoing fee to the provider. A portal with sensitive customer data also requires encryption and access controls.
- Maintenance. When the portal connects to multiple systems, it has to be kept in step as those systems are updated. Budget for ongoing maintenance.
A simple ROI model
The nice thing about a customer portal is that you can actually calculate it. Start with the cost per support ticket:
Say a routine ticket – “where’s my invoice”, “what’s the status of my case” – takes 10 minutes of an employee’s time. At an hourly cost of a few hundred kronor, that’s a clear cost per ticket. If the portal can remove a few thousand such tickets a year through self-service, the savings show up fast.
Weigh the annual savings against the build cost and you get a payback period. For many businesses with high ticket volume, it lands at one to two years – after which the portal is pure savings, while customers get faster answers. It’s also worth factoring in what’s harder to measure: happier customers who get answers around the clock, and employees who are freed from the most repetitive questions and can spend their time on what actually requires a human.
Start with what removes the most questions
The most common mistake is trying to build the entire portal at once. A portal that’s meant to do everything becomes expensive, drags out, and risks being hard to use. The smarter approach is to start with the information customers contact you about most – often invoices and ticket status – and add the rest in stages.
That way, two good things happen. The investment spreads out, and the first version starts delivering value and reducing support load long before everything is in place. You also see what customers actually use, so the next step builds on real demand instead of guesswork. A cheap portal nobody logs into is wasted money – it’s usage, not the feature list, that determines whether the investment pays off.
A concrete scenario
Say a service company wants to give its customers a portal where they can see their contracts and invoices and create support tickets, with BankID login and a connection to the business system. That’s a portal with a couple of integrations – budget SEK 1,100,000–1,600,000 to build. If it removes a large share of incoming routine questions, it pays for itself within a reasonable time.
At Weapp we build customer portals and always start by calculating what self-service will actually save you. See our services or get in touch with your systems and ticket volume and we’ll put together an estimate.
Frequently asked questions
What drives the price of a customer portal?
Mainly the integrations. A portal is most valuable when it shows real data – invoices, tickets, contracts, orders – and each such connection to a business system is its own sub-project. Login and security add to that. The number of systems the portal needs to talk to largely determines where in the range you land.
What does BankID login cost in a portal?
BankID and SSO are separate cost items, not something included automatically. The integration itself with a BankID provider requires development and testing, and there's often an ongoing fee to the provider on top. Budget for it as a separate line item, distinct from the portal build itself.
How do you calculate the payback on a customer portal?
Start with what a support ticket costs you in time. Multiply that by how many tickets the portal's self-service can remove per year. If customers can see invoices, ticket status and contracts themselves, a large share of routine questions disappears, and weighing that sum against the build cost gives you a clear payback period.
What should a customer portal include?
It depends on the business, but common building blocks are secure login, an overview of the customer's tickets and contracts, invoices and payments, and the ability to create and track support tickets. Start with what removes the most routine questions and build out from there instead of taking on everything at once.
Can you start with a simple portal and expand later?
Yes, and that's often wise. A first version with login and the most requested data delivers value quickly and reduces support load. More integrations and features can then be added in stages, as you see what customers actually use and ask for.