Xcelerate
Menu
Get in touch
All articles on crm and business growth

CRM and business growth

Designing a CRM for a New Zealand service business

Map customers, sites and decision makers before you buy a CRM. Use a sample maintenance contract to test whether the system fits a growing NZ service business.

A service team reviews a customer record and property map on screen.
AI-generated editorial image.

The most revealing question in a CRM workshop is often “Who is the customer?” For a maintenance firm, the caller might be a tenant, the person who admits the technician a caretaker, and the organisation paying the invoice a property manager. A contact list can hold all three names. A useful customer relationship management system tells the dispatcher whom to ring when the gate is locked.

What does one customer record represent?

Sketch a small Wellington maintenance contract on paper. Give the property manager an account, each building a site, and each person a contact. Attach a role to the relationship. Someone can approve work at one site and hold a key at another. A single “main contact” field loses that distinction the moment you take on the second building.

Write a question next to each field. Dispatch needs an arrival contact. Accounts wants the billing organisation and purchase reference. A salesperson wants the renewal date. If nobody can explain when they use a field, leave it out of the first version. The Privacy Commissioner’s guidance on collection gives the team a useful starting point for deciding which personal details belong on the form.

Where does an NZBN lookup help?

The New Zealand Business Number service says its API can prefill business details such as a legal name. Use the result as a suggestion when staff open a business account. Show the selected organisation to the coordinator before saving, and keep the trading name the customer uses on the phone searchable in its own field.

An NZBN lookup cannot tell the technician where to park, who has authority to approve a variation or whether the school office closes early on Friday. Give operational details a named owner and a review point. When a caretaker leaves, staff should be able to retire the contact at that building while preserving the history of completed jobs.

Keep the register check separate from your own updates. A customer may ask for invoices to go to a different address from the one on a public register. Show the source beside each address and allow accounts to keep an agreed billing instruction when the public details change.

How should a supplier prove the design?

Give each supplier the same invented job. A caretaker reports a leak, the property manager approves a callout and a tenant requests a different arrival time. Ask a dispatcher to find the site from its street address and record the change. Then ask accounts to identify who pays without opening the tenant’s private correspondence.

Change the billing organisation for future work halfway through the demonstration. Open a previous job and confirm that its original billing party is still identifiable. Search under the old trading name, export the contact relationships and look for duplicate organisations. A successful demonstration leaves your staff with a sample record they can explain and a list of decisions to settle before connecting finance or importing real customers.

Sources and further reading