Look at the apps open on your screen right now. Odds are you didn't choose most of them. You inherited them. Your bookkeeper liked one. A CRM showed up in a Google search years ago. A scheduling tool came bundled with something else. Today, with AI doing a lot of the heavy lifting on code, nearly every one of those apps could be rebuilt around how your business actually works. That makes custom software vs off the shelf for a small business a real choice, maybe for the first time. The honest answer, though, is that most of your apps should stay exactly where they are.
The ceiling on building custom just got a lot lower
Five years ago, custom software meant a development shop, a six-figure quote, and a year of waiting. That's why "buy it off the shelf and make it work" became the default for every small business. It was the only sane choice.
That math changed. I've been building with AI every day since ChatGPT launched in November 2022, and the gap between "I wish our software did this" and "it does this now" has shrunk from months to days for a lot of tools. A quote builder that pulls from your past jobs. A lookup tool that answers questions from your own SOPs. A dashboard that shows one number you actually care about instead of forty you don't.
So yes, the title of this post is true. Almost every app on your desk is replaceable now.
Replaceable doesn't mean you should replace it
Here's the contrarian part. The fact that you can rebuild something is a terrible reason to rebuild it.
Software is moving fast right now. The tool you replace today might ship the exact feature you wanted next quarter. And every custom tool is something that has to be maintained, backed up and understood by somebody. That's a real cost, even when the build is cheap.
My default is boring on purpose: work with what you have first. Most of the pain I see in small businesses isn't that a tool is bad. It's that two decent tools don't talk to each other, so a person sits in the middle copying data from one to the other. That's a process problem, and it's usually fixed with a connection, not a rebuild.
Where off-the-shelf software runs out
Off-the-shelf tools are built for the average customer in your category. That's their strength and their limit. They start to hurt when:
- You've built workarounds on top of the tool (a spreadsheet next to the CRM, a sticky note system next to the scheduler).
- You pay for a big plan to get one feature, and the rest goes unused.
- Your process is genuinely different from your competitors', and that difference is why customers pick you.
- The vendor's roadmap and your needs keep heading in different directions.
One of those alone isn't a reason to build. Two or three on the same tool is a signal worth taking seriously.
A 5-question test: keep, connect, or rebuild
Pull up your list of software and run each tool through these five questions. Write the answers down. It takes about twenty minutes.
- Does anyone actually use it? If the honest answer is "barely," cancel it. That's not a build decision, it's a cleanup.
- Is it regulated or high-risk? Payroll, accounting, payments, anything with compliance attached. Keep it. Let the vendor carry that weight.
- Is the pain inside the tool or between tools? If people retype data from this app into another one, the fix is a connection. Mark it "connect."
- Have you built a workaround to make it fit? A side spreadsheet, a manual checklist, a shared inbox someone babysits. Mark it "rebuild candidate."
- Would it hurt to lose it tomorrow? If a custom version would carry real business risk without a backup plan, keep the vendor until you have one.
When you're done, most tools will land on "keep" or "connect." That's normal. You're looking for the one or two that keep fighting you.
What usually makes the rebuild list
In my experience, the best custom candidates are wrapped around your own knowledge and your own process, not generic accounting or payments. A few examples:
- Quoting and proposals. You know what a good quote looks like for your work. A form plus AI drafting from your past jobs beats copying last month's Word file.
- Internal knowledge. Binders and folder trees nobody opens. I helped a multi-location fire protection contractor turn SOP binders into an online training hub with role-based access and onboarding tracks. You can see that and other examples on my work page.
- Reporting. A single dashboard that pulls from the tools you already pay for, instead of logging into four of them on Sunday night.
- Intake and follow-up. The steps between "someone filled out the form" and "someone called them back" are almost always custom, whether you admit it or not.
If you want the dollar side of this before you decide anything, I broke down subscription costs in Do You Really Need 10 Software Subscriptions?, and I walk through a sample replacement step by step in this afternoon build walkthrough.
How I'd approach this
I'm a process guy before I'm a software guy. Most small businesses have good people and a product that works. The process in between is what breaks. So I don't start with your tech stack. I start with the one bottleneck that costs your team the most time each week.
From there it's the same order every time: cut what nobody uses, connect what's worth keeping, add AI where it actually saves hours, and build custom only for the piece that truly doesn't fit. When I build, I use n8n for workflows, Supabase for data, and Claude, ChatGPT or Gemini where AI helps. It runs in your accounts and you own all of it. The details are on how I work.
Frequently asked questions
Is custom software better than off-the-shelf software for a small business?
Neither wins by default. Off-the-shelf software is the right call when your process is standard and the tool fits it without workarounds. Custom is the right call when one tool keeps fighting how your business actually runs, and you've already tried connecting it to your other systems. Most small businesses I see need a few good off-the-shelf tools plus one or two custom pieces.
Which apps should a small business never rebuild?
Payroll, core accounting, payment processing, and anything heavily regulated. Those vendors carry compliance, tax tables and security work you don't want to own. Keep them, and connect them to everything else so nobody retypes data. The better rebuild candidates are tools wrapped around your own process and documents, like quoting, intake, internal knowledge, and reporting.
How long does it take to build a custom business app?
A focused tool that does one job, like a quote builder or an intake workflow, can be working in days. A tool that touches several systems or several roles takes longer, mostly because of permissions and edge cases, not the screens. I start with the single biggest bottleneck so something useful ships early instead of waiting on a giant project.
Who owns a custom app if you build it?
You do. Everything I build runs in accounts you control, and you own the workflows, the database and the documentation. If you ever stop working with me, the tool keeps running and any competent developer can pick it up. That's a big part of why custom can make sense: you stop renting a process you depend on.
Start with the tool that's fighting you
You don't need a new tech stack. You need to know which one tool, or which one gap between tools, is slowing your team down. If you want a second set of eyes on that, book a 30-minute conversation. Bring your biggest bottleneck and I'll tell you honestly whether to keep it, connect it, or rebuild it. No pitch.
