Build, buy or automate?

When a team hits a software problem, the conversation often jumps straight to how: which framework, which vendor, which AI model. The more useful first question is what kind of problem it is, because that decides most of the answer.

Four questions, in order

• Is this a common problem? Payroll, accounting, CRM and support desks are solved problems. Buy, and spend your energy on adoption.
• Does your process fit the tool? If it mostly does, configure the tool and change the process at the edges.
• Is the gap in the glue? Often the tools are fine and the pain is in moving data between them. Automate the connections; it is cheaper than replacing either side.
• Is it part of what makes you different? If the software is your product or your edge, build it, and plan to own it.

The hidden cost of building

Building looks expensive at the start and is usually more expensive later. The first version is the cheapest part. Then come the security updates, the new devices, the integration that changed its API, and the feature the team needs next quarter. Custom software is a commitment, not a purchase.

“Build what makes you different. Buy what makes you the same.”

When building is right

Building is right when the software is the business: a product you sell, a workflow that is genuinely your advantage, or a customer experience your competitors cannot copy off the shelf. In those cases, owning the code is worth the cost, and the cost is worth planning for honestly, from the first sprint to the fifth year.