How much does a custom client portal cost?

It varies significantly based on complexity. A focused portal with document sharing, status tracking, and client login might cost NZD $5,000–$15,000 to build. More complex portals with integrations, workflows, and custom logic can run $20,000–$50,000+. The right question is whether the time savings and improved client experience justify the investment — for most service businesses processing 20+ active clients, it does.

Should I use an off-the-shelf portal or build a custom one?

Start with off-the-shelf if your workflow is fairly standard. Tools like HoneyBook, Practice Ignition, or industry-specific portals handle common service business workflows well. Go custom when your process is genuinely unique, when you need integration with specific systems (like a bespoke job management tool), or when the off-the-shelf tools require your clients to adapt to the software rather than the other way around.

What's the most common mistake businesses make with client portals?

Building too much at once. The temptation is to replicate every communication channel, document type, and workflow in the portal. This creates a complex tool that's hard to use and slow to build. The businesses that get the most value start with one specific pain point — usually document signing or status visibility — and expand from there once clients are actually using it.

Will my clients actually use it?

Adoption depends almost entirely on whether it's easier than what they're doing now. If your portal requires a login to see something they could get in a quick email, they'll skip it. Design for the client's convenience first. Clear login, mobile-friendly, fast to find what they need. Portals that solve a real frustration for the client (like not having to email you to check a status) get used. Portals that only help the business side get ignored.

Do You Need a Custom Client Portal? A Guide for NZ Service Businesses

A client portal can transform how you work with customers. But do you actually need one? Here's how to decide — and what it should include.

The phrase "client portal" gets thrown around a lot. For some businesses it's a game-changer. For others, it's an expensive project that clients never actually use. The difference usually comes down to whether you've built the right thing for the right reason — or whether you've built something that sounded impressive but didn't solve a real problem.

This article is for NZ service businesses thinking about whether a client portal makes sense for them. I'll walk through what a portal actually is, when it genuinely adds value, what it should include, and how to decide between building custom versus buying off-the-shelf.

What Is a Client Portal, Really?

A client portal is a secure, private area where your clients can log in and interact with you and your business. That's it. The specific features vary enormously depending on what your business does, but the core idea is consistent: instead of everything happening over email, phone, and scattered document attachments, there's one place for the client to go.

Common things a portal might include:

Document sharing and signing (proposals, contracts, reports)
Project or job status tracking ("your build is in the consenting phase")
Invoice viewing and payment
Messaging or communication threads
Form submission (onboarding questionnaires, intake forms)
Access to deliverables (photos, completed reports, files)
Booking or scheduling

Not every portal needs all of these. The best portals typically do a small number of things very well.

The Signs You Might Actually Need One

Before jumping to a solution, it's worth diagnosing the problem. Here are the specific signals I look for when talking to a service business about whether a portal is worth it:

You're answering the same questions repeatedly

"Where are we up to with my project?" "Has my contract been signed yet?" "Can you resend that invoice?" If you're fielding these questions more than a couple of times a week, a portal with real-time status visibility pays for itself quickly — both in your time and in the client experience.

Document handling is painful

Emailing PDFs back and forth, losing track of which version was signed, chasing clients for documents you need before you can start work — these are classic portal problems. A simple, secure document hub with e-signature capability eliminates most of this.

Onboarding new clients is slow

If getting a new client set up takes a lot of back-and-forth — collecting information, sending welcome material, getting forms filled in — a portal can compress this into a single, self-guided process. The client gets everything in one place; you get the information you need without individual follow-ups.

You have many active clients simultaneously

The more clients you're managing at once, the more the communication overhead multiplies. A portal that reduces per-client communication by even 30 minutes per month saves significant time at scale. For a business with 30 active clients, that's 15 hours a month.

You're in a trust-sensitive industry

Legal, financial planning, accounting, healthcare, mortgage broking — industries where sensitive personal information changes hands benefit significantly from a portal. It's more secure than email, easier to audit, and signals to clients that you take their privacy seriously. This matters more than ever under the NZ Privacy Act 2020.

When You Probably Don't Need One

Equally important: not every service business needs a portal. Here's when the investment likely isn't worth it:

