Websites & web design
Customer Portal Development 2026: Cost, SaaS or Custom Build
Customer portal development in 2026: SaaS, CRM portals, low-code or custom build compared, with costs, features, GDPR, accessibility, e-invoicing and timelines.

Key takeaways
In short:
- A customer portal is a secure, login-protected web application where customers view and manage their own documents, invoices, tickets, bookings and order status.
- You have five options: help desk/portal SaaS, CRM-native portals (HubSpot, Salesforce, Zoho), WordPress plugins, low-code (e.g. Softr, Bubble) or custom development.
- Cost in 2026: software from about €17 per agent per month; custom portals range, according to published agency figures, from roughly €8,000 (lean MVP) to well over €150,000 (platform). Roles, integrations and operations are what make portals expensive.
- Rule of thumb: standard process (support, tickets, FAQ) → buy. Unique process, deep ERP/industry-software integration or thousands of external users → custom or hybrid.
- Must-haves for 2026/27 in the EU: GDPR (processing agreements, roles, 2FA, logging), the European Accessibility Act for consumer portals, the new withdrawal function for online contracts and e-invoicing for invoice portals.
If your team keeps hearing "Could you send me that invoice again?", you don't need friendlier support. You need a channel where customers can serve themselves. This guide covers the features a customer portal needs, the options for building one, what they cost based on publicly listed prices, and how to decide between buying and building. It is written for European businesses, with German rules as the detailed example where national law differs. As of November 2026.
What is a customer portal?
A customer portal (also called a client portal, self-service portal or, in B2B, a partner or dealer portal) is a web application behind a login that gives customers access to their own data and transactions: contracts, invoices, orders, tickets, appointments, project status. Unlike a website, a portal doesn't show every visitor the same content. Each customer sees exactly what belongs to their account.
Three things shape every portal project:
- Identity: who is logged in, which company do they belong to, what role do they have?
- Authorisation: which records may this person see or change?
- Data connection: where do invoices, statuses and documents come from (CRM, ERP, accounting, document management or industry software)?
The name depends on the industry: client portal (law firms, accountants), owner portal (real estate), guest portal (hotels, holiday rentals), dealer or B2B service portal (manufacturing, wholesale). Portals for your own staff are employee portals, which have different requirements for roles and single sign-on.
Which features does a customer portal need?
Not every portal needs everything. Start with the features behind most of today's emails, calls and follow-ups.
| Feature | Typical benefit | What to watch |
|---|---|---|
| Login, SSO, two-factor auth | Secure access, company accounts with multiple users | Invitation flow, password reset, 2FA at least for sensitive data |
| Documents & invoices | Fewer "please resend" emails | Versioning, approvals, download log, e-invoice formats |
| Tickets & requests | Structured requests instead of email threads | Categories, required fields, status notifications |
| Status & order tracking | Customers check progress themselves | The data source must be current, or you create new questions |
| Appointment booking | Less phone tag | Calendar sync, reminders, rescheduling |
| Messaging & chat | Conversation attached to the case, not the inbox | Ownership, response times, archiving |
| AI assistant | 24/7 answers to standard questions | Approved sources only, hand-over to humans, AI disclosure |
| Payments | Settle open items directly | Payment provider, reconciliation with accounting |
| E-signature | Contracts and approvals without paper | Simple signatures suit many cases; some need a qualified signature |
| Self-service master data | Addresses, contacts, bank details stay current | Review step before syncing into the ERP |
Two notes on the newer features. For chatbots, the EU AI Act requires that people know they are talking to a machine; according to the European Commission, the transparency rules have applied since August 2026. For e-signatures, Article 25 of the eIDAS Regulation gives only a qualified electronic signature the same legal effect as a handwritten one across the EU. Many approvals need less than that. Where national law requires written form, get legal advice.
What are the options for building a customer portal?
| Option | Examples | Public pricing (as of 6 Nov 2026) | Strengths | Limits |
|---|---|---|---|---|
| Help desk / portal SaaS | Freshdesk, Zendesk, SuiteDash | Freshdesk Growth €17 per agent/month; Zendesk Suite Team €55 per agent/month (both billed annually); SuiteDash from $19 per month, not per user | Live in days, tickets and knowledge base included | Ticket-centric; custom processes and ERP data are limited |
| CRM-native portal | HubSpot Service Hub, Salesforce Experience Cloud, Zoho Creator | HubSpot: only in Service Hub Professional and Enterprise; Salesforce: licence prices on request; Zoho Creator from €8 per user/month (billed annually), customer portal add-on from €100/month for 250 portal users | Data already in the CRM, roles and workflows exist | Licence and platform lock-in, customisation needs specialists |
| WordPress plugin | WP Customer Area and others | Core plugin free, paid add-ons | Runs on your existing site, no per-user fees | Security and updates are on you; limited roles and integrations |
| Low-code / no-code | Softr, Bubble | Softr $19 / $99 / $329 per month, Bubble $32 / $119 / $349 per month (billed annually) | Fast prototypes, your own data model | User and workload limits, platform lock-in, GDPR review needed |
| Custom development | Agency or in-house team | Project price; published agency ranges below | Fits your process exactly, deep integration, no per-customer licence | Higher upfront investment, needs an operations plan |
Help desk and portal software
Freshdesk includes a "customer portal & knowledge base" in its Growth plan, and Zendesk includes the Help Center in all Suite plans. Pricing is per agent, meaning per support employee, not per customer. That makes these tools cheap for companies with many customers and a small service team. But they mainly cover the support process: a ticket comes in, an answer goes out. Project status from the ERP, individual document sharing or ordering are not built in, or only possible through integrations.
CRM-native portals: HubSpot, Salesforce, Zoho
If your customer data already lives cleanly in a CRM, that CRM's portal is the obvious first candidate.
- HubSpot: customers can view and reply to their tickets and use the knowledge base. HubSpot says the feature is available to Service Hub Professional and Enterprise customers. HubSpot also requires paid onboarding on Professional and Enterprise plans, so include it in the total cost.
- Salesforce Experience Cloud: external users need Experience Cloud licences such as Customer Community, Customer Community Plus or Partner Community. Salesforce lists availability in the Enterprise, Performance, Unlimited and Developer editions and quotes prices individually. It's powerful, but it's a platform project.
- Zoho Creator: a low-code platform with a customer portal add-on. Customers, suppliers and partners can log in, submit data and view and edit their records. Pricing is tiered by number of portal users.
WordPress customer portals
Many companies already run WordPress, so a plugin seems obvious. WP Customer Area has more than 10,000 active installations on WordPress.org and is actively maintained (last updated 3 November 2026). For simple file sharing with a handful of clients, that can be enough. With confidential documents, though, keep in mind that the portal shares a server, database and admin accounts with your public website. Every additional plugin is another supplier with its own update process. We explain why we're cautious about this setup in WordPress drawbacks for business websites.
Low-code: Softr, Bubble and similar tools
Low-code is a good way to test a portal with real customers before you invest. Check the plan limits. Softr counts logged-in app users (the Pro plan includes 10 team users and 50 client users, for example) and only offers two-factor authentication on the Business plan. Bubble meters server load in "workload units" and offers 2FA from the Growth plan. As the portal grows, costs scale with users and load, and moving off the platform later usually means rebuilding.
Custom development
A custom portal is built around your process and reads from your systems through APIs. It pays off when the portal is part of what you sell, when data comes from several systems, or when you want to onboard thousands of external users without per-head licences. Many good projects are hybrid: tickets stay in the proven help desk, while the portal adds status, documents and invoices from the ERP.
How much does a custom customer portal cost?
Custom builds have no list prices. Published ranges from German agencies vary widely because "customer portal" can mean a document login for 20 clients or a multi-tenant platform:
| Source (date) | Entry / MVP | Mid-size portal | Large portal / platform |
|---|---|---|---|
| Happycoding (July 2026, net) | €8,000–20,000 | €20,000–60,000 (roles + ERP/CRM) | €60,000–150,000 |
| hafencity.dev (June 2026) | €40,000–90,000 | €90,000–180,000 | from €180,000 |
| TJ Labs (2026) | €30,000–50,000 | €60,000–120,000 | €150,000–300,000+ |
These are agencies' own figures, not neutral market data. Rates also vary across Europe, so treat them as a German reference point. They do show what drives the price:
- Roles and permissions: one account per customer is simple. Company accounts with admins, approval levels and sites are where the effort goes.
- Integrations: a modern REST API connects quickly, a legacy ERP without an API does not. More on this under integrations & APIs.
- Data quality and migration: duplicate customers, missing links and old file shares cost time.
- Security: 2FA, logging, penetration testing, backups and an incident plan.
- Operations: hosting, updates, monitoring, support and further development. Happycoding puts infrastructure and operations alone at roughly €270 to €675 per month after launch, excluding new features.
So compare offers over three years, not on project price alone. A SaaS plan with 10 agents at €55 costs €19,800 over 36 months (Zendesk Suite Team, billed annually), plus setup and integrations. A custom MVP can land in the same range but carries no licence fees per employee or customer.
Buy or build? A decision framework
Work through these seven questions in order. The more you answer "yes", the stronger the case for a custom or hybrid solution.
- Is the core process unique? Is it more than tickets and FAQs, for example claims, construction projects, client case files or order approvals?
- Does the data live in several systems? For example status in the ERP, documents in a DMS, contacts in the CRM.
- Is there no suitable industry solution? Before you build, check whether your sector software (legal, real estate, hotel) already includes a portal.
- Will there be many external users? With per-portal-user licences, costs rise as you succeed.
- Is the portal part of your offering? If customers choose you partly for the portal, it shouldn't look like every competitor's.
- Are there strict privacy or confidentiality requirements? For example professional secrecy, health data or hosting in a specific country.
- Do you have an operations plan? Who handles updates, security advisories and further development? Without an answer, a custom build is risky too.
0–2 × yes: start with help desk SaaS or your CRM's portal. 3–4 × yes: test with low-code or a small custom MVP. 5–7 × yes: plan a custom or hybrid solution with a clean integration architecture. How to scope an MVP sensibly is covered in our guide to MVP development cost.
Which rules apply to customer portals in 2026/27?
The points below are not legal advice. They are project requirements to clarify early with your data protection and legal advisers.
GDPR and security
- Data processing agreement (DPA): every provider that processes portal data on your behalf (hosting, SaaS, email delivery) needs a contract under Article 28 GDPR.
- Hosting and transfers: EU hosting simplifies the assessment. With US vendors, check whether they're certified under the EU-US Data Privacy Framework (adequacy decision of 10 July 2023) or rely on standard contractual clauses.
- Privacy by design: Articles 25 and 32 GDPR require appropriate technical measures, including encryption, roles and data minimisation.
- Check permissions on the server: broken access control is again number one in the OWASP Top 10:2025. OWASP found some form of it in 100% of the applications tested. For a portal, this is the key question: can customer A open customer B's invoice by changing a URL?
- 2FA and logging: at least for admins and sensitive documents. Logs show who downloaded what and when.
Regulated professions: many EU countries impose extra confidentiality duties on lawyers, tax advisers and medical practices when they use IT providers. In Germany, for example, providers with access to client secrets must be carefully selected and bound to confidentiality in text form (§ 43e BRAO, § 62a StBerG).
Accessibility: European Accessibility Act
The European Accessibility Act (Directive (EU) 2019/882) has applied in member states since 28 June 2025. Germany implemented it through the BFSG. It covers e-commerce services, meaning online services through which consumers conclude contracts. A B2C portal with booking, ordering or contract features is therefore usually in scope. Pure B2B portals are not. Microenterprises providing services (fewer than 10 employees and annual turnover or balance sheet of no more than €2 million) are exempt from the service requirements. Retrofitting accessibility costs far more than designing it in from the start.
Withdrawal function
Directive (EU) 2023/2673 requires traders who conclude distance contracts with consumers through an online interface to provide a withdrawal function from 19 June 2026. The function must be continuously available, include a confirmation step and trigger an acknowledgement on a durable medium. The recitals note that a consumer who is already logged in should not have to identify themselves again, which makes a portal a natural place for it. In Germany the rule sits in § 356a BGB.
E-invoicing 2027
National e-invoicing mandates differ across the EU. The EU's VAT in the Digital Age (ViDA) package allows member states to introduce mandatory e-invoicing and brings e-invoice-based digital reporting for cross-border B2B transactions from 1 July 2030. Germany is a useful example: according to the Federal Ministry of Finance FAQ, all businesses may still issue other invoices (e.g. a PDF with the recipient's consent) for domestic B2B supplies until the end of 2026. Businesses with prior-year turnover up to €800,000 can do so until the end of 2027. After that, structured e-invoices are mandatory between domestic businesses. The ministry explicitly lists download via an internet portal as a valid delivery route. For invoice portals, that means offering the structured file (XRechnung or ZUGFeRD 2.0.1+, excluding the MINIMUM and BASIC-WL profiles) alongside the PDF and agreeing the delivery route with business customers. Invoices to consumers are not affected. Read more in Germany's e-invoicing mandate 2027/28.
What does a portal project look like?
| Phase | Content | Outcome |
|---|---|---|
| 1. Analysis | Which requests cost the most time today? Which systems hold which data? | Prioritised use cases |
| 2. Concept | Role model, data flows, integrations, privacy, accessibility | Specification and buy-or-build decision |
| 3. Prototype | Clickable design tested with real customer scenarios | Approved design, fewer late changes |
| 4. Build & integration | Build the portal, connect systems, test permissions server-side | Test system with real (anonymised) data |
| 5. Pilot & rollout | Start with one customer group, invitations, help texts | Measurable adoption, feedback |
| 6. Operate & extend | Updates, monitoring, new modules | Portal grows with demand |
On timing: for a custom MVP, vendors quote 6 to 12 weeks or 8 to 12 weeks, while TJ Labs plans 2 to 4 months. SaaS and CRM portals can often be configured in days if the data is already in the system. In almost every project, integrations and data clean-up delay the schedule, not the front end.
Examples by industry
- Real estate – owner portal: sellers see enquiries, viewings, feedback and marketing progress for their property without calling the agent. Data comes from the agency's CRM. If the agency contract is concluded online with consumers, the withdrawal function and accessibility apply.
- Law firms and accountants – client portal: upload receipts, retrieve tax assessments and reports, handle deadlines and questions on the case instead of via email attachments. Check what your practice software already offers and fill only the gaps. Confidentiality agreements with all providers are mandatory.
- Tourism – guest portal: view the booking, submit arrival details and requests before arrival, book extras and download the invoice. Many EU countries require guest registration. Germany, for example, requires a registration form for foreign guests under § 29 BMG, and paragraph 5 allows electronic capture under certain conditions. Guests are consumers, so booking features usually fall under the accessibility rules.
- Mid-sized B2B – service portal: dealers and industrial customers see orders, delivery status, serial numbers, maintenance logs and e-invoices, and report service cases directly against the machine. Company accounts with multiple users and an ERP integration are at the core.
Which mistakes should you avoid?
- Starting with technology instead of requests. First count which questions arrive and how often.
- Building everything at once. A portal with two features that people actually use beats ten half-finished ones.
- Hiding permissions only in the front end. Every request must be checked on the server.
- Ignoring data quality. A status that is three days old creates more calls than no status at all.
- Forgetting the rollout. Without invitations, an easy first login and consistent redirection ("your invoice is in the portal"), customers stick to email.
- Not projecting the licence model. Calculate per-agent or per-portal-user costs over three years and at twice your customer count.
- No exit plan. Clarify upfront how you export data and documents if you switch vendor or platform.
Conclusion
A customer portal pays off when recurring requests tie up your team and customers could find the information faster themselves. For pure support, help desk software or your CRM's portal is usually the cheapest route. Once your process is unique, data comes from several systems or many external users would trigger licence costs, a custom or hybrid portal is the better investment. Either way, roles, integrations and operations decide cost and security, not the design.
Contentoren builds customer portals and connects them to CRM, ERP, document management and industry software. Development, hosting and support come from Germany, with offices in Cologne and Berlin. There are no flat prices, because every portal's scope and integrations differ. If you'd like to work out whether software, low-code or a custom build fits your case, book a no-obligation call.
Sources
Accessed 6 November 2026
- Freshworks: Freshdesk pricing
- Zendesk: Pricing
- SuiteDash: Pricing
- HubSpot: Customer Portal and Pricing incl. onboarding FAQ
- Salesforce Help: Learn More About Experience Cloud Licenses
- Zoho: Zoho Creator pricing and customer portal add-on
- WordPress.org: WP Customer Area; vendor: wp-customerarea.com
- Softr: Pricing; Bubble: Pricing
- Happycoding: Was kostet ein Kundenportal 2026?
- hafencity.dev: Custom Customer Portal Development 2026
- TJ Labs: Kundenportal Kosten 2026
- EUR-Lex: GDPR (EU) 2016/679; eIDAS Regulation (EU) No 910/2014; European Accessibility Act (EU) 2019/882; Directive (EU) 2023/2673
- European Commission: EU-US data transfers; AI Act regulatory framework; VAT in the Digital Age
- OWASP: A01:2025 Broken Access Control
- German federal law (gesetze-im-internet.de): BFSG § 1, § 356a BGB, § 43e BRAO, § 62a StBerG, § 29 BMG
- German Federal Ministry of Finance: E-invoicing FAQ
All prices as shown on vendor pages on 6 November 2026, without guarantee; vendors change plans frequently. This article is not legal advice.
Frequently asked questions
How much does customer portal development cost?
Off-the-shelf help desk and portal software usually costs a few dozen euros per agent per month, for example Freshdesk from €17 or Zendesk Suite Team from €55 per agent per month billed annually. For custom portals, German agencies publish 2026 ranges from roughly €8,000 for a lean MVP to more than €150,000 for multi-system platforms. Roles, integrations and operations drive the cost far more than the number of screens.
When is a custom portal better than SaaS?
A custom build pays off when your process is not standard, the portal needs deep integration with your ERP, industry software or document management, or per-user licences would grow sharply with your external user base. If a ticket and knowledge-base portal for support is enough, off-the-shelf software is usually faster and cheaper.
Can I build a customer portal with WordPress?
Yes. Plugins such as WP Customer Area provide private client areas with file sharing, and paid add-ons for projects and invoices. That works for simple document sharing. With sensitive data, many roles or integrations, keeping plugins updated and secure quickly becomes the real project.
Does a customer portal have to be accessible?
Under the European Accessibility Act, applied in EU member states since 28 June 2025, e-commerce services through which consumers conclude contracts must meet accessibility requirements. A B2C portal with booking or ordering functions is therefore usually in scope, while pure B2B portals are not. Microenterprises providing services are exempt from the service requirements.
How long does it take to build a customer portal?
A SaaS portal can often be configured in days if the data already lives in your CRM or help desk. For a custom MVP, vendors typically quote 6 to 12 weeks, and several months for portals with multiple roles and ERP integration. Integrations and data clean-up need the biggest time buffer.


