Choose build, buy or hybrid with a six-part fit test

Off-the-shelf software offers established capability, vendor-managed change and bounded configuration. It is often the sound choice for standard functions.

Custom software gives the business control over a specific experience or capability, together with responsibility for its operation and evolution.

A hybrid keeps standard functions in proven products and builds only the interface, coordination or data layer that is missing.

Use three to five representative scenarios, including a difficult exception. Score what each option supports natively, through configuration, through integration and through continuing manual work.

Record evidence and uncertainty beside every score. A polished demonstration is not proof that permissions, data exchange or exception recovery will work in service.

• Fit: users, rules and exceptions
• Differentiation: value from doing this differently
• Integration: access, exchange and consistency
• Control: priorities, continuity and change
• Adoption: training, behavior and governance
• Economics: ownership costs and workarounds

For a product, include subscription, configuration, migration, integration, training, limits and manual work left behind.

For custom software, include discovery, delivery, infrastructure, support, documentation and internal product ownership.

Vendor dependency and custom-delivery risk are different, not absent. Name each risk, its owner and the evidence needed before commitment.

Ask vendors to demonstrate your scenarios with realistic roles and data. For a custom option, use discovery or a bounded prototype to test the same unknowns.

Keep a written result for every scenario so the decision survives sales presentations and internal preference.

• Can the task finish without parallel tracking?
• Do roles and approvals match reality?
• Can systems exchange dependable data?
• Can staff recover from failure?
• Who can change the capability later?

Choose buy when fit is acceptable and adaptation costs less than ownership. Choose build when the unmet capability is important, specific and durable.

Choose hybrid when the standard core is sound but one layer creates material value. Reject options whose critical unknowns remain untestable.

Document the evidence, assumptions, owner and review date. If build wins, use the planning guide to prepare the commission.