Every growing business eventually hits the same question: should we build a custom tool or buy something off the shelf?
The answer is almost never obvious, and getting it wrong is expensive in both directions — either you spend six months building something that already exists, or you spend two years fighting a tool that doesn't actually fit your workflow.
Here's the framework we use when helping clients make this decision.
Start with the workflow, not the technology
Before you evaluate any tool or estimate any build, document exactly what you need the software to do. Not in technical terms — in business terms.
What does the process look like today? Who touches it? What are the pain points? What would "good" look like?
This sounds basic, but skipping it is the number one reason companies buy the wrong tool or build the wrong thing.
When to buy
Buy when the problem is well-understood and common. Accounting, email marketing, CRM, project management — these are solved problems. The tools are mature, well-supported, and cheaper than anything you'd build.
Buy when speed matters more than fit. If you need something working next month, not next quarter, an off-the-shelf tool with 80% fit beats a custom build with 100% fit that won't be ready for six months.
Buy when the tool is not your competitive advantage. If the software you're evaluating isn't core to what makes your business different, don't build it. Your engineering time is better spent elsewhere.
When to build
Build when your workflow is genuinely unique. If no tool on the market handles your specific process without heavy customization — and you've actually looked, not just assumed — custom software will serve you better long-term.
Build when you need deep integration. If the tool needs to talk to five internal systems, process data in a specific way, and present it in a custom UI, you'll spend more time fighting an off-the-shelf tool's API limitations than you would building from scratch.
Build when the off-the-shelf cost doesn't make sense. Enterprise SaaS pricing can be aggressive. If you're looking at $50k+/year in licensing for something a competent team could build and maintain for less, the math might favor custom.
Build when you're creating a competitive advantage. If the software itself is what differentiates your business — how you serve customers, how you process data, how you operate — that's worth owning.
The hybrid approach
The best answer is often: buy what you can, build what you must.
Use off-the-shelf tools for the common stuff (payments, email, auth) and build custom software for the parts that are unique to your business. Connect them with APIs.
This is exactly how we approach it. When we built Spekco, we didn't build our own payment processor — we integrated Stripe. We didn't build our own email infrastructure — we use Resend. The custom work went into the things that make the platform unique: the repair workflow, the multi-tenant architecture, the unified POS.
Red flags in both directions
Red flags you're about to build something you should buy:
- "We just need a CRM, but customized"
- The requirements doc looks like a feature list from an existing product
- You're reinventing auth, file storage, or email sending
Red flags you're about to buy something you should build:
- You need three integrations just to make the tool do what you need
- The vendor's roadmap doesn't include the features you're waiting for
- You're spending more time working around the tool than working in it
The real cost of each
When comparing costs, don't just look at the sticker price.
Off-the-shelf true cost: License fees + implementation + training + customization + integration + ongoing vendor dependency + the cost of adapting your workflow to the tool's assumptions.
Custom build true cost: Development + testing + deployment + hosting + maintenance + future feature work + the risk of building the wrong thing.
Neither is "cheaper." The right answer depends on your specific situation.
Not sure which way to go?
This is one of the most common conversations we have with clients. If you're weighing build vs. buy for a specific project, let's talk it through. No pitch — just an honest assessment of your options.