At some point in every business, the question stops being “do we need software for this?” and becomes “how do we get it?” There are now two honest answers. You can buy one. You can build one. Both are reasonable, and both have costs that are easy to understate if you are not looking at the full picture.
This is a decision your whole business runs on for the next five to ten years, so it deserves more than a gut feeling. Some people feel that if you can get it in the app store, you should not be paying to build. Others feel that if your business is yours, your software should be yours too. Neither is wrong. The answer depends on what the software actually does for you, and on which of your costs are visible and which are hiding.
In this post we walk through both options the way we walk them with our clients. What buying gets you, and what it quietly costs. What building gets you, and what it quietly costs. A handful of questions that separate a good decision from a bad one. And a worked example with real numbers.
Why this question is harder than it looks
Most of us default to “just buy” because the buying decision takes twenty minutes. You compare three tools, check the pricing page, run a card, and be done. The build decision takes a conversation: a quote, a timeline, a scope. The first feels like shopping, the second like a project.
But the twenty-minute decision keeps making itself. Every tool you buy adds a monthly charge, an update cycle, and a small chance the company behind it raises its prices or disappears. And every tool you did not buy keeps asking for your time, in the shape of the workarounds: the extra click, the manual copy-paste, the “close enough” report that answers a different question than the one you need.
Neither option is free. Buying trades cash for friction. Building trades cash and time for fit. The decision is about which cost your business can absorb more easily, in which part of the stack.
The layers of a small business tech stack
Before you decide, it helps to know what you are actually buying or building. Most small business software needs fall into a small number of layers, and the right answer usually changes from layer to layer.
- Identity and access. Who can log in, and what they can see. Almost always fine to buy, or use what your core tool already includes.
- The record. Where the important data lives: clients, jobs, inventory, orders. This is your company’s memory, and you will live with this choice the longest.
- The work. The software that runs your actual daily process: scheduling, dispatching, quoting, intake, tracking. This is where buy versus build splits widest, because it is where your process is either standard or not.
- The money. Invoicing, payments, payroll, tax. Most of the time, buy it. The stakes are high, and the vendors have already paid the tuition.
- The glue. Automations, integrations, and reports that connect the pieces. Frequently the first place a small custom build earns its keep, because off-the-shelf tools only talk to each other in the ways the vendors have decided to support.
You are not choosing “buy or build” for your whole business. You are choosing, layer by layer. And the pattern that works for most small businesses is a boring mix: buy the standard layers, build the one or two that touch what makes your business yours.
What buying actually gets you
When you buy a SaaS tool, you are not just buying software. You are buying a set of promises from the company that made it.
It works on day one. The feature you need exists, tested by thousands of users who hit every bug before you did. The value is immediate, and that matters when the need is immediate.
You never own the maintenance. Updates, security patches, hosting, the small things that break at 4am – that is the vendor’s job. For a team without a dedicated IT person, that is a real and permanent saving.
The ecosystem is already there. Integrations with the tools you already run, a community of users who know the workarounds, support that answers in hours. A tool that fits your stack well is worth more than a better-but-isolated one.
Now the costs that are not on the pricing page.
You pay per seat, and seats grow. The price today is for the team you have. The team in three years is bigger, and the bill follows. Your software bill is tied to your headcount for as long as you stay.
You pay for the whole toolbox to use one drawer. Every subscription is priced to cover features you do not use, aimed at customers who are not you. You buy the platform’s ambition at retail, for the slice you actually need.
The process bends to the tool. This is the big one, and the one that compounds. The moment your tool does something a specific way, your team stops doing it your way. The gap becomes a permanent daily tax, paid in clicks and workarounds, until you switch – and switching is where the bill finally shows up.
Switching is expensive. Your data in their format, your team trained on their interface, your other tools wired into theirs – leaving is a project, not a click. The real cost of switching runs several times higher than most companies estimate, and most do not estimate until they are actually leaving. That asymmetry, easy to enter and expensive to leave, is why a good fit today matters more than a low price today.
What building actually gets you
When you commission custom software, you are buying the opposite set of promises.
You are the only customer, and the customer for life. The software is designed around your process from the first drawing, not around the average of ten thousand other businesses. The workarounds disappear, because there is nothing to work around.
The price does not grow with your headcount. A custom tool is yours. Adding the sixth person costs you nothing. The per-seat escalator, the “upgrade your tier” emails, the annual price increase – none of it applies.
You own the data, in a format you control. Your clients, your history, your numbers, stored and portable the way you want them. Owning the record means no one else holds the key.
It can keep growing with you. When your process changes, the tool can change with it, instead of you changing your process to survive the tool.
Now the costs that are not in the quote.
The money is front-loaded. A subscription is a small monthly bill you have been trained to ignore. A build is one number, up front, that has to be real and present. Most small businesses carry a steady drip more easily than a single payment, and that psychology is part of the decision.
It is slower to start. A focused custom tool takes weeks to a few months, not days. If the problem is urgent and the tool has to exist this week, the build is not the answer.
Maintenance is now your problem. Even a well-built tool needs a floor of care: updates, the occasional fix, the improvements that pile up. So the honest custom cost is the build price plus a maintenance line that shows up every year. Skip the maintenance and the savings start to leak back out.
The typical ranges are useful for setting expectations. Focused, single-purpose tools for a small team generally land in the low-to-mid five figures for the build, with maintenance in the low thousands a year. Once a project grows past that, the decision should be made on paper, not on a handshake.
The five questions that actually decide it
Once you have seen both sides, the decision stops being a mood and starts being a set of questions. Run these before you sign or before you scope.
-
Is this process standard, or is it yours? If ten thousand other businesses do this step the same way, a well-built off-the-shelf tool will fit well and the build premium is hard to justify. If your process is different in the ways that matter, that difference is exactly what a build can capture and a subscription can only approximate.
-
How much of the tool do you actually need? If you need the whole thing, buying wins on price. If you need a drawer, the gap between “what you need” and “what you pay for” is the hidden cost of buying – and the hidden savings of building.
-
How long do you have? A need that has to be solved this week gets a subscription. A need that can wait for a few weeks of careful work has room for a build.
-
Can you maintain it if you have to? If you cannot realistically fund a small amount of care every year, the tool will quietly degrade and the savings will quietly stop.
-
What happens if you want to leave? For anything you buy, be able to answer: how does the data get out, in what format, and what does it cost? If the answer is “we have to find out at renewal time,” the vendor is doing your planning for you. For anything you build, the answer is “it is yours.”
Answer these in order, and the decision usually sorts itself out by question three.
When buying is the right call
The case for buying is stronger than most small businesses give it credit for, and buying badly is worse than not buying at all. Buying is the right call when:
- The job is standard. Invoicing, payroll, email, document signing, general scheduling: the problem is so common that the best tool on the market is very good.
- The need is urgent. The problem is happening now, and the workaround is costing real money every week it takes to build.
- The price is small relative to the problem. If the tool costs $40 a month and the problem costs $400 a month, the build case has to be very strong to beat the arithmetic.
- Your team already lives in the ecosystem. The tool plays well with the other tools you run.
When you buy, buy for fit, not for the lowest price. The vendor with the slightly higher price that matches your process costs less every month than the cheap one you have to work around, because the workaround has a price too.
When building is the right call
Building is the right call when:
- The software touches what your business is actually known for. If your clients hire you because of how you run the work, and the tool fights you at every turn, that fight is happening on the customer-facing side.
- You are spending real hours every week to close the gap. If the team is losing four or five hours a week to manual workarounds, those hours have a number on them, and the number is usually large enough to carry a build.
- The data is the asset. If the record you keep is the thing you would fight to protect, the question is not just “where does it live” but “do we own it.”
- You are growing, and the price is following you. A custom tool is the one line in your budget that does not rise the month you hire.
When you build, build narrow. The tool that does one thing around your process, beautifully, beats the custom platform that tries to be everything, badly.
What a good mix actually looks like
The stack you end up with should read like a decision, not a brand list. A typical small business that has done this on purpose:
- The money layer is bought: invoicing, payments, payroll. Standard, high stakes, proven.
- The communication layer is bought: email, chat, calendar. You are not going to build a better inbox.
- The core record is bought, chosen for data portability: a CRM or practice-management tool whose export you have actually tested.
- One or two pieces of the work layer are built: the tool that runs the process your clients hire you for, and the glue that reports it back without a human re-typing the numbers.
The test of a good stack is not how much it costs. It is how few of its pieces you think about. A well-built stack runs in the background and asks for your attention only when something is genuinely wrong.
A worked example, with the real numbers
A five-person team. Their core tool is a subscription at $30 per seat per month, and the team will grow to eight people over the next five years.
The buying side: five seats for three years ($30 x 12 x 5 x 3 = $5,400), then eight seats for two years ($30 x 12 x 8 x 2 = $5,760). The subscription totals about $11,200 – and you would still be paying the daily tax of the workarounds the whole time.
The building side: a focused custom tool at $15,000 up front, plus $1,200 a year of maintenance over five years ($6,000). The build totals $21,000.
On paper the build looks twice as expensive. But the build removes a gap the subscription never closed: three hours a week of manual work, at an all-in cost of $30 an hour – about $23,400 over five years. The subscription never saves those hours, because it was not built to close that gap. The build does. So the true five-year cost of the subscription is $11,200 plus $23,400 of hours, against $21,000 for the build. The build, which looked more expensive, ends up cheaper by roughly $13,000 – and you own the tool, the data, and the fit at the end of it.
The exact numbers change with your rates, headcount, and tool. The structure does not. Once the workaround hours have a real number on them, the gap between “the subscription is cheaper” and “the build is cheaper” closes faster than almost anyone expects.
The classic mistake on each side
On the buy side: collecting tools. The mistake is not buying. It is buying without a map, so the stack ends up with two tools doing the same job, none doing the one that matters, and the data split between them. Map your process first, find the gap, and only then ask whether the gap is a buy or a build.
On the build side: building the platform. The mistake is commissioning the custom thing the way you would commission a building: one project, one scope, a vision of everything. Custom software is not a house. It is a set of tools, and the ones that earn their cost are the narrow ones around your process.
And the mistake in the middle: deciding once. The tool you bought in year one is the one to look at hardest in year four, because it is the one whose fit has drifted furthest from where the business has gone.
The Acherus Take
When we help a business sort this out, we start the same way every time: map the process first, and let the gap speak. In almost every business, the stack sorts itself into the standard layers that are well-served by the tools everyone buys, and one or two places where the tool fights the process. Those places are where your hours are going, and where the build pays for itself.
The second thing we keep for the build is narrow. One thing, done around your process, with the data in your hands, priced so it does not grow with your headcount. The businesses that get the most out of custom software are not the ones with the biggest platforms. They are the ones with the quiet tool that runs the part of the work everyone else has to work around.
The third thing is the revisit. The answer you give in year one will not be the right answer in year four, because the business moved. Buy the standard. Build the distinctive. Keep the mix on a short leash, and check it every year. If the build case is real but the scope is fuzzy, that is exactly the kind of question we like to sit down with. You bring the process. We bring the arithmetic, and the tool that ends up running in the background where it belongs.
Frequently Asked Questions
How do I know if the problem is worth building for at all?
Put a number on the hours. Log a week of the workaround – the copy-paste, the re-typing, the manual report – total it, and multiply by what that time costs you, all-in. If the annual number is in the low four figures, a focused build pays for itself within a couple of years and keeps paying. If it is in the low three figures, buy the tool that closes the gap and move on.
How long does a focused custom build actually take?
For the kind of tool most small businesses need – one purpose, around one process, wired into the tools they already run – expect a few weeks to a couple of months from first conversation to first use. Anything you cannot picture as a first working version is a scope that should be cut, not funded.
Can I run custom software alongside my off-the-shelf tools?
Yes, and most good stacks are exactly that. The custom piece does the job the subscription cannot do well, and it talks to the subscriptions through their normal connections. The test is whether the data moves between them without a person. If it moves without a person, you are running a system. If it needs a person, you are running a mess with better branding.
About Acherus Inc.
Acherus is a software company that builds practical, well-engineered tools for small and growing businesses. We help owners and operators pick and implement the technology that actually fits how they work, so the software saves time instead of creating a new job.
© 2026 Acherus Inc. All rights reserved. This article is provided for general informational purposes and does not constitute professional advice. Prices and features are approximate and subject to change. Confirm details with each vendor before purchasing.