Buy for commodity problems, build where the workflow is your edge. The hard part is recognising the moment a bought tool starts costing more than it saves.

Let us start with the unfashionable truth for a company that builds software: most software problems should be solved with software you buy. Email, accounting, document storage, HR - these are commodity problems, and commodity tools solve them well. Custom software is expensive to build and more expensive to neglect. It has to earn its place.
Off-the-shelf tools stop fitting quietly. Watch for these symptoms:
Map the workflow before evaluating anything. Not the org chart - the actual sequence of information, decisions, and hand-offs. Fit can only be judged against that map.
Separate the core from the edges. The core is the workflow that makes your business yours - the way you schedule, price, assess, or deliver. The edges are commodity. Buy the edges. Consider building only the core.
Count the whole cost. A bought tool's real price includes the workaround hours, the errors from re-keying, and the opportunities missed because the tool cannot do what the business needs next.
The biggest misconception about building is scale. A custom system does not need to replace the whole tool - only the core workflow the tool gets wrong. Scoped to the actual constraint, custom systems are smaller, faster to build, and cheaper to run than their reputation suggests. And unlike a licence, the capability is yours.
Buy for commodity problems. Build where the workflow is your edge.
Practical lessons from building software, data, automation, and AI systems that work in production. One email a month, no hype.