SMBDashboardSpreadsheet vs CRM: When a Spreadsheet Wins
By Mark Fulton · 2026-08-20 · 12 min read
Almost every page you can find on this question is published by a company that sells CRM software, and every one of them arrives at the same conclusion. So let me give you the answer they will not. If you have a few dozen customers, no sales team, and you are the only person who touches the file, a spreadsheet is a perfectly good customer list and you should keep using it. The spreadsheet does not fail because of size. It fails at three specific jobs: two people editing it at once, follow-up dates that have to surface on their own without you going looking, and history you can read in five seconds while someone stands at the counter. Hit any one of those three and it is time to move. Hit none of them and a CRM will cost you money and a weekend to get you exactly where you already are.
I build a small-business dashboard, so the customer list is something I sell. That is a reason to be careful here, not a reason to lean on the scale. The honest version of this comparison is better for me anyway, because the owners who move for a real reason stay, and the ones who move because a blog post told them to are back in the spreadsheet within a month.
What is a spreadsheet genuinely good at for customers?
More than the vendors admit, and it is worth being specific about why.
It has no shape you have to accept. A CRM ships with somebody else's sales process baked in: leads, opportunities, stages, close dates. A landscaper does not have opportunities. A salon does not have a pipeline. A spreadsheet starts as an empty grid, so the columns end up being the things you actually track, which for most owners is name, phone, what they had done, when, what it cost, and a note about the dog.
Reading it is instant and free. Scanning a hundred rows with your eyes is a genuinely fast operation. No page loads, no filters to set, no clicking into a record to see the one field you wanted. For a list you already know well, visual scanning beats search.
Everyone already knows how to use it. Nobody needs onboarding. There is nothing to configure, no seats to buy, no import to plan, and no vendor who can change the terms next year.
It is yours in a way software rarely is. The file sits on your drive. You can email it, back it up, open it in ten years, and hand it to an accountant without asking permission. That is not a small thing, and it is the one advantage that gets quietly skipped in every vendor comparison.
The math is right there. Total spend per customer, a count of visits, a sort by last purchase date. All one formula. If your customer file mostly answers money questions, a spreadsheet is arguably a better fit than a CRM, which typically wants to talk about deals rather than totals. That side of things is a separate topic, and I covered the money version of it in the small business dashboard in Excel walkthrough.
Which three jobs does a spreadsheet fail at?
Not "at scale" and not "as you grow." These are switch-like. The spreadsheet works completely, and then one of these three appears and it stops working the same week.
One. A second person needs to edit it. This is the hard one, and it is a genuine technical limit rather than a preference. Real-time co-authoring in Excel requires the workbook to live on OneDrive or SharePoint Online, in a supported file format, with AutoSave on and a current subscription. Microsoft's own co-authoring requirements note that if even one person opens the file in an unsupported version, everybody else gets the locked error. Google Sheets handles simultaneous editing far better, but it still does not stop two people typing conflicting notes into the same customer's row, and it does not tell you who was right. The moment your file is emailed around as attachments, you no longer have a customer list. You have several disagreeing customer lists.
Two. Follow-up dates have to surface without you going looking. A spreadsheet is passive. A date in a "next contact" column is inert text until a human opens the file, sorts by that column, and reads it. That human is you, on a Tuesday, when you remember. Conditional formatting turns the cell red, which helps only if you are already looking at the cell. Every follow-up you have ever dropped was dropped in the gap between writing the date down and happening to look at it again. This is the failure that costs actual revenue, and it is the one I wrote a whole system around in stop losing track of customer follow-ups.
Three. History has to be readable while somebody is standing in front of you. Customer history in a spreadsheet lives in one of two bad places. Either it is crammed into a single notes cell that grows until it is unreadable, or it is spread across one row per visit, which means the person's story is scattered down a sheet sorted by date. Excel allows up to 32,767 characters in a single cell, which is exactly the problem: the software will happily let you build a wall of text nobody can skim. When a customer calls and you need to know what happened last time in five seconds, neither layout gives it to you.
Notice what is not on that list. Row count is not on it. Neither is "professionalism," "insights," or "scaling." Those are marketing arguments. These three are mechanical.
What does a full CRM add that a small business will never use?
A real CRM is built for an organisation with sales staff, and most of its surface area exists to manage people who do not work for you.
Pipeline stages and probability weighting exist so a manager can forecast a quarter. Lead scoring and routing rules exist to allocate inbound leads between reps. Email sequences and cadences exist so a rep can work two hundred prospects at once. Territory management, quota tracking, approval workflows, custom objects, sandbox environments, permission sets: all of it is infrastructure for coordinating a team. Then there is the reporting layer, which is largely designed to tell a manager which rep is behind.
If you are the only person who talks to customers, every one of those is a field you leave blank or a screen you never open. Worse, most of them are not optional. You configure them once during setup, and then the software keeps asking about them forever. That is the actual cost of a CRM for a small business, and it is not the monthly fee. It is being asked, at every interaction, to describe your work in a vocabulary designed for somebody else's job.
There is a narrower version of this argument in a simple CRM is enough for most small businesses, which walks through the four things owners actually need from customer software.
What sits in between?
There is a middle option the vendor comparisons skip entirely, because none of them sell it: a plain customer list. Records with a name, contact details, tags, notes, a next-follow-up date, and a readable history, with no pipeline and no sales process attached. It fixes the three breaking points and adds nothing else.
Here is how the three options compare on the six jobs a small-business owner actually needs from a customer file.
| Job | Spreadsheet | Simple customer list | Full CRM |
|---|---|---|---|
| Find a customer fast | Good. Ctrl+F, or just scan the rows. Slows down once you cannot see the whole list on one screen | Good. Search across name, phone, tag and note text, so partial memories still land | Good, but usually two clicks deeper, because search returns records, deals and activities together |
| Remember the last conversation | Weak. Either one bloated notes cell or the story scattered across dated rows | Strong. A timestamped history you can skim in seconds while the customer is in front of you | Strong, and often too detailed. Emails, calls and system events land in one activity stream |
| Surface today's follow-ups | Fails. The date is inert until you open the file and sort by it | Strong. Due follow-ups appear on the screen you already open, without you going to look | Strong, usually via tasks and reminders, sometimes with email notifications you will end up muting |
| See who's gone quiet | Possible. Sort by last-contact date, but only if you have kept that column honest by hand | Strong. Last-touched is computed from what you logged, so it stays right without maintenance | Strong, often automated, though "quiet" is defined by the vendor's pipeline logic rather than your trade |
| Hand off to someone else | Fails. Real-time editing has hard prerequisites, and emailed copies fork the truth immediately | Good. One shared record, though most simple tools are built for one operator rather than a staff roster | Strongest. This is what per-seat CRM pricing is genuinely paying for |
| Get the data back out | Strongest. The file is yours, offline, in a format everything can read | Good, provided there is a plain CSV export you can run yourself | Varies. Contacts export easily, but custom fields, activity history and attachments are where lock-in actually lives |
Read the table honestly and two things stand out. The spreadsheet wins on ownership and loses on the three jobs from the previous section. The full CRM only pulls decisively ahead on the handoff row, which is the one job that genuinely needs a multi-user system. If nobody else touches your customers, you are paying per seat for a feature you are the sole user of.
How many customers before the spreadsheet cracks?
Fewer than you think, and it has nothing to do with the row limit.
The technical ceilings are enormous. Microsoft's Excel specifications and limits put a worksheet at 1,048,576 rows by 16,384 columns. Google's Sheets size limits allow up to 10 million cells and 18,278 columns. No small business will ever approach either number with a customer list. When someone tells you spreadsheets cannot scale, they are not talking about the software.
The real ceiling is human, and it arrives in two stages. The first is the point where you can no longer hold the list in your head, which for most owners lands somewhere in the low hundreds of customers. Below that, you know who is who, and the spreadsheet is just an aide-memoire. Above it, you start relying on the file to tell you things, and a file that only answers when asked is not reliable enough for that.
The second stage is the one that actually decides it, and it can happen at twelve customers or at four hundred. It is the first day somebody else needs to write in it. Hiring one part-time person breaks a spreadsheet customer list more thoroughly than tripling your customer count ever will.
So the useful question is not how many customers you have. It is whether you are still the only one who edits this, and whether you are still remembering to open it.
How do you move without losing your notes?
The migration itself is small. The care goes into the notes, because the notes are the part with no equivalent column anywhere.
Clean the sheet first, in the sheet. One row per customer, not one row per visit. Split anything compound: full name into first and last if you will ever sort by surname, address into its own field, phone numbers stripped to digits so the import does not choke.
Then decide what the notes actually are. Most spreadsheet notes cells contain three different things blended together: durable facts about the person (gate code, allergy, the dog's name), a log of past events, and a reminder about something upcoming. Those belong in three different places after the move. The durable facts become a profile field or a tag, the log becomes history entries, and the upcoming thing becomes an actual dated follow-up. If you paste the whole cell into one field, you have moved your problem rather than solved it.
Export as CSV, not as .xlsx. Import, then check ten records by hand against the original file before you trust the new one. And keep the original spreadsheet. Do not delete it, do not overwrite it. It costs nothing to keep and it is the only rollback you have.
Finally, run both for two weeks. Not forever, and not as a permanent double-entry habit, but long enough to catch the field you forgot to map.
Frequently asked questions
Is Excel good enough as a CRM?
For a solo operator with a customer list they mostly already know, yes. Excel handles finding, listing and calculating perfectly well. It stops being good enough the moment you need follow-up dates to surface on their own, or a second person to edit the same file, because those are the two things a passive single-user document structurally cannot do. Judge it on those two questions rather than on your customer count.
How many contacts can a spreadsheet handle?
Technically, far more than you will ever have. Excel supports 1,048,576 rows per worksheet, and Google Sheets supports up to 10 million cells per spreadsheet. Practically, a customer spreadsheet gets unreliable somewhere in the low hundreds, because that is roughly where you stop being able to verify by eye whether the file is still accurate. The limit is your memory, not the software's.
What's the difference between a CRM and a customer list?
A customer list stores who your customers are and what has happened with them. A CRM does that too, then adds machinery for managing a sales process across multiple people: pipeline stages, forecasting, lead routing, sequences, quotas, and per-user permissions. If you have no sales team, that extra machinery is the entire difference, and it is all cost with no return.
Can I export my data if I switch later?
Confirm it before you import, not after. Ask whether you can export a plain CSV yourself without contacting support, and whether the export includes notes and history rather than just names and phone numbers. Contact fields almost always come out cleanly. Activity history and custom fields are where data gets stranded. Any tool that cannot answer that question in its own documentation has told you something useful.
If the three breaking points describe your week, the customers module in SMBDashboard is the middle option from that table: contacts, tags, notes, dated follow-ups that appear on the screen you already have open, and a last-touched column computed from what you log. You can open the customers module free with no account, or read what it does on the free CRM for small business page first. The free tier holds 25 customers and Pro removes the cap entirely, and your data stays in your browser unless you turn on Pro sync.