Build vs Buy Software: A Plain-English Framework for Small Business Owners
Should a small business buy off-the-shelf software or build custom? A simple framework with real numbers to help owners decide without guesswork.
TL;DR
Most small businesses do not need custom software. They need a few of their existing tools to stop fighting each other. Buy off-the-shelf when the workflow is the same as every other business in your industry. Build custom (or connect what you already pay for) when the workflow is how you actually make money.
Key takeaways
- Buy off-the-shelf software for commodity work like accounting, payroll, email, and basic scheduling.
- Build custom software when the workflow is unique to how your business makes money and you are paying for three or more tools to fake one process.
- A third option (integration and automation) usually costs 10-20% of a full custom build and solves most "tools that do not talk" problems.
- Office workers lose around 10% of their week to manual data entry, and manual entry carries a 1-4% error rate (ProcessMaker, 2024; Smartsheet).
- If your SaaS bill for a single workflow exceeds the one-time build cost over 2-3 years, building is worth pricing out.
A build vs buy decision is the choice between paying for pre-made software (buy), commissioning software made for your business (build), or connecting tools you already own so they behave like one system (glue).
What are the three options, in plain English?
There are three options, not two: buy, build, or glue. Most owners only consider the first two and overpay either way.
- Off-the-shelf software is pre-made software many businesses use, like QuickBooks or Square. You rent it monthly.
- Custom software is a tool built specifically for your business. You pay once to build it, then a smaller amount to maintain it.
- Integration and automation ("glue") is a small piece of custom code that makes your existing tools pass data to each other automatically.
When is buying off-the-shelf the right call?
Buy when the workflow is a commodity that looks the same in every business your size. Accounting, payroll, email marketing, basic CRM, calendar scheduling, and card payments are solved problems. Thousands of companies already pay engineers to make that software better every month, and you cannot out-build them on a small budget.
If you find yourself thinking "we do payroll just like everyone else," that is the signal to buy.
When should you consider building custom?
Build when the workflow is unique to how your business makes money and existing tools cannot fit it without duct tape. Three signs:
- You pay for three or more SaaS tools to fake one workflow.
- Someone on your team spends multiple hours a week copying data between systems.
- Your three-year SaaS cost for that workflow is higher than a one-time build.
Off-the-shelf software often costs more than custom over three or more years for non-commodity workflows (Syberry).
What is the middle option most owners miss?
The middle option is integration, also called automation or "glue." It usually costs 10-20% of a full custom build because nobody is rebuilding QuickBooks or Square. A developer writes a small connector that moves data between the tools you already pay for.
This matters because 69% of employees switch between up to 10 apps per hour (Tallyfy), and 46% of small businesses say paper-intensive processes waste time every day (FileCenter). Most of that pain is a connection problem, not a software problem.
A 5-question decision checklist
Score each question yes (1) or no (0):
- Does every business in my industry run this workflow the same way?
- Is there a well-reviewed SaaS tool that already covers 80% of it?
- Is the manual work under two hours per week?
- Is my three-year SaaS cost lower than a one-time build quote?
- Am I fine giving up custom features to keep things simple?
4-5 yes: buy off-the-shelf. 2-3 yes: look at integration/automation first. 0-1 yes: price a custom build.
A worked example: the Austin bakery
A 14-person specialty bakery in Austin uses Square for POS, QuickBooks for accounting, Google Sheets for custom cake orders, and Mailchimp for email. The assistant spends about 6 hours a week copying custom cake orders from email into the sheet, then into Square, then re-keying weekly totals into QuickBooks.
The math:
- Labor: 6 hours × 52 weeks × $22/hr = $6,864/yr
- Errors: 4% of ~800 orders/yr = ~32 mis-keyed orders × $40 = $1,280/yr
- Total drag: ~$8,144/yr
The three paths:
- Buy: a bakery-specific all-in-one POS at $400/mo = $4,800/yr, plus migration pain and losing Square's payment rates.
- Build: $35,000-$60,000 full custom order system. Overkill for this size.
- Glue: $4,000-$7,000 one-time integration that pulls web-form orders into Square and QuickBooks. Payback in 6-10 months, and the bakery keeps the tools the team already knows.
For this bakery, glue wins. For a 200-person manufacturer with a one-of-a-kind production schedule, build would win. For a brand-new solo consultant, buy would win.
FAQ
Is custom software only for big companies?
No. Small businesses regularly commission custom tools that cost $4,000 to $20,000, especially small integrations and internal dashboards. The "custom software is for enterprises" idea is outdated.
How much does custom software cost for a small business?
A small integration or single-purpose tool usually costs $4,000 to $15,000. A full custom system that replaces several SaaS products typically runs $30,000 to $80,000. Maintenance afterward is usually 10-20% of the build cost per year.
What is the difference between custom software and an integration/automation?
Custom software is a new application built from scratch. An integration is a small piece of code that connects tools you already pay for so they share data automatically. Integrations are much cheaper because they reuse existing software.
How long does it take to build a small custom tool?
A focused integration or internal tool takes 3-8 weeks. A full custom system that replaces multiple SaaS products takes 3-6 months. Anything advertised as "two weeks for a full system" is usually a template, not a custom build.
What happens to my SaaS subscriptions if I build custom?
You usually keep the commodity ones (accounting, payroll, email) and cancel the SaaS products you were using to patch over a missing workflow. Most builds replace 1-3 subscriptions, not all of them.
How do I know if my workflow is "unique enough" to justify building?
Ask whether the workflow is how you make money or just how you run the business. Payroll is how you run the business. Custom cake orders, custom quoting, custom routing, and custom production are how you make money. Those are the workflows worth building for.
A quick note from us
At RevenueLyft we build custom software and automations for small businesses, and we tell owners to buy off-the-shelf more often than we tell them to build. If you want a second opinion on your stack, we offer a free decision review: we look at the tools you pay for today and tell you honestly whether to build, buy, or just connect what you already have.
Sources
Want help building this for your business?
We build the automations and custom software so you don't have to. Free first call, no pressure.
Book a Free Consultation