What a client portal actually needs, and what it does not
Most client portals fail because they were scoped as a product instead of a shortcut. What to include, what to cut, and what it costs to run.
Client portals have a poor track record. They get built, announced, used for a month, and then everyone goes back to email. The software still runs, the hosting bill still arrives, and nobody opens it.
The failure is almost never technical. It is that the portal was scoped as a product with features, when what clients wanted was a shortcut around one specific annoyance.
Start from the annoyance, not the feature list
Ask your clients what they email you about most often. The answers are boringly consistent across industries:
- “Can you resend the invoice?”
- “What is the status of my job?”
- “Where is that document we signed?”
- “Can I get the report from last quarter?”
Every one of those is a person asking a computer question through a human. A portal that answers those four things and nothing else will get used daily. A portal with messaging, notifications, a dashboard, a document library, a knowledge base and a support ticket system will not, because none of it is better than emailing you.
The rule that holds up: a portal only survives if it is faster than sending you an email. Faster than typing one sentence and pressing send. That is a high bar, and most feature lists fail it.
What earns its place
In practice, four things justify a portal for a small business:
Status without asking. One page, one line per job, plain language. Not a Gantt chart. “Submitted, in review, waiting on you, complete.”
Documents that stay put. Invoices, contracts, reports, permanently addressable. The value is not storage, it is that the client stops asking you to resend things from 2024.
A way to hand you something. Uploads. Most client friction is a document they need to give you, and email attachments have size limits and no record of what arrived.
Self-serve payment, if you invoice. This one pays for the portal on its own, because it shortens the gap between invoice and payment more reliably than any reminder you will ever send.
That is the whole list for most businesses. Everything else is a feature you will maintain forever in exchange for a handful of clicks a year.
What to cut, specifically
Messaging. You will build a worse email client and clients will not check it. Send email. Link into the portal from the email.
Notification preferences. Nobody configures these. Pick sensible defaults, send few notifications, and make each one useful.
Dashboards with charts. A small client has three jobs, not three hundred. There is nothing to visualise, and a chart of three data points looks like padding because it is.
A mobile app. A responsive web page reaches every device with no app store, no review process and no second codebase.
Role hierarchies. Two roles, staff and client, cover the vast majority of small businesses. Add the third only when a real person actually needs it.
The part that is genuinely hard
The interesting engineering in a client portal is not the interface. It is making certain that client A can never see client B’s data, under any circumstance, including a guessed URL, a stale session, a shared link and a mistyped ID.
That is worth being paranoid about, because the failure mode is not a bug report, it is a phone call from a client who saw someone else’s invoice. In practice it means:
- Every query scoped to the logged-in account at the database layer, not in the page template where someone will eventually forget.
- Document links that expire and are checked against the session, rather than long unguessable URLs that live forever in an email thread.
- Access decisions in one place, tested, rather than repeated in fifteen files.
- A log of who looked at what, so you can answer the question if it is ever asked.
Getting this right is most of the difference between a portal you can defend and one you cannot. It is also the part that gets skipped when a portal is priced purely on screens.
Build or buy
Buy it if your industry has a mature tool that matches how you already work. Legal, accounting, medical and property management all have credible options, and matching an existing product beats building one.
Build it when the portal has to reflect a process that is genuinely yours, when it needs to read from systems you already run, or when per-client pricing on a hosted product outgrows the cost of owning the thing. The build versus buy question is worth working through properly rather than by instinct.
A focused portal covering the four items above is a small project, and it runs cheaply because portals get very little traffic. Ten clients logging in twice a week is nothing. The cost is in building it carefully, not in running it.
How to tell if it worked
One measure: count the emails you used to get asking for status, documents and invoice copies. If that count has not dropped within two months, the portal did not replace anything, and adding features will not fix it.
If you are weighing a portal against carrying on with email, tell us what your clients keep asking for and we will tell you honestly whether it is worth building.
Related: web app or website, why staff ignore internal tools, and our web application work.
Further reading
Topics in this article
Get new articles by email
One email when something new goes up, roughly twice a month. Plain writing on what software costs and what is worth building. No sequences, no sales calls, and one click to leave.
Keep reading on the same subject
-
Booking systems: when to buy one and when to build
Off-the-shelf booking software fits most businesses. The specific cases where it does not, and what building instead actually costs.
Weigh booking options -
Should you build custom software or buy off the shelf?
A practical framework for deciding between off-the-shelf software and a custom build, including the costs both options tend to hide.
Work through the decision -
Web app or website: which one do you actually need?
The difference between a website and a web app in practical terms, what each costs to build and run, and how to tell which one your business needs.
Tell the two apart