Skip to main content

Client Portal Development

Portals your clients actually log into. The question that decides success is whether it saves them effort or only saves you email.

The Question That Decides Whether This Works

Does it save the client effort, or only save you email?

This is where portals succeed or quietly fail, and the failure looks like a portal nobody logs into.

Plenty are commissioned to reduce inbound questions. That is a genuine benefit to the business and no benefit at all to the client, who now needs another password to reach information that used to arrive without asking. Given the choice they will email you anyway, and you will have both the portal and the emails.

Portals that get used give the client something better than what they had. Information at eleven at night without waiting. A complete history in one place rather than scattered across a year of correspondence. The ability to do something themselves instead of asking.

If you cannot state what the client gains, the build will not fix that.

What People Actually Use

Consistently, across professional services:

Documents in one place, current and historical, without having to ask.

Status without chasing. Where something has got to, updated automatically. This removes the single most common inbound question in most service businesses and is usually the strongest reason to build.

Approvals, with a record of who approved what and when.

Invoices and payment. Frequently the most-used feature, because it removes friction on both sides.

Structured requests, so what arrives contains what you need rather than three rounds of clarification.

What Reliably Does Not Get Used

Anything asking the client to maintain data for your benefit. Reporting they never requested. Messaging that competes with email, which almost always loses because email is where they already are.

Feature count is not the point. Four things used weekly beats twenty things visited twice.

The Flaw To Test For

The most common serious defect in portals is not exotic and you can check it yourself in a minute.

Open one of your own records and look at the address. If it contains an identifier, change it. If you see somebody else’s data, the system is checking that you are logged in and never checking whose data you asked for.

Automated scanners rarely catch this, because nothing about the request is malformed. Only the business rule is missing. Ask any supplier to demonstrate it is not possible, including on exports and reports, which are where the check is most often forgotten.

What Moves The Price

How many client roles there are. One contact per client is simple. Multiple people with different permissions, plus the ability for the client to manage their own users, is a permissions model.

Whether it reads from existing systems or holds its own data. Reading live from your CRM, accounting or project tools is the better answer and the integration is where the work is.

Document handling. Upload, versioning, retention and access control. Straightforward individually, and it accumulates.

Whether clients pay through it. Payments bring their own failure paths.

Branding depth. Your logo is trivial. Per-client branding is a feature.

Where Portal Projects Go Wrong

Built and then offered. Adoption fails when the portal is an alternative rather than the route. What works is switching: information that used to be emailed now arrives as a notification pointing to the portal.

Login friction. Password reset is the most-used feature of any portal. If it is awkward, people stop coming back and you never hear why.

Ignoring mobile. Clients check status and approve things on phones. A portal reviewed only on a desktop will disappoint in exactly the moment it matters.

No answer for the client who will not use it. There will be some. Decide in advance whether they keep getting emails, because deciding under pressure produces two processes.

Questions To Ask Whoever Builds It

  • Can a client see only their own data, on every route including exports? Ask for a demonstration.
  • What does password reset look like? The most-used feature.
  • What happens on a phone? Specifically approvals and document viewing.
  • How does a client get their people added and removed? If that needs you every time, it is your admin burden not theirs.
  • What do we do about clients who will not adopt it?

A Brief You Can Send Anyone

Who our clients are: [and how technical they are]
What they ask us most: [the top three questions, verbatim]
What we send them now: [documents, updates, invoices, and how]
What they should be able to do themselves: [in priority order]
Where that information lives today: [systems, and whether they have APIs]
How many people per client: [one contact, or several with different access]
Whether they pay through it: [yes / no]
What must not be visible to them: [internal notes, margins, other clients]

How We Approach It

Start with the questions clients actually ask, because that list is the specification. Read from the systems that already hold the answers rather than duplicating data, so the portal cannot drift out of step with reality.

Then switch rather than offer, so it becomes the natural route rather than an extra one.

Where this is central to how the business runs it is worth designing deliberately: client portal systems covers the delivered product, and the pricing page covers how a portal project is scoped and quoted. Get in touch with the three questions your clients ask most and we can scope from there.

If you are still deciding whether to build one at all, build vs buy a client portal sets out where a subscription product serves well and where it stops fitting.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.