1. Map the request before the demonstration
Write down where an enquiry arrives, which records must be checked and who decides the next step. Identify the patient, provider, insurance and authorization information that staff need. Use a fictional example. Ask the presenter to show how that example becomes an order or visit, and how another team member picks up the work.
2. Follow equipment into delivery
List the products your business handles and the inventory information staff need when planning an order. Then follow the delivery handoff: assignment, route, driver details and the office team's view of progress. If mobile access matters, request a demonstration on the kinds of devices your staff will actually use.
- Who assigns and changes delivery work?
- What can a driver see on a mobile device?
- How does dispatch review field activity?
3. Continue through billing and payment follow-up
Do not stop the demonstration at delivery. Review how the relevant procedures and records reach billing, how remittance information is handled and how the team follows checks or outstanding work. Ask which steps are supported by the proposed product and which still depend on another system or a manual process.
4. Make implementation requirements explicit
Separate essential workflows from optional improvements. Identify existing data formats, historical records, user roles and communication channels. Request a written scope covering configuration, data import, training and support. Ask your own security and compliance team to review access and data-handling requirements; do not infer certification from a feature list.
5. Compare proposals on the same basis
Compare the workflows included, intended users, provider dependencies and implementation work, rather than only a headline price. Record unanswered questions and arrange a follow-up demonstration for them. DME offers a tailored proposal for operational software and optional communication products, so your priorities help define the scope.