When does a spreadsheet stop being enough?

A spreadsheet that does its job is worth keeping. It is quick to change, easy to inspect and often understood by the person running the business. Moving the same rows into an expensive application does not automatically improve anything.

The question is what you now have to do around the spreadsheet to keep the work moving. If the answer involves several copies, reminder messages and one person who knows which columns must never be touched, look more closely.

Separate an untidy file from a broken process

Some problems need an afternoon of housekeeping. Consistent column names, protected calculations and a clear rule for entering a new record can make a file much easier to use.

Other problems sit outside the file. Perhaps a customer changes an address and someone must update it in four places. Perhaps a row needs approval before work starts, but the only signal is an email. Perhaps two people disagree about which quote the customer accepted.

Those problems involve records, permissions or a sequence of actions. They deserve a process decision before a software decision.

Look for the workarounds people repeat

Ask the people using the file to show you their last completed job. Watch where they copy information, ask a colleague for permission or check another system.

A few useful questions:

• Can you identify the current record without asking its owner?
• Can someone make a change they should not be able to make?
• Is it clear who needs to act next, and by when?
• Does a customer update have to be entered more than once?
• Could another person run the process if its usual owner was away?

One awkward answer does not mean you need a new application. Several recurring workarounds give you a specific scope to investigate.

Try the smallest change that removes a problem

If the only issue is inconsistent entries, a form feeding the existing sheet may be enough. If several people need a reliable customer history, an off-the-shelf CRM may be a better fit. If the rules are particular to your business, a focused custom tool may be justified.

Consider a trade business tracking quotes. The spreadsheet holds names and values well enough, but photos live on a phone and accepted versions are buried in email. A useful replacement would connect those records and show the next action. Recreating every colour and tab would miss the point.

The quoting software guide describes that workflow in more detail. You can also connect a sheet to another tool without replacing it immediately; see website enquiries and customer records.

Budget for the move, not just the build

Before replacing a spreadsheet, work out which data should move. Old duplicates, abandoned enquiries and unexplained abbreviations do not become useful just because they enter a database.

Choose a small set of records and test the import. Check totals, attachments and customer histories with someone who knows the work. Agree which system is the source of truth during the changeover and when the old file becomes read-only.

Keep an export and a recovery plan. Ask how you would get your information out of the new system later. Ongoing hosting, support and third-party charges belong in the decision alongside the initial setup.

Write the requirement in ordinary language

A useful brief might be: “We need anyone in the office to find the accepted quote and the next action for a job, without searching someone’s inbox.”

That is specific enough to compare a tidier spreadsheet, a standard CRM and a custom build. Kerbside can help with that comparison and the software that follows. Sometimes the right outcome is to keep the sheet and remove one awkward step around it.