Three people asked me the same question this month. Can you build this so we own it?

Five years ago I’d have talked every one of them out of it. I spent thirteen years at Comcast Labs watching custom builds turn into maintenance bills. The first version was never the problem. The tenth was. Somebody had to keep it running, patch it, and change it every time the business changed, and renting made that somebody else’s problem. For most of my career that was the right trade.

I don’t give that answer anymore. Here’s why, and how to tell if it applies to you.

The pattern we keep seeing

Buyers are walking into first calls asking to own the thing. Not license it. Own it.

AI didn’t make custom software free. It made the part that used to kill you, the maintenance and the changes, cheap enough that ownership is back on the table. Meanwhile renting got worse. Seat pricing punishes you for growing. The roadmap goes wherever the vendor’s biggest customer wants it to go. Both sides moved at once and most companies are still doing math from five years ago.

That’s why the question keeps coming up. Buyers didn’t get braver. The math moved and they noticed before the vendors did.

Try this tomorrow

Pull up your next renewal. Three questions, five minutes.

What is the job? Not the features. One sentence. “Takes customer messages and turns them into tickets.” If you can’t say it in one sentence, renew it. The job is too big to rebuild.

What would it take to walk away? Can you get your data out, and does anything else break if this tool disappears? If leaving is easy, you have leverage either way. If leaving is hard, that’s why the price keeps going up.

When did we last question this line? If the answer is never, the math was done under conditions that don’t exist anymore.

One sentence job, easy to leave, never questioned. That’s the one worth pricing an alternative for. Everything else, renew and move on. You’re not looking for a reason to cancel everything. You’re looking for the one tool where the math flipped and nobody noticed.

What I’d renew every time

Since I’m telling people to build, here’s where I won’t.

• Anything with a compliance stamp. Payroll, accounting, tax, anything an auditor expects to see a known name on. The vendor’s liability is part of what you’re paying for.

• Anything where the network is the product. Payment processors, marketplaces, scheduling tools your customers already have on their phones. You can’t build the other side of the network.

• Anything your whole industry runs on. If every peer, partner, and new hire already knows the tool, the switching cost isn’t the software. It’s the people.

If your resented renewal is on this list, resent it and renew it. The build case is for the narrow tools around these.

One thing worth knowing

“We own it” means three different things.

There’s the code, the logic that makes it yours. There’s the data, everything it learns from and everything it produces. And there’s the model, the AI underneath doing the reading and writing.

You can own the first two and rent the third. Most companies should. The model keeps getting cheaper and better every few months, and renting it means you can swap it when something better ships. Owning the code and the data is what makes that swap yours to make instead of a vendor’s. That’s the real reason the math moved.

We support ownership models and the details get settled at scoping. But know the three layers and you’re a sharper buyer no matter who you build with.

The short version

If a renewal is coming and you can’t say what the tool does in one sentence, renew it. If you can, and you resent the bill, it’s worth a conversation.

That’s what I do all day. Book 30 minutes

Shawn