What to Include in a Client Portal: Essential Features for NZ Service Businesses

A client portal is one of those tools that sounds great in theory — a single place where clients can find everything, communicate with you, see their project status, and sign documents without a single email. In practice, a lot of portals get built, launched with enthusiasm, and then quietly ignored because the features nobody actually wanted outnumber the features people actually needed.

I've built portals for NZ financial advisors, accountants, mortgage brokers, lawyers, and consultants. Here's what I've learned about which features earn their place and which ones look great in a proposal but collect dust in production.

The Features That Actually Get Used

1. Secure Document Sharing

This is the single most-used feature in almost every portal I've built. The ability to upload a file and have your client access it securely — without emailing a PDF that could end up forwarded, printed, or sitting in their inbox forever — is genuinely valuable.

For accountants and financial advisors in New Zealand, this isn't just convenient. The Privacy Act 2020 requires you to take reasonable steps to protect personal information. Emailing tax returns, financial statements, or investment reports as unencrypted attachments is a real risk. A portal with proper access controls and encrypted storage removes that risk entirely.

Good document sharing in a portal means: clients can only see their own documents (not anyone else's), files are versioned so the latest signed contract replaces the draft automatically, and there's a record of when a document was uploaded and when it was viewed. That last part matters more than people expect — "I never received that" stops being a conversation when you can see exactly when they opened it.

2. Project or Job Status Visibility

The number one reason clients send "just checking in, how's it going?" emails is that they don't know how it's going. A simple status view — even just a progress tracker with a few stages like "In Progress", "Waiting on You", "Under Review", "Complete" — cuts those emails dramatically.

For mortgage brokers, this might be the stages of an application: pre-approval submitted, bank assessment underway, approval received, settlement booked. For a consultant running a project, it might be milestones with completion dates. The specifics depend on your business, but the principle is the same: clients who can see where things are don't need to ask.

This feature does require you to actually keep statuses updated. The portals that work best are the ones where status updates are built into your existing workflow — not an extra thing you have to remember to do separately.

3. Invoice and Payment Status (Linked to Xero)

"I just sent the invoice — let me know if you have any questions" is a sentence most NZ service businesses say dozens of times a month. A portal with invoice visibility removes the need for it entirely.

When a portal connects to Xero via their API, it can pull the invoice status automatically. Clients log in and see: outstanding invoices, their amounts, due dates, and whether payment has been received. No resending invoices. No "did you get my invoice?" No chasing via email and then apologising for chasing. The client just knows.

This integration is one of the most popular things I add to custom portals for NZ businesses, because Xero is so widely used here. It's not complicated to build, and the time it saves on accounts receivable admin every week adds up fast.

4. Messaging and Communication Log

Every portal needs some way for clients to contact you and for you to respond — and for both sides to have a record of what was said. This is different from email in one important way: all the messages live inside the context of the project or engagement, not scattered across inboxes.

A mortgage broker fielding questions from 40 active clients across an email inbox is constantly searching for context. Which client asked about the rate? Which one sent that document last Tuesday? A portal message thread attached to each client's record means the context is always there.

The most common implementation is a simple message thread per client, with email notifications when a new message arrives so neither party has to keep logging in to check. This gives you the structure of a portal with the immediacy of email — best of both.

5. E-Signature

If you send engagement letters, service agreements, authority forms, or any other documents that need a client signature, having e-signature built into the portal is significantly better than using a separate tool.

The reason is simple: the signed document lives right next to the project. You don't need to track whether the DocuSign went out, whether they clicked the link, whether you saved the signed copy back into the right folder. It happens inside the portal, and the signed version is automatically stored in the client's document area.

For lawyers, financial advisors, and accountants in New Zealand, this also creates a clear audit trail — who signed, when, from what IP address — which has genuine legal and compliance value.

6. Onboarding Checklists for New Clients

The beginning of any client engagement is where most of the friction lives. "Can you send me a copy of your ID?", "I need your last two payslips", "Please fill out this information form" — these requests go back and forth over days or weeks, usually over email, with things getting missed and resent.

An onboarding checklist in the portal solves this. When a new client is created, a checklist appears on their dashboard: upload these documents, complete this form, sign this agreement. They can see what's done and what's outstanding. You can see it too, from your admin view. The back-and-forth collapses into a single structured process.

This is especially powerful for accountants starting with a new client (AML/KYC requirements, authority to act, prior year returns) and mortgage brokers collecting supporting documents for an application.

Features That Sound Good But Often Get Ignored

I believe in being honest about this, because building features nobody uses is a waste of your money and mine.

Complex Gantt-Style Project Timelines

Clients open these once at the start of a project, think "oh that looks professional", and never open them again. The time it takes to maintain a detailed project timeline view is rarely worth it for service businesses. A simple status indicator ("In Progress / Waiting / Done") is used far more than a full timeline.

Built-In Chat Features

Most clients are already using email, Teams, or Slack. Adding a real-time chat inside the portal creates another channel to monitor, and in practice one of them gets ignored. Usually it's the portal chat. A simple message thread that sends email notifications works better because it doesn't require clients to change their habits.

Self-Service Knowledge Bases (If You Won't Maintain Them)

A knowledge base — a library of FAQs, guides, and how-tos — sounds great and can be genuinely useful if it's kept current. But a stale knowledge base where the most recent article is from two years ago actively damages trust. Build it with the questions you answer on every onboarding call, commit to keeping it updated, and it earns its place. Otherwise, skip it.

Appointment Booking

This one's borderline. If you're a consultant or advisor who spends significant time booking and rescheduling meetings, appointment booking inside the portal is useful. But if most of your client relationships are ongoing (not appointment-based), it's rarely used. Consider whether you'd use it before building it.

How to Decide What Your Portal Needs

The best way to work out what to include is to map your current client communication and find the friction points. What do clients ask you most often? What do you have to chase them for repeatedly? What processes currently happen over email that involve documents, signatures, or status updates?

Those friction points are your portal feature list. Start with the top three or four. Build them well. Launch. Add more based on what clients actually ask for — not what seemed like a good idea upfront.

I've seen portals launched with 20 features that get used less than portals with 5, because the 5 were exactly the right ones. More is not better. Relevant is better.

A Note on NZ-Specific Considerations

If you're a financial advisor, mortgage broker, or accountant in New Zealand, your portal needs to account for some specific compliance requirements. The Privacy Act 2020 means any personal information stored in the portal needs proper access controls, encryption, and a clear data retention policy. The FMA and IRD have their own expectations around how financial and tax-related documents are handled and stored.

This is one of the reasons I'm cautious about recommending off-the-shelf portal tools to NZ financial professionals. Many of the popular options are built for US or Australian compliance standards, and the data residency question — where is the data actually stored? — often has an uncomfortable answer. A custom-built portal can be hosted on NZ or Australian infrastructure with data governance that meets your specific obligations.

Where to Start

If you're thinking about building a client portal, start with a list of the five things you do most repeatedly with clients: the requests you make, the documents you share, the questions you answer, the updates you give. That list is your MVP feature set. Build those, and build them well, before anything else.

A portal that does five things perfectly is worth ten times as much as one that does twenty things poorly. The goal is to make your clients' lives easier — and yours. If a feature doesn't do that, it doesn't belong in the portal yet.

If you'd like to talk through what a portal for your specific business might look like, I'm happy to have that conversation. No obligation — I'm just genuinely interested in the problem, and most of those conversations end up being useful regardless of whether we work together.