Skip to content

Build or Buy? How I’d Actually Decide

For the software that runs your business internally, I’d build a lean version before I’d buy one — most of the time. Not because building is fashionable. Because buying usually means renting a fix to a problem you could own outright, and paying for it every month for the rest of your company’s life.

That’s the answer. Here’s the reasoning, including the cases where I’d tell you to buy and not waste a developer’s afternoon on it.

What “buy” actually costs

The sticker price on SaaS is the smallest number you’ll pay. The real bill is four things stacked on top of each other.

You pay forever. A £400/month tool is £24,000 over five years, and that number only goes up — per seat as you grow, per tier as you need the feature they put behind the next paywall. You never stop renting.

You pay for software you don’t use. Off-the-shelf tools are built for the average of ten thousand companies, which means roughly 80% of the product exists for someone who isn’t you. You’re funding their roadmap, not yours.

You integrate it anyway. The promise is “it just works.” The reality is you still spend weeks wiring it into the rest of your stack, exporting and re-importing, and building the glue between the three tools that were each supposed to be the whole solution.

And you hand over your data. More on that below, because it’s the one that actually matters.

The MVP-first math

Here’s the move most people miss. You don’t build the whole thing. You build the 20% that does your actual job, and you build it fast.

The work that one off-the-shelf tool does for you — the bit you genuinely use — is usually small and well understood. A lean version of it is a few weeks of focused build, not a moonshot. And the money you were about to spend on year one of subscriptions very often covers that build outright.

So year one roughly washes. The difference is what happens in year two. With SaaS, you start year two paying again, from zero, with nothing to show for the first year’s spend. With a system you own, you start year two having already banked the subscription money — and now you compound. You extend the MVP into the next thing you need. You connect it to the system next door. Every month after the build, your ROI gets shorter, not longer.

Every year you keep renting starts from zero. Every year you own starts further ahead.

You’re not buying software — you’re renting access to your own data

This is the principle underneath all of it: own your data and systems, so you can actually do something with them.

When your operation lives inside someone else’s tool, your data is their hostage. It’s in their schema, behind their API limits, exportable only in the shape they allow, and gone the day you stop paying. You can’t easily join it to anything else. You can’t automate across it. You can’t ask a new question of it without their permission and usually their upgrade.

When you own the system, the data is yours to connect, query, automate, and build on. That’s the leverage. The CRM isn’t valuable because it stores contacts — it’s valuable because the contact data can feed your invoicing, your reporting, your outreach, the thing you haven’t thought of yet. Rented tools wall that off and charge you for limited access. Own the system and the data is fully yours to use.

When I’d tell you to buy

I’m not dogmatic about this, and you should distrust anyone who is. There’s a clear line, and on the far side of it, buying is the correct answer and building is ego.

Buy the commodity. Buy the things that are mature, undifferentiated, heavily regulated, and not your competitive edge — payroll, the accounting ledger, email, card processing. The off-the-shelf option is cheap relative to the build, battle-tested by millions of users, and getting it wrong has legal consequences. Do not build your own payroll engine to save £30 a month. That’s not leverage; it’s risk you didn’t need to take on.

The rule is simple: buy the commodity, build the thing that’s actually yours. Your edge — the workflow only your business runs, the way you actually serve your clients — is exactly the thing no off-the-shelf tool will ever fit, and exactly the thing worth owning. Everything generic, rent and forget.

The question almost nobody asks

When someone comes to me asking “what’s the best CRM?” or “which project tool should we buy?”, they’ve usually skipped the only question that matters.

The question isn’t which tool to rent. It’s whether this should be a tool you rent at all. “Best CRM software” is the wrong search. It assumes the answer is a subscription and just argues over whose. Back up one step. Ask what the system actually has to do for you, how much of that is your edge versus a commodity, and whether the thing you genuinely need is small enough to own. Most of the time it is, and you never needed the comparison table.

A pattern I see constantly

The most common version of this is the business paying four separate subscriptions and gluing them together with a spreadsheet and someone’s Tuesday afternoon. A CRM that doesn’t talk to the invoicing tool, which doesn’t talk to the reporting, so a person re-keys the same data three times and calls it operations.

That business isn’t running on software. It’s running on the gaps between four pieces of software it rents, and a human filling those gaps by hand. One lean system they owned — built around how they actually work — would replace the lot, cost less over any real timeframe, and turn the data they’re currently re-typing into something they could automate. They didn’t have a tooling problem. They had a “we kept buying instead of building” problem.

Who this isn’t for

If you want zero technical involvement and the lowest possible monthly line item this quarter, buy something and move on — genuinely, that’s the right call for you, and we don’t need to talk.

This is for people who want leverage: who’d rather own the thing their business runs on than rent it, and who understand that a few weeks of building now is how you stop paying rent forever.

The call, in one line

Buy the commodity. Build the thing that’s yours. And when you build, MVP it first, bank the money you’d have spent renting, and compound from there.

This is one of my playbooks — the same honest decision help runs through when you actually need a fractional CTO and how to evaluate a software quote. If you’ve already decided to build, how I’d build the MVP is the next step.

If you want to talk through the build-or-buy call for your specific situation, talk to me — it’s usually a 20-minute conversation that saves a five-figure mistake. And if what you need turns out to be a full system with a team and a process behind it, that’s exactly what my agency, Digital Royalty, is for.