Guide · ERP selection
Make the demo prove a complete workflow.
Use the same script for every ERP on your shortlist. Bring a small sample of your own data, include an exception, and record what was demonstrated instead of scoring the number of screens shown.
By the Tellency team · Updated
1. Prepare a small transaction pack
Use a sample customer, supplier, two products, two locations and an opening balance. Add a realistic order, delivery date and expected invoice. Remove confidential information that is unnecessary for the evaluation.
Assign a reviewer from sales, operations and finance. Each person should define the result they need to accept, including reports and approval decisions.
2. Follow enquiry, quotation and order
Show lead ownership, qualification, the quote and the order handoff. Change a quantity or delivery requirement after the first draft and inspect how the change is handled.
Record whether the required templates, approvals and communications were demonstrated, configured during the session or deferred to additional work.
3. Introduce a stock shortage and partial receipt
Ask the buyer to review available stock and prepare the purchasing response. Receive only part of the order, then demonstrate what the warehouse and customer-facing team can see.
Include a branch transfer with a short receipt or a count difference. Review the approval, correction and posting records rather than accepting an unexplained final balance.
4. Add production where it is part of your business
Use a BOM revision, material requirement and work order. Ask the planner to show a capacity constraint, the operator to record progress and the quality reviewer to handle a failed inspection.
Inspect the relevant standard-cost, WIP and variance outputs. Specialist machine integrations, regulated records and detailed production requirements need their own evidence and scope.
5. Reconcile the financial result
Review the invoice, payment, stock posting and required journals. Include a return or correction and show its impact on the balance and reporting.
Ask finance to reconcile a bank-statement line and review the approval controls. Separate product behaviour from any manually prepared report or external accounting step.
6. Score evidence and agree the gaps
Use a consistent status for each requirement: demonstrated, needs configuration, needs integration, needs development or not supported. Record the document or screenshot reference and reviewer alongside the status.
Add acceptance criteria, owner, cost and timing to every unresolved item. For an AI-assisted action, demonstrate a permitted request, an approval request and an action the user cannot perform. Test the role and resulting record, not just the conversational answer.
- Requirement and business owner
- Input record and expected result
- Demonstrated evidence and reviewer
- Gap, implementation owner and acceptance date
- One-time cost, recurring cost and operating responsibility
Your questions, answered
Can we use the script with competitors?
Yes. The purpose is a consistent comparison using your own workflows. Record what each proposed configuration demonstrates and what remains to be delivered.
Does every requirement need a yes/no score?
A binary score can hide implementation work. Separate demonstrated capability, configuration, integration, development and unsupported requirements, then cost and validate the proposed work.
Evaluate Tellency against your own workflows.
Bring your current systems, user count, and operating requirements. We’ll discuss the fit, migration scope, deployment, and total cost.
Book a personalised demo