How to Run a Fair Software Demo: The Hard Questions Buyers Forget to Ask
In short
- A demo is a performance. Your job is to turn it into a test.
- Write three to five of your own scenarios before any vendor calls, and give every vendor the same script.
- Ask what is configuration, what is custom code and what is a promise on a roadmap.
- Ten hard questions on compliance, data, security, cost and exit decide more than any feature tour.
- Score every vendor within 24 hours, using weights you agreed before the first demo.
Every software demo is polished. The data is clean, the screens load instantly and the happy path works. That is not a criticism of vendors; it is what a demo is for. The problem is that buyers often judge the performance, not the product, and find out the difference months after signing.
This guide shows how to run a demo as a fair test: how to prepare, what to ask the vendor to do on screen, and ten hard questions that buyers of financial software, from lending and payments platforms to investment and onboarding tools, tend to forget. It works whether you are comparing two vendors or six.
Why most demos are not a fair comparison
- The vendor sets the script. You see the strongest features in the best order.
- Data is staged. Clean sample records hide the awkward cases that fill a real week.
- Different vendors show different things, so you end up comparing stories, not capabilities.
- The room is too big and too passive. Six people watch, nobody pushes, and the meeting ends with a general feeling instead of a score.
- Features crowd out fundamentals. Nobody remembers to ask about audit trails, data export or what happens in year three.
Before the demo: build your test
- Write three to five scenarios from your real operations. Choose your hardest, not your most common. For a lender, that might be a restructured loan with a missed payment and a partial refund. For an investment platform, an investor who changes country of residence mid-offer. For a payments product, a failed payout that must be retried and reconciled.
- Agree your scorecard first. Decide what matters and how much, before a vendor charms the room. Weights should reflect your risks, not the vendor’s strengths.
- Send the same brief to every vendor. Include the scenarios, the time limit and the questions you expect answered. A vendor that refuses to follow your brief is telling you something.
- Limit the room. One decision-maker, one person who knows operations, one who knows compliance or risk, and one who will use the system daily. Everyone else can watch the recording.
- Ask for a sandbox, not only a slide-led demo, and agree what you will test in it afterwards.
A simple scorecard
The weights below are a starting point. Change them to match your business, but decide them before the first call.
| Area | Suggested weight | What a high score means |
|---|---|---|
| Fit with your scenarios | 25% | Your hard cases ran without workarounds |
| Compliance and reporting | 20% | The product supports your licences, records and regulator-facing reports |
| Data, security and resilience | 15% | Clear ownership, strong controls and a credible recovery plan |
| Integrations and APIs | 10% | The connections you need exist and are documented |
| Total cost over three years | 15% | All-in price is clear and stable |
| Support and delivery | 10% | A realistic plan, named people and relevant references |
| Roadmap and exit | 5% | Commitments are in writing and you can leave cleanly |
Score each area from one to five straight after the demo, individually, then compare notes. Scoring alone first stops the loudest voice in the room from deciding for everyone.
A demo script that works
- Context (5 minutes). The vendor restates your needs in their own words. If they cannot, they have not listened.
- Your scenarios (30 to 40 minutes). The vendor works through each one live, using your data shape, not theirs. You choose the order.
- Break it (10 minutes). Ask them to enter bad data, reverse a transaction or change a rule mid-flow. How the product fails matters as much as how it succeeds.
- Administration (10 minutes). Show how an administrator changes a rule, adds a user, finds an audit record and runs a report, without help from the vendor’s engineers.
- Hard questions (15 minutes). The list below.
- Next steps (5 minutes). Agree sandbox access, references and a date for written answers.
The ten hard questions
These are the questions that rarely come up in a demo and often matter most later. Ask them of every vendor and ask for the answers in writing.
1. What did I just see that is configuration, what needed custom code, and what is not built yet?
This is the single most useful question. Configuration is something your team can change. Custom code means paying the vendor and waiting. “On the roadmap” means it does not exist. Ask the vendor to label each feature they showed, and write the answers on your scorecard.
2. Which regulations and standards does the product support today, and who keeps it current?
Name the ones you care about. Depending on your business, that could be anti-money-laundering and know-your-customer rules, data protection laws such as the GDPR, payment standards such as PCI DSS, or the EU’s Digital Operational Resilience Act (our guide to DORA covers what it asks of firms). Ask how rule changes reach you, whether they are included in the price, and how quickly.
3. Can I see the audit trail for a single decision, from start to finish?
If a regulator or an angry customer asks why something happened, you need to answer from the system, not from memory. Ask the vendor to open one record and show who did what, when and why, including changes by administrators.
4. Who owns my data, and exactly how do I get it out?
Ask for the export format, whether it includes history and attachments, what it costs and how long it takes. A vendor that is vague here is one you will struggle to leave.
5. What happens when something goes wrong?
Ask about backups, how quickly service is restored, how and when you are told about incidents, and what is promised in writing. If you operate in the EU, the incident reporting clocks in DORA mean your vendor’s speed becomes your obligation.
6. Who else touches my data?
Hosting providers, identity checks, payment processors and support tools may all be subcontractors. Ask for the list and where data is stored. You are responsible for your supply chain even when the vendor chooses the links.
7. How do updates work, and will my customisations survive them?
Some platforms upgrade smoothly. Others break custom work every time. Ask how often updates ship, whether they need downtime and what happens to changes built for you.
8. What is the real cost over three years?
Ask for implementation, integrations, third-party data fees, support, extra environments, change requests and annual increases. Our guide to white-label software pricing models explains how to compare licence, subscription and revenue-share deals on equal terms.
9. Who will actually deliver this, and can I speak to a customer like me?
Ask for the name of the implementation lead, a realistic time to first live customer, and two references of similar size and regulatory setting. Ask the references what surprised them after launch.
10. What does leaving look like?
Ask about notice periods, transition help and what happens to your data and configuration if the vendor is acquired or stops trading. A confident vendor answers this calmly. Reluctance is information.
Red flags during a demo
- The demo uses invented data and cannot be repeated with yours.
- Questions are answered with “we can do that” instead of a demonstration.
- Basic reports or integrations are described as custom projects.
- Rule changes require a ticket to the vendor’s engineers.
- There is no clear answer on data ownership, export or exit.
- Every reference customer looks different from you.
- Written answers never arrive, or arrive vague.
Common mistakes buyers make
- Judging the interface and ignoring the audit trail.
- Letting the vendor choose the scenarios.
- Comparing demos from memory, a week later.
- Asking about features but not about people, delivery and support.
- Treating a roadmap slide as a commitment.
- Skipping the sandbox because the demo looked convincing.
After the demo
- Score within 24 hours, individually, then compare.
- Send written follow-up questions and a deadline for answers.
- Test your scenarios in the sandbox with real-looking data and an administrator, not the vendor’s engineer.
- Call the references.
- Compare three-year costs on the same scope.
- Make the decision against the scorecard, and record why. You will be glad of that record later.
Our view
A fair demo is not about catching vendors out. The best vendors welcome a tough test because it shortens the sale and starts the relationship on honest terms. In our view, the right number of vendors to compare is three, because fewer gives you no leverage and more gives you no depth. Spend the time you save on the sandbox and the references, because that is where the real product shows up.
Frequently asked questions
How long should a software demo last?
About ninety minutes works for most financial software: enough for your scenarios and the hard questions without losing the room. Complex products may need a second session for administration and integrations.
Should we let the vendor use their own data?
Only for the introduction. For your scenarios, ask them to use data shaped like yours, including messy cases.
Who should attend from our side?
A decision-maker, someone from operations, someone from compliance or risk, and a daily user. Everyone else can watch the recording.
What if a vendor will not answer in writing?
Treat that as an answer. Anything that matters should be in the contract, and a vendor that will not write it down in the sales process is unlikely to write it down later.
This article is general information, not legal, financial or compliance advice. Requirements differ by country and product, so check them with your own advisers. See our disclaimer. Last reviewed October 28, 2026.
Published by The Funding Journal Editorial. Practical, sourced writing on fintech, crowdfunding, investment platforms, SaaS and AI, and the stories of founders who raised capital.
