CRM for New Zealand Accounting and Bookkeeping Firms

Ask a partner where last year's new clients came from and you will get names of people, not channels. That is the correct answer for this profession. What is missing is that the answer lives in three or four heads and has never been written down, which means it cannot be acted on.

Consider what a practice loses by not recording referral sources. It cannot tell which lawyer, banker or existing client is genuinely generating work rather than merely being friendly. It cannot tell whether a referral relationship that produced four clients three years ago has produced nothing since, which is exactly the moment to take somebody to lunch. It cannot tell whether the enquiries coming from one source convert at half the rate of another, which would change how much effort is worth putting in. And when a partner retires, the map of who sends work retires with them.

The fix is unglamorous: one field, filled in on every enquiry, naming the person or firm that sent it. Not a category like word of mouth, but a name. After twelve months that field is the single most valuable piece of business development data a practice owns, and it cost nobody more than ten seconds per enquiry to build.

The second unglamorous point is that referrals are not passive. A practice that reviews its referral list quarterly and deliberately re-contacts the relationships that have gone quiet will out-grow one that waits for the phone. But you cannot review a list you have not kept.

Most practices do have a process here. It is just not written down, so it varies by partner and it fails silently. Making it explicit costs a morning and stops the two most common leaks.

• Enquiry received. Name, source, service needed, rough size, and the partner or manager who will own it. Owned within a day, or it is nobody's.
• Scoping conversation held. The point at which you decide whether this is a client you want. Not every enquiry should progress, and recording the ones you declined is as useful as recording the ones you took.
• Proposal sent. With a date, an expected annual fee and a chase date set at the moment it goes out. This is leak number one.
• Engagement letter issued and signed. The formal boundary. Everything after this point belongs to your practice system.
• Onboarding complete. Information gathered, authorities in place, introductions made. This is leak number two, because a client who signed six weeks ago and has heard nothing since is already reconsidering.

The two leaks are worth naming plainly. A proposal that goes out on a Friday and is never chased is the most expensive document a practice produces, because all of the cost was incurred and none of the revenue was. And a new client who signs and then sits in silence during onboarding forms their entire opinion of your responsiveness in those weeks. Both are solved by the same mechanism: a dated task with a named owner, created automatically at the point the stage changes. The general pattern is covered on the sales and follow-up automation page, and the proposal side on the proposal and quoting software page.

These are different categories and the honest framing is that one sits in front of the other. Practice management software is built for the work you have been engaged to do, and it is good at it. A CRM is built for everything before the engagement and for the relationship that spans engagements. Written by HelloGrowthCRM, so weigh the last column accordingly.

If your practice already runs a good practice management system, nothing on this page is an argument to change it. The argument is that there is a stage of the client lifecycle sitting entirely outside it, currently being run out of a partner's inbox.

Most firms plan the busy season backwards. They wait to see what comes in, then scramble to resource it, then conclude in October that they took on too much or too little. The information needed to do it the other way round already exists, it is just not written down anywhere.

A pipeline with two extra fields becomes a forecast. Put expected annual fee and service type on each opportunity and you can answer questions in advance that firms usually answer in hindsight. How much new annual work is likely to land before the season starts. How much of it is compliance rather than advisory. Which partner has committed to the most new relationships relative to their capacity. Whether the pipeline supports the additional staff member you are considering, or whether it is one good month being extrapolated.

This does not require sophisticated forecasting. It requires that every live opportunity has a number and a probable month attached, which takes seconds to record when the opportunity is created and is nearly impossible to reconstruct later. Pipeline forecast views and real-time dashboards then do the arithmetic, and AI-assisted sales forecasting sharpens the view as history accumulates.

The second-order benefit is the harder conversation it makes possible: deciding not to take work. A practice that can see it is already at capacity in July can price accordingly or decline gracefully in April, which is a much better outcome than accepting the work and delivering it late.

Almost every practice has the same story. A manager notices during a year-end that a client is running a business decision on a spreadsheet and could genuinely use help. They mention it. The client says they will think about it. Nothing further happens, and eighteen months later the client mentions they have engaged a consultant.

Nothing went wrong there except that the observation was never recorded as an opportunity. It was a comment in a conversation, and comments in conversations do not survive a busy season.

Treat advisory as a pipeline in its own right, running over the same client records the compliance relationship uses. Each identified opportunity gets a stage, an owner and a next step with a date. That is the whole system, and it works because it makes the absence of progress visible. An advisory opportunity that has been at initial conversation for five months is a fact somebody can see and ask about, whereas the same opportunity in a manager's memory is simply gone.

Two practical notes. First, the identification should stay human. This is a professional judgement about a specific client, and it should not be triggered by a rule about turnover bands. Second, keep the stages short: identified, discussed, scoped, proposed, engaged. Long advisory pipelines with nine stages get abandoned by the second quarter. The mechanics of running a second pipeline over an existing base are much the same as any other, and the lead management page covers the routing and ownership side.

In most practices, ownership is real but undocumented. Everybody knows that a particular partner looks after a particular family group. It is simply never written down, which produces two distinct failures.

The everyday failure is the assumed handover. A manager moves to another team and the client quietly has nobody, because both the incoming and outgoing person believed the other was looking after it. The client discovers this when they ring with a question and get passed around.

The expensive failure is departure. When a manager with a decade of context leaves, what walks out is not the file. The file is in the practice system. What walks out is the context around the file: which family members are involved in the business, why the structure was set up the way it was, that the client hates phone calls and prefers email, the conversation about succession that has been circling for two years. Rebuilding that takes years, and the client feels every month of it.

A shared relationship record is the only defence. It means recording an owner and a backup on every client, keeping conversation notes on the client record rather than in a personal mailbox, logging calls against the record as a matter of course, and flagging the opportunities and sensitivities that a successor would need on day one. None of it is difficult. It just has to be normal, which means the partners have to do it too. There is more on structuring those records on the customer management software page.

One obligation to be deliberate about while you build this: New Zealand firms holding client personal information have duties under the Privacy Act 2020 covering how that information is collected, used, stored and disclosed, including Information Privacy Principle 12 on disclosing personal information overseas. Decide what belongs on a relationship record and what does not before the habit sets, rather than after.

HelloGrowthCRM covers the front end and the relationship layer. Enquiries land in one pipeline with a referral source and an owner. Proposals go out from the client record with a chase date attached automatically. Advisory opportunities run as a second pipeline over the same base. Custom fields, modules and pipeline stages let you model your own onboarding sequence rather than a generic one, and territory and team management makes partner and manager ownership explicit. Real-time dashboards and custom reports give you the pipeline by partner, by service and by source. Unlimited contacts and deals mean prospects who are not yet clients have a permanent home.

It is not a practice management system and does not try to be one. Job workflow, time recording, the client ledger and billing all stay where they are. What changes is that the stage before the engagement letter, and the relationship context that spans engagements, stop living in individual inboxes. Smaller firms weighing this up alongside general options can compare on the CRM for small business page.

On cost: a free plan is available with no credit card, the Growth plan is NZ$17/user/mo on annual billing or NZ$22/user/mo billed monthly, and paid plans include a 14-day free trial. There are no seat minimums, so a practice can start with the two partners doing business development rather than licensing everyone. Full details, plan comparison and GST treatment are on the New Zealand pricing page.