Signs you've outgrown spreadsheets for customers and jobs

Keep the spreadsheet if the people using it can find the right record, update it reliably and see what needs doing next. A simple customer list or occasional job tracker does not justify a software build just because the business is growing.

Having several users is not, by itself, a reason to replace Excel. Supported versions can edit the same workbook through OneDrive or SharePoint Online. Microsoft also provides version history. One shared file can solve the confusion caused by emailing different copies, provided everyone uses a supported setup.

A busy sheet becomes a warning when it needs repeated repairs, leaves important work to memory or makes staff keep separate records elsewhere. You need to fix those problems, but the answer may still be a better spreadsheet.

Write down what actually goes wrong over a normal working week. Record the task, who was affected and the time spent putting it right. A long list of columns matters less than a missed booking or a customer getting two different answers.

• Staff copy the same customer details into the job sheet, calendar, quote and invoice, then have to correct each copy separately.
• Nobody can quickly tell which jobs are waiting for a quote, customer approval, materials or payment.
• Two versions disagree about an appointment, address or job status. Finding the right one means checking messages or asking the owner.
• One customer has several sites or repeat jobs, but their history is scattered across rows and separate tabs.
• Only one person understands the formulas or remembers what the colours mean. Their absence delays ordinary work.
• A worker needs the address and job instructions on a phone, but opening the sheet also gives them access to unrelated customer or financial information.
• Reports take manual counting and reformatting, so decisions use figures that are already out of date.

Choose a typical job and follow it from first enquiry to completion and payment. List where each detail is entered, who changes it and what tells the next person to act. Include email, paper, calendars and messaging apps, not just the spreadsheet.

Then try a less tidy case, such as a returning customer, a rescheduled visit or work that needs approval before it continues. These are the cases a new system must handle. Buying software before you understand them can leave the same workarounds in a different place.

A CRM, short for customer relationship management system, keeps customer records and their interactions together. A sales CRM may track enquiries and quotes well without handling staff scheduling, stock or completed-job evidence. Name the tasks you need rather than assuming anything labelled CRM will cover them.

For a fictional repair business, a customer can have several properties and each property can have several visits. The useful structure is a customer record linked to properties and visits, with a history for each. Repeating the customer's contact details on every visit row makes corrections harder.

Count time spent finding information, entering it twice, checking for mistakes and preparing reports. Separate that from useful work you would still do in any system, such as discussing a customer's requirements.

Use a realistic internal hourly cost to value that time. It is a way to compare options, not a promise of cash savings. If the same staff remain employed, saving admin time may mean more capacity rather than a smaller wage bill.

Record actual corrections and missed work separately. Do not invent a lost-sale value for every mistake or assume a new system will remove all administration. Compare the problems it would genuinely solve with its setup and ongoing costs.

Suppose duplicate entry takes 15 minutes a day, on five working days a week. That is 1.25 hours a week. At an assumed internal cost of £24 an hour, over 48 working weeks, it represents £1,440 a year of staff time. Replace those assumptions with your measured time and your own cost.

If inconsistent entries and duplicate copies explain most of the trouble, tidy the current setup before shopping for a replacement. These improvements also make your data easier to move later.

If those changes solve the problem, keep using the sheet. If the team still needs separate records and repeated copying to do ordinary work, you have a stronger reason to replace it.

• Choose one shared master file and stop circulating editable copies. Agree who maintains its structure and what staff are allowed to change.
• Give customers and jobs stable reference numbers. Keep names, dates, phone numbers and status in separate columns, with one record per row.
• Use a short agreed list of job statuses, with a dropdown where the spreadsheet supports it. In Google Sheets, data validation can reject entries outside the list instead of allowing several spellings of the same status.
• Record the responsible person and next action date. Do not rely on a cell colour as the only record of what happens next.
• Check duplicate customers and missing dates before repairing formulas. Keep the original data available securely until you have checked the result.
• Test whether someone other than the usual owner can find an open job and update it without help.

Google says protected sheets and ranges are not a security measure. People can still copy or export the data, and editors can unhide hidden sheets. Use protection to prevent accidental edits, not to conceal financial or personal details from someone who can open the file.

Review who has access, including former staff and external helpers. Use individual accounts and multi-factor authentication where available, which asks for another check as well as a password. Avoid public sharing links for customer records. If different staff need different information, give them access only to the records they need.

The ICO says personal data needs security measures appropriate to its risks, including suitable access controls and the ability to restore availability. Confirm how records are backed up and test recovery. A spreadsheet, a subscription CRM and a custom system all need this work. Buying software does not make your data handling compliant on its own.

Try a ready-made CRM if you mainly need shared contacts, enquiry stages, follow-up reminders and a clear history. If appointments or field visits dominate the day, test booking or trade job-management software too. A specialist tool may already handle the work better than a general sales CRM.

A custom system becomes worth considering when your important records do not fit the standard structure, several tools need to exchange information, or permissions and approvals reflect how your team actually works. It can connect the enquiry, customer, site and job rather than asking staff to rebuild that connection every day.

Ask a supplier to demonstrate your awkward cases, not just a clean sample customer. If a ready-made tool handles them with sensible configuration, it may be the better buy. If the demonstration depends on extra sheets, manual copying and several paid add-ons, price a custom alternative against that whole arrangement.

Start a custom build with the part that causes the most repeated work. You do not have to replace working accounting or booking software. Agree what connects to it, what the first version must do and who supports it afterwards.

Use fictional records to test a shortlist before uploading customer information. Check that the new system handles a returning customer, a changed date and a cancelled job. Try the phone view and the permissions for each staff role, not only the owner's account.

Before migration, agree how customers, jobs and notes map to the new records. Check that dates, leading zeros in phone numbers, attachments and links between records survive. Compare record counts and spot-check histories after the import.

Pilot with a small team and a clear end date. Decide which system is authoritative during the pilot so staff do not update both and create disagreements. Make the old sheet read-only at the agreed switch, keep a secure backup and set a retention period rather than leaving editable copies everywhere.

Ask for an export of the new records before committing. Check what it includes and whether another supplier could use it. For a custom build, agree code rights, administrator access, backups and ongoing support in writing. Ownership should mean you can maintain and recover the system, not merely that your logo is on it.