MonolithTechnologies Limited
Strategy

Build or buy? A simple framework for software decisions

Five questions and a simple scoring approach to decide whether to build software, buy a product or combine both.

Abraham Olagunju

27 Oct 2026 · 2 min read

Build or buy? A simple framework for software decisions

Every growing organisation reaches the same question: do we build this software ourselves, buy a product, or combine both? Most teams answer it by instinct, then live with the consequences for years. A short, honest framework gives a better answer in an afternoon.

Start with what makes you different

Ask whether the capability is part of how you win, or just a cost of doing business. Payroll, email and accounting are the same for most companies, so buy them. A booking flow that is central to your service, or a workflow nobody else runs, is where custom software earns its cost.

Five questions to ask

  • Differentiation: Would doing this better than competitors change your results?

  • Fit: Does an existing product cover at least 80 percent of what you need without painful workarounds?

  • Total cost: Over three years, what do licences, customisation, integration, hosting and maintenance cost for each route?

  • Control and risk: Can you export your data? What happens if the vendor raises prices, changes the product or disappears?

  • Speed: How soon do you need it working, and who will run it afterwards?

The hybrid usually wins

In practice the best answer is often both: buy the commodity pieces, such as payments, identity and messaging, and build the layer that is specific to you on top. The skill is in the seams, so connect products through their APIs and webhooks, keep your own data model, and avoid letting a vendor's schema become yours.

Common mistakes

  • Underestimating maintenance. Software is never finished, and building means owning it.

  • Comparing a polished demo with a custom project estimate instead of two real three-year costs.

  • Customising a bought product so heavily that you carry the cost of building with none of the control.

  • Skipping an exit plan. Always know how to leave.

A simple scoring approach

List your requirements, mark each as essential or nice to have, and score each option on essentials met, three-year cost, risk and time to value. Share the table with the people who will use the system. The conversation it starts is usually more valuable than the number it produces.

Build what makes you different. Buy what makes you the same as everyone else.

0 Comments

Loading comments…

Related articles