The Real Cost of 'Good Enough' Software
A practical guide to the build vs. buy decision for growing businesses
The spreadsheet was called MASTER_leads_FINAL_v3_USE_THIS_ONE.xlsx.
That's when I knew we had a real problem. The founder had hired me to build a CRM, but what I found was seven SaaS tools that didn't talk to each other, a Zapier account running 47 automations (12 of which were broken), and a team that spent their Monday mornings copying data between systems instead of selling.
The monthly software bill was $2,400. The actual cost was much higher.
The Accumulation Problem
Nobody sets out to build a mess. It happens gradually. You start with a free tool because you're not sure what you need yet. Then you hit a limit and upgrade. Then you need something it doesn't do, so you add another tool. Then you need them to share data, so you add Zapier. Then Zapier can't handle the edge case, so you add a workaround spreadsheet. Then someone leaves and nobody knows how the spreadsheet works.
Each decision made sense at the time. The result doesn't.
The real cost isn't the subscriptions—it's what economists call opportunity cost. Every hour your team spends fighting your tools is an hour they're not spending on the work that actually grows your business. Every customer who falls through the cracks because of a sync delay is revenue you'll never see. Every manual process is a bottleneck that limits how fast you can scale.
Most businesses underestimate this by an order of magnitude.
When Custom Software Becomes the Cheaper Option
Custom software isn't always the answer. For plenty of businesses, Shopify or Notion or Airtable is exactly right. The question is whether you've outgrown that stage.
Three signals that you probably have:
Your process is your product. If how you do something is central to why customers choose you, generic tools will always hold you back. They're designed for the average case. You're trying to be better than average.
You're paying for ten features to use one. Enterprise SaaS pricing bundles capabilities you'll never touch. If you're spending $500/month on a tool because you need one specific thing it does, that's a $6,000/year tax on your business.
Your integrations have integrations. When you need a third tool to make two tools work together, and then a fourth tool to handle what the third tool can't, you've crossed a threshold. The complexity cost now exceeds what you'd spend on something purpose-built.
The Math That Actually Matters
A custom web application typically costs $30,000 to $150,000 to build, depending on complexity. That sounds like a lot until you run the real numbers.
Take that $2,400/month software stack: $28,800 per year. Add the 10+ hours weekly that the team spent on manual workarounds—at $50/hour, that's $26,000 per year. Add the deals that slipped because the system couldn't keep up. Add the senior employee who quit because she was tired of fighting the tools instead of doing her job.
The custom CRM I built cost $45,000. It paid for itself in seven months. Three years later, it's still running, the team has doubled, and the monthly software cost is $200 for hosting.
That's not a universal outcome. But it's also not unusual.
The Part Nobody Talks About
Here's what I've learned from doing this for years: the technology is usually the easy part. The hard part is understanding the problem well enough to build the right thing.
Most failed software projects don't fail because of bad code. They fail because someone built a solution to the wrong problem. They automated a process that shouldn't exist. They added features nobody needed. They optimized for the wrong metric.
The first thing I do on any project is listen. Not to what you think you need—to what's actually happening. Where does work get stuck? Where do people create workarounds? What would change if the constraint disappeared?
The answers to those questions matter more than any technology choice.
If you're running a business on software that's fighting you instead of helping you, it might be time for something better. I help companies figure out whether custom development makes sense—and if it does, I build it. Let's talk about what you're dealing with.