Almost every organisation eventually faces the same question about some piece of software: do we buy this, or build it ourselves? The decision is usually made on instinct — developers lean toward building, finance leans toward buying — when it is answerable on evidence.
The Question That Settles Most Cases
Before comparing anything, answer one thing: is this process a competitive advantage, or is it plumbing?
If the way you do this is genuinely better than your competitors and customers notice, building protects that advantage. Forcing it into a generic product means either losing the differentiator or paying for heavy customisation that recreates the build cost without the control.
If it is plumbing — payroll, accounting, email, authentication, file storage — building is almost always a mistake. You will spend years catching up to products that have had thousands of engineer-years invested, to end up with something merely adequate at a task that was never going to win you a customer.
Most systems are mostly plumbing. That is why buying wins more often than engineers expect, and why the hybrid answer below is usually the right one.
What Each Side Hides
| Build | Buy | |
|---|---|---|
| Visible cost | Development quote | Licence or subscription |
| Hidden cost | Maintenance forever, key-person risk, security patching | Per-seat growth, integration work, migration out |
| Time to value | Months | Days to weeks |
| Fit | Exact | Approximate, improves over time |
| Who fixes a bug at 2am | You | Them |
| Risk if it fails | Sunk cost, nothing to show | Switch supplier |
The build cost people forget
A build quote prices version one. The permanent costs begin after delivery: dependency upgrades, security patches, browser and OS changes, the feature requests that start the day real users arrive, and the institutional knowledge that walks out when a developer leaves. A reasonable planning figure is that annual upkeep runs at a meaningful fraction of the original build — our software cost calculator shows this as a separate line precisely because it is the part most often left out of budgets.
The buy cost people forget
Per-seat pricing scales with headcount, which is fine until you triple. Integration with your existing systems is rarely included in the sticker price. And the question nobody asks during procurement is the one that matters most three years later: can we get our data out, in a usable format, if we leave? Ask it before signing, not after.
The Hybrid Most Teams Should Choose
Framing this as binary is the most common error. Modern systems are typically 80% solved problems and 20% genuinely specific to the business. The strongest answer is usually:
- Buy the commodity layers. Authentication, payments, email delivery, accounting, analytics, file storage. These are mature, cheap and not where you compete.
- Build the thin layer that is yours. The pricing rule, the scheduling logic, the workflow your staff actually follow.
- Integrate deliberately. Keep the custom part separable, so a bought component can be swapped without a rewrite.
This gets you an exact fit where it matters and someone else's maintenance burden everywhere else. If you take one thing from this article, take that split. Our guide to open-source alternatives to expensive SaaS covers a third option that sits between the two.
A Decision Checklist
- Write down the actual requirement in plain language before looking at any product. Requirements written after a demo tend to describe that demo.
- Count how much of it is commodity. If more than roughly three quarters is standard, start from buying.
- Trial two products properly with real data and real staff. Most "nothing fits" conclusions come from a thirty-minute demo.
- Price both over five years, including maintenance, integration, training and internal time.
- Test the exit. Export your data from the trial. If you cannot, treat that as a cost.
- Name the owner. If you build, who maintains it in three years? If there is no answer, you are choosing to buy whether you realise it or not.
Key Takeaways
- Build what differentiates you; buy the plumbing — and most systems are mostly plumbing.
- Build quotes price version one; the permanent cost is maintenance.
- Check you can export your data before you sign, not when you want to leave.
- The hybrid — buy commodity, build the thin specific layer — beats the binary choice.
- If nobody owns maintenance in year three, you have already chosen to buy.
Written by the WritePures newsroom. Spotted something that needs updating? Tell our editors.
0 Comments
Join the conversation
Replying toNo comments yet. Be the first to share your thoughts.