Buy when an existing product supports the required workflow with acceptable configuration and change. Build custom software when the operating advantage, permissions, integrations, or customer experience cannot be achieved responsibly with available products.
Prepared with AI assistance. These are practical scoping recommendations; examples are illustrative, not client results.
Define the operating capability
Describe one workflow from trigger to completed outcome, including users, records, decisions, exceptions, and connected systems. Avoid starting with a feature wishlist. The decision is easier when the team can demonstrate what a product must let them complete and which parts of the current process create measurable cost, delay, risk, or customer friction.
Test products against real scenarios
Use representative examples in vendor demonstrations or trials: an ordinary case, missing information, a changed decision, an unavailable approver, and an integration failure. Record whether each scenario works through configuration, requires a workaround, or is unsupported. A long feature list cannot show whether the product fits the sequence and responsibility of your operation.
Compare four realistic options
The choice is rarely only buy or build. Compare using the current process, configuring an existing product, connecting tools with automation, and developing a focused custom layer. A custom portal or work queue may fill the important gap while established CRM, accounting, or scheduling products remain in place.
| Option | Fits when | Main risk to test |
|---|---|---|
| Keep the current process | The problem is infrequent or cheaper to manage manually | Hidden handling and error cost |
| Configure a product | Standard capabilities cover the workflow | Workarounds and plan limitations |
| Connect existing tools | Each tool works but the handoff fails | Ownership, failure recovery, and provider changes |
| Build focused custom software | The unresolved workflow is important and distinctive | Product ownership, adoption, and long-term cost |
Calculate total operating cost
For products, include licenses, implementation, configuration, migration, integrations, add-ons, training, support, and the continuing workaround. For custom software, include discovery, design, development, infrastructure, security, monitoring, support, and future changes. Use the same time horizon and show uncertain assumptions instead of forcing false precision.
Identify the strategic difference
Custom development is easier to justify when the workflow influences delivery quality, margin, capacity, customer experience, or a defensible operating advantage. It is harder to justify for a generic capability already served well by mature products. Distinctive does not mean unusual terminology; it means the way the business creates value cannot be supported adequately by the available option.
Make a reversible first decision
Choose a first release or product pilot with clear acceptance criteria, a budget boundary, an owner, and a review date. Preserve export and transition options. The best decision is not the one that predicts the next five years perfectly; it is the one that solves a valuable problem now while keeping the next change understandable.
Primary references
The guidance above is AgenticShip's proposed approach. These references provide technical background for the relevant recommendations.