The demo that never fails
Every vendor deck has the same shape: clean records, instant search, a report that makes the room nod. That is their Tuesday, not yours. If you have not mapped your process first before the call, the demo becomes theatre — and the contract still signs on your messy reality. The room leaves feeling informed; ops leaves knowing they will still be re-keying half the job into a spreadsheet by Thursday.
Before the call, pick one real case from end to end — quote to job to invoice, or lead to fulfilment to cash. Name the system of record for each fact along that path. Then bring the edge case that broke the last tool: partial delivery, credit note, split billing, a customer who changes scope mid-job, whatever makes your ops lead sigh. If you cannot describe that case in five minutes without saying "it depends", fix the map before you invite vendors in.
During the demo, ask them to enter your data shape — not paste a CSV they prepared overnight. Ask where ownership lands when step three fails: who gets the alert, who can override, what audit trail exists. Ask for export and API paths before you ask about AI add-ons. If they cannot show your handoff without reaching for "we would configure that in professional services", note the fit cost — the same calculation as working out whether custom software is worth it.
Red flags that sound polite
Some vendor phrases should make you write things down. "That is on the roadmap." "We usually handle that in the integration phase." "Most customers do not need that." Translation: you will pay in re-keying, shadow spreadsheets, or operational debt. Compare three vendors on the same ugly case, not three polished tours of feature grids.
The good signs are less obvious but more useful. They ask clarifying questions about your handoff. They show permissions and posted records, not just pretty dashboards. They admit a gap and quote the effort honestly rather than waving at a future phase.
Score the demo like a test, not a date
Turn your case into pass or fail criteria before anyone shares a screen. Something like: given a job that is 80% complete with a credit note pending, show me the invoice line, who approved it, and the export finance uses. If two of five criteria fail, that is data — not rudeness. Work through twelve questions for bespoke versus off the shelf before you reach signatures.
Bring someone who runs Tuesdays, not only someone who signs cheques. The ops lead who will live in the tool should be able to say "I would still use the sheet for step four" while the demo is running. That sentence is worth more than a feature matrix.
After the call: decide without amnesia
Within 48 hours, write what worked, what was hand-waved, and what must be true before you proceed. Share it with finance and the floor — the same discipline as clear ownership for system work. If every vendor failed the same test, your process or data may be the real blocker. A process audit beats another round of identical demos.
Procurement without losing the plot
Procurement will ask for feature matrices and commercial terms, and that is fine. Insist the technical score includes your test cases, not checkbox theatre. Capture integration estimates in writing when vendors wave at professional services. Compare total cost of ownership at year three, including the re-keying you already pay for today. A cheaper licence that fails your ugly case is not actually cheaper.
Book a free systems review if you want a second pair of eyes in the room — we are based in Teesside and the North East and work remotely when the fit is right. What we offer includes a process audit before you sign, not after.