Describe the problem before choosing a product
Start with the task that is slow, error-prone or difficult to see. Follow the information from the first request through to the finished job, including the people and tools involved.
This often reveals that a process change, a better use of existing software or a small integration may solve the issue without replacing the whole system.
- Where does information first enter the business?
- Who needs to act on it, and what do they need to know?
- Where are details copied, checked or entered more than once?
- What must be recorded for customers, staff or reporting?
See whether an existing product is a good fit
List the essential requirements separately from the features that would simply be convenient. Compare products against the essential list, and try the everyday tasks with realistic examples before making a decision.
Check the full operating arrangement as well as the feature list: user limits, integrations, data export, support, contract terms and what happens if the price or product changes.
When a tailored system may be worth exploring
A custom system may be worth scoping when important steps do not fit an existing product, staff must maintain awkward workarounds, or several systems need to exchange information in a specific way.
That does not mean every step should be custom-built. A focused tool that handles one well-defined gap may be easier to introduce and maintain than recreating a complete business platform.
Include the ongoing responsibilities
A proposal for custom software should identify who will maintain it, where its data is stored, how access is managed and how backups and updates are handled. It should also explain external services, licences and any reliance on third-party systems.
Agree what is in scope for the first release, what can wait, how changes are requested and how the business can retrieve its data. These questions help make the decision about long-term fit, not just the initial build.
Decide with evidence from the real workflow
Write down a typical job from beginning to end. Use that example to compare a process improvement, an existing product and a tailored option. Record what each approach solves, what it leaves manual and what it will take to support.
If the requirements are still uncertain, begin with discovery and a small, testable scope rather than treating an early conversation as a fixed quote.