You have a small number of long-term clients who already have easy communication with you and aren't asking for anything a portal would provide.
Your projects are short and simple. If a typical job is done in a day or two with one document exchange, the overhead of a portal exceeds the benefit.
Your clients are unlikely to use it. Some client bases — particularly older demographics or less tech-comfortable industries — genuinely prefer phone and email. Build for your actual clients, not your ideal ones.
An existing tool already solves it. If your accounting software, project management tool, or industry-specific platform already has decent client communication features, adding a separate portal creates fragmentation.

Off-the-Shelf vs Custom: The Honest Answer

This is the question I get asked most often, and I try to give an honest answer rather than a self-interested one.

Off-the-shelf tools to look at first:

Practice Ignition / Ignition: Popular with NZ accountants and professional services businesses. Great for proposals, engagement letters, and automated billing.
HoneyBook or Dubsado: Good for creative services, consultants, event businesses. Combines CRM, contracts, invoicing, and client communication.
BuilderTrend or CoConstruct: Built specifically for construction and renovation — project timelines, client communication, change orders.
Cliniko or Nookal: Healthcare and allied health practices in NZ use these widely — bookings, notes, client records.

If one of these fits your workflow, start there. The cost is predictable, you're not waiting for development, and they're maintained by people who specialise in your space.

When to go custom:

Custom is the right choice when your workflow is genuinely distinct and existing tools require you to compromise in ways that hurt the client experience or create manual workarounds. Specific triggers:

You need the portal to integrate with systems that don't have standard integrations (a bespoke internal system, an unusual data source, a legacy platform)
Your process has enough specific logic that off-the-shelf tools feel like wearing shoes on the wrong feet — technically it works but it's uncomfortable for everyone
You want the portal to reflect your brand completely — not just a logo swap, but a genuinely differentiated experience
The off-the-shelf per-seat or per-client pricing becomes more expensive than amortised custom development over two to three years

What Should Your Portal Actually Include?

If you've decided a custom portal makes sense, here's my practical advice on scope. Start with less than you think you need.

The most successful portals I've built for NZ businesses started with two or three core features, launched, got real client feedback, and iterated. The least successful were ambitious multi-feature builds that took six months before clients saw anything — and by the time it launched, half the assumptions were wrong.

A good first version for most service businesses includes:

Secure login — individual accounts per client, with proper authentication (not just a shared password)
Status/progress visibility — even a simple "your job is at Stage 3 of 5" is hugely valuable for reducing check-in emails
Document upload and access — both you uploading things for them, and them uploading things for you
Basic messaging — threaded, so there's a record and nothing gets lost in email

Invoicing integration (connecting to Xero), e-signature, and more advanced workflows can come in a second phase once you know the portal is being used.

The Client Adoption Problem

I want to address this directly, because it's where a lot of portals fail. You can build the most well-designed portal in New Zealand, and if clients don't use it, it's worthless.

Client adoption comes down to a few things:

Ease of first login. If it takes more than two minutes to get in the first time, you'll lose half your clients at the door. Password reset flows, magic link email logins, and Google sign-in all help here.
Immediate value. The portal needs to show the client something useful the moment they log in — not a blank dashboard.
You using it consistently. If you upload documents to the portal sometimes and email them other times, clients won't build the habit. Make the portal the default for everything it covers.
Mobile-friendly design. Many of your clients will access the portal on their phone. It needs to work well on a small screen, not just on a desktop.

The businesses I've seen get the best results from their portals treat it as a cultural change, not just a software rollout. They update their onboarding emails, their email signatures, their intake process — the portal becomes part of how they work, not an add-on that clients can ignore.

A Realistic Expectation on Cost

Custom portal development in New Zealand typically starts around NZD $5,000–$8,000 for a focused, well-scoped first version. More complex portals with integrations, custom workflows, and polished design run $15,000–$40,000. Ongoing hosting and maintenance is usually $1,000– $3,000 per year depending on scale.

Whether that's worth it depends entirely on your numbers. If a portal saves you and your team five hours a week, and that time is worth $100/hr, that's $26,000 in recovered time per year. The maths usually works — but only if the portal actually gets used.

The question to ask before building anything: "What is the specific problem this portal solves, and how much is that problem costing me right now?" If you can't answer that clearly, you're not ready to build yet.