Custom software or off-the-shelf: a practical buying framework

List the workflows that make your business distinctive and those that resemble common administrative tasks. An existing product may handle a standard process more economically than custom development. Custom software becomes more compelling when the workflow itself creates an advantage, when integration constraints are unusual or when the available products require persistent workarounds.

Do not compare a polished vendor demonstration with an imagined custom application. Give shortlisted products the same representative scenario, including permissions, exceptions, exports and reporting. Ask users to complete it themselves. Record what works through configuration, what requires an extension and what cannot be supported. These distinctions matter more than the raw feature count.

Include licenses, implementation, migration, integrations, administration, support and likely changes. For a custom option, include product ownership, hosting, maintenance and security updates. Document assumptions about user counts and transaction volumes rather than presenting one precise number without context. Compare the cost of leaving the workflow unchanged as a third option.

For a purchased platform, examine usable data exports, integration limits and the effort needed to move away. For custom development, examine source ownership, infrastructure access and the ability of another team to maintain it. Ownership of code is useful only when the build, deployment and operational knowledge can also be transferred.

The choice is not always a complete purchase or a complete build. A standard platform can manage a commodity function while a custom layer supports the distinctive workflow. Keep the integration boundary explicit and avoid duplicating conflicting business rules. A short evaluation phase should produce a recommendation, its assumptions and a list of risks to validate, rather than a predetermined argument for custom software.

Ask a vendor to demonstrate a realistic task using representative data, including an exception rather than only the happy path. For a custom option, estimate the effort to deliver that same task and keep it running. Use an equivalent scope when comparing the alternatives.

• Include configuration, migration and training costs.
• Check access controls and integration limits.
• Test data export in a usable format.
• Clarify responsibility for upgrades and incidents.

Keep assumptions visible in the decision. A packaged tool may cover common workflows well, while a small custom integration handles a distinctive process. The useful comparison is the complete operating solution, not just licence cost versus development cost.