On this page
A spreadsheet can be a sensible customer register. A CRM becomes worth considering when people need a dependable way to coordinate relationships and next actions. The decision is less about the number of rows than the work happening around them.
Before purchasing software, find the actual failure: a missed follow-up, conflicting records, an unclear owner, or information visible to the wrong people. If nobody consistently records the next action, changing the tool alone will not establish that habit.
Decision at a glance
Compare the work, not the feature list
| Your situation | Starting point | What to verify |
|---|---|---|
| One owner, simple stages, reliable updates | Improve the spreadsheet | Every active record has a next action |
| Handoffs repeatedly lose context | Trial a CRM workflow | The next owner can act without asking around |
| Different people need different visibility | Assess access controls | Allowed and denied actions match your rules |
| Duplicates and inconsistent stages dominate | Clean the process and data first | Fields and ownership have agreed definitions |
Scroll horizontally to see the full comparison.
Map one relationship from enquiry to handoff
Follow a representative enquiry through qualification, follow-up, agreement, and delivery handoff. Write who owns each step, what information they require, and where it currently lives. Distinguish a missing software capability from a missing rule. “Someone should follow up” needs an owner and a date regardless of the system.
Give the spreadsheet a fair test
Standardise the existing register before migrating it. Use one agreed working file, a clear definition of each stage, and a routine for reviewing overdue actions. Keep only fields someone uses to make a decision. A carefully maintained simple register may be all your business needs today.
- Give each record a stable identifier and named owner.
- Record the current stage, last contact, next action, and due date.
- Agree how to identify and resolve duplicate entries.
- Identify who maintains the fields and handles departures from the team.
Test a handoff before selecting a platform
Hypothetical example, not a client project: two colleagues share an enquiry register, but the follow-up context remains in separate inboxes. Give a colleague an active record and ask them to identify the latest commitment and next step. If they cannot, trial a shared activity record and task assignment. If one additional column and a working routine solve it, postpone the CRM purchase.
Test access with real roles
Write down who may see, edit, export, and delete information. Google explicitly warns that protecting a Sheets range is not a security measure; protected spreadsheets can still be copied. Do not treat hidden tabs as confidentiality controls. For any proposed CRM, test your required permissions in the relevant product plan using representative accounts. A label such as “role-based access” is not an acceptance test.
Buy the missing capability in a small first scope
If missed tasks, difficult handoffs, or access requirements persist, start with the enquiry workflow. Define essential fields, stages, ownership, tasks, and a useful view of outstanding work. Import a cleaned sample and rehearse an export before moving all records. Compare an existing CRM with configuration against custom development; choose custom work only when the required workflow justifies its maintenance.
Bring a process brief to the conversation
Prepare an anonymised sample, your stage definitions, access rules, failure examples, and the person responsible for adoption. Agree how to test a handoff, an overdue task, and a data export. Chronicle quotes scoped projects in USD; clarify software subscriptions and ongoing support separately. If the baseline works reliably, continue using it and revisit the decision when an identified need changes.
Before you commit
Your decision checklist
- Fix unclear ownership before buying a system.
- Test a real handoff and an overdue action.
- Verify permissions in the plan you would use.
- Keep migration, adoption, and export in the first scope.
Sources and further reading
The next step
Customer management (CRM)
If this is the right direction for your business, start with a clear scope, testing plan, and handover.