Book a live demo

Articles

How to Prepare for an ERP Demo: Bring Your Own Scenarios

Get more from any ERP demo: write down your real scenarios, bring the right people, and test the software on your own work, not the vendor's script.

An ERP demo is only useful if it shows the software doing your work, not the vendor's. The best way to prepare is to write down a handful of real scenarios from your own business, bring the people who live with those problems, and ask the vendor to walk through them live. The rest of this article explains how to do that well.

Why the vendor's script is not enough

Every vendor arrives with a polished demo. The sample company has perfect stock, every invoice ties, and nobody ever forgets to record anything. It looks impressive, and it tells you very little.

Your business has a half-delivered order sitting in the godown. It has a regular party who pays part of his udhaar (what he owes on credit) in cash and part by cheque. It has a production run that used more material than planned because a batch was rejected. A scripted demo answers "can the software do X?" The question you need answered is different: "What happens when X goes wrong on a busy afternoon, with three people involved?"

You will only see that answer if you bring the situation with you.

Write down your scenarios before the demo

Sit with your team before the demo and list the moments where things usually go wrong. Five or six good scenarios are enough. Here are the kinds that tend to reveal the most:

  • A purchase that needs approval. Today it might happen over a phone message or on a paper slip. Who requests it, who approves it, and where is the approval recorded?
  • Goods that arrive short or damaged. The supplier's bill says one quantity, the godown counts another. How does the difference get recorded, and does accounts find out?
  • A credit sale to a regular party. He pays in instalments, sometimes late. Can you see what he owes at a glance?
  • A production run. Raw material goes in according to the bill of materials, but actual consumption is different. Is the cost calculated or still estimated?
  • A stock count that disagrees with the records. The register says one figure, the shelf says another. What does the software do about it?
  • The report you wait days for. Whatever the owner asks for every month and gets late, ask to see it built in front of you.

Make them messy

Write each scenario as a short story: who starts it, who touches it next, and where it ends. Include the exception, because that is where software shows its quality. "Customer orders 200 cartons, we dispatch 150, he returns 10 as damaged, then pays for 120" is far more useful than "create a sales order".

Keep your real data at home

You do not need to hand over your actual books for a demo. Use realistic item names, units and quantities, but change the figures. The point is to test how the system behaves, not to expose your accounts to someone you have not hired yet.

Bring the right people to the room

Owners often attend demos with only their accountant. That is a mistake. The people who will use the system every day see things you will not.

Bring your storekeeper, someone from sales, and your production supervisor if you make things. Many of them are not IT-trained, and some will be quietly worried about new software. Watch their faces. If a screen confuses them in the demo, it will be bypassed in real life, and you will be back to registers within months.

Ask each of them to bring one question of their own. A storekeeper's question ("How do I record stock that moves between two godowns?") often uncovers more than a director's.

What to watch for during the demo

Once your scenarios are on the table, keep the vendor on them. A good demo session follows this kind of path:

  1. Follow one transaction from start to finish. When goods are received in the godown, does that same entry reach stock and accounts, or does someone have to type it again?
  2. Ask who made each entry, and when. If the system cannot tell you, it cannot help you find where stock went missing.
  3. Switch roles. Ask to see the same screen as the storekeeper and then as the director. Who can change what?
  4. Ask to see it on a phone. Much of your business happens away from a desk.
  5. Break something on purpose. Enter a sale that would take stock below zero, or leave a required field empty. Does the system notice, and does anyone get told?
  6. Ask for the trial balance at the end. If the books do not tie in a clean demo, they will not tie in your business.

Questions to ask any vendor before you sign

Some answers matter as much as the software itself. Ask every vendor these, and ask for the answers in writing:

  • What happens during an internet outage or load-shedding? Can staff keep working, and what happens to entries made during the cut?
  • Where is our data kept, who backs it up, and how do we get a copy of it?
  • Can you move our existing spreadsheets and registers into the system, and who does that work?
  • How does the system handle the tax invoicing rules that apply to our business?
  • What are your support hours, and who exactly do we call when something breaks?
  • What does the price depend on, and what is not included in it?

A vendor who answers vaguely during the sale will answer vaguely after it.

How a Sentinel demo fits into this

Sentinel is one system for every department: CRM, sales, purchase, inventory, manufacturing with bills of materials, dispatch, accounting, HR, payroll, warehouse and documents. That makes it a good fit for the scenario approach, because your stories cross departments, and so does Sentinel.

Bring your list to a Sentinel live demo and ask us to follow it. The screens use sample data, so you can test the flow without sharing your books. Things worth checking against your scenarios:

  • Every entry records who made it and when, so the stock ledger and the books show who did what.
  • Accounting reconciles across one or several companies, with a trial balance that ties.
  • Access is by role: each person sees and changes only what their role allows.
  • It works on desktop and on every phone, and shop-floor screens can be in Roman Urdu for staff who are used to running their part of the business in spreadsheets.

Ask the AI agent a question in plain English or Roman Urdu, such as "Kis item ka stock kam hai?" It reads every department, runs checks for stock below zero, totals that do not add up, missing fields and unfinished work, and raises each problem to the person responsible. It never changes a record by itself.

On price: Sentinel is demo first, then a quote and an invoice. The quote depends on how many people use it, how many companies it keeps the books for, and which departments you need. You can read more on the plans page.

Questions owners ask

Should I share my real books before an ERP demo?

No. Describe your scenarios with realistic but changed figures. A good demo tests how the system handles your situations, and that does not require your actual accounts. Share real data only once you have chosen a vendor and agreed how it will be handled.

Why do some vendors not give a price before the demo?

Because the price often depends on things they do not know yet, such as how many users you have and which departments you need. That is reasonable, but you should still ask, before the demo, exactly what the price will depend on. If a vendor cannot tell you that, be careful.

Is one demo enough to decide?

Often it is not. If your scenarios were not all covered, ask for a second session focused on the ones that were skipped, and bring different people from your team. Decide only once the people who will use it daily have seen their own work on screen.

Book a live demo

If you have a list of the situations that cost you sleep, from a short delivery to a stock count that never matches, bring it along. Book a live demo of Sentinel, bring your team, and see how one system handles your work, not a script.

Sentinel

ERP · CRM · AI agent