A software demo is designed by the vendor. It runs half an hour, follows a script they have delivered a hundred times, and ends right before the uncomfortable questions come up. You leave with the feeling that everything looked fine and without a single answer you can compare against the next vendor.
These fourteen questions flip that dynamic. They are not a script to read aloud: they are the points where products in this category genuinely differ, with the answer you should hear and the red flag worth writing down. Take them to every demo and compare answers, not impressions.
One warning first: none of these questions help if you are not clear on what you need. If you are still deciding on criteria, the framework for choosing quality management software comes before this.
Table of Contents
Before the demo: prepare it in four steps
The difference between a useful demo and a sales presentation is decided before you connect.
- Send your real case in advance. One of your procedures and one of your nonconformities, with names changed if you prefer. If the vendor refuses to prepare the demo with your data, that is already information.
- Write down the three workflows you want to see end to end. For example: publishing a document revision, opening and closing a corrective action, and pulling the evidence an auditor would ask for.
- Invite someone from outside quality. The production or warehouse lead. They are the ones who decide whether the tool gets used or abandoned.
- Reserve the last fifteen minutes for questions only. Say so at the start of the meeting. If you do not reserve it, the script eats the hour.
Block 1. Coverage of the standard
1. Show me a full corrective action cycle, from detection to verified closure
What you want: root cause analysis, assigned owner, deadline and, above all, effectiveness verification as a mandatory step. Clause 10.2 asks for that last step and it is where most products fall short.
Red flag: the action closes by ticking a box, with no evidence and no follow-up verification.
2. How do I know which version of a document is current and who approved the change?
What you want: visible version history, a review and approval workflow that records who approved, and automatic withdrawal of the previous version from circulation.
Red flag: version control that depends on how you name the file.
3. Where does the indicator data come from?
What you want: clause 9.1 indicators fed by what is already in the system. If the software only charts what you key in by hand, you have swapped one spreadsheet for a more expensive one.
Red flag: «you load them in every month».
4. What happens with internal audits, from annual programme to closing findings?
What you want: planning, execution, findings log and a direct link between each finding and its corrective action. Clause 9.2 lives complete or it does not live.
Red flag: audits that are just a repository of attachments.
Block 2. How it actually gets used
5. How many clicks does a once-a-month user need to complete their task?
What you want: have them prove it live with the person you invited, unassisted. It is the most honest usability test there is and it costs nothing.
Red flag: «a two-hour training session makes it clear».
6. How does someone find out they have something pending?
What you want: notifications that leave the system and reach the person, with a due-date reminder. A system that only tells you when you log in is not telling you.
Red flag: follow-up that still depends on someone sending emails.
7. Does it work from a phone on the shop floor?
What you want: field tasks, raising a finding or uploading evidence, doable without going back to a desk.
Red flag: being shown a shrunken desktop view and being told it is the mobile version.
Block 3. Your data: getting in, staying in, getting out
8. How does what I already have get in, and who does that work?
What you want: a clear migration scope, what gets migrated, who does it and what it costs. The honest answer is almost never «it just uploads».
Red flag: migration presented as free and then arriving as a separate line in the proposal.
9. If I leave in two years, how do I take my data with me?
What you want: full export in an open format, documents included, without having to ask for it as a favour. It is the most uncomfortable question and the one that protects you most.
Red flag: silence, or an answer that depends on «discussing it at the time».
10. Where does my data live and how is it backed up?
What you want: a concrete answer on hosting, backup frequency and what happens if the vendor stops operating.
Red flag: «it is in the cloud» as a complete answer.
Block 4. Money and commitment
11. What is the total first-year price with everything included?
What you want: licence, users, implementation, migration, training and support, added up into one figure. In this category list price and real price diverge a lot.
Red flag: pricing that depends on modules and headcount, because it grows with usage exactly when the project starts working.
12. What happens if my team is not using it two months in?
What you want: a written refund policy. A vendor who carries part of the risk has skin in the game; one who does not leaves all of it with you.
Red flag: a guarantee that is «handled case by case».
13. How many users are included and what happens when we grow?
What you want: the exact limit and the cost of the next tier. Remember that most of the people who will log in do not work in quality.
Red flag: named-user pricing when half your people will log in once a month.
14. Who do I talk to when something breaks, and how fast do they answer?
What you want: channel, hours, language and a committed response time. If you operate outside the vendor’s hours, this weighs more than any feature.
Red flag: support by web form only, with no time commitment.
How to close the demo
Ask for three things before you hang up: the proposal with the total first-year price in writing, the refund policy also in writing, and a second session with the non-quality person driving the tool unassisted. If the vendor agrees to all three, you are on a good track.
Once you have everyone’s answers, compare them against your own criteria. If you want to see how we answer these same questions, they are covered in who QualityWeb 360 works for and who it does not. And if the document block is what worries you most, clause 7 on support and documented information defines the minimum the tool has to handle.
Frequently asked questions
How many demos should you see before deciding?
Three is usually the sensible number. With one you have nothing to compare against, and with five the process drags on so long you forget the first ones. What matters is not the count but asking the same questions in all of them, so you can line the answers up side by side.
What should I bring to an ISO 9001 software demo?
A real procedure and a real nonconformity from your company, the list of three workflows you want to see end to end, and one person from outside quality who will actually be a user. With that, the demo stops being a presentation and becomes a test.
How long should a demo last?
An hour, with the last fifteen minutes reserved for questions and announced up front. Half an hour only covers the sales script, and two hours will lose the occasional user you invited, who is exactly the person whose opinion matters most.
Is it a bad sign if a vendor does not publish prices?
It is not disqualifying on its own, but it does mean asking for the total first-year price in the first meeting and getting it in writing. In this category it is common for pricing to surface only after several sessions, which stretches the decision without giving you new information.
Should I ask for a free trial of the software?
You can ask, but a trial on an empty database tells you little: with none of your documents or workflows in it, everything looks tidy. A refund guarantee that lets you run the system on real data for weeks is usually more useful, because that is when adoption problems actually show up.
