If you research customer portal costs in July 2026, you will find published ranges anywhere from €12,000 to well over €300,000 — for what looks like the same deliverable. That is not because half the vendors are overcharging. It is because "customer portal" describes everything from a document login for twenty existing customers to a multi-tenant platform serving three ERP systems and five country subsidiaries. If you need to request a budget, you don't need a single number — you need to know which portal class your project falls into, and at what threshold custom development becomes cheaper than SaaS licenses.
This article publishes our own price anchors, puts the published market ranges in context, and breaks down the running costs that most cost guides simply omit. One scoping note up front: we are talking about customer-facing self-service portals for external customers — with login, roles, and integration with your ERP or CRM. The short version of the decision fork: external customers with a login and self-service — customer portal. Your own employees and internal processes — a web app, not a portal. No login, and the goal is lead generation — a website. How to classify your case cleanly, and what each class costs, is covered in our decision guide to websites, web apps, and portals.
Published market prices — and why they contradict each other
A look at the German cost guides that rank for customer portal pricing: TJ Labs quotes €30,000–50,000 for an MVP portal, €60,000–120,000 for a standard portal, and €150,000–300,000 and up for enterprise projects — with ERP integration priced separately at another €10,000–25,000. CodeGuides puts a basic portal at €25,000–35,000 and a B2B portal with ERP integration at €60,000–100,000. falconDev, in turn, cites roughly €20,000 as a guideline for custom development, while the Swiss provider Microservice Solutions ranks with entry-level portals from about €12,000 at six to eight weeks of development time. All figures as of 2026.
These ranges only appear to contradict each other. Behind them sit three differences: what each provider counts as a "customer portal" (a login area or a platform), which team setup is priced in (junior-heavy project teams with overhead, or small senior teams), and whether discovery, operations, and integrations are included in the price or listed alongside it. The honest verdict: almost all published numbers can be accurate — for different projects. They only become comparable once you compare project classes instead of individual figures.
Our price anchors for customer portals (as of July 2026)
We publish our price ranges because a CIO or department head should know before the first call whether they are in the right shop. The ranges come from real projects on our standard stack — Next.js, Supabase, and Keycloak, hosted in the EU. The stack is fully open source: there is no license component in the price and no license scaling as your customer count grows. Important for comparability: the ranges include concept, implementation, and launch on EU infrastructure. Not included are ongoing operations and further development — we break those down separately below instead of hiding them in the project price.
| Portal class | Price range (net) | Typical scope |
|---|---|---|
| Portal MVP | €8,000–20,000 | Keycloak login, 1–2 self-service features (e.g. documents, order status), basic role model, EU hosting — live in 6–12 weeks |
| Customer portal with roles and ERP/CRM integration | €20,000–60,000 | Company accounts with multiple users, role and approval model, tenant separation, first ERP/CRM interface, SSO |
| Portal platform | €60,000–150,000 | Multiple tenants, brands, or countries, multiple system integrations, portal as a modern layer in front of the legacy ERP |
As of July 2026. All prices net of VAT. Ranges come from real projects; the price becomes binding after a discovery phase that includes a make-or-buy check.
For context against the market: our MVP range starts well below the €30,000 that TJ Labs cites as a floor. That is not a loss-leader price — it is a matter of scope. An MVP with one or two self-service features on a license-free stack is deliberately small, so you can validate the business case against real user behavior before committing to the larger investment. In the platform class, by contrast, the ranges converge: with multiple tenants and integrations, the effort is structural and barely depends on the stack anymore.
Running costs: the part that's usually missing from the budget request
Most cost articles stop at the project price. For your TCO calculation, that is half the truth — a portal is a product, not a project. These line items belong in the request:
| Cost block | Range | What it covers |
|---|---|---|
| Infrastructure (EU hosting) | €20–50/month | Standard setup; high-availability environment €150–400/month |
| Operations | 2–5 h/month at approx. €120/h | Updates, monitoring, security patches — roughly €240–600/month |
| Further development (optional) | €4,000–12,000/month retainer | Continuous expansion with quarterly prioritization instead of hiring your own senior engineer |
| 3-year TCO of the stack | €40,000–80,000 | Supabase, Keycloak, hosting, and operations calculated over three years |
In concrete terms: a mid-class portal costs roughly €260–650 per month for infrastructure and operations after launch — further development not included. We have disclosed in detail how the €40,000–80,000 three-year TCO breaks down: what the Supabase-Keycloak stack really costs. For comparison: TJ Labs cites €500–5,000 in monthly running costs — a plausible range for setups with licensed software, middleware products, or larger operations teams, but by no means the only possible operating model.
What actually drives the price
Depth of ERP/CRM integration. The single biggest cost driver. A portal that displays order data read-only is a different project from one that writes orders and approvals back into the ERP. Rule of thumb: read first, write later — the available integration patterns and what your legacy system actually needs to support are covered in our guide to SSO and ERP integration.
Role and tenant model. B2B reality means company accounts with multiple users, approval levels, and clean data separation between customer organizations. A portal for individual users is a full class cheaper than one with an organizational structure.
Number of self-service processes. Every task customers should handle themselves — documents, order status, invoices, tickets, reorders — is its own piece of business logic. Two processes done well are worth more than six done halfway; that is another reason we recommend a tightly scoped MVP.
Compliance and hosting. EU hosting and GDPR-clean data handling are standard with us, not a surcharge. Compliance gets expensive when it has to be retrofitted into a US SaaS architecture after the fact.
The make-or-buy threshold: when custom development pays off
SaaS portal software looks unbeatably cheap at first glance. According to Zendesk's pricing page (as of July 2026, billed annually), Suite Team costs €55 and Suite Professional €115 per agent per month; the Copilot add-on adds another €50 per agent, and Enterprise is quote-only. Freshdesk, per the Freshworks pricing page (also as of July 2026), comes in somewhat lower at $19–89 per agent per month plus $29 for the Freddy AI Copilot — which changes nothing about the underlying seat-scaling pattern. A sample calculation, not a quote: twelve service agents on Suite Professional with Copilot come to 12 × €165 = €1,980 per month, or €23,760 per year — a good €71,000 over three years, without any deep ERP integration included. A mid-class custom portal runs €20,000–60,000 one-time plus roughly €3,000–8,000 per year in operations.
The structural difference: SaaS scales with agent seats, add-ons, and storage — a custom portal scales with feature scope, not with your customer or user count. You have reached the custom-development threshold when at least two of these three conditions apply: your processes need deep ERP/CRM integration rather than standard ticketing, your seat and add-on costs are set to grow predictably over years, and the portal is meant to differentiate you in the market rather than merely process support requests. The complete decision framework with a criteria table is in our article Customer portal: make or buy?
And when is SaaS the better answer? I say this regularly in first calls: if you need standard support — tickets, knowledge base, chat — without deep integration into your systems, buy Zendesk or Freshdesk for a few hundred euros a month and skip the development. A custom portal would be the wrong investment in that case, and an agency that sells you one anyway is optimizing its revenue, not your business case.
Does it even pay off? The honest deflection math
The classic cost anchor comes from Gartner (2019): a live contact via phone, chat, or email costs $8.01 on average, a self-service contact around $0.10 — a factor of 80. The number is old, but it remains the canonical source. More important is the nuance from the same study: 70% of customers attempt self-service, but only 9% resolve their issue entirely without live contact. The savings, in other words, don't come from the mere existence of a portal — they come from its quality.
Budget accordingly conservatively. Vendor aggregations from 2026 — caveat: blog-grade material, not a primary study — put realistic AI self-service deflection in B2B SaaS at a median of around 22%; best-in-class teams reach 35–45%, and 10–15% is typical in year one. Build your business case on the 30–50% from vendor slide decks and it will blow up in your face in year two. The complete calculation logic with disclosed assumptions is in our article on the business case for a customer portal.
The next step: determine your class first, then run the numbers
Before you request a budget, answer three questions: Which two self-service processes would relieve your support team the most? Does the portal need read or write access to the ERP? And is your case actually above the make-or-buy threshold — or is a SaaS enough? These are exactly the three questions we resolve in a discovery with a make-or-buy check, before a single line of code is written. You'll find the packages and the pricing logic behind them on our customer portal development page — or bring your case straight to a free 30-minute intro call.
