Blog
The problem isn't Excel
Sooner or later there’s a week where the sheet stops working. The same quote goes out twice. Two people edit pipeline_final_v3 and one version quietly wins. Someone asks which deals are still live, and the honest answer takes forty minutes to assemble.
The conclusion most owners reach is: we’ve outgrown Excel. That’s half right. The wrong half is expensive, because it sends you shopping before anything has been written down.
What actually broke
Take the last three things that went wrong on your sheet and ask what would have prevented each one. It’s rarely a feature.
- The duplicate quote wasn’t a spreadsheet failure. Nobody had written down who owns an inbound enquiry.
- The column of dead-but-still-listed deals isn’t a formula problem. There is no rule for when a deal is dead.
- The forty-minute answer wasn’t slow software. Two of your people would put the same deal in two different stages, so the list has to be re-argued every time it’s read.
None of that improves in a new tool. It gets rebuilt there, on a subscription. It’s the same failure mode as a CRM project that dies in 60 days: the software was never the missing piece.
Say out loud what a spreadsheet is actually good at
Worth being honest here, because “stop using spreadsheets” is usually advice from someone holding a license to sell.
A sheet genuinely beats a configured system on three things. It changes shape in seconds. While you’re still working out what your stages are, that’s an advantage. A system configured around a process you haven’t finished writing is worse than a sheet, not better. It has no learning cost. Your team already knows it, so adoption is never the reason a sheet fails. And it’s the cheapest place to write draft one of anything.
If you have a modest number of open deals, one person maintaining the list, and a thin record per deal, a sheet is a legitimate answer rather than a stopgap. Long-cycle B2B firms run on one for years.
The ceiling: four things no formula fixes
- A cell holds a value, not a history. Overwrite a date and the previous date is gone. In project and installation work, the useful information is usually what changed, when, and why. That’s exactly what the cell throws away.
- A deal is a conversation; a row is a line. Quote version one versus version three, the spec exception you agreed to, the reason the site survey was redone. None of it fits in a cell, so it lives in someone’s mail instead.
- Nothing enforces the rule you wrote. A sheet will happily accept a blank next step, a stage that means nothing, a deal with no owner. A rule enforced by goodwill lasts about three weeks.
- It never comes and finds you. Nothing tells you a deal has sat untouched for forty days. Someone has to remember to look.
Notice that three of those only bite once several people share the work, and once your cycle is long enough that memory stops covering the gap. Below that, you’re not at the ceiling.
Five markers that you are:
- More than one person needs to change the same file on the same day.
- More than roughly 30–40 open deals at once. Past that, actually reading the whole list every week stops happening.
- You need to answer “what exactly did we promise” from the record rather than from a person. That’s the handover problem.
- Updates have to happen on a phone, from a site, the same day.
- Not everyone should see every column.
Two or fewer: fix the sheet, not the tool. Four or five: the tool is a real constraint, and moving is a reasonable decision once you’ve read the next section, not before.
Can you build a sales system on Google Sheets?
Further than most people expect, if you accept three rules.
One file, no copies, ever. The moment a version gets emailed or sent in chat, you have two truths and no way to merge them. Shared, live, one link. This removes the most common spreadsheet failure on its own.
Stages are a dropdown, not free text. One validated list, with the definitions written on a second tab. If two people can type their own stage names, you don’t have stages. You have labels.
The weekly review runs off the sheet, on screen. Deals not on it don’t get discussed. That single rule is what makes people update it, and it costs nothing.
Keep the required columns down to the handful that answer questions you already ask out loud. Five is usually enough. Then accept what a sheet still won’t do: it won’t remind anyone, it won’t hold the conversation, and it won’t stop a rule from being ignored. Those three are what you’re actually buying when you eventually move. Buy them knowingly.
Writing how a deal moves is what survives the migration
Whatever you end up in, the thing that decides whether it works is a page you can write this week, in your own words:
- Entering. What counts as a deal, and who owns it from the first minute.
- Moving. What must be true to leave each stage. An artifact or a dated event, never a feeling. This is stage-exit criteria, and it’s the hardest page to write.
- Sitting. How many days a deal may stay in one stage before it must be re-dated, moved back, or closed.
- Recording. What gets written the same day it happens, and by whom.
- Dying. What makes a deal dead, and who is allowed to say so.
That page is tool-independent. A spreadsheet is a perfectly good place to write it. Do it first and the eventual move is a copy rather than a rethink. Skip it and you’ll pay to rebuild the same mess in a nicer interface, which is the order most companies buy in.
If you can’t tell whether the sheet is your constraint or your cover, book a 45-minute call. We’ll go through the file you’re using now, and you’ll leave knowing how many of the five markers you actually hit, plus how a deal moves written out for at least one stage. That’s yours whether or not you go further with us. That’s the shape of a BUILD 30 install from B2B Sales System, a ZestMate Solution program: we design the pattern, your team installs it, and day 30 is measured against three criteria written on day one.