Start with one job the software needs to handle, such as assigning leads or reconciling stock across outlets. Ask the people who do it to show you a recent example, including an exception that needed manual work.
Test a ready-made product against both cases. Include setup, subscriptions and integrations in the cost. For a custom build, ask who will handle hosting, fixes and updates once the first release is live.
A build may be worth considering when a recurring problem is costly and available products still leave staff doing it by hand. Write down what the first release must do and how you’ll test it before asking developers to quote.