The first automations to set up in a small business
Five automations worth setting up first, and where a person checks each one.
A shared spreadsheet is a fine first home for enquiries. This guide says when it stops being enough, what to move into a CRM first and what decides the cost for a small team.
Updated 29 October 2026, about 9 minutes to read
The short answer
You need a CRM when the spreadsheet no longer shows who owns each enquiry and when it is next followed up: enquiries fall between people, two of you call the same lead, or quotes go quiet with no next date. One person with a few enquiries a week rarely needs one. If your booking or job software already keeps customer records, use those first.
A spreadsheet is a list. A CRM, customer relationship management software, is a list that also remembers: who each person is, every call and email, who on your team owns them and what happens next, with a reminder when the next step is due. The question is whether your business needs that memory.
Stay with a spreadsheet while one or two people handle enquiries, everyone can see the whole list at a glance and nothing waits more than a day without someone noticing. Move to a CRM when follow-ups start to depend on someone's memory, because that is the part a spreadsheet cannot do for you.
The first automations to set up recommends a spreadsheet as the first home for enquiries, and it still is. This guide is about the point where you outgrow it. Before you buy anything, look at the software you already use: many trades and clinics have a CRM without calling it one.
If two or more of these sound familiar, it is time to look at a CRM:
Size alone is not a sign. A spreadsheet with two thousand rows works if one person owns it and the follow-ups are kept. A sheet with forty rows fails if three people work it and nobody owns a row.
Many businesses already pay for a tool that keeps customer records, sends reminders and shows what is due. Use it fully before you add another one:
If most of your customers already have a record in one of these, a separate CRM means two places to update and two versions of the truth. Ask instead what is missing, such as enquiries that never became jobs, and whether the tool you have can hold them.
A separate CRM earns its place when the selling happens before the booking or the job: quotes, proposals, site visits and calls that go on for weeks, as they do for builders, agencies, consultants and firms that sell to other businesses.
If only one of the signs applies, a better spreadsheet may be enough. A shared Google Sheet, or an Excel file in Microsoft 365, works when it follows a few rules:
Then look at it at the same time every day. A spreadsheet with a daily five-minute check beats a CRM nobody opens.
A bathroom fitting firm in home services has three people: the owner, who visits and quotes, a fitter, and an office manager who answers the phone. Enquiries arrive from the website form, phone calls and Facebook messages.
Before, the office manager added each enquiry to a shared sheet, and the owner kept his visit notes on his phone. In one week a customer was called twice by different people, a quote went unanswered for three weeks because nobody owned the follow-up, and nobody could say which enquiries came from the new Google Ads campaign.
After, each enquiry is a record in a CRM with five stages: new, visit booked, quote sent, won and lost. The website form creates the record with its source attached. The office manager books the visit, and the record moves to the owner, who adds his notes and photos from his phone after the visit, sends the quote and sets a follow-up date. If the date passes with no answer, the CRM reminds him, and the office manager can see it too. Each lost job gets a reason, such as price or timing.
On Monday the three of them look at one screen: what came in, what is waiting and why jobs were lost. The old spreadsheet stays, read-only, for the history. Saving the campaign with each enquiry is covered in how to track leads from Google Ads.
CRMs publish their prices, so compare the plans yourself. These are what decide the bill for a team of three:
Price the CRM for a year at the number of users you expect next year. Then work out what one extra won job is worth to you, and how many quotes went quiet last year. If the CRM saves a few of them, you can see whether it covers itself. If you want the website form and your other tools connected to it, our own prices for that are on the prices page.
Try two or three with your own real enquiries rather than the demo data. Check that each one:
Pick the simplest one that passes. A CRM with more features than your team uses is harder to keep tidy, and an untidy CRM is a spreadsheet that costs more.
Do not move the whole history on day one. Move what someone has to act on:
Leave closed and old rows in the spreadsheet, set to read-only, and bring them across later if you need them. Before the import, clean the rows you are moving: remove duplicates, put phone numbers in one format, split full names if the CRM wants first and last names, and give every row an owner and a stage.
Running the spreadsheet and the CRM side by side for long means updating both, and soon neither is right. Plan a clean switch:
If someone keeps going back to the spreadsheet, ask what is missing: a field, a view or an easier way to add notes on a phone. Each of those can be fixed.
A CRM gathers personal details in one place, which makes them easier to look after than a spreadsheet copied to laptops. Keep it that way:
What you may store, for how long and on what basis depends on where you and your customers are. Ask whoever advises you on data protection before you import anything.
A CRM pays off most when nobody types into it what another tool already knows. Once the team uses it every day, connect it:
Each connection depends on what both tools' APIs allow, so check before you plan around one. Enquiry follow-up shows the first two in detail, and Zapier, Make or n8n compares the platforms that connect them. We connect forms, inboxes and CRMs where their APIs allow, with an alert when a connection fails: see automation.
A spreadsheet stores a list. A CRM keeps one record per customer with every call, email and visit, an owner, a stage and a next step, and reminds the owner when that step is due. It also controls who can see and change what, which a shared spreadsheet does badly.
Yes, for a while. One shared sheet with a row per enquiry, dropdowns for the owner and stage, a next action date and a filtered view per person covers a small team. It stops working when follow-ups depend on memory, several people work the same rows or customer history lives in inboxes.
There is no single best one. HubSpot's free CRM covers up to two users and 1,000 contacts, and Zoho CRM's free edition covers three users, with limits that change. Try the free plans with your real enquiries, and check what you would pay once automation or another user comes in.
Often not. If you handle every enquiry yourself and get a few a week, a spreadsheet with a next action date and a daily look does the job. A CRM becomes worth it when follow-ups slip, when you hire, or when sales take weeks of calls and quotes before a job.
Often, yes. Booking and job software usually keeps client records, history and notes, and sends reminders. Use it fully first. A separate CRM is worth adding when the selling happens before the booking, such as quotes and proposals that take weeks, and your booking software has nowhere to keep them.
The business. Set it up on a business email address, give at least two people admin rights and keep the billing in the business's name. When the person who set it up leaves, the customer records, history and connections should stay exactly where they are.