Rent what you can replace. Own what runs your business.
Some of the software your company depends on is a commodity you can safely rent. Some of it is too critical to leave in someone else's hands. Here's how to tell the difference — before a renewal notice forces the question.
Most of the software your business runs on isn't bought — it's rented. You pay per month, per user, or per usage, and in return someone else keeps it running. Most of the time that's exactly the right deal. But there's a risk owners rarely price in: for the tools your operation genuinely depends on, the terms and the price can change at renewal — and by the time they do, moving is expensive enough that you don't really have a choice. It's worth thinking about before a renewal notice forces the question, not after.
Renting is usually the right call
We tell clients this on most projects: don't build what you can rent. Email, video calls, standard accounting, payments, storage — these are commodities. Someone else maintains them, patches them, and improves them, and you get all of that for a predictable monthly fee. Building your own version of a solved problem is almost always a waste of money. The goal was never to own everything.
Until a tool becomes load-bearing
The risk shows up when a rented tool quietly stops being a convenience and becomes the thing your business runs on. Your data lives in it. Your team's daily work flows through it. Other systems are wired into it. At that point the cost of leaving — re-platforming, retraining, rebuilding integrations, the operational risk of the switch — becomes large. And that switching cost is precisely what removes your leverage if the renewal terms change. The tool didn't get worse; your position did.
A simple test
For each major piece of software you depend on, ask one question: what happens if the price doubles at renewal? If the honest answer is 'we pay it, because we can't move,' you have a lock-in exposure. That's not a reason to panic — it's a reason to plan. The time to reduce that exposure is while you still have room to move, not the week the new pricing lands.
- Map your stack. List every tool the business depends on and rate each one on how hard — and how expensive — it would be to switch away from it.
- For the tools that are both critical and hard to switch, ask whether the work they do is generic, or whether it's a workflow specific enough to your business that owning a custom version would be cheaper over five years.
- Keep your data exportable. If a tool won't let you get your data out in an open format, that difficulty is itself a form of lock-in.
- Look at renewals 9–12 months ahead, not the week before. Having time to move changes the whole conversation.
- Build the parts that are your competitive advantage. Rent the parts that aren't.
What owning actually buys you
Software you own can't be repriced overnight, and its terms can't be rewritten without your say. That's the real case for building the parts that matter to you: you own the code, you own the data, and no one else can change the deal underneath you. It isn't about building everything — that would be its own kind of waste. It's about being deliberate over which few pieces are too important to rent, and making sure those are the ones you control.
The way we usually start is simple: a 30-minute call to look at which parts of your business are genuinely critical and which are fine to rent. Often the answer is that renting is still right — and we'll say so. Where it isn't, we can show you where owning a small, specific piece would pay for itself. Either way, you leave knowing where you stand.