A customer portal is a private area of your website where each customer logs in to see their own information: the status of their job or matter, their documents, their invoices and a place to message you. The features people actually use are the ones that answer the question they would otherwise phone or email about, and the rest tend to sit untouched.
What a customer portal is, and what it replaces
Many businesses already run a portal by accident. It is the email thread with seven attachments, the shared folder link that expired, and the text that says “any update?” A portal moves those into one place that belongs to the customer, with a login, so they can check at 9pm without waiting for you.
Some people say client portal and some say customer portal. They mean the same thing: a logged-in area where your customer sees records that are theirs and no one else’s. What differs is the data behind it, and that is why the examples below look so different from each other.
Customer portal examples by type of business
The same four building blocks (status, documents, payments, messages) appear in nearly every example. What changes is which block matters most.
| Business | What the customer wants to see | The block that carries it |
|---|---|---|
| Home builder or renovator | Which stage the job is at, selections still needed, variations to approve | Status and approvals |
| Accounting or bookkeeping practice | What the practice still needs, where returns are up to, documents to sign | Documents and checklists |
| Legal or advisory firm | Matter progress, secure document exchange, invoices | Documents and messages |
| Clinic or allied health | Upcoming appointments, forms to complete beforehand, receipts | Bookings and forms |
| Trade or maintenance contractor | Job booked, technician on the way, completed work and photos, invoice | Status and payments |
| Property manager | Maintenance requests and their progress, statements, notices | Requests and documents |
Each of these started as a repeated question. A builder who gets twenty “where are we at?” messages a week has a status problem. An accounting practice that chases the same missing bank statement every March has a documents problem. Name your repeated question first and the portal practically designs itself.
The features people use
Status
The most used feature in almost every portal is a simple answer to “what stage are we at, and what happens next?” A short list of named stages with the current one highlighted, plus a plain sentence of what is waiting on whom, does more than a detailed schedule nobody reads.
Documents
Quotes, contracts, drawings, certificates, tax summaries and photos, each attached to the right job or matter. The useful extras are small: a clear “needs your signature” marker, a date on each file, and an upload box for the customer to send things back so they stop coming by email.
Payments
Invoices with a pay button, a history of what has been paid, and receipts. Where it links to your accounting system, a paid invoice should show as paid in both places without anyone retyping it. This is the feature that most directly affects your cash flow, because people pay faster when the invoice is one tap away. Our guide on how tradies get paid faster covers the habits around it.
Messages
A thread attached to the job, so the conversation sits next to the documents and status it refers to. The test is whether your team prefers it to email. If staff keep answering by email anyway, customers will too, and the portal becomes a notice board.
Approvals and forms
Choosing a tile, approving a variation, completing an intake form, accepting a quote. These work well because they replace a back-and-forth with a single recorded decision.
What people do not use
The features that tend to go unopened are the ones added because they sounded good: activity feeds, dashboards with charts, social-style comments, a document library the customer must search. If a feature does not answer a question the customer has, leave it out of the first version. You can add it when someone asks.
The other common failure is the login. A customer who has to reset a password every time they visit stops visiting. A sign-in link emailed on request, or a short code sent by text, keeps the barrier low while keeping the data private. Security still matters: each customer must be able to see only their own records, and a portal that holds identity documents or financial records deserves proper review by someone who builds these for a living.
A worked example with your own numbers
Take a builder with 12 jobs running at once. Count, for two weeks, every call, text or email asking for a status, a document or a payment detail. Suppose the count comes to 60 in a fortnight, and each takes six minutes to answer and get back to what you were doing, including the interruption. That is 360 minutes, or six hours, every two weeks.
If a portal answered even half of those questions, you would save around three hours a fortnight. Put your own hourly cost on it and compare the result with the build and the monthly running cost. The calculation also works in reverse: if your count is five, a portal will not pay for itself, and a well-written weekly update email will do the job. The benefit that does not appear in the sum is the customer who feels informed and tells a friend, but treat that as a bonus and not the reason.
What it takes to build
A portal has four parts: a login system, a place where each customer’s records live, the screens that display them, and the connections that keep those records current. The first three are well understood. The fourth is where the effort tends to sit, because the status, documents and invoices usually already live in other systems (a CRM, a job management tool, accounting software). Our article on API integration cost explains what makes those connections cheap or expensive.
The decision most owners face is whether to buy a portal from a software vendor or build one that fits their process. We cover that in client portal: build or buy. Buying suits a business whose process matches the product, and building suits one whose process is the thing that sets it apart. Start with the smallest version that answers your repeated question, and watch whether customers use it before you add more.
Questions to settle before you build
- Who is a customer? One person per job, or a couple, a company with several contacts, or a tenant and an owner who each see different things.
- Who updates the status? If a site supervisor must remember to tick a box, it will go stale. Better that moving a job in your CRM or job tool moves it in the portal.
- What happens when the job ends? Some customers will want their documents for years. Decide how long access lasts and what is archived.
- Who answers messages, and how quickly? A message box with no one watching is worse than no message box.
- What can be shown and what must not? Margins, internal notes and other customers’ details need to stay out of every screen.
These questions cost nothing to answer and change the build more than any design choice. Write the answers down before anyone starts.
Making sure customers use it
- Introduce it at the start of the job, not halfway, and send the first login yourself.
- Stop answering status questions by phone with the answer; reply with a link to the place it lives.
- Send notifications that carry the news (“your selections are due Friday”) so people do not have to log in to find out.
- Check which parts are opened and drop what is not.
If you would like help working out which of these fits your business, CentriWeb builds custom software including customer portals, and starts by finding the repeated question that costs you most. For a first version of the enquiry side, our guide to an online quote calculator shows how the front of the process can feed into the same system.