CRM systems · New Zealand
A CRM becomes useful when several people need the same customer history, responsibility is unclear or the next action keeps disappearing between inboxes, spreadsheets and memory. That does not automatically mean buying a large platform or commissioning custom software. We can help map one customer lifecycle, stabilise the current process, compare a configured platform or define a tailored workflow.
Follow one enquiry from first contact to completed work, then test whether your current tools need discipline, configuration or a tailored system.
SYNTHETIC EXAMPLE
ENQ-024The relationship thread stops here. A system can hold the record, but it cannot decide who owns the response.
This is a working method demonstration, not a deployed client system or measured result.
01 · Follow one enquiry
The relationship ledger
The useful record grows as people make decisions. Contact, organisation, enquiry, quote, job, activity and task have different meanings, owners and evidence. Select a stage to see what changes and where an unclear handoff interrupts the work.
A website enquiry has been accepted into the register. It still needs a named person and an agreed response point.
The form submission and the human response are separate states.
SYNTHETIC EXAMPLE02 · Choose a route
Proportion before platform
A more complex system is not automatically a better one. Compare the daily operating burden, the proof needed before commitment and the route out if the decision proves wrong.
Swipe to compare the full table
| Route | Good fit | Proof before commitment | Operating burden | Reason to stop |
|---|---|---|---|---|
| Keep the current process | One accountable user, low volume and a controlled record. | Open items remain findable, owned and recoverable. | Named file owner, backup and periodic review. | Copies diverge or the next action disappears. |
| Improve the spreadsheet | The workflow is understood but fields, lists or controls are weak. | One source can hold stable definitions and permissions remain simple. | Field rules, change control, backup and correction. | Several roles need different views, history or approvals. |
| Use a hybrid | A standard CRM owns relationships while analysis stays in a governed sheet. | Export and reconciliation can be repeated without losing identity. | Two owners, an agreed boundary and routine reconciliation. | People cannot tell which system owns a field. |
| Configure an established CRM | The lifecycle is common and supported configuration meets most needs. | Representative users complete real tasks in a sandbox. | Licences, administration, training and controlled changes. | Workarounds become the normal process. |
| Investigate a tailored workflow | The record relationships or operating interface are materially distinct. | A narrow prototype proves the boundary, owner and maintenance path. | Product ownership, testing, hosting, support and future changes. | A standard platform can meet the accepted requirement. |
Custom does not mean everything from scratch. A tailored interface can still rely on established identity, hosting, databases or services.
One department can go first. The pilot still needs an export path, ownership and an agreed boundary with the rest of the business.
Doing nothing can be responsible. Keep the current tool when the record is controlled and a new system would add more burden than value.
03 · Responsible record
Purpose before fields
Each field needs a purpose, source, appropriate audience, correction route and retention trigger. Free-text notes carry more privacy and interpretation risk than tidy fields, while an email address or phone number may not be a reliable unique identity.
Attached records belong only where their purpose and access can be explained. Uncertain duplicate candidates go to human review instead of destructive automatic merging.
Swipe to compare field responsibilities
Collect and retain only information the organisation can justify and operate responsibly. Privacy requirements depend on the client’s exact circumstances and need appropriate review; this page is general information, not legal advice.
04 · Roles and access
One record, different authority
Named identities, minimum necessary access, supported multi-factor authentication, role-change reviews and controlled emergency administration should be considered with the selected platform. An audit trail is not a backup.
Swipe to compare access by role
| Task | Staff user | Manager or approver | System owner | Person represented |
|---|---|---|---|---|
| View | Assigned and relevant | Approved team scope | Support scope only | Access request route |
| Create or correct | Create; request or make permitted correction | Review material changes | Support rule and audit | Request correction |
| Assign or approve | Request or accept assignment | Assign and approve within authority | Configure approved rule | Not applicable |
| Export | Restricted | Approved dataset | Controlled administrative export | Defined access process |
| Archive or delete | Request | Approve against policy | Execute with evidence | Defined request and response |
| Configure and audit | None | Approve business rule | Implement, log and review | Transparent notice where required |
05 · Spreadsheet fit test
A useful answer without a sales call
This diagnostic uses operating conditions, not a marketing score. “Unknown” is a valid answer. Nothing entered here is submitted or stored.
Describe classes and conditions only. Do not enter names, customer details, credentials or sensitive records.
06 · Follow-up
Human responsibility stays visible
One safe automation can create an internal reminder for an open, human-reviewed record with a named owner and an overdue next-action date. It should not silently send a customer message or treat a provider’s acceptance as customer receipt.
Basis and reviewer recorded.
A delivery attempt is authorised.
This is not proof of receipt.
Outcome and next action remain human-reviewed.
07 · Migration and adoption
Acceptance is more than import
An “import successful” message proves only that a tool accepted a file. Reconciliation, permissions, relationships, real user tasks, rollback and old-access retirement still need evidence.
Name every copy, owner and dependency.
Map meaning, source, destination and transformation.
Decide what should move, remain controlled or be removed under authority.
Hold uncertain matches for review.
Check relationships, permissions, attachments and error handling.
Compare counts, samples and exceptions.
Create, find, assign, correct, quote, hand over, close and export.
Name the decision point and recovery path.
08 · Connections
Clear ownership at every boundary
Every connection needs a source, destination, stable identifier, direction, permission, failure path, reconciliation owner and exit behaviour. A named product or integration is never assumed before platform access and supported interfaces are confirmed.
Persists an accepted enquiry and passes agreed fields. The CRM owns relationship and assignment.
Website systemsMoves or prompts a defined step. The CRM remains the context and exceptions retain an owner.
AutomationReads defined fields with freshness and limitations. It does not repair weak source data.
DashboardsReturns authorised job or site evidence. Technical and safety authority stays with competent people.
Field technologyShares approved identifiers or states only after direction, access and reconciliation are confirmed.
09 · Situations
The model follows the work
These are operating patterns, not one-size-fits-all industry packages. All content remains available without filtering.
Connect client, site, quote, job, callout, variation, field update and completion evidence without hiding the handover between commercial and delivery work.
Organise client request, site details, planning inputs, quote, booking, approved references, job records and closeout. Authorised people retain technical and safety authority.
Relate lead or tender, organisation, stakeholder roles, site context, quote revisions and the commercial-to-delivery handover without replacing programme, cost or document control.
Coordinate client demand, candidate record, stated availability and placement activity with sensitive access. The system does not make employment or suitability decisions.
Keep enquiry, appointment or job, responsible owner, follow-up and repeat relationship proportionate to the team and the decisions it actually makes.
10 · Cost and time
Drivers, not invented packages
The cheapest subscription can become expensive when nobody owns the system. A tailored build can be unnecessary when a standard platform fits. Scope and timing should be confirmed in writing after the operating model is understood.
11 · Before you commit
Procurement questions
The organisation should nominate the business process owner, tenant or account owner, system administrator, data stewards and support route. A supplier can provide an agreed service without becoming the invisible owner of business meaning or customer decisions.
Yes. A controlled spreadsheet may remain proportionate when one accountable person manages a low-volume, well-defined process and access, history, relationships and approvals remain simple.
Not by default. First compare process repair, spreadsheet improvement, an established configurable platform and a hybrid boundary. Tailored work should earn its place through a materially distinct requirement and a sustainable owner.
Start with the purpose for collecting each class of information, appropriate notice, minimum necessary fields, access, security, accuracy, correction, retention and disposal. The exact obligations require client-specific privacy review.
Confirm what the platform protects, what exports or attachments sit elsewhere, how often backups occur, who can restore them and whether restoration has been tested. Activity history or an audit log is not the same as a recoverable backup.
Reconcile source and destination counts, samples, relationships, permissions, held exceptions and rejected records. Then test representative staff tasks, cutover, rollback and old-access retirement.
Define the last accepted state, retry behaviour, duplicate prevention, warning route, responsible owner, reconciliation method and what users should do while the connection is unavailable.
Before commitment, confirm the export format, attachments, history, identifiers, permission to retrieve data, deletion process, notice period and the effort required to reconstruct relationships elsewhere.
12 · Evidence
Method shown honestly
The specimens on this page demonstrate analysis and interface method. They are not client results. Future work should remain clearly labelled as concept, prototype, configured sandbox, deployed, observed or measured.
Seven states, visible ownership, exceptions and record boundaries.
Open specimenA transparent diagnostic that can recommend keeping the current tool.
Run diagnosticTasks and authority separated across four perspectives.
Review matrixAccepted, held and rejected records remain traceable to the control total.
Review specimen13 · Smallest next action
Start with one real process
Prepare a plain-language workflow, current tool names, user roles, a blank or redacted field list, common exceptions and one report or decision the team needs. The review may conclude that a checklist, spreadsheet repair or established platform is preferable to custom work.
Do not send customer exports, credentials or sensitive records through the enquiry form.