A vendor demo answers one question well: what can this system do? It is the wrong question to start with. The one that decides whether a programme succeeds is what you need the system to do, and that is settled in the boardroom, not in the demo room.
Why the order matters
Demos are persuasive by design. Every vendor shows the process that works best in their product, and after three of them a team starts describing its own requirements in a vendor's vocabulary. From there the selection runs on features, the business case is written backwards, and the operating model becomes whatever the configuration workshops happened to produce.
Settling five questions first takes a few weeks. It saves the months that are otherwise spent reopening decisions during implementation.
The five questions
- What should HR be known for in three years?Not a mission statement: two or three things the business will say about HR that it cannot say today. Faster hiring in growth markets, one view of the workforce across countries, managers who run their own team data. Everything else is ranked against these.
- Which decisions are global, and which stay local?Grades, job architecture and core processes usually belong at group level. Labour law, payroll rules and working patterns do not. Deciding this up front keeps a multi-country design from turning into a negotiation in every workshop.
- Which processes will you change to fit the standard?Modern HR platforms reward organizations that adopt standard processes and punish those that rebuild their old ones. List the processes where you will adapt, and the few where your way of working is a real advantage and worth the cost of an exception.
- Who owns the system after go-live?Name the team, its size and its skills before the selection, because the answer changes what you buy. A platform that needs specialists you cannot hire is the wrong platform, however good the demo.
- What does success look like in numbers the board cares about?Time to hire, cost per transaction, payroll accuracy, manager adoption. Pick the handful that link to the business plan and record today's value. A business case without a baseline cannot be defended a year later.
From answers to a demo script
With the answers on paper, the demo changes character. You send vendors a script built from your own scenarios, such as a hire in two countries, a reorganisation or a year-end pay review, and every vendor shows the same things. The scoring model follows the priorities from the first question, and the scores are yours, not the consultant's.
It also gives you a fair way to say no. A system that cannot support a decision you have already made is out, however impressive the rest.
No vendor demo until the operating model is agreed. It sounds slow. It is the fastest route to a decision that holds.
What you have at the end
- A one-page HR ambition that leadership has signed
- A map of global and local decisions
- The processes you will standardise, and the exceptions you will keep
- An ownership model for the years after go-live
- A baseline for the business case
None of it mentions a product. That is the point.
In short
- Decide what HR should deliver before you look at what systems can do.
- Five answers on paper turn a demo from a sales pitch into a test.
- The scoring and the decision stay yours.
Sample article, written to show the format. Aim-Up replaces or edits it before launch.