A demo can look simple when everything goes as planned. The useful test is different: what happens when an appointment changes, two practitioners need the same room or you need to retrieve a document without interrupting a consultation? Start with those situations.
This guide is written by TalumCore. It is not an independent comparison or a ranking of brands. You can use it with any provider, including TalumCore.
Bring your workflow to the demo, not an endless feature list
Before booking, note how many people will use the platform, how many rooms you share and who manages scheduling, records information and handles payments. They are not always the same person.
Choose three specific problems to solve: finding a slot with a room available, checking follow-up notes without searching several folders or understanding which setup to buy. Separate day-one essentials from what you could add later.
Test a full day in the calendar
Ask the provider to create a fictional appointment, assign a practitioner and room, then change its time. Test what happens if the new time conflicts with another appointment or an absence. What matters is not whether a button exists, but which warnings appear and who can make the change.
If you run group sessions, review capacity, enrolment and how groups differ from individual appointments. Ask whether this is included in the subscription or requires an additional module.
Internal scheduling and patient booking are different journeys. Check what patients can book, the availability they see and what happens when they cancel. Do not assume a calendar subscription includes a booking portal, WhatsApp reminders and groups.
With TalumCore, you can review the scope of scheduling and online booking separately. Group management is an optional module, also included in the Complete plan.
A test you can prepare in advance
Fictional example: three practitioners, two rooms and a clinic that wants centralised scheduling and online booking. This does not represent a customer or results achieved with TalumCore.
- 09:00
Two appointments until 10:00, one in each room with different practitioners.
- 09:30
A third practitioner tries to book room 1. Ask to see what happens with this conflict.
- 10:00
Move the third appointment to the time the room becomes free. Add an absence for that practitioner and check what happens.
Note whether the platform blocks, warns or allows the change, and who can do it. Include a buffer if you need time between sessions. Decide what behaviour your clinic requires. This is an evaluation script, not a test already performed or a guarantee of TalumCore’s behaviour.
Follow a fictional patient from appointment to record
Ask for a walkthrough using invented data: find an appointment, open the patient record, locate a sample document and return to the calendar. Then try it yourself. An organised screen should help you understand where you are and what you can do next.
Note what information you need to keep and in which format. If you use documents, templates or consent forms, ask which are included and which need configuration or an additional module. Do not consider a feature confirmed just because it appears in a screenshot.
You do not need to share real clinical records or upload patient documents for a commercial evaluation.
Review permissions and responsibilities with two test accounts
Ask for a demonstration of what a receptionist sees and what a practitioner sees. Check with the provider how access to areas outside each role is restricted, and how access is removed when someone leaves the team.
If self-employed practitioners handle their own invoicing, explain this at the start: it may affect the setup and cost. Also ask who administers accounts and how the actions available in the system are reviewed.
A sales demo alone does not establish compliance with all of your clinic’s obligations. Request the applicable documentation and clarify responsibilities before subscribing; do not settle for a blanket claim of “fully compliant”.
Calculate the cost of your setup, not just the starting price
Request a breakdown separating the base subscription, additional practitioners and locations, modules, variable usage and setup services. Ask what support is included and what terms apply when you change the configuration.
Budget example, not a personalised offer: using TalumCore’s published prices on 24 September 2026, a clinic with up to three practitioners can start with the €39/month core package and add the app and online booking for €12/month: €51/month, including VAT.
This example excludes other modules, WhatsApp usage, additional practitioners or locations, and any migration. Compare this setup with the Complete plan only after confirming which modules you need and which costs remain separate. Migration is quoted separately according to complexity.
Check current pricing and terms before deciding. You do not have to enable everything at the start: choose what you need to work and what you would add once your team has validated it.
Define migration before choosing your switch-over date
Prepare the name of your current software, its available export formats and an estimated volume. Distinguish patient profiles, documents, future appointments and financial information: being able to transfer a list does not mean every attachment and relationship will import in the same way.
Ask for a clear scope: what will be transferred, what is excluded, who prepares the export, how the result will be checked and which conditions must be met before you stop using the previous system.
A list of fields or an invented example is enough for the first conversation. Do not send patient data through a sales form or a channel that has not been agreed. TalumCore assesses migration by source, format and volume; scope and timing require a case review.
Finish the demo with answers, not a score
Note the evidence you have seen for each decision. You do not need an overall score or an automatic winner: you need to know what has been demonstrated, what remains unconfirmed and what does not fit your clinic.
Copy these questions into your notes and assign one of these statuses to each answer:
- Demonstrated
- Awaiting confirmation
- Not a fit
- Scheduling and rooms
- A fictional appointment created and moved; behaviour when a conflict occurs.
- Patient booking
- Booking journey explained and module scope confirmed.
- Connected information
- Journey from appointment to patient record and a sample document.
- Team access
- Differences between two roles demonstrated with test accounts.
- Full cost
- Breakdown of your setup, taxes and separate variable costs.
- Changing software
- Migration scope, responsibilities and checks.
- Support and continuity
- Support channels, terms and specific commitments.
If an important answer is still pending, resolve it before subscribing. If the workflow fits, test everyday tasks with the people who will use it: a good choice needs to work during their day, not just during the presentation.