Spreadsheets

Spreadsheet or a real system?

Spreadsheets run more small businesses than any software you can buy, and often they are the right tool. This page is about knowing the day they stop being: the signs, the cost of waiting, and the steps in between.

Get a quote The short answer

The short answer

Stay on spreadsheets while one or two people use them, the data is simple and nothing depends on it being instantly right. Move to a system when several people edit the same sheet, when a mistake costs money, when you re-type from one sheet to another, or when a customer or a deadline slips because the information was in the wrong place. You don’t have to jump to a full system: a shared sheet with structure, then a small system, is a legitimate path.

Side by side

Custom vs spreadsheets, factor by factor.

Factor	A custom system	spreadsheets
Cost model	A build cost in phases, then hosting and optional support.	Almost free: Excel and Sheets come with Microsoft 365 or Google Workspace, which you may already pay for per user.
Fit to your process	Screens, rules and documents built for your steps, with the data validated as it goes in.	Infinitely flexible. Anything is possible, which is also why no two sheets, or two people’s versions, quite agree.
Time to start	Weeks for a first version.	Today. Open a sheet and start.
Several people at once	Roles and permissions: sales sees the pipeline, the office sees invoices, and every change is logged.	Shared editing works in Google Sheets and in Excel on Microsoft 365, but nothing stops a person overwriting a formula or a row.
Errors and duplicates	Required fields, duplicate detection and one record per client.	Typos, duplicates and broken formulas are caught by whoever notices, usually late.
Automation and reminders	Follow-ups, overdue invoice chasers, WhatsApp and email sent from the data.	Some is possible with scripts and add-ons, but it tends to depend on one person who knows how.
Customers and portals	Clients can log in, see their records and book or pay.	Not designed for this. You send files by email.
Data ownership and export	Your data in its own database, in a documented structure you can export. Agree what you receive at handover in writing.	Your files, in your account, in a format everything can open. A genuine strength.
Scaling with team size	Built for more people and records without slowing.	Gets slower and riskier as rows, tabs and editors grow.

Choose spreadsheets if

One or two people use the sheet and the data is simple.
You’re testing a process and don’t yet know what it should be.
A mistake in it would be annoying, not costly.
You need it now, at no extra cost, in a tool everyone already knows.
You need ad hoc analysis. A spreadsheet is better at that than most systems.

Choose custom if

Several people edit the same sheet and someone has overwritten work.
The same client or order is typed into two or three sheets.
Customers wait because the answer is in someone’s file.
Money depends on it: invoices, stock, payments, deadlines.

The signs a spreadsheet has done its job

A spreadsheet doesn’t fail all at once. It fails by degrees, and the signs are practical rather than technical. If three or more apply to you, a system is probably already costing you less than the workarounds.

Two people edited the same row and one change was lost.
A formula was overwritten and nobody noticed until a number looked wrong.
The same client appears in several files, spelled differently.
A new starter needs a walkthrough to understand which tab is the real one.
You keep a ‘master copy’ and a ‘latest’ copy.
A customer asked for a status and nobody could answer without opening three files.
One person is the only one who understands how the workbook works.

What it really costs over three years

A spreadsheet looks free, and the licence is. The cost is staff time: hours spent re-typing, checking, reconciling and looking for the current version, multiplied by the people who do it, multiplied by the weeks. Add the cost of the mistakes that get through, a missed renewal, a quote not followed up, a double booking.

A system has a build cost, which depends on what you need it to do, and then hosting and support. The comparison is the build against the staff time you would get back, plus what the mistakes cost. If the time is small and the mistakes are cheap, stay on the spreadsheet.

You can also take it in steps. A well-structured shared sheet with validation and one tab per thing is a real improvement. Next comes a small system for the part that hurts most, usually customer records or invoicing, which grows from there.

What moves across, and what a system adds

The first thing a system does is take your data. Customers, contacts, orders, stock and history are imported from your sheets and checked against the source. The guide to moving from spreadsheets to a CRM walks through the steps, and the data migration guide covers the cleaning.

Then it adds what a sheet can’t. Required fields and duplicate detection keep the data clean. Roles stop the wrong person editing the wrong thing. Reminders happen without anyone remembering. Customers can log in, and every change is recorded. MCMA is a good illustration: applications, enrolment, schedules and payments were handled by hand, and now run on one system with student and tutor portals. The MCMA case study shows the result.

Where each one breaks

Spreadsheets break on people and scale: more editors, more rows, more tabs and more hidden formulas, with nobody owning the rules. They also can’t talk to customers, or send a WhatsApp message when an invoice is overdue.

A system breaks when it is overbuilt for the problem. If your process is still changing weekly, building rigid software around it is premature. Start with a sheet, learn what the process is, then build. A good developer will tell you if you are not ready, and I will.

FAQ

Questions, answered.

Is Excel or Google Sheets good enough for a small business?

Often, yes. For one or two people, simple data and low stakes, it is the best tool. The trouble starts with several editors, money riding on the data or customers waiting on the answers.

Should I use a CRM product before building a custom one?

Usually. A product like HubSpot or Zoho is a good intermediate step. If it fits, you are done. If you keep a spreadsheet next to it for what it can’t do, that is the sign a custom system might be worth it.

Can you import our spreadsheets?

Yes. Spreadsheets are the most common starting point. I clean and import them, and check the result against the originals before you switch.

Will my team actually use it?

The system has to be easier than the spreadsheet or they won’t. That’s why you see a working preview early, with your own data in it, and why the first phase covers the job people do every day.

Do I lose the ability to analyse data in a spreadsheet?

No. Everything in the system can be exported to a spreadsheet when you want to explore it, and reports cover the numbers you check regularly.

Go deeper

Get a fixed quote.

Not sure which way to go? Scope it in the quote builder and I’ll tell you honestly whether custom is worth it for you.

Start the quote builder Or talk to me first