Med spa software demo checklist: test the exceptions

Prepare one shared scenario

Create a fictional patient, two providers, one shared room or device, a prepaid package and a membership. Ask each vendor to demonstrate the same service journey on the plan in its written quote. Give staff a task to observe and a question to answer.

Keep personal and patient information out of a public demo environment. A realistic scenario does not need a real person’s record. If an actual migration test later needs practice data, use the approved secure process agreed with the responsible team.

Test booking and the patient record together

Book the fictional patient into a service that requires a particular provider and resource. Try to reserve the same resource with the other provider at that time. Reschedule the appointment and check whether the original reminders and forms still apply.

Complete a test intake and consent workflow. Find the submitted document from the patient record, identify its version and show the team’s review step. Ask the clinical reviewer to inspect how a correction or additional note is recorded. A form-builder demonstration alone cannot answer those questions.

Ask for a billing exception, not only checkout

Redeem part of the package, reverse the redemption and explain the remaining balance. Then simulate a failed membership charge. Confirm who sees the failure, how a retry is handled and whether benefits are issued once or more than once.

Boulevard documents recurring billing and benefit tracking, but your demo still needs to prove the exact freeze, refund and redemption rules your practice uses. Write down manual steps and add-ons instead of interpreting the feature name as a complete answer.

Check reporting and access with a second role

Ask a restricted test user to perform a front desk task without receiving unnecessary clinical or financial access. Then ask a manager to reconcile the day’s receipts, refunds and package activity. Have the vendor define what its revenue and retention reports actually count.

For multiple locations, compare a local view and a consolidated view. Watch for location permissions, duplicate patients and different service names. A dashboard with the desired label is not proof that every location uses the same definition.

Close the demo with a decision log

Record each task as shown, documented, promised, unknown or unsupported. Include the plan, additional product, implementation work and person responsible. Ask for an answer date for every unresolved must-have.

Copy this demo log into a worksheet: task; expected result; observed result; plan demonstrated; evidence state; manual step; extra fee; follow-up owner; due date. Keep sales promises distinct from delivered features and put material commitments into the proposed scope.

Decide whether another meeting will change the decision

If remaining uncertainty concerns one workflow, request a focused demonstration with the relevant staff member. If it concerns cost, compare complete written quotes in the total-cost tool. If a critical capability is unsupported, remove the platform rather than adding more preference points to compensate.