Buy when the process is common and the product fits. Build when the workflow is strategically important and workarounds create more cost or risk than ownership.
Measure workflow fit
List the high-value steps, rules, roles and exceptions. Score the candidate product against those needs without allowing impressive peripheral features to hide a broken core workflow.
Count the cost of workarounds
Licensing is only one cost. Include duplicate data entry, spreadsheets maintained beside the product, missed handoffs, custom exports and staff time spent reconciling systems.
Consider configuration and integration
The real choice is rarely binary. A configured platform connected to a focused custom layer may preserve commodity capability while improving a unique workflow.
Understand ownership
Custom software creates responsibility for maintenance, security and product decisions. It is a good investment when the organization is prepared to own the capability, not merely fund version one.
A practical checklist
- Name the business outcome in plain language.
- Map the current people, systems and exceptions.
- Separate necessary scope from attractive extras.
- Make ownership, security and operating cost visible.
- Choose the smallest next step that reduces a material unknown.
What to bring to a first discussion
Bring one real example of the current workflow, the people involved, the constraint you feel most often and what a useful outcome would change. You do not need a finished specification.