How to Run a Software Demo That Tells You the Truth
Most software demos are built to impress, not to inform. This article gives Indian business owners a practical way to run the demo themselves, using real transactions, real staff and awkward cases, so the decision rests on evidence.
A vendor demo is a rehearsed performance. The sample customer has a tidy name, the invoice has one item, the payment arrives in full, and every screen loads the first time. None of that is dishonest, but none of it looks like your Tuesday afternoon either.
If you are choosing business software, whether a ready product such as Easy Khata, LegalPrime, MANUPRIME or Sahayak, or a custom build with a technology partner, the demo is your best chance to learn how the software behaves under your conditions. This article shows how to take control of it.
Decide what you are testing before you sit down
Before the call, write down five jobs your business does every week. Use real ones, not categories. For example:
- Raising an invoice for a regular customer who always pays in two instalments.
- Recording a purchase where the supplier's bill does not match what was delivered.
- Handling a return or a credit note a week after the sale.
- Checking who owes you money and how long they have owed it.
- Giving your accountant what they need at month end.
These five jobs become the agenda. If the vendor wants to start with their own script, ask politely to begin with yours. How they react tells you something already.
Bring your own messy samples
Pull out a handful of real documents: a few invoices, a supplier bill, a customer ledger, perhaps a spreadsheet you currently use. Remove anything you would not want shared, but keep the awkward parts. Include:
- A customer with a long, inconsistent name, entered three different ways over the years.
- An invoice with items at different GST rates.
- A part payment that was adjusted against an older bill.
- A product or service that is sold in more than one unit.
Ask the vendor to enter these live, or to show how they would be brought in. You are not trying to catch anyone out. You are finding out whether the software expects your business to be tidy, or whether it can cope with how things actually are.
Run five tests that a polished demo skips
1. The ugly case
Pick the most complicated transaction from your samples and walk it through from start to finish. Count the steps. Notice where the person doing the demo hesitates or says “we can look at that later.”
2. The wrong-person test
Ask the person who will use the software every day, a billing clerk, a store keeper, a front-desk assistant, to join the demo and take the mouse for ten minutes. Owners often judge software by the reports. Staff judge it by how many taps it takes to finish a job during a rush. If they struggle in the demo, they will struggle in the shop.
3. The mistake test
Everyone makes errors. Enter an invoice with the wrong quantity, then correct it. Cancel one. Ask what is recorded about the change: who made it, when, and what the original said. A system that lets you fix mistakes cleanly and keeps a trail is far safer than one that either blocks you or silently overwrites.
4. The access test
Ask to see what a junior staff member can and cannot see. Can they view your margins? Can they delete a record? You should be able to decide this without asking the vendor to change something behind the scenes.
5. The exit test
Ask how you would get all your data out, in a readable format, if you stopped using the product in two years. Ask to see it, not just hear it described. Your records belong to you, and a clear answer here signals a vendor who expects to earn your business each year.
Ask about the people, not just the product
Software is only half of what you are buying. The other half is what happens when something goes wrong at an inconvenient time, such as the day before a filing deadline. Ask plainly:
- Who will help us set this up, and will it be the same person each time?
- In which languages can your team support us and our staff?
- How do we raise a problem, and how will we know it has been received?
- What does training include, and is it for the owner only or for the staff too?
Notice whether the answers are specific. “We will take care of you” is warm but tells you nothing. “Your setup will be done by one person, who will sit with your billing staff for the first sessions” is something you can hold them to.
Keep a simple scorecard
Memory is unreliable after a good presentation. During the demo, or straight after, score each of your five jobs on three points:
- Could it do it? Yes, partly, or no.
- Could my staff do it? Without help, with a little help, or only with training.
- Was the answer clear? Shown on screen, promised for later, or vague.
Anything marked “promised for later” deserves a written follow-up. Ask the vendor to confirm in an email what will be available, from when, and whether it is included in the price. A promise that exists only in conversation is easy to forget on both sides.
If you are asking for a custom build
When you are hiring a technology partner to build or run software for you, there is no finished product to demo. The equivalent is a small working slice. Ask the partner to show you one real workflow, for example, entering a job order and producing the document you need, using your own sample data, before the full project begins. Look at how they ask questions. A good partner will want to see your paperwork, watch your staff, and understand your exceptions before proposing screens. A partner who starts with a feature list and a timeline, and has not yet asked how your counter works, is guessing.
Also ask what you will own at the end: the code, the data, the documentation, the hosting accounts. Get the answer in writing before work starts.
What a good demo feels like
After a demo that has told you the truth, you will feel slightly less excited than after a polished one, and much more certain. You will know which of your jobs the software handles easily, which it handles with effort, and which it does not handle yet. You will know what your staff thought. You will know what you are being promised and what you are being shown.
That is a better position to decide from. Sometimes the answer will be that a product is a good fit with one small gap. Sometimes it will be that the fit is not there, and it is cheaper to learn that in an hour than after a year.
If you would like to run this kind of session with us, bring your five jobs and your messy samples. You can reach the team through AnantaTech Hub, and we will work through them with you.
Tags
- AnantaTech Hub

