Software selection guide
Buy standard software or build a custom system?
Start with the tasks people need to complete. A feature list alone will not reveal the work that remains between tools.
Compare three routes
Consider a standard product, its configuration and a custom module. If an ERP handles accounting well but order approval still travels through email, an integrated portal may be sufficient. You do not need to rebuild the accounting workflow that already works.
Test a complete scenario
Follow one order from receipt to completion. Record who enters data, who approves it, where the status changes and how an error is resolved. Test each option with the same scenario, including an exception, rather than only the opening screen of a demonstration.
Compare the full cost of use
Include licences, implementation, configuration, integrations, migration, training and maintenance. Ask what happens when switching suppliers: how data can be exported, who holds code and documentation, and how connections receive updates. A low initial quote does not answer these questions.
Prepare a first stage
Gather a workflow diagram, user roles, a system list and an anonymised data sample. The first stage might produce a prototype or an integration test. Agree what users must be able to verify before committing to broader development.
Apply this to your needs
Check your assumptions.
Use the planner to explore scope, calculate time value and submit a specific request.
Plan a project →