CRM or spreadsheet? Start with the follow-up.

When a spreadsheet can still fit

A spreadsheet can be a useful starting point when the work is straightforward and the people using it can keep it current. The important test is whether you can answer practical customer questions from the record, rather than relying on memory or searching through messages.

Before replacing it, check whether clearer fields and a regular review would solve the immediate problem. A new tool will not decide who owns an enquiry unless your team agrees on that responsibility.

• Customer or business name and contact details.
• Enquiry date and service requested.
• Current status, such as new, awaiting information or closed.
• One person responsible for the next action.
• Next action and its due date.
• A short record of the latest customer contact.

Signs to assess a CRM

A CRM, or customer relationship management system, is worth evaluating when your team needs a more consistent way to share customer records and manage the work attached to them. Capabilities differ, so test the actual product and account plan rather than assuming a feature exists.

Look at the failure points in your process. More enquiries alone do not prove that you need a new system; repeated uncertainty about ownership, status or follow-up gives you something specific to assess.

• Two people respond to the same enquiry without seeing each other's work.
• A customer's latest response is difficult to find.
• Follow-up is missed because a due date is not reviewed.
• A staff change leaves customer context behind in one person's inbox.
• Your team repeatedly copies the same details into different tools.

Try the same enquiries in both approaches

Choose a small, representative set of records you are allowed to use. If you are testing an unfamiliar service, use fictional or anonymized details until access and data handling have been checked.

The following scenarios are illustrative planning examples, not 1120 client results. Try a new quote request, a customer waiting to provide information, a repeat customer and an enquiry that has been closed.

For each scenario, compare how easily someone can find the current status, identify the owner, record a reply and see the next action. Test changing the owner and closing the record too. A system is easier to assess when you use the actual work rather than a generic demonstration.

• Can a colleague understand the record without asking its original owner?
• Can you see which actions need attention today?
• Can you distinguish a new enquiry from an existing customer's request?
• Can you correct a duplicate without losing useful history?
• Can you retrieve or export the information you need when leaving the tool?

Improve the process before automating it

Write down the trigger, action and exception for any proposed automation. For example: a new enquiry arrives, it is assigned for review, and an incomplete submission is held for a person to check.

A follow-up rule should also say when to stop. A customer reply, a closed enquiry or an agreed appointment may change what needs to happen next. Confirm that the chosen tools can detect the relevant event before promising an automatic response.

Keep human review where judgement is needed. Automation should support a defined process; it should not silently decide a quote, customer commitment or unusual request.

Move a bounded part of the work first

If a CRM passes the trial, define a limited first stage rather than moving every historical record at once. Agree which records are included, how fields map, who can access them and how corrections will be handled.

Check the import result for missing fields, duplicate records and incorrectly assigned actions. Keep a recoverable copy of the source information, and agree which system becomes the working record after the switch. Avoid maintaining two conflicting live versions.

The relevant account plan, access controls, integration options and ongoing costs need assessment. This guide does not recommend a vendor or quote a subscription price.

Measure the work, not the number of features

Choose a few practical checks before the trial. For example, can your team find overdue actions, understand a colleague's customer record and complete a handoff without re-entering information?

Compare those checks against your starting process. Record unresolved problems as well as improvements. This is a way to evaluate your own workflow, not a forecast of time savings or revenue.

• Choose a clearer spreadsheet process if it resolves the problem.
• Assess a CRM if shared records and follow-up remain difficult.
• Consider a specific integration if the repeated handoff is between existing tools.
• Discuss custom software only when the requirements justify it.

Discuss the enquiry workflow with 1120

1120's published capabilities include lead and CRM automation, business websites, booking and email workflows, customer portals and custom business software.

Bring one typical enquiry, one difficult handoff and the names of your existing tools to a project discussion. That gives the assessment a concrete starting point. Specific integrations and deliverables need to be checked before they are committed.

Start with your business process.

Describe how customers reach you and what your team needs to do next.

Explore 1120 capabilities