Build vs buy: a decision framework for SMB software.

The build vs buy question in one line

Buy what every business needs the same way. Build the one workflow that makes you money. The whole decision comes down to whether the job is generic or core, and how well a tool already fits it.

Most owners frame build vs buy as a money question. It is not, at least not at first. It is a fit question. A $20-a-month tool that does the job cleanly is a bargain. A $20-a-month tool you fight every day, plus three more like it that almost overlap, is the expensive option, even though each line item looks cheap.

So before you compare prices, ask one thing: is this software doing a generic job that thousands of businesses do the same way, or is it carrying the workflow that actually sets you apart? Email is generic. How you quote a job, schedule a crew, onboard a client, or track an order usually is not. Buy the first kind. Strongly consider building the second.

The scorecard below turns that gut call into five numbers you can defend.

The 5-factor build-vs-buy scorecard

Five factors decide the outcome more than any other: how core the workflow is, how well tools fit, whether seat costs are climbing, how much you need to own your data, and your timeline. Here is what each one looks like on the buy side and the build side.

The build column is highlighted because it is the column owners systematically underweight. Each row on its own is rarely decisive. The pattern across all five is.

How to use the scorecard

Score each factor 1 to 5, where 1 leans hard toward buying and 5 leans hard toward building. Add them up. The total tells you which way the decision actually points.

Go down the five factors and give each one a number from 1 to 5. A 1 means it strongly points to buy. A 5 means it strongly points to build. A 3 means it could go either way. Be honest, especially on "how core it is," because that is the factor people inflate to justify a build they already want.

Then total the five scores out of 25 and read it like this:

• 5 to 11: buy. The job is generic and a tool fits. Pay the subscription and move on. Custom software here is a trophy, not a tool.
• 12 to 18: hybrid or wait. Some factors push each way. Buy for now, watch the per-seat and fit factors, and revisit when they climb. Or build only the one piece scoring highest.
• 19 to 25: build. The workflow is core, nothing fits, the bill is growing, and you will run it for years. Renting is quietly becoming the expensive choice.

One rule on weighting: if "how core it is" scores a 5 on its own, give it extra weight. A generic tool can almost fit a support job and you live with it. A generic tool that almost fits the workflow you make money on costs you a little every single day, in time lost and deals fumbled, long before the subscription line ever looks expensive.

Three real scenarios from working with small businesses

The scorecard is easiest to trust once you see it run on real situations. Here are three patterns we see again and again with contractors, agencies, and clinics.

Scenario one: a generic tool that fits, so you buy. A two-person studio needs to send invoices and take payments. Dozens of tools do this well, the job is the same for every business, the team is not growing fast, and the data is not a competitive secret. Score it and you land near the bottom: core is low, fit is high, seat pressure is low. This is a clean buy. Pay the monthly fee and never think about it again. Building your own billing tool here would burn money and time for no edge.

Scenario two: a core workflow no tool fits, so you build. A field-service company quotes jobs in a way no two competitors do the same, then hands them to crews, tracks materials, and bills against them. They have tried four products. Each one forces a workaround, so the real source of truth quietly lives in a spreadsheet next to the software they pay for. Core is a 5, fit is a 1. This is the textbook build. A CRM we built and run our own business on started exactly here: tools that almost fit, plus a spreadsheet doing the real work.

Scenario three: a growing team hit by per-seat fees, so you build. An agency runs a stack of four subscriptions priced per user. At three people the bill is manageable. They hire, then hire again, and at six people the per-seat stack roughly doubles while the work it does has not changed. Core is medium, but the seat-cost factor is screaming. Owning the workflow stops charging them a tax on growth. The build pays for itself faster the bigger the team gets.

The most common build-vs-buy mistakes

Three mistakes account for most regret on both sides: building something generic, buying for the core, and deciding on sticker price instead of three-year cost.

Building something generic. The classic over-build. Someone decides to build their own email tool, their own calendar, their own accounting. These jobs are solved. Thousands of businesses run them the same way, and a mature product will always do them better and cheaper than a one-off you have to maintain. If the job is generic, buy it, full stop.

Buying for the core. The quieter, more expensive mistake. You let a generic tool run the workflow you actually compete on, then spend years bending your business to its limits and patching the gaps with spreadsheets. It feels safe because the monthly fee is small, but the cost shows up as friction, lost time, and a process shaped by a vendor instead of by you.

Deciding on sticker price, not 3-year cost. A subscription looks cheap next to a one-time build because you are comparing one month to the whole thing. Line them up over three to five years and the picture flips, especially once per-seat fees and price hikes stack up. Decide on total cost of ownership, not the number on the monthly invoice. Here is the real 3-year math, worked out.

The hybrid path most small businesses should take

You almost never have to choose all-build or all-buy. Buy the commodities like email and accounting, and build the one core workflow that makes you money. That mix beats either extreme.

The build-vs-buy debate makes it sound like a coin flip. It is not. The right answer for most small businesses is both, applied to the right parts. Keep paying for the generic tools that do generic jobs well. There is no edge in building your own inbox or your own payroll, and plenty of cost.

Then take the one workflow at the center of your business, the one every tool "almost" fits, and build that. That is the part where owning beats renting on fit, on per-seat cost, and on control. You stop bending your process to a vendor's limits, and you stop paying to customize software that was never shaped for you. The commodity tools keep running quietly in the background. The core runs the way you actually work.

This is also the cheapest path to test. You do not have to rebuild your whole stack to find out if building is worth it. Build the one workflow scoring highest on the card, keep everything else as is, and let the result make the next call for you. If you are not sure which piece that is, mapping it is exactly what a discovery call is for. If the answer lives in a spreadsheet today, start there.

Questions people ask first

When does building software make more sense than buying?

Building wins when the workflow is core to how you make money, when no single tool fits so you are paying for three or four that overlap, when per-seat fees climb every time you hire, or when you need to own your data and avoid lock-in. If three or more of those are true, build. If the need is generic and a mature tool fits cleanly, buy.

Is custom software always better than SaaS?

No. Custom wins for the core workflow you will run for years across a growing team. SaaS wins for generic jobs like email, accounting, and payroll, where a mature tool already does it well for everyone. The smart move is rarely all of one. Buy the commodities and build the one workflow that makes you money.

What is a hybrid build-vs-buy approach?

A hybrid approach buys off-the-shelf tools for commodity needs like email, accounting, and document signing, and builds a custom app only for the core workflow that sets you apart. You stop paying to customize generic tools and you stop renting the part of your business that should be yours. Most small businesses land here.

How do I know I've outgrown off-the-shelf software?

The signs are clear once you look. You pay for three or four tools that overlap, your team keeps tasks in spreadsheets the software cannot handle, onboarding a new hire means teaching them five workarounds, and your bill jumps every time you add a seat. When the tool dictates how you work instead of the other way around, you have outgrown it.