Most vertical SaaS founders think they're competing with legacy software. They're not — or at least, not primarily. The most common "software" in a small to mid-sized service business is a spreadsheet someone built in 2013 and has been maintaining ever since.
That spreadsheet has one major competitive advantage: the person using it knows exactly how it works. It took years to develop into a workable system. Replacing it is a project, not a purchase. Understanding this competition is the difference between a sales process that works and one that generates endless "interested but not right now" responses.
Why Spreadsheets Win More Than They Should
Spreadsheets win because they're free, fully customizable, and don't require training. That sounds like a weak argument until you're sitting across from an owner-operator who built their entire business on a Google Sheet that tracks dispatch, invoicing, and customer history in one color-coded tab.
The emotional investment is real. That spreadsheet wasn't bought — it was built. Replacing it means admitting the manual system had limits, and trusting your data to a third party, which for some operators is a meaningful psychological barrier.
It also means change management. The owner knows the spreadsheet. The crew doesn't. Training people on new software has a cost and a risk. If the software breaks or the vendor disappears, you lose everything. The spreadsheet is local, controllable, and backed up somewhere.
This is not irrational thinking. This is exactly how a careful business owner should evaluate software adoption. Your job as a founder is to make the case that those concerns are addressable — not dismiss them.
The Failure Mode That Hurts You
The mistake vertical SaaS founders make is trying to compete with the spreadsheet on flexibility. They add feature after feature, trying to build a tool that does everything the spreadsheet does. This is the wrong approach.
Spreadsheets are infinitely flexible. You'll never out-flexible one. The more you try to mirror its flexibility, the more complex your product becomes and the harder onboarding gets.
Pick the worst workflow failure. Build the best possible solution for that specific problem. A product that solves one critical workflow failure better than the spreadsheet can is a much easier sell than a product that tries to replace everything. The operator founder advantage is knowing which workflow is the right one to start with, because you've lived all of them.
The Migration Is the Sale
The biggest objection to replacing a spreadsheet isn't price or features. It's migration. "How do I get my existing data in there?" kills most deals before they start.
If your product makes migration easy — a one-click import from common formats, a brief onboarding call where someone handles the data entry, or a service tier that includes migration support — you remove the single biggest barrier to switching.
The cost of providing migration support in the early stage is real but recoverable. The deals you lose by not offering it are not. Operators who've been on the buying side of this know exactly how painful migrations feel. Build the migration experience your buyers are afraid of, and make it easy.
What to Say When They Say "We Already Have a System"
"We already have a system" means a spreadsheet in about 60% of cases. Your response shouldn't be a feature comparison. It should be curiosity.
"Can you walk me through how you handle [specific workflow]?" is the right question. Not "let me show you what we can do instead." When you let them explain how their current system works, two things happen: you learn where the actual friction is, and they often hear themselves describing a broken process out loud for the first time. That second thing changes how they think about it.
The buyer who just heard themselves explain why they copy invoice data from one tab to another every Friday is more receptive to seeing a better solution than the buyer who heard a feature pitch. The sale doesn't happen in that moment, but the groundwork for it does.
The spreadsheet isn't a sign that the market isn't ready for software. It's a sign that no one has made software that feels less risky than the spreadsheet. That's the bar you're clearing.