Guide
Build vs. subscribe: when custom software is worth it
Off-the-shelf software is the right call more often than not — it's fast, cheap to start, and someone else maintains it. But there's a point where renting stops paying off and owning starts to. Knowing where that line is saves you from both mistakes: building what you should have rented, and renting what you should have built.
By Miguel Alejandro Hayes· Founder, Hayes Projects
What a subscription really is
A SaaS subscription is a rental. You get software you didn't have to build, kept up to date, for a monthly fee — a great deal when the tool fits your needs and the price is small. Most businesses should run on off-the-shelf tools for most things, and that's not a compromise, it's good sense.
The catch shows up over time. The fee is forever and tends to rise. Your data and workflow live inside someone else's product, so leaving gets harder the longer you stay — that's lock-in. And you get the tool the vendor built for everyone, not the one shaped around how you actually work. None of that is a problem until it is.
When building starts to make sense
Custom software earns its cost in a few specific situations. When a process is core to how you make money and no off-the-shelf tool fits it well. When you're paying for several subscriptions plus the manual work of gluing them together, and the total rivals a build. When the per-seat fees keep climbing as you grow. Or when the workflow is your edge — something a competitor can't just buy the same tool to copy.
In those cases you're not paying for features you could rent; you're paying for fit and ownership. The build is a one-time cost that turns a growing rent into an asset you control — the code, the data, the workflow, all yours, with no one able to change the terms on you.
A sane way to decide
Don't build to replace a $30/month tool that works fine — that's effort spent for nothing. Do look hard at the places where you're stacking subscriptions, paying rising per-seat fees, or bending your business around a tool that doesn't quite fit. Add up what you pay yearly, including the manual glue work, and compare it to a one-time build that fits and that you own.
And whatever you build, insist on ownership: the code, the data, and the access should be yours, with no lock-in. A short paid validation can define the scope and the real number before you commit — so it's a decision, not a leap. If you want a starting point, we can map which of your processes are worth owning and which are fine to keep renting.
Frequently asked
Should I build software to replace my SaaS tools?
+
Usually not for tools that fit and cost little — renting those is smart. Building pays off when a process is core to your business, when stacked subscriptions plus manual glue-work rival a build, or when per-seat fees climb as you grow. Compare the yearly cost to a one-time build you own.
Isn't building custom software risky and expensive?
+
It can be, done badly. The way to de-risk it is a short paid validation that defines scope and the real cost first, then shipping the highest-return piece before committing to the rest. You pay for a plan, not a guess.
What happens if I stop working with the developer?
+
If you own it, nothing breaks: you have the code, the data, and the access, and anyone can pick it up. That's the whole point of insisting on ownership and no lock-in — you're not trading one dependency for another.
About the author
Miguel Alejandro Hayes — Founder, Hayes Projects
Economist and essayist turned developer. He founded Hayes Projects, a Miami venture studio and custom software lab, to build software that ships, scales and solves real problems.
Meet the founder→Not sure whether to build or keep renting? Book 20 minutes — no pitch — and we’ll map which of your processes are worth owning.
Book 20 min — no pitch →