Guide · 12 November 2026
What is a client portal, and what should one let customers do?
A client portal is a private login where each customer sees their own work and nothing else: where it is up to, their documents and invoices, anything waiting on them, and what happens next. A good one answers the question your team is asked most, before the customer picks up the phone. It is worth having once the same status questions and the same chased documents are filling your week.
What a client portal actually is
It is a window onto your own system, cut down to one customer. The job, the documents, the invoices and the next step already live somewhere in the business; the portal shows a customer their share of that, in plain words, whenever they want to look.
That is what separates it from a shared folder or a long email thread. A folder holds files but cannot tell anyone what happens next. A portal reads from the same record your team works from, so when the job moves on in the office, the customer sees it move on too, without anybody writing an update.
The customer's view and the team's view are kept separate on purpose. Your internal notes, your margins and the conversation about the awkward customer stay on your side of the line.
What it should let customers do
See where their job is up to, described the way they would describe it. "Survey booked for Tuesday" is useful; a status code from your system is not.
Find the latest version of every document in one place: the quote, the contract, the plans, the certificate at the end. Nobody should have to search their inbox for the attachment called final-2.
Do whatever is waiting on them, there and then. Sign the agreement, upload the photo or the paperwork you asked for, approve the extra work, pay the invoice. Each of those is a reason the job would otherwise stall while somebody chases.
Ask about something with the job attached. A question raised from inside the portal arrives already linked to the right customer and the right piece of work, rather than as a fresh email somebody has to match up by hand.
Start with the question your team hears most
A portal that tries to show everything gets ignored. One that reliably answers the most common question gets used, and the rest can follow.
A simple way to find it: for two weeks, have whoever answers the phone and the inbox note down what each customer was asking for. "Where are we up to?", "Did you get my documents?", "What do I owe?" and "When are you coming?" tend to come up again and again. The one at the top of the list is what the portal's front page should answer.
Not everything needs a login
A login suits customers you work with over weeks or months, who will come back to check on things. For a single action, such as signing one agreement, filling in one form or leaving feedback after a job, asking somebody to create an account first is the surest way to make sure they never do it.
For those, a secure one-off link works better: the customer opens it, does the one thing, and the result is filed against their job. A good system can use both, a portal for the ongoing relationship and links for the one-off tasks, and both read from the same record.
What to settle before anything is built
Who sees what. Decide whether a customer sees every job they have ever had or only the live one, whether two people at the same customer see the same things, and what your staff can see of each other's customers. That decision shapes everything else, so it comes first.
How sensitive documents move. If you currently email contracts, identity documents or financial paperwork because it is the easy way, the portal is the place to stop. Each document should be visible to the people it belongs to and nobody else, and never sit on a public web address.
Who did what, and when. When a customer signs, approves or uploads something, the system should keep their name and the time against it. That record is what settles a disagreement months later.
Signs your business is ready for one
Different customers ask the same status question every week, and answering it is part of somebody's job. Documents go back and forth by email until nobody is sure which is the latest. Getting a new customer started takes a chain of emails that stalls when someone is on holiday. Work waits because a signature, a form or a payment is sitting in a customer's inbox.
If none of that sounds familiar, you probably do not need a portal yet. A clear email at each stage of the job may be all your customers want.
How we build one
We decide first what each customer is allowed to see, because that shapes everything else, and then we make the portal answer the one question your team hears most. In an internal business system we built, customers sign in and see their own project, documents, invoices and progress, kept separate from the team's view of the same work.
Around the portal sit the pieces that stop the chasing. When a deal is agreed, the system creates the agreement from a template and hands the customer a signing link. Intake forms go out as links the customer opens without logging in, and their answers are saved against the job. Feedback after the work comes back the same way, with no account needed. The portal is one part of the same system that runs the jobs, so it never needs updating by hand.
Where to go next
Think this is you?
Tell us what is getting in the way, and we will tell you what it would take to fix it.
More guides
- What does a custom CRM give you that an off the peg one doesn't?What a custom CRM gives a business: your own sales stages, follow ups the system sends for you, and a customer record that stays up to date by itself.
- What is job management software, and what should it do?Job management software in plain English: what it does from enquiry to invoice, what to look for, and why it works best built around how you run jobs.
- What is an instant quote tool, and does my business need one?What an instant quote tool and quoting software do, the one test that says whether your business is ready, and when a proper quote request works better.
- What is custom business software?Custom business software explained: what it is, real examples of systems and apps built around one business, what it replaces, and who owns it at the end.
- Is custom software worth it for a small business?When custom or bespoke software is worth it for a small business: the honest test, where it pays first, what a build includes and how to start small.
- How long does custom software last?Software does not wear out, but everything around it moves. What actually ages, what looking after it involves, and when a rebuild is the honest answer.
- What software do personal trainers actually need?What software personal trainers and online coaches need: payments, programme delivery and client records, and when your own coaching app starts to pay.
- What decides what custom software actually costs?The five things that move the price of custom software, what a quote should say it leaves out, and the questions that tell you a figure is worth trusting.
- How long does custom software actually take to build?Honest timescales for a website, a business system and a first product, and the three things that make a project late that have nothing to do with the code.
- What is a business automation system, and when is one worth it?Business automation in plain English: what it is, real examples of it running, the signs your business needs it, and how to tell whether it would pay.
- Build or buy business software: when your own system paysBuild or buy, answered straight: which parts of a business are worth building around how you work, and the questions that tell you which side you are on.
- Six signs your spreadsheet has quietly become a business systemA spreadsheet stops being a spreadsheet long before anyone notices. Six specific signs, and what each one is actually costing.
- What actually changes when your software company is down the roadDoes a local software company matter? What being nearby genuinely changes, what it does not, and the two questions that predict a project far better.
