Customer portal: what it is, examples and when you need one

You keep answering the same questions by email: where is my order, can you resend the invoice, what is the status of my request. A customer portal is the usual answer. In plain words, it is a password-protected area of your website or web app where clients log in and find their own documents, invoices, orders and requests without asking your team. This guide explains what a customer portal is, shows customer portal examples by industry, and helps you decide whether you need one now, later or not at all.

Short answer: you need a portal when the same client questions arrive often enough that answering them by hand costs more than a page that answers them automatically. Below: the signals, the typical contents, client portal software versus a custom build, integrations, GDPR, cost and a phased plan.

What is a customer portal?

A customer portal is a web application with accounts and roles. Each client sees only their own data; your team sees everything through an admin panel behind it. It sits between your public website and your internal systems, reading from the CRM, invoicing tool or calendar and showing each client a permission-controlled slice.

The term overlaps with a few others:

• Self-service portal — the same thing, described from the client's side: they serve themselves instead of writing to you.
• Partner portal — a portal for resellers, agents or suppliers rather than end customers.

Customer portal examples by industry

Portals look different depending on what the client wants to get done. A few customer portal examples we see most often:

• Agency or consultancy. Project status, deliverables to approve, hours used against the retainer, invoices, a message thread per project.
• Real estate. Buyers and partners see listings matched to them, viewing appointments, offers and the document pack for a property. Our Harbor Atelier project is a partner desk of this kind: agents log in, manage their listings and track enquiries.
• Clinic or practice. Appointments, test results, referrals, invoices and consent forms.
• Logistics and transport. Shipment tracking, proof of delivery, recurring bookings, damage claims with photos.
• B2B wholesale. Customer-specific price lists, reorder from history, open invoices, credit limit, delivery slots.
• Finance and accounting. Document exchange, monthly reports, deadlines, signatures, with stricter security.
• Education and training. Course schedule, materials, certificates, payments, attendance.

What a customer portal typically contains

Most portals are built from the same six blocks. Start with the two or three your clients ask about most and add the rest later.

A portal does not have to include all six. If bookings are the main thing, an online booking system with a client login (from €2,500) may be all you need, and you can grow it into a fuller portal later.

How clients log in to a customer portal

Most people who type "customer portal" into Google are looking for the login page of a company they already buy from. That tells you something useful: for clients, the portal is the login. If signing in is slow or confusing, nothing behind it gets used.

Good portals make the first login almost invisible:

• Invitation, not registration. Your team adds the client in the CRM or admin panel; the portal emails an invitation link. The client sets a password or signs in with Google or Microsoft.
• Magic links for occasional users. Clients who log in twice a year get a one-time link by email instead of a password they will forget.
• One obvious entry point. A "Client login" link in the website header, in every email signature and on every invoice. Clients should never have to search for it.
• Two-factor authentication where the data needs it. Mandatory for your admin roles and for finance or health data; optional for a simple order-status portal.

Signals that you need a customer portal

You rarely need a portal on day one. You need one when the volume of repeat questions turns into a real cost. Typical signals:

• Email ping-pong. The same request needs three or four replies before it is complete: a missing file, a question about the file, a confirmation.
• "Where is my…" calls. Clients phone to ask about order, shipment or project status, and your team opens an internal system to read it out to them.
• Manual status updates. Someone on your team spends part of every day writing "just to let you know" messages that could be a line in a table.
• Clients asking for it. Larger clients, especially in B2B, increasingly expect a login rather than an inbox.

A quick test: count the client-facing messages your team sends in a normal week. If a third or more only report status or re-send something, a portal will pay for itself quickly. If the bigger problem is that your own team cannot see the full picture of each client, read when you need your own CRM first — the portal usually comes after the internal system, not before.

Client portal software vs a custom build

There are two routes: subscribe to ready-made client portal software, or have a portal built around your workflow.

Ready-made software is a sensible first step when your process is close to standard and you have fewer than a few dozen active clients. It becomes expensive and awkward with hundreds of clients, an unusual workflow, or systems the vendor cannot connect to.

A custom portal is custom web application development, and at Pazl it starts from €2,500 for a first version with accounts, the two or three core blocks and one integration — see customer portal development for what is included. Prices on the market vary widely, and they depend less on the portal itself than on the number of roles and on the systems it has to talk to. When you compare quotes, compare them on those two things.

Integrations, security and GDPR

Integrations: the portal should read, not duplicate

A portal is only useful if it shows the truth, so it should read from the systems where your team already works rather than keep its own copy. The usual three:

• CRM — the client list and their deals or cases. A new client in the CRM gets a login without anyone typing their details twice.
• Invoicing or accounting — open and paid invoices, payment links, receipts. The client pays in the portal; the accounting tool sees the payment.
• Calendar — availability and appointments, so a booking in the portal blocks the slot and the reminder goes out automatically.

