Build vs. buy for a 20-person team

At some point every growing business hits the same fork: there’s a job that needs doing, and you can either buy a tool that mostly does it or build something that does it your way. For a big company with a platform team and a budget to match, this is a normal trade-off. For a 20-person business, it can quietly turn into a money pit in either direction — an expensive subscription nobody fully uses, or a custom build that becomes a second job to maintain.

The good news is that the decision is more predictable than it feels. You don’t need a platform team, and you shouldn’t pretend you do. You need a plain way to tell which situation you’re actually in. Here’s the framework we use.

Start by being honest about what you are

A 20-person company is not a small big company. It’s a different kind of thing. You don’t have spare engineers sitting around, you can’t afford a six-month project that doesn’t pay off, and every tool you adopt is one more thing someone has to learn, log into, and look after.

That reality should make your default lean toward buy. Most of the time, for most jobs, an off-the-shelf tool is the right call — it’s cheaper to start, someone else maintains it, and you can be running this week instead of next quarter. Building should have to earn its place against that default, not the other way around. So the real question isn’t “should we build or buy.” It’s “is this one of the few jobs where building actually pays for itself?”

The question under the question: is this core to you?

The most useful line to draw is between the work that is your business and the work that merely supports it.

Email, accounting, payroll, scheduling, your help desk, document storage — these support almost every business, but they aren’t what makes you you. Thousands of companies need the same thing, which is exactly why good, cheap tools exist for them. Building your own version of something a polished product already does well is how small teams burn months reinventing a worse wheel. Buy these. Move on.

Then there’s the handful of things that are genuinely yours — the specific way you quote a job, the particular shape of your customer relationships, the workflow that’s a little weird because your business is a little different, and that difference is the reason customers pick you. When AI or automation touches that work, an off-the-shelf tool often gets you eighty percent of the way and then asks you to change how you operate to fit its assumptions. That last twenty percent — the part that’s actually yours — is where a small custom build can be worth it.

The test is simple to ask and clarifying to answer: if we did this exactly like everyone else, would we lose what makes us us? If no, buy it. If yes, building is at least on the table.

When buying wins

Lean toward buying when the job is common, the available tools are mature, and your needs sit comfortably inside what they already do. Signs you’re here:

• Lots of other businesses have the exact same need, so the market is well served.
• A tool exists that does 90% of what you want out of the box.
• The 10% it misses is a nice-to-have, not a deal-breaker.
• You’d rather pay a predictable monthly fee than own the upkeep.

The honest cost of buying isn’t just the sticker price — it’s the per-seat fee times your headcount, times the number of tools you’ve accumulated, forever. That adds up, and it’s worth auditing once a year. But for supporting work, it’s almost always cheaper than the true cost of building and maintaining your own.

When a small build pays off

Lean toward building when the work is core, the fit is bad, and the volume is high enough that the difference compounds. Signs you’re here:

• The task is specific to how you operate, not how businesses in general operate.
• Off-the-shelf tools force you to change your process to fit them, on work you care about.
• You’d be paying for a big platform to use one corner of it.
• The thing happens often enough that small frictions add up to real hours.
• You want to own the system — the data, the logic, the ability to change it — rather than rent it.

Notice that “build” here doesn’t mean “construct an enterprise platform.” For a 20-person team, a good custom build is small and sharp: one workflow, wired into the tools you already use, doing the specific thing the market doesn’t do for you. The aim is a system you own and can change, not a software product you now have to run.

The trap on both sides

Each path has a failure mode, and knowing them helps you avoid the worst outcomes.

The buying trap is tool sprawl: a drawer full of subscriptions, each solving a sliver of a problem, none of them talking to each other, all renewing quietly. The fix is discipline — every new tool should replace something or clearly earn its seat, and someone should review the whole stack once a year and cancel what’s gone cold.

The building trap is the maintenance tail. The build is the cheap part; keeping it alive is the cost people forget. A custom system needs an owner, a little documentation, and a plan for what happens when the person who built it moves on. If you build, build for that from day one — write down how it runs, keep it small enough to understand, and make sure it doesn’t depend on one irreplaceable head. (We’ve written a whole separate note on why this is what makes or breaks an automation.)

A 20-minute version of the decision

You don’t need a committee. Sit down with the people who’d actually use the thing and walk through five questions:

1. Is this core to what makes us us, or is it supporting work? Supporting work leans buy.
2. Does a tool already do 90% of it well? If yes, buy and stop here.
3. Would off-the-shelf force us to change work we’re proud of? If yes, building moves onto the table.
4. Does it happen often enough that the difference adds up? Rare problems rarely justify a build.
5. If we build, who owns it next year? No clear answer means you’re not ready to build.

Run a job through those and the answer is usually obvious — and “buy” will be the answer more often than not. That’s fine. The goal was never to build for its own sake. It was to spend your limited time and money where they actually move the needle, and to be clear-eyed about the rest.

That clarity — knowing which of your problems are genuinely yours and which are everyone’s — is most of the decision. The build-or-buy part mostly takes care of itself once you’ve answered it honestly.

---

PineyWoods helps small and medium businesses make the build-vs-buy call without the hype — and when a small custom build is the right answer, we build it on tools you already own and hand it off. Weighing a decision like this? Book a free call. Thirty minutes, a straight answer, useful either way.