Every business eventually faces this question: do we buy software that mostly fits, or build something that fits exactly? After 16 years of building custom systems — and watching clients use off-the-shelf tools — I've developed a clear framework for making this decision.
When Off-the-Shelf Wins
Your problem is common and well-defined. Accounting, CRM, project management, email marketing — these are solved problems. The best commercial tools have thousands of person-years of development behind them. You won't outbuild Salesforce for standard CRM needs, and you shouldn't try.
Speed to deployment matters more than perfect fit. If you need something working next week, not next quarter, buy. A 70% fit today beats a 100% fit in six months — especially for early-stage businesses still discovering their workflows.
Your differentiator isn't the software. If software is a supporting function rather than your core product, off-the-shelf is almost always right. A restaurant doesn't need a custom reservation system.
When Custom Software Wins
The software IS your product or core differentiator. If your competitive advantage depends on how your software works — proprietary algorithms, unique workflows, specialized data processing — you need to own the code.
Integration complexity exceeds what SaaS tools support. When you need to connect five systems with custom business logic at every junction, the "glue code" between off-the-shelf tools becomes more complex than building the core system would have been.
You've outgrown the commercial tool. This is the most common trigger I see: a company starts with Shopify, Airtable, or Zapier, and eventually hits walls — performance limits, missing features, vendor lock-in. At that point, the migration cost is unavoidable.
The Decision Framework
I walk clients through four questions:
- Is this a core differentiator? If yes, build. If no, buy.
- Does a commercial tool exist that covers 80%+ of your needs? If yes, buy and customize. If no, build.
- Will your requirements change significantly in the next 12 months? If yes, build with flexibility. If no, buy the stable solution.
- Do you have the budget and team to maintain custom software long-term? Building is the easy part — maintaining is the commitment. If you can't sustain it, buy.
The Hybrid Approach
Most of my clients end up with a mix: off-the-shelf tools for supporting functions, custom software for their core differentiator, and well-designed APIs connecting everything. This is usually the right answer — it's just not the simple one.