The questions your team answers all day
Most small businesses have a set of questions they answer over and over. Where's my job up to? Can you send me that invoice again? What did we order last time? Has the report been finished? Can I move my booking to Thursday?
Each one takes a few minutes. Someone stops what they're doing, opens two or three systems, finds the answer, and writes it back in an email or says it on the phone. None of it is hard, and none of it feels like a problem on any given day. Add it up across a week and across the team, though, and it's often a surprising amount of time spent being a human search engine for information you already have.
A customer portal is a place on your website where clients log in and find those answers themselves. Done well, it takes a category of routine work off your team and gives customers something they generally prefer: an answer at 9pm on a Sunday without having to wait for someone to reply.
What a portal actually replaces
The specifics depend on the business, but the same handful of jobs come up in almost every conversation we have about portals.
Job or order status is the most common. A builder, a fabricator, an accountant or a repair business can show where each piece of work is up to, so the client doesn't have to ask. Documents are next: quotes, signed contracts, reports, certificates, plans and photos, all in one place rather than scattered through email threads that nobody can find later.
Invoices and payments are a natural fit. Clients see what's outstanding and pay online, and you spend less time chasing. For businesses that sell to other businesses, reordering is often the big one. A trade customer who orders the same twenty items every month wants to log in, see their previous orders and their agreed pricing, and repeat one with a click. Bookings and appointments round out the usual list, particularly where clients need to see history or manage several bookings at once.
The common thread is that the information already exists in your systems. The portal is mostly about letting the right customer see the right slice of it.
Signs you need one
A portal isn't for everyone. If you have a small number of clients and a personal relationship with each, a phone call may be the better service. We'd rather say that than build something nobody logs into.
The signals that it's worth it tend to look like this:
- The same questions keep coming in. If you could write a list of the five questions your team answers most, and they're all lookups rather than judgement calls, that's a portal's job.
- Information lives in someone's inbox. If only one person can answer "where's my job" because the details are in their email, you have a key-person problem as well as a time problem.
- You resend documents regularly. Every "can you send that again" is a sign the document should have a permanent home the client can reach.
- Repeat customers order the same things. Trade and wholesale customers in particular will happily serve themselves if it's quicker than ringing you.
- Your spreadsheet has become the system. If job tracking lives in a shared spreadsheet, a portal is often the visible half of replacing it, which we wrote about in replacing the spreadsheet.
- Clients ask for it. Larger clients increasingly expect to log in somewhere, and some will ask before they ask anything else.
Start with one job, done properly
The most common mistake with portals is trying to build everything at once. A long list of features takes a long time to deliver, and by the time it launches, nobody is sure which parts matter.
We'd suggest picking the single most frequent question and building the portal around that first. If it's job status, the first version shows a client their jobs and where each one is up to, and nothing else. It goes live, customers start using it, and you learn quickly what they look for next. Documents or invoices come in the second round, informed by real use rather than guesses.
This keeps the first version affordable, gets it in front of customers sooner, and means each later piece is built on evidence. It also gives your team time to change their habits, which matters more than most people expect.
Off the shelf or built for you
Plenty of software you may already use comes with a client portal of some kind. Practice management tools, accounting software, booking systems and job management platforms often include one. If yours does, and it covers what your clients need, switch it on and use it. That's almost always cheaper than building.
The case for a custom portal comes when your information lives in several systems that don't talk to each other, when the built-in portal shows the wrong things or shows them in a way your clients find confusing, or when the portal itself is part of how you win work. A business whose clients compare suppliers partly on how easy they are to deal with can get real value from a portal that's designed around its own process rather than a generic one.
A custom portal doesn't usually mean replacing your existing systems. More often it sits in front of them, pulling job data from one place, invoices from your accounting software and documents from wherever they're stored, and presenting them together. That integration work is the bulk of most portal projects, and it's where most of the value is. It's the kind of thing we do in our custom web application work.
Getting security right from day one
A portal puts your clients' information behind a login on the public internet, so it needs to be built with that in mind from the start.
Each person gets their own account. Not one login per client company that gets shared around the office, but one per person, so you can see who did what and remove someone when they leave. Access is limited to what each person should see: a client sees their own jobs and documents, and within a larger client, a site manager might see different things from the accounts team.
Logins should be harder to steal than a password alone. Two-factor authentication is the minimum, and passkeys are increasingly the better option because they're both more secure and easier for clients to use. We covered the trade-offs in our piece on passkeys.
Behind the scenes, it means sensible handling of documents and personal information, logging of who accessed what, and a plan for what happens if something goes wrong. Your obligations around client data don't change because a portal is involved, but a portal does make it more important to have thought them through. If you hold sensitive information such as health or financial records, get specific advice on your obligations. This isn't legal advice.
Getting people to use it
A portal only saves time if clients use it. The ones that succeed tend to share a few habits. Invitations are personal and come with a short explanation of what's in it for the client. The team points people to the portal when they ask a question it can answer, kindly and consistently. And the information in it is kept current, because a portal that shows stale job status is worse than none at all.
It's normal for adoption to build over a few months. Some clients will take to it immediately and others will keep ringing for a while, and that's fine.
If your team spends a good part of each week answering questions the systems already know the answers to, we're happy to talk it through and tell you honestly whether a portal, an existing tool, or something simpler would solve it. Get in touch.
