Rent or Own? A Practical Test for Every Tool in Your Stack

Quick answer: rent tools that are commodities, that change faster than you could keep up with, or that carry regulatory and security burden you do not want. Own the thin layer that is specific to how your business actually works. Most small businesses have this backwards: they rent their differentiator and build nothing.

Our tagline is built to be owned, not rented, so this is a biased essay. It is also the honest version, including the parts where renting wins.

When Renting Is Clearly Right

Some categories are not worth building, ever, and anyone telling you otherwise is selling hours.

• Anything with a compliance surface. Payment processing, payroll, tax calculation. You are not just buying software, you are buying somebody else's obligation to keep up with rule changes.
• Genuine commodities. Email hosting, calendars, video calls, file storage. The market has driven these to a few dollars a seat. Nothing you build competes.
• Fast-moving categories. If the field changes every quarter, a vendor amortizes that across thousands of customers. You would amortize it across one.
• Anything you have not used yet. Renting is how you find out what you actually need. Build after you know, not before.

When Owning Wins

The case for owning is rarely about the monthly number alone. Four signals matter more.

1. The subscription is a tax on a stable process

If a workflow has not meaningfully changed in two years and you are paying per seat or per record for it, you are renting something that stopped evolving. The vendor is not improving it for you anymore. You are just paying rent on a shape that is now fixed.

2. You are paying for a platform to use one feature

The classic pattern: a $400 a month tool where the team touches one report and one automation. Platform pricing assumes you use the platform. When you use a corner of it, the effective cost of that corner is absurd, and it is usually the easiest thing in the world to replicate.

3. The process is your differentiator

If the way you do something is genuinely part of why customers pick you, running it inside a generic tool forces you to bend your advantage into someone else's data model. You end up with workarounds, custom fields nobody understands, and a process that is slightly worse than what you actually do.

4. Your data is hostage

Export options tell you a lot. If getting your own records out means a CSV missing half the relationships, or a support ticket, or a plan upgrade, you do not have leverage. Migration cost is the real switching cost, and vendors know it. Pricing tends to discover that fact around year three.

The Math People Get Wrong

Break-even is not build cost divided by monthly fee. That calculation ignores the entire right-hand column of what owning actually costs.

Owned software is not free after launch. It needs a host, security updates, and someone who can change it when the business changes. Budget for that honestly or the comparison is fiction. In practice, for a focused internal tool, that ongoing cost tends to be a small fraction of a platform subscription, which is why the break-even usually lands somewhere in the first two years rather than never. But run your own numbers, including the maintenance line.

The Pattern That Usually Wins: Rent the Commodity, Own the Layer

This is rarely an all-or-nothing decision, and treating it that way is how people end up either paying for eleven overlapping platforms or trying to rebuild an email client.

Keep renting the infrastructure. Keep the CRM if it earns its place. Then own the thin layer that encodes how your business specifically operates: the routing logic, the pricing rules, the quoting workflow, the client portal that matches your actual process. That layer is small, it changes slowly, and it is the part no vendor will ever fit properly. It is also the part that is cheapest to build and most expensive to rent, because platform pricing does not care that you only need one corner. That is exactly what our SaaS replacement work targets.

A Ten Minute Audit

• List every recurring software charge with its annual total. Sort descending. Most people are surprised by the sum and by the order.
• For each of the top five, write the one sentence describing what it actually does for you. Not what it advertises.
• Mark anything where that sentence describes a small, stable, business-specific process.
• For those, check the export. If your data does not come out clean, note it. That is lock-in, and it belongs in the cost.
• Whatever is left is your rent-forever list, and that is fine. Stop feeling bad about it.

The Broader Point

Every recurring cost is a decision your future self is obligated to keep funding. Sometimes that is a fair trade for real ongoing work someone else is doing on your behalf. Sometimes you are paying monthly for a decision that was made once and has not changed since.

The same reasoning applies inside your automations, where a model call re-derives an answer you already knew. We wrote about that in AI or Just Automation. Different layer, same question: are you paying repeatedly for something that only needed to be decided once?

Frequently Asked Questions

Is custom software cheaper than SaaS?

Not always, and the comparison is only honest if you include maintenance. Owned software still needs hosting, security updates, and someone to change it when the business changes. What it does not do is scale in price with seats, records, or volume, and it does not stop working when you stop paying. For a small, stable, business-specific workflow the break-even commonly lands within the first year or two. For commodity or compliance-heavy categories, renting usually stays cheaper indefinitely.

Which tools should I never build myself?

Anything carrying a compliance burden, such as payment processing, payroll, and tax calculation, where you are effectively buying a vendor's obligation to track rule changes. Also genuine commodities like email, calendars, storage, and video, where market pricing is already lower than your build cost. And anything you have not used long enough to know your real requirements.

How do I know if I am overpaying for a platform?

Write one sentence describing what the tool actually does for you day to day. If that sentence describes one report and one automation on a platform priced for full adoption, the effective cost of the part you use is very high, and that corner is usually straightforward to replicate.

What is vendor lock-in and how do I check for it?

Lock-in is when the cost of leaving exceeds the cost of staying, regardless of price increases. Test it by exporting your data today. If the export is missing relationships between records, requires a support ticket, or sits behind a higher plan, you have limited leverage and should count migration difficulty as part of the tool's real cost.