Do you actually need a customer portal, or will email keep working?

"Can you resend that invoice?" "Where are we up to?" "What did we agree to again?" If you answer some version of those questions by email most days, the question is not whether a customer portal would help. It obviously would. The real question is whether it is worth building one yet, or whether email and a shared spreadsheet still have a year or two left in them.

The signs you have actually outgrown email

A portal is worth it when the pain is structural, not occasional. These are the signs worth checking against your own week:

• The same three questions arrive on repeat, from different clients, about things they could see themselves if there were somewhere to look: job status, the next milestone, an invoice total, a document you already sent.
• Documents get resent because they get lost. Someone asks for "that contract from March" and it takes ten minutes to find in an inbox, if it is found at all.
• Approvals happen in reply-all threads with no clear record of who agreed to what, and when a dispute comes up nobody can point to the exact message.
• A bigger client has started asking if you have a portal, because the last supplier they used had one. That is a competitive signal as much as an efficiency one.
• More than one staff member is answering the same kind of client email, which means the knowledge of "what to tell this client" is trapped in people rather than in a system.

If none of that sounds like your week, a portal is a solution looking for a problem. Plenty of small operations run cleanly on email, a shared drive and a good filing habit, and there is no prize for automating something that is not actually costing you anything.

What a portal replaces, specifically

A customer portal is not "a website with a login." It is a small, focused application that gives each client their own view of exactly what they need, and nothing else:

• Status, in plain language rather than internal jargon: what stage a job, order, project or case is at right now.
• Documents and invoices in one place per client, so nobody is searching an inbox for "that contract from March."
• Approvals and sign-offs, recorded with a name and a timestamp, so there is a record when a dispute comes up.
• Payment, so an open invoice can be settled from inside the same login rather than a separate email with a link.
• A place for the client to send things back, such as a form, a photo or a document, that lands in your system rather than a shared inbox.

The test we use when scoping one: if a feature does not remove an email that currently gets sent, it probably does not belong in the first version.

What it costs, and what moves the price

A customer portal typically costs $2,500 to $7,500 to build, in AUD excluding GST, with hosting, storage and support from $69 a month. Those are the ranges on our customer portals service page; your figure may differ depending on scope, and you get a fixed price in writing before anything is built.

What moves the number within that range:

1. How many things a client can see. A single status page is cheap. Status, documents, invoices, approvals and messaging together is a bigger build.
2. What it has to connect to. Pulling job status from a system you already use, invoices from Xero, or documents from a shared drive takes longer than a portal that stands alone, but it also means no double entry, which is usually the point.
3. Whether clients can pay from inside it. A payment gateway connection adds scope but often pays for itself quickly if it shortens how long invoices sit open.
4. How many roles exist. A portal with one type of client login is simpler than one that also has a staff view, an admin view and maybe a referral-partner view.

We built two portal-style applications for a business advisory firm, VentureGuard Global, that turned their assessment process into something clients could work through and get a report from themselves. You can read about it in our VentureGuard Global case study.

When email is still the right call

Skip a portal, at least for now, if:

• You have a handful of repeat clients and the "resend that invoice" emails number one or two a month, not one or two a day.
• Your process changes every few months. A portal is worth building around a process that has settled down; if you are still figuring out how you work, a spreadsheet is easier to change than software.
• The bottleneck is not information, it's decisions. If clients are not confused about status but are waiting on you to make a call, no amount of self-serve login fixes that.

A lighter first step is often enough: a customer invoice and statement generator that sends a clean, branded statement automatically, or a job booking and workflow tracker that at least gives your own staff one place to see status, even before clients get a login. Both are smaller builds, and either one can be the first module of a fuller portal later if the case for it grows.

How to check before committing

Track, for one real week, every email that starts with a client asking something they should be able to see themselves. Multiply the minutes each one takes by how often it happens. If that number is a meaningful chunk of a working day, a portal usually pays for itself inside a few months. If it is not, keep the spreadsheet. A portal you don't need is just another thing to maintain.

If the numbers do add up, tell us what your clients keep asking you and we'll scope a portal around exactly that, with a working prototype to click through before you pay anything.