Workflow questions
1. Can we take a new enquiry through to a paid invoice? 2. Can a dispatcher reschedule a job and notify everyone affected? 3. Can a technician create a quote from a phone? 4. Can we handle a recurring visit without recreating the job each time?
Plan and cost questions
5. Which exact tier includes each feature demonstrated? 6. How many paid users do we need, including office staff? 7. Which phone, messaging, payment or automation charges are separate? 8. What is the total first-year cost and the regular renewal cost?
Migration and control questions
9. What customer, job and attachment data can we import? 10. What can we export if we leave? 11. Can permissions separate technician, office and financial access? 12. What are the term, cancellation notice and refund rules?
Use a simple evidence scale
For each requirement, record “demonstrated”, “confirmed in writing”, “not supported” or “unresolved”. A salesperson saying a feature is on the roadmap is not the same as a feature available in your selected plan. Keep unresolved items open until you have an answer.
Score the important tasks first
Choose three must-have workflows before the call. If a product cannot do one of them, document the workaround and its cost. Avoid scoring a nice-looking interface so highly that it cancels out a missing requirement.
Download the editable checklist, use one copy per product and compare the evidence after the demonstrations.
This is a suggested evaluation method, not a claim of measured savings or hands-on results from any provider.