By Mo Hussein

5 min read

A client portal is a private login where your customers can see where things stand: their job, their documents, their invoices, their messages to you. Client portal software is simply whatever provides that login, whether you buy it, build it or add it to a system you already run.

Most small businesses don't need one on day one. A few need one badly.

What do customers actually do in a client portal?

Less than the feature lists suggest. In practice it comes down to a handful of things:

  • Check progress: is the job booked, under way, finished?
  • Download documents: reports, certificates, contracts, the thing you emailed last month and they've lost.
  • Approve things: a quote, a change, a sign-off, with a date recorded.
  • See invoices and what's been paid.
  • Send a message or request, and see the reply in the same place.

If your customers already ask for those five things by phone and email, you're the sort of business a portal helps. If they don't ask for any of them, a portal is a solution looking for a problem.

Signs you need a client portal

  • Your inbox is full of "just checking in" messages, and each one pulls someone off real work.
  • The same document gets sent three times because the first two got buried.
  • Nobody can say for certain what the customer agreed to, because it was settled on a call.
  • Customers ask for updates at hours you're not working.
  • You've started copying details into a shared folder or a spreadsheet just so you can send customers a link.

One of these is an annoyance. Three or four is a pattern.

Off-the-shelf, custom or bolted on: which route?

There are three realistic routes to a portal.

Off-the-shelf client portal software comes first. Plenty of products offer a branded login with file sharing, messaging and invoices. If your needs are ordinary, they're quick to set up and you don't maintain anything. Check how the pricing scales as you add customers, and whether it can show your own job or booking data, because that's where generic tools tend to stop.

A custom client portal is built around your process. The status stages are the ones your work really goes through, the customer sees exactly the things you choose, and your team manages it all from an admin view. That suits you when your customers need to see something specific, such as progress reports for parents or a history of visits, that a generic tool can't show. Our page on custom client portal development covers what we build.

A third route is a portal added to a system you already have. If your jobs, bookings or invoices live in one place already, a portal can read from it. Where a system has an API, a portal can show its data, such as invoices from Xero or bookings from your diary. You keep the tools your team knows, and customers get a window onto them. It's often the smallest and cheapest of the three, and the same thinking as in our guide to connecting your tools to Xero.

Rule of thumb: start with the least you can get away with. If a shared-folder tool and a decent invoicing system solve it, stop there. Build only when the off-the-shelf options keep forcing your customers or your team to work around them.

What to get right

Logins come first. Customers need a proper account with a password reset, not a shared link or a shared password. Each customer should see only their own records, and you want to be able to check that before launch rather than assume it.

Then, what clients see. Resist showing everything you could. A customer looking at internal notes, draft prices or other people's tickets is a bad day for everyone. Decide what's useful to them (status, documents, invoices, approvals) and show only that.

Keep it simple. A portal people can use without instructions gets used. One with five menus and a tutorial gets ignored, and you're back to phone calls. It should work in a browser on any phone, tablet or computer, with nothing to install.

Last, email nudges. A short email when something changes ("your report is ready") brings people back.

When not to build one

Be honest with yourself here. A portal isn't worth it if you have a handful of customers who are happy with email, if your work doesn't have stages anyone wants to follow, or if the real problem is that your internal process is a mess. A portal on top of a muddled process just shows the mess to your customers. Fix the internal side first, perhaps with a proper internal tool or CRM, then decide.

Not sure what custom means here? Our plain guide to what bespoke software is sets out the trade-offs.

Common questions

What is a client portal?

A client portal is a private, secure website where your customers log in to see their own information: progress, documents, invoices and messages. It saves them chasing you and saves your team answering.

Do customers need to install anything?

No. A well-built portal runs in the browser on any phone, tablet or computer, so there's no app to download.

Can a portal show data from our other systems?

Usually. If the system has an API, the portal can read from it, for example invoices from your accounts software or bookings from your diary. We check what your setup allows before anything is built.

Is customer information kept secure?

It should be. Each customer sees only their own records, logins use secure sessions, and the data sits with mainstream hosting providers. Ask any supplier, including us, exactly how that works.

See what we build under client portals, get a price range with the project estimate, or book a free discovery call to talk it through.