If those systems do not yet talk to each other, the portal is often the moment to fix it; we covered the mechanics in from scattered services to one system.

Security and GDPR

A portal holds personal and often financial data, so the basics are not optional:

• Strong password rules or single sign-on, two-factor authentication for admin roles, short-lived sessions.
• Role-based access: a client sees only their records, a partner only their listings, an employee only what their job requires.
• Encryption in transit and at rest, backups, and an audit log of who opened or changed what.
• GDPR: a lawful basis for each data type, a privacy notice written for the portal, data stored in the EU, a process for access and deletion requests, and data processing agreements with hosting, email and payment providers.

Common customer portal mistakes

Most portals that fail do not fail because of the technology. They fail because clients have no reason to log in, or because what they see there is out of date.

• Launching with everything. Six blocks, three roles and four integrations in version one means months of work before a single client logs in. Start with the two or three questions clients ask most.
• A portal that keeps its own copy of the data. If staff update the CRM and forget the portal, clients see stale statuses and go back to email. The portal should read from the system of record, not duplicate it.
• Statuses nobody owns. "In progress" means nothing if nobody is responsible for moving an order to "ready". Agree the statuses and who changes each one before the build.
• Still answering by email. If the team keeps replying to "where is my invoice?" with an attachment, clients will never switch. After launch, answer with a link to the portal.
• Hiding the login. A portal that clients cannot find is a portal they do not use. See the login section above.
• Treating GDPR as a final step. Roles, data location and deletion requests are cheaper to design in than to retrofit.

Cost, timeline and a phased build plan

What drives cost

Three things move the price: the number of roles (client, partner, admin, staff), the number of integrations, and whether payments are involved. A documents-and-status portal with one CRM integration is at the low end; a multi-role portal with payments, bookings and three integrations at the high end.

Timeline

A first version covering the two or three most common requests usually takes three to six weeks from kick-off to a live portal with real clients. Larger portals take two to three months. What slows projects down is rarely the code: it is unclear statuses or missing API access to an old system.

A phased plan that keeps the first version small

1. Week 1 — map the requests. List every recurring client question, group it into the six blocks, pick the top three. Define the statuses and who changes them.
2. Weeks 2–4 — build the core. Accounts and roles, the three blocks, one integration with the system that holds the truth, an admin view for your team.
3. Week 5 — pilot with ten clients. Watch what they open and what they still email about. Fix the wording before adding features.
4. Week 6 — open it to everyone. Put the login in your email signatures and invoices, and stop answering by email what the portal already shows.
5. After launch — add blocks quarterly. Payments, bookings, messages, a second integration. Each addition should remove a specific category of email, or it does not go in.

Customer portal checklist: before you start

Use this list whether you are trialling client portal software or briefing a developer.

• We have counted the repeat client questions for one normal week and know the top three.
• We know which system holds the truth for each of them: CRM, invoicing, calendar, ERP.
• Those systems have an API, or we know who can export the data.
• Each status has a name, a meaning and an owner on our team.
• We know who the users are: clients only, or also partners, suppliers, staff.
• We know whether clients will pay inside the portal. If yes, see how to accept payments online.
• We have a GDPR basis for every data type the portal shows, and an EU hosting preference.
• We have ten friendly clients ready to pilot it.
• We know what we will stop doing by email once the portal is live.

If you tick fewer than half of these, start with the internal side first — often a CRM or a cleaner set of tools — and come back to the portal later. If the portal is your first web product and you want to keep version one small, the approach in how to build an MVP web app applies almost unchanged.

Frequently asked questions

Is a customer portal the same as a CRM?

No. A CRM is your team's view of clients; a portal is the client's view of their own data. They usually share the same database, but they serve different people with different permissions.

How do clients get their login?

Typically your team creates the client in the CRM or admin panel and the portal sends an invitation email. Clients set their own password or sign in with Google or Microsoft.

What does a customer portal cost to run?

Hosting for a small portal is usually a few tens of euros a month, plus your payment provider's transaction fees if you take payments and a support arrangement for updates. There are no per-user fees with a custom build.

Do we need a mobile app as well?

Usually not at first. A responsive web application works on any phone without an app store. A native app makes sense later if clients need push notifications or offline access, and it can reuse the same backend.

Is a client portal the same as a customer portal?

Yes. "Client portal" is more common for agencies, accountants, lawyers and consultants; "customer portal" for product and B2B companies. Both mean a login area where each client sees their own data. "Self-service portal" describes the same thing from the client's side.

Can a customer portal replace email with clients?

Not completely, and it should not try. A portal replaces the repeat messages — status updates, re-sent invoices, missing documents. Conversations that need judgement still happen by email, phone or in the portal's message thread. A good target for the first version is removing a third of routine client email.