"We spent $180K building a custom CRM. We could have used HubSpot for $500 a month."
That was a founder who came to us in late 2025. Eight months of engineering time. Three developers. A CRM that worked, more or less, but couldn't integrate with their new outbound tool and had no mobile app. Now they're looking at either rebuilding it properly or migrating to HubSpot and spending another two months cleaning data.
Here's the other side of that story. Last year, a different founder bought Salesforce for an 11-person team. $80K a year in licences. Two custom integrations that Salesforce's API couldn't support without middleware that cost another $25K to build. Eighteen months of workarounds that became load-bearing parts of the sales process. They came to us after a top salesperson quit, partly because the CRM workflow was so painful.
Build vs buy. Both founders made the wrong call. Both mistakes were preventable with the right conversation before they committed.
The Build Trap
Here's what usually happens when a founder decides to build. The developer gives an estimate. The founder adds 20% for safety margin. Six months later, the actual cost is double the estimate and the scope is half of what was planned.
It's not because developers lie. It's because build estimates almost never include:
- Ongoing maintenance (typically 15–20% of build cost per year, forever)
- The six months of lost feature velocity while the team works on internal tooling
- What happens when the developer who built it leaves
- Security updates, infrastructure scaling, and compliance overhead
The real cost of a $150K custom build: $150K upfront + $25K/year maintenance + $40K of lost product velocity = ~$215K in year one, $240K in year two. The equivalent SaaS stack often runs $20K–40K/year.
The build trap has a very specific emotional driver: founders want control. They're tired of being limited by someone else's product roadmap. That instinct isn't wrong — there are absolutely situations where building gives you competitive advantage. But control of a system that isn't your core product is a liability, not an asset.
Not Sure Which Way to Go?
We help founders work through build vs buy decisions before they commit — not after they've spent $100K finding out the hard way.
Talk It Through →30 minutes • No obligation • Honest feedback
The Buy Trap
Buying is also wrong when it's wrong. This happens in three specific situations I see regularly.
The workflow is genuinely unique. Some businesses have operational processes that no SaaS has productised well. Niche manufacturing quality control. Specialist legal matter management. High-complexity project scoping. If the closest SaaS covers 60% of your workflow and requires significant manual process to cover the rest, you're not saving time — you're just moving the work.
The integration cost exceeds the subscription savings. Some SaaS tools look cheap until you add up the integration work. I've seen $12K/year SaaS products that required $60K in integration development to connect to an existing system. The build would have been cheaper and more maintainable.
It's your core competitive advantage. If the software capability is what differentiates your product — your pricing algorithm, your recommendation engine, your underwriting logic — buying a vendor who sells the same capability to your competitors makes no sense. That's the one situation where building is clearly right.
The test: If a competitor bought the same SaaS product you're evaluating, would they achieve the same capability? If yes, the SaaS gives no competitive edge. Build when the answer is no.
How We Make This Decision With Founders
When a founder comes to us with a build vs buy question, here's what the conversation looks like.
First, we get specific about what's actually being decided. "We're thinking about building a customer portal" isn't a decision — it's a vague intention. "We need authenticated client access to project status, document sharing, and invoice history" is a decision. The specificity matters because it determines whether a SaaS solution actually exists or not.
Then we do a real evaluation of the SaaS options. Not a demo. A 30-minute call with a sales engineer where we specifically ask about the things the demo won't show: API limits, data export format, what happens to our data if we cancel, and which features on the roadmap are actually shipping versus just on a slide.
Then we model the three-year cost both ways. This isn't complex maths — it's just forcing the comparison to be honest. Build cost plus maintenance plus engineering time. SaaS cost plus implementation plus admin plus projected user growth.
In most cases, that comparison makes the right answer obvious. When it doesn't, we look at the two factors that override cost: is this core competitive IP, and does the team have the capacity to maintain a custom build for three years without compromising the product?
Most recently: A fintech founder came to us having spent two months evaluating whether to build a custom KYC workflow. We found a specialist SaaS product they hadn't evaluated that covered 90% of their requirements at $2,000/month. The build estimate was $120K. Decision took three weeks, not three months.
Stop Going in Circles on This Decision
We've made this call dozens of times across different industries and company sizes. We know which questions to ask and which SaaS tools consistently disappoint. Let's work through it together.
Get Clarity on Your Decision →30 minutes • No obligation • Honest feedback
Three Ways We Can Help
Depending on where you are in the decision, there are a few different ways to work with us on this.
Decision audit ($2,500 flat). You're currently evaluating a specific build vs buy decision. We'll review your requirements, evaluate the SaaS options you've identified (and find any you've missed), model the three-year TCO for both paths, and give you a recommendation with reasoning. One focused engagement, clear output, no ongoing commitment.
Fractional CTO engagement ($5K–$8K/month). You need an ongoing technical partner who's across all your technology decisions — not just this one. Build vs buy is one of the things we tackle, alongside vendor selection, architecture decisions, and technical team management. Most founders who've been burned by a wrong build vs buy call want this layer going forward.
Technical review before committing ($1,500). You've already decided to build. Before you sign the contract or start development, we review the scope, the technical approach, and the estimate. We find the gaps in the estimate and the risks in the approach while there's still time to course-correct. Roughly one-third of these reviews result in a significant scope change.
All three options start with the same conversation: you tell us what you're deciding and what you already know. We take it from there.
Let's Talk About Your Situation
Whether you're at the start of the decision or you've already committed and want a second opinion, book a call. We'll tell you honestly what we think — even if the answer is "you don't need us for this."
Book a Discovery Call →30 minutes • No obligation • Real talk about your specific decision