Quick checklist
- How often does someone ask you to resend a quote or an invoice?
- How long does a quote sit unanswered because approving it is awkward?
- Can a customer find out where their job is up to without ringing you?
- If you were away for a week, could clients still get what they need?
- Are you emailing the same three documents over and over?
“Customer portal” sounds like enterprise software. In practice it is a much smaller idea: a place where your customers can see their own things without going through you.
Their quotes. Their jobs. Their invoices. What has been paid and what has not.
That is the whole concept. Whether it is worth building comes down to how often you are currently the bottleneck.
The thing it actually replaces
Not a system. A pattern of interruptions.
“Can you resend that invoice?” · “Did we approve that quote or not?” · “Where’s the job up to?” · “What was the price again?”
None of those take long individually. Together they are a running tax on the person who knows where everything is, and they arrive at the least convenient moments. Worse, they slow down the two things you actually want to happen fast: quotes getting accepted, and invoices getting paid.
A quote sitting in an inbox waiting for someone to print, sign and scan it is a quote losing momentum. A quote with an Accept button on it is a decision.
What it looks like when it works
A customer gets a link. They open it and see their quote, laid out properly, with an accept option. When they accept, it becomes a job on your side without anyone retyping anything. Later, the same customer can look up what has been invoiced and what they have paid.
The detail that matters most is the least impressive one: no password. Portals that require an account get used once. A secure link that goes straight to the thing they wanted is the difference between a portal and an unused login page — and it is the design decision we care most about, because it is the one everybody gets wrong.
We know because we run one. The portal in our own platform works exactly like this: token links, no logins to manage, expiring where it needs to.
When you genuinely don’t need one
If you have a dozen active customers and you know all their names, a portal is solving a problem you do not have. Email them the invoice. It is faster, and they will read it.
If your work is one visit and one payment, with no back-and-forth, a portal adds a step to a process that does not need one.
And if your quotes are already being accepted quickly, do not build a portal to fix quote acceptance. Find where the actual delay is first.
The point at which it starts paying is when the same handful of documents get requested repeatedly, or when the number of “where’s it up to” messages starts to be noticeable, or when a week of leave means a week of things going stale.
What it costs, roughly
A customer portal starts from $6,500, and the pricing page has the rest of our starting prices. What moves it is the same thing that moves any build: how much it has to talk to. A portal that reads quotes and invoices from a system you already have is much less work than one that needs the system building underneath it too.
If you are not sure which of those you are, that is a normal place to be, and it is precisely what a business systems review is for. It is free, and a fair number of them end with us saying you do not need this yet.
Bottom line
A portal is worth building when your customers keep asking you for things you have already sent them. Below that, it is a login page nobody uses.
Want a hand with this?
Tell us what you're trying to sort out and we'll give you practical, plain-English advice before you spend money.
