An existing product is worth testing when it already represents the task well. Custom software needs a clearer reason than wanting an interface built to preference.
Identify the mismatch
Describe the step that returns to email, a spreadsheet or a private note after the existing tool is introduced. Determine whether configuration or training resolves it before treating it as a product limitation.
A meaningful mismatch is a rule, relationship or exception that the organisation repeatedly needs and cannot represent reliably. Keep examples of the failed cases rather than a list of disliked features.
Compare complete operating options
Include setup, migration, maintenance and manual correction work in the comparison. A subscription with substantial manual follow-up may cost more to operate than its invoice suggests. A custom build also needs ownership after release.
Use observed effort where possible. Mark uncertain estimates rather than presenting an exact return on investment without evidence.
Define a bounded build candidate
The candidate should own the mismatched workflow while leaving suitable specialist tools in place. Verify that records can enter and leave it without creating another reconciliation step.
The decision checklist provides a fuller comparison of keeping, buying and building. HATT's services describe the path from that decision to product development.