Search toggle

Start with What You Need, Not What the Market Is Selling

Start with What You Need, Not What the Market Is Selling

The first few demos go well. Each vendor shows something polished, such as an AI assistant, a slick dashboard or a smart onboarding journey, and “we should have that” gets said in the room.

A few demos later, the requirements list has grown. Nothing the team originally needed has been dropped, but the essentials are now buried among the nice-to-haves, and the list looks more like a stack of vendor brochures than a statement of what the business needs.

Nobody made a bad decision. The market simply started writing the requirements.

The short answer: define what you need before you meet vendors. Start with outcomes and prioritise them, and have the main stakeholder groups (typically HR, IT and Finance) sign them off before any vendor is approached. Then test them against real-life scenarios, and let the market show how it can meet them.

How the market quietly writes your requirements

Demos, brochures, analyst feature grids and comparison sites all do the same job: they show what a system can do. That is useful information, but it is not the same as what you need. When it arrives before your requirements are written, it fills the gap. Impressive features turn into requirements, and the most persuasive presentation becomes the standard everyone else is measured against.

By scoring time, the list often reflects the demos the team saw rather than the business it runs.

Write needs as outcomes, not features

A feature describes the system. A need describes what has to be true for your business. A few examples:

  • Feature: "A configurable workflow engine." Need: "Managers can approve leave and pay changes without emailing HR."
  • Feature: "Advanced analytics dashboards." Need: "HR can answer a headcount-by-region question for the board without asking IT or building a spreadsheet."
  • Feature: "Multi-country payroll." Need: "We pay people correctly in every country we employ in, with a clear audit trail."

Outcomes are easier for stakeholders outside HR to challenge, and easier for vendors to answer with evidence instead of a generic yes.

What a good set of requirements covers

  • Context. Why you are selecting, and what success looks like twelve months after go-live.
  • Scope. Regions, headcount, number of HR users, workforce types, and the systems involved, including what the new system must connect to.
  • Priorities. Every requirement scored Must have, Should have, Could have or Won't have, so a nice-to-have can't outweigh a non-negotiable.
  • Real-life scenarios. Specific situations your teams actually face, including the awkward ones, such as an employee who moves between countries mid-year. They are short examples, not process maps, and they let vendors show how their system handles your situations rather than running a generic demo.
  • 5. Sign-off. HR, IT and Finance each confirm the requirements that matter to them before any vendor is approached, and the named decision maker approves the final version.

Three tests for every requirement

  • Could someone outside HR understand it?
  • Could a vendor answer it with evidence, not just a yes?
  • Would losing it change the decision? If not, it is probably a Could have.

Traps to avoid

  • Copying a peer's list. Their needs reflect their business, not yours.
  • Describing the current system. A list built from today's screens carries today's limits into the new platform.
  • Making everything a Must have. If everything is critical, nothing is.
  • Letting the loudest voice set the priorities. Many contributors can shape the list, but one named person owns the final call.

Where independent support helps

This is where Udder's Vendor Selection service begins. You know your business, and we bring structure and market knowledge. We work with you to turn business needs into requirements that vendors can respond to meaningfully, then use them to assess the market and build a long-list.

Your input shapes every part of it, from context and scope to priorities and sign-off, and the decision stays with you. We have no software to sell.

Where to start

Our free Requirements Starter Template (an editable Excel workbook) is built around exactly this approach. The Business Context tab captures what is driving the selection, what success looks like, your timeline and budget, your scope and who is accountable for the decision. The Systems Required tab lists the types of system you need and what they must connect to. The Requirements tab covers eight categories, each scored Must have, Should have, Could have or Won't have.

If you would rather have us lead this with you, talk to our Vendor Selection team.

Choose With Confidence.


Choose With Confidence.

Louise Kabban

Louise Kabban

Related posts