Skip to content
DT Nova

Client portal cost: what a customer portal costs to build and run

Client portal cost depends first on whether the portal comes with a system you already use or is built for your customers. A portal included in a CRM, accounting or practice system is priced by the vendor, often per external user. A custom portal is priced on the work: how many kinds of users log in, what they can see and do themselves, how many systems it reads from and writes to, and how strict the login, permission and privacy rules are. This guide explains each cost driver, compares the routes over five years, lists the costs people forget and shows how to compare quotes. Client portal and customer portal mean the same thing here.

It does not quote our own prices. It explains how a portal budget is built, so any quote you receive, from us or from anyone else, makes sense. For what we build, see portal development; for portals for your own staff, see our guide to intranet cost.

The short version

  1. The first version: login, permissions, the self-service actions, integrations, testing and launch.
  2. Running costs: hosting or vendor fees, identity services, email delivery and storage.
  3. Maintenance: security updates, monitoring and fixes, every year.
  4. Support: questions from customers, which a good portal reduces.

People's time is most of the bill

A custom portal is built from hours: understanding what customers ask for today, designing the self-service flows, building login and permissions, connecting the systems behind it and testing. What an hour costs follows where the team works. Eurostat's release of 31 March 2026 puts average hourly labour costs across the whole economy in 2025 at €34.9 in the EU and €38.2 in the euro area, from €12.0 in Bulgaria to €56.8 in Luxembourg (read on 12 November 2026). These are whole-economy figures, not software rates. Compare totals for the same scope, not hourly rates.

What drives client portal cost

DriverWhy it adds workHow to keep it in check
User typesConsumers, business customers, partners and suppliers each see different dataLaunch for the user type that asks for the most today
Company accountsSeveral users per customer, with an administrator who invites and removes colleaguesDecide early whether customers manage their own users
Self-service actionsEach action, such as ordering, booking, paying or changing details, needs rules and testsShow first, let users act later
IntegrationsERP, CRM, billing, document and ticketing systems each have their own interfaceRead from the system that answers most questions first
Login and identityPasswords, single sign-on for business customers, multi-factor login and account recoveryUse a proven identity service
DocumentsInvoices, contracts and reports must be generated or fetched, with access controlLink to documents in the system that already holds them
AccessibilityForms, tables and documents are where portals usually failTest against WCAG 2.2 from the first release

Built-in portal or custom: compare five years

If the portal in your existing CRM, accounting or practice software covers what customers need, using it is usually right, and a good supplier will say so. A custom portal pays off when customers need data from several systems in one view, when your permissions or processes do not fit the vendor's model, when the vendor charges per external user and you have many, or when the portal is part of your product.

  • Built-in portal: the fee per external user or the portal add-on, times your expected users, times sixty months, plus set-up and any add-ons.
  • Custom portal: the build, then hosting, identity service, maintenance and planned changes each year.
  • Both: support time, content and document work, and the cost of moving customers to another portal later.

Security and personal data are part of the scope

A portal that shows personal data must protect it with security appropriate to the risk (Regulation (EU) 2016/679, Article 32). It can also make two obligations easier to meet: the right of access (Article 15) and the right to data portability, which gives people their data in a structured, commonly used and machine-readable format (Article 20). Any supplier that hosts the portal for you needs a data processing agreement (Article 28; all read on 12 November 2026). If the portal is used to sell products or services to consumers, the European Accessibility Act has applied to e-commerce services since 28 June 2025 (Directive (EU) 2019/882, Article 31). Planning these in costs far less than adding them after launch.

The hidden costs of a client portal

  • Data quality. A portal shows customers the data in your systems as it is; errors that staff worked around become visible.
  • Account management. Invitations, lost passwords and leavers at customer companies need a process.
  • Per-user creep. Built-in portals priced per external user grow with every customer you win.
  • Adoption. Customers need a reason to log in instead of sending an email.
  • Integration upkeep. Systems behind the portal change, and each connection needs looking after.
  • Security testing. A portal open to the internet should be tested before launch and after large changes.

Pricing models and who carries the risk

ModelHow it worksWho carries the risk
Fixed priceAn agreed price for a written scopeThe supplier carries estimation risk; the buyer carries the risk of a wrong scope
Time and materialsHours billed as worked, against an estimateThe buyer carries overrun risk; most flexible
Phased fixed priceRead-only portal first, self-service actions priced one at a timeShared: each phase is based on real use
Vendor add-onA monthly fee, often per external userThe buyer carries the risk of fees growing with customers

How to compare portal quotes

  • Which user types and self-service actions are included, by name?
  • How do users log in, and is multi-factor login included?
  • Can customer administrators manage their own colleagues?
  • Which systems does it read from and write to, and what is assumed about them?
  • Is security testing included before launch?
  • Is accessibility tested, and against which standard?
  • For a vendor portal: what does it cost with your expected external users in three years?
  • Are the code, database and hosting in your company's name?

Ways to spend less without cutting quality

  • Answer the top questions first. The three things customers ask about most pay for the portal.
  • Show before you act. A read-only portal is far less work than one that changes data.
  • Use a proven identity service. Login is not where to save on testing.
  • Fix the data first. Clean data in the systems behind it saves rework.
  • Own the code. Code in your own repository keeps every future change open to competition.

Related reading: web app development cost, API integration cost, penetration testing cost and booking system cost. All our services are on the services page, and every guide is in the guides library.

Questions people ask

How much does a client portal cost?

It depends on the route and the scope: a portal built into your CRM, accounting or practice software is priced by the vendor, often per external user, while a custom portal is priced on the number of user types, the self-service actions, the systems it reads from and the security and privacy rules it must enforce. Any figure given before that scope is written down is a guess.

What is the difference between a client portal and a customer portal?

Mostly the word. Professional services firms tend to say client portal, product companies say customer portal. Both give external users a login to see their own data, documents and requests. The cost drivers are the same.

Is a built-in portal cheaper than a custom portal?

When the data lives in one system and the standard roles fit, usually yes. When customers need data from several systems in one place, when companies have many users with delegated administrators, or when the vendor charges per external user and you have many, a custom portal can cost less over five years.

What are the running costs of a customer portal?

Hosting or vendor fees, identity and login services, email delivery, maintenance and security updates, and the support time that customer questions take. A good portal reduces support work; a poor one adds to it.

Does a client portal have to meet GDPR requirements?

Yes, if it shows personal data. It needs security appropriate to the risk (GDPR Article 32), and it can make access and portability requests easier to answer (Articles 15 and 20). If a supplier hosts it for you, you need a data processing agreement (Article 28).

Sources

Your client portal scope checklist

Write one line for each before you request quotes. The answers make quotes comparable.

  • The questions customers ask most today, and how they ask them.
  • User types: consumers, business customers, partners, suppliers.
  • Expected users at launch and in three years.
  • What users see, and what they can do themselves.
  • Systems behind the portal, and how they expose data.
  • Login: passwords, single sign-on, multi-factor.
  • Company accounts and who administers them.
  • Documents shown or generated.
  • Security and accessibility standards to test against.
  • Ownership: code, database and hosting in your company's name.