Blog

Client portal software vs a custom client portal

Benjamin · · 7 min read

Customers want to help themselves, but most portals go unused because the information in them is out of date. How the main client portal software compares, and how a portal connected to your tools keeps itself current.

A client portal is a secure, login-protected place where your customers can see what matters to them, such as the status of their job, their documents, invoices and messages, without emailing you to ask. Done well, it cuts the "any update?" emails, makes you look organised, and gives customers answers at 10pm on a Sunday. Done badly, it becomes one more login that nobody uses, because the information in it is out of date.

This guide compares the main client portal software and how it works, explains why so many portals go unused, and shows how a portal connected to the tools you already run keeps itself up to date.

What the research says about self-service

  • Customers want to help themselves first. In Harvard Business Review's "Kick-Ass Customer Service" (2017), Matthew Dixon and colleagues reported that across industries, 81% of customers try to take care of matters themselves before reaching out to a live representative. (Harvard Business Review)
  • Chasing status is expensive on both sides. Asana's Anatomy of Work Index found that around 60% of working time goes on "work about work", including chasing the status of work and searching for information. (Asana) Every "where are we with this?" email from a client creates that work for your team too.

A portal answers the question before it's asked, but only if the answer in the portal is current.

What a client portal should do

The best portals cover a few jobs very well:

  1. Show status. Where the job, order, case or application is, and what happens next.
  2. Share documents both ways. Clients upload what you need, and download what you send, without email attachments.
  3. Handle requests. New orders, bookings, changes or support requests, captured in a structured form rather than an email thread.
  4. Show money. Quotes to approve, invoices to pay, payment history.
  5. Keep the conversation in one place, attached to the job rather than scattered across inboxes.
  6. Respect permissions. Each client sees only their own data. Within a client, different people may see different things.

The client portal software, and how it works

Portals built into tools you already use

How they work: many business tools include a portal for their own data. HubSpot's customer portal lets customers log in to see and reply to their support tickets and use your knowledge base. (HubSpot) Helpdesks like Zendesk and Freshdesk have similar help centres, accounting tools let customers view and pay invoices online, and practice-management software for accountants and law firms often includes a client portal.

Where they shine: no build, and the data is always current because the portal sits on the tool itself.

Where they stop: each portal only shows one tool's data. A customer might log in to one portal for tickets, follow a link for invoices, and email you for job status. That's three places, and none of them shows the whole picture.

All-in-one client portal products: SuiteDash and similar

How they work: products that bundle a white-label client portal with their own CRM, file sharing, invoicing and project tracking.

Where they shine: small service businesses happy to run client work inside one product.

Where they stop: the portal works best when you move your CRM, projects and invoicing into the same product. If you already run on other tools, you're either duplicating data or replacing systems.

No-code portal builders: Softr and similar

How they work: Softr builds client portals and internal tools on top of data you already have, such as Airtable, Google Sheets, Notion, SQL databases or its own database, with logins and permissions. (Softr)

Where they shine: a good-looking portal on top of an Airtable base or sheet, quickly, without developers.

Where they stop: the portal shows whatever is in that one data source. If job status lives in a scheduling tool and invoices live in Xero, someone still has to copy them into the base for the portal to be right.

Why most client portals go unused

Clients stop logging in when the portal can't be trusted. That happens when:

  • The status is stale, because someone has to remember to update it by hand.
  • Half the information is elsewhere, so the client emails you anyway.
  • It's hard to get in, with forgotten passwords and confusing invitations.
  • It doesn't work well on a phone.
  • Nothing pushes them there: no notification when something changes, so they don't know to look.

Every one of those is a data problem first, and a design problem second.

A portal that keeps itself up to date

The portals clients actually use are the ones that pull live information from the systems your team already works in. Nobody updates the portal. It updates itself:

  1. Connected to your real systems. Job status comes from your scheduling or job tool, invoices and payment status from your accounting package, documents from wherever you store them, and messages from your inbox or helpdesk.
  2. One shared record per client and job, so the right information appears for the right client, matched by ID rather than by name.
  3. Requests flow straight into your tools. A booking request creates the job in your system, and an uploaded document is filed against the right record, with no retyping.
  4. Notifications when something changes, so clients come to the portal instead of your inbox.
  5. Your brand, your rules. Your logo and domain, the permissions you need, and the steps that match how you actually work.
  6. Simple sign-in, such as a one-time email link, and screens that work properly on a phone.

Your team keeps working in the CRM, job tool and accounting package they already use. The portal is a window onto them for your clients.

How to decide

  • Clients mainly need support tickets and help articles: use the portal in your helpdesk or CRM.
  • You're a small service business willing to run everything in one product: an all-in-one portal product.
  • Your client data already lives in Airtable or a sheet, and it's up to date: a no-code portal builder.
  • Client information is spread across several tools, and you want one portal that's always right: a custom portal connected to those tools.
  • The portal is part of what you sell, like a property, logistics or staffing service where clients judge you on visibility: custom, so it fits your service exactly.

Before you build: list the questions clients ask

  1. Go through a month of client emails and calls. List every question, like "has it shipped?", "can you resend the invoice?" or "did you get my documents?"
  2. Count them. The most frequent five or six questions are your portal's first version.
  3. For each answer, note which system holds it today.
  4. Note what clients send you: documents, approvals, requests. Each should become a structured upload or form.
  5. Decide who at each client needs access, and what each person should see.

How we build client portals at Lephlo

Customer portals are one of the things we build for growing businesses. We connect them to the tools you already use, so status, documents and invoices are always current without anyone updating the portal. Requests from clients flow straight into your systems.

It starts with a free consultation. We scope the first version around your clients' most common questions, give you a fixed price, and build it in short steps you can try. You own the code, fixes are free during the fix period after launch, and we stay on hand as it grows.

Related reading: system integration for small businesses and internal tools: the apps you already use, and how to connect them. To size a first version, try the Build Scope Planner, or book a free consultation.

Frequently asked questions

What is a client portal? A secure website or app where your clients log in to see the status of their work, share documents, approve quotes, pay invoices and send requests, without emailing your team.

What is the difference between a client portal and a customer portal? In practice, nothing. "Client portal" is more common for service businesses like agencies, accountants and law firms, and "customer portal" for product and subscription businesses.

Is a client portal secure? It should be. Each client must only ever see their own data, permissions must be checked on every request rather than just hidden in the interface, and access should be logged. Ask any provider how they do this.

Can a portal connect to Xero, QuickBooks or our CRM? Yes. Most modern tools let other software read their data through an API, so a portal can show live invoices, payments and status from the systems you already use.

Will clients actually use it? They will if it's faster than emailing you. That means current information, simple sign-in, a good phone experience and notifications that bring them back.

Sources