Rent vs Own: The Math Nobody Shows You

I have sat on both sides of this table.

For a decade I was the vendor. OOMDO, the agency I co-founded and ran from 2012 to 2023, drove $60M+ in client sales with a team of 20+ and proprietary lead-capture and conversion tech. I built pricing, I wrote renewal letters, and I know exactly which clauses make a client easy to keep. Since then I have spent years on the buying side as an operator and an engineer: signing for tools, ripping tools out, and replacing some of them with systems the business owns outright.

This guide is the math I wish someone had put in front of me before my first vendor contract. Not the demo math. The five-year math.

The invoice is not the price

Rented software is priced to look small. A monthly number, per seat or per rooftop, that fits comfortably under a single deal's gross. That framing is deliberate, and it works, because almost nobody multiplies.

The real price has four parts the invoice never shows:

1. The escalator. Renewal increases compound the same way interest does.
2. The add-ons. The module you actually needed was never in the base tier.
3. The integration tax. Connecting the tool to your CRM and DMS costs setup fees, and sometimes a monthly fee, to access your own data.
4. The exit. Getting your history out at the end, if you can get it at all, costs time, money, and leverage.

Per-seat math compounds quietly

Per-seat pricing is the quietest of these. A fee that sounds trivial per user becomes a real number across a sales floor, a BDC, and the managers who all need logins. Per-rooftop pricing does the same thing to groups: the system costs the vendor roughly the same to run for one store or twelve, but the invoice multiplies by twelve. Owned systems do not behave this way. Code does not charge per seat.

Run the quick version on a napkin. Say a tool costs $79 per user per month, and between the floor, the BDC, and the desk you carry 25 logins. That is $23,700 a year, before the renewal letter, for one tool. Stack five tools with that shape and the store is carrying a six-figure rent bill that got approved $79 at a time. Invented numbers, real shape. Nobody signed off on the total, because the total never appeared on any document anyone signed.

The illustrative five-year table

Let me show the shape with deliberately round, made-up numbers. These are not quotes from any vendor and not figures from any store. Build your own version from your own invoices; the shape is the point.

Say your store rents a stack of point tools, chat, equity mining, a reporting layer, a desking add-on, for $2,500 a month: $30,000 in year one, with a 7% increase at each renewal. And say the owned alternative costs $60,000 to design and build in year one, plus $15,000 a year to host, maintain, and improve.

Illustrative numbers, remember. But look at the shape.

The lines cross in year four. By year five the rented stack has cost roughly $37,000 more, and the gap widens every year after, because year six rent is around $42,000 and climbing while the owned system holds steady. More important than the gap: at the end of year five, rent has bought you nothing you keep. Own has bought you an asset: code, data, workflows, and the right to change all three.

Run the same table for a dealer group and the math gets brutal. Per-rooftop rent multiplies by store count. An owned system mostly does not.

And this table still understates the case, because it leaves out the cost that decides more renewals than price ever does.

Switching costs are the real product

Here is what a decade on the selling side taught me: a vendor's pricing power at renewal is exactly proportional to how much it would hurt you to leave. Lock-in is not an accident of the product. For many vendors, lock-in is the product, and the software is the delivery mechanism.

Switching costs come in four flavors:

• Data hostage. Your history lives in their format, behind their export policy. Years of customer conversations, recordings, and outcomes you cannot take with you.
• Integration gravity. Everything else in the store is wired through their pipes, so replacing one tool means re-plumbing five.
• Training debt. Two years of muscle memory across your whole team, repriced to zero the day you switch.
• Process capture. Your workflow has quietly reshaped itself around the tool's assumptions, so the tool now looks essential to a process the tool created.

When a salesperson tells you the platform gets more valuable the longer you use it, listen carefully. From your side of the table, that sentence often means leaving gets more expensive the longer you stay. Sometimes both are true. Know which one you are buying.

You can put a number on your own lock-in, and you should, once a year. Price the exit while you are still happy: request a full export and time how long it actually takes, list every integration that would need re-plumbing, estimate the retraining hours, and write down everything the vendor owns that you would have to replace, from phone numbers to templates to history. That figure is your real renewal price. Bring it to the negotiation, because the vendor already has.

Build vs buy vs own

Buying is renting; the word on the contract does not change the economics. Building means your own payroll writes the software. And owning is the third door most dealers never get shown: commission the system, pay for the build, and hold the keys. The code, the data, the infrastructure, the right to modify. You do not need a dev team on payroll to own software, any more than you need to be a general contractor to own your showroom.

Here is the framework I use when I am deciding which door a given system belongs behind:

The pattern that falls out of that table is consistent: rent the commodity, own the edge. Payroll, e-signature, telecom: rent them and never think about them again. The system that captures your leads, scores your opportunities, and holds your customer history? That is your edge and your equity. Renting your edge means funding a vendor's moat with your own operating data.

Two honest warnings about the third door, from someone who builds behind it. First, owning obligates you: an owned system needs a budget line for maintenance and a person who answers for it, the same way a service drive needs a manager. Second, the build quote matters less than the builder's exit terms. Commissioning a system from a developer who keeps the keys is renting with extra steps. The contract should put the code in your repository, the data in your warehouse, and the infrastructure in accounts you control, from day one, not at some future handover.

The clauses that decide leverage

Price gets negotiated once, at signing, when your leverage is highest. Leverage gets decided by clauses most buyers never read. Before you care about the monthly number, read for these:

• Data export. Full export, machine-readable format, on demand, at no fee, including activity history and recordings, not just contact records. If export costs extra or takes thirty days, that is not an export clause. That is a ransom note with a schedule.
• Portability. Who owns the configurations, templates, integrations, and anything trained or tuned on your data? Ask specifically about call-tracking numbers: if the vendor owns the numbers your customers have been dialing for years, every ad those numbers appear on becomes a switching cost.
• Termination. Notice window, read-only access to your data after termination, certified deletion when you ask for it, and no auto-renew that is longer than the original term.
• Escalation cap. A written ceiling on annual increases. No cap means the five-year table above is the optimistic version.
• Raw access. Your analytics stack receives raw events, not just the vendor's dashboard. This is the clause that keeps your attribution vendor-independent.

A vendor who agrees to these readily is a vendor planning to keep you with the product. A vendor who fights them is telling you, in writing, what the renewal conversation will feel like in three years. Believe them.

One more note from the vendor side of the table: the time to win these clauses is before the first invoice, when the salesperson has a quota and you have alternatives. Ask early, in the first conversation, and be visibly willing to walk. After two years of integration and training, you are not negotiating anymore. You are asking.

When renting is the right call

I sold rented software for ten years, and plenty of it was the right call for the store buying it. Owning everything is not the lesson. Owning deliberately is.

Rent when:

• The function is a true commodity and vendors compete on price. Competition is your escalation cap.
• The category changes faster than you would maintain. Compliance-heavy and OEM-mandated categories punish owners.
• You are still learning the shape of the problem. Rent first, learn what you actually use, then own the version you keep. A year of rent as tuition is cheap compared to building the wrong thing.
• Nobody in the building will own the system. Owned software without an owner rots. If you cannot name the person, rent.
• The vendor's scale is the feature: marketplace audiences and cross-market data you could never assemble alone.

And one rule that overrides the whole list: never rent the system of record for your customer history without a full-export clause, no matter how good the demo is. Whatever else you rent casually, the data that compounds is the one part of the stack you cannot rebuild later. Tools are replaceable. Ten years of customer conversations are not.

The discipline is to make rent a decision instead of a default. Every rented system should be able to answer one question annually: what would leaving cost us, and is that number shrinking or growing?

Read your own invoices

Here is the homework, and it takes one afternoon. Pull twelve months of tech invoices. Sort them into rent-the-commodity and rent-the-edge. For everything in the second pile, build the five-year table with your real numbers and your real renewal history, then read the contract for the five clauses above.

Most stores that do this find at least one system where they are funding a vendor's moat with their own data, at compounding prices, with no exit clause. That system is the candidate for the third door.

Walking stores through that decision, and building the owned version when the math says own, is the work I do. See the work for systems I have built and pricing for how an engagement starts.