What Build vs Buy Actually Means
Build vs buy is the choice between building a piece of software you’ll own and renting a ready-made one off the shelf. That’s the surface. Underneath, it’s a choice between keeping leverage you compound and paying rent for limited access — which is why it matters far more than it looks.
Most people frame it as a simple cost comparison: building is expensive and slow, buying is cheap and fast, so buy. That framing is wrong, and it’s wrong in a way that costs companies a great deal of money over time. The real decision isn’t “which is cheaper this quarter.” It’s “which do I want to own.”
When the build-vs-buy question actually matters
It matters every time you catch yourself about to buy software to run a part of your business — and it matters most for the parts that are actually yours.
Here’s the distinction that decides everything: is this thing a commodity, or is it your edge? Payroll, accounting, email, card processing — commodities. Mature, regulated, identical for everyone, not where you compete. Buy those, every time; building them is risk you don’t need. But the workflow only your business runs, the way you actually serve your clients, the operation that is the company — that’s not a commodity, and no off-the-shelf tool will ever fit it, because it was built for the average of ten thousand other companies. That’s where build vs buy gets real, and where the default “just buy something” quietly costs you ownership of your own edge.
So the question matters precisely when the software touches what makes you you. For everything generic around the edges, rent it and forget it. For the core, stop and think hard before you hand it to a vendor.
Why “buy” costs more than the sticker
The reason I lean build for the core comes down to what buying actually means, defined honestly rather than as the vendor frames it.
When you buy, you don’t own a solution — you rent access to one. You pay every month forever, and that number only climbs: per seat as you grow, per tier as the feature you need moves behind the next paywall. You fund a product that’s 80% built for someone who isn’t you. You still spend weeks integrating it into the rest of your stack. And — the one that matters most — your data lives in their system, in their shape, reachable only on their terms. “Buy” is a verb that should really be “rent,” and once you read it that way the decision looks different.
Building, done my way, isn’t the heroic months-long project people imagine either. You build the lean slice that does your actual job — the 20% you genuinely use — fast, and you own it. The cost is often roughly what year one of the subscription would have been, and then the maths inverts: every year you own starts further ahead, every year you rent starts from zero.
When buying is the right call
Don’t take this as “always build” — distrust anyone who’s dogmatic about it, including me if I ever sound it. Buy the commodity. Buy the mature, undifferentiated, heavily-regulated thing that millions already rely on and that getting wrong has legal consequences. Building your own payroll engine to save a few pounds a month isn’t leverage, it’s a liability you volunteered for. The rule is clean: buy the commodity, build the thing that’s actually yours. The skill is telling which is which, honestly, without ego on either side.
The worldview throughout is simple: own your data and systems so you can do more with them, and prefer the simplest thing that solves the real problem. Build vs buy is that worldview applied to a purchase order. Most of the time, for the core of your business, the simplest thing that you also own wins.
Where to go next
I define this plainly because “build vs buy” usually arrives pre-loaded with the assumption that buying is the sensible default — and that assumption is the whole problem. It’s inseparable from owning your data, which is what “build” really buys you, and from MVP, which is how you build without the heroic cost.
The actual decision framework — how I’d weigh it for your specific situation, with the MVP-first math in full — is my build-or-buy playbook. If you’re staring at a buy decision right now and want a straight second opinion, tell me what you’re about to buy and I’ll tell you whether you should.