Win the Room:
Getting Stakeholder Buy-In for HR Technology

Part 1 and Part 2 of this series focused on building a case your leaders can trust. This article will help you get people with different jobs and priorities to trust the same case.

Most of that work will be translation. You’ll need to figure out how to tailor the same story to different perspectives.

In this article, we’ll walk through how to:

• Understand what each stakeholder is actually protecting
• Share your case before it’s finished—on purpose
• Sequence conversations instead of simply scheduling them
• Prepare for the objections most likely to stall the decision
• Turn stakeholder alignment into rollout readiness
  
  

Know what each stakeholder is protecting.

A strong case can still stall when everyone hears the same pitch.

Gartner found that content focused on one stakeholder’s concerns can reduce group consensus by 59%, while content built for the full buying group makes a high-quality decision three times more likely. Tailor the conversation, not the case. The facts should stay the same, but what you emphasize should change.

When we asked HR leaders which stakeholder was hardest to win over, nearly everyone named finance. Not because finance doesn’t understand HR, but because they’re weighing this investment against every other request the business will make.

Finance needs something it can compare. Show what the problem is costing today, what the investment could change, and why it deserves priority now.

But the hardest stakeholder isn’t always defined by title. Sometimes it’s simply the person with the least time and attention to give you.

You don’t need to build five different business cases. But you need to understand what each person is responsible for protecting—and make it easy for them to see how the same investment supports it.

CEO

What they're protecting: The company’s ability to execute strategy and get more from its investment in people.

What earns their support: A clear case for how better talent decisions will improve business performance.

Where they'll push back: “Why is this a priority over the other things we could fund?”

CFO

What they're protecting: Capital that could be invested elsewhere.

What earns their support: A defensible return based on full costs, conservative assumptions, and measurable results.

Where they'll push back: “Why is this worth more than the alternatives we already have?”

CHRO

What they're protecting: Their credibility as a leader who can turn people strategy into business results.

What earns their support: A plan tied to the outcomes they report to the CEO, with a credible path to adoption.

Where they'll push back: “How do I know this will deliver where past HR tech hasn’t?”

IT

What they're protecting: The security and reliability of the company’s systems.

What earns their support: Early involvement and a specific plan for data security, integration, and support.

Where they'll push back: “Will this create risk or another system we have to maintain?”

Procurement

What they're protecting: The company’s ability to secure favorable terms and limit vendor risk.

What earns their support: A chance to evaluate alternatives and negotiate before making a vendor decision.

Where they'll push back: “Have we committed to this vendor before checking the cost and contract?”

Managers & HRBPs

What they're protecting: Their calendar and their team’s attention.

What earns their support: Something that makes work easier and decisions clearer—rather than more complicated.

Where they'll push back: "This just feels like one more tool to learn."

Share your case before it's finished.

Your instinct might be to perfect your case before letting anyone see it. But the most experienced HR leaders we spoke with bring stakeholders in while there’s still something left for them to influence.

A finished case can feel like a decision that’s already been made. That puts stakeholders in critique mode. An unfinished case gives them something to help shape—and makes it more likely they’ll support what comes out of the process.

Sharing early doesn’t mean taking a half-formed idea to everyone at once. You still need to be deliberate.

One HR leader recommends starting with the departments that have the most influence over the decision and the people most likely to object. Also identify the real decision-maker and learn what matters to them before deciding how to present the case.

Approvers who aren’t as involved in shaping the proposal want that early conversation, too.

Before you lock in your business case, ask each stakeholder three questions:

• What would you need to see to believe this is worth doing?
• What would make you say no?
• Who else should be part of the conversation?

Then use their answers to strengthen the case. You’ll face fewer surprises—and spend less time defending it later.

Sequence your conversations intentionally.

Who you involve—and when—should be a deliberate plan, not a distribution list.

A few principles can help you get the sequence right:

Start with who might say no outside of the room.

You can choose the vendor, but someone above you may still decide whether the investment happens. And they may never attend a meeting you lead or a demo you organize.

Find that person early. If you can’t meet with them directly, ask your sponsor what they’ll need to see and build it into the case.

Bring IT in before you have a favorite vendor.

It’s tempting to wait because you don’t want to ask for their time until you know you need it. But when you bring in IT late, you’re asking them to assess a product they’ve never seen, with little context for the business problem it solves. The conversation will quickly narrow to provisioning, security, and data flows.

Bring IT in early enough to shape the requirements. Ask about single sign-on, HRIS integrations, data access, security review, and internal capacity. Share the vendor’s security documentation before anyone asks for it, and bring a rough integration map they can edit instead of making them build from scratch.

Ask managers about the problem before you ask them about a product.

If you invite managers to a vendor demo without involving them in the decision first, you’re asking them to evaluate software without context. They’ll naturally focus on the most obvious question: How much more work will this create for me?

Bring managers in before you build a shortlist. Ask what’s hard about the current process, where they lack context, and what would help them make better decisions. Use what you hear to shape your requirements and evaluate vendors. You may also identify early champions who can make the case more credibly than HR can on its own.

Give yourself more runway than the price suggests.

If the investment isn’t budgeted, you may have to wait until it is. But budget isn’t the only thing that sets the timeline. The scale of the change often determines how many people need to agree.

A platform that changes how managers set goals, hold 1-on-1s, review performance, and make talent decisions will take longer to approve than a tool used by three people. Build that reality into your timeline from the start.

Prepare for the objection underneath the objections.

Three objections stall more HR technology cases than almost any others:

• Can't we consolidate this into our HRIS?
• Can't we do this with a general AI tool?
• Can't we keep doing what we're doing?

They sound different, but they all ask the same question: Can we get where we want to go without buying anything?

That’s a fair challenge. Treat each alternative seriously, then compare it with the investment based on what leaders can see, decide, and act on today—and what would change.

Price the current state.

Doing nothing still costs something. Calculate the time employees spend pulling data together, the decisions leaders delay, and the problems they identify too late. Then ask whether the current approach will still work at the size and complexity you expect two years from now.

Some of those costs look like normal work, which makes them easy to miss. Korn Ferry found that 71% of leaders rely on instinct rather than insight when making talent decisions. Only 4% feel highly confident in those decisions when talent data is disconnected, compared with 55% when it is connected.

Root your comparison here: what leaders can confidently decide today versus what they could decide with a fuller picture.

Compare the work required on both sides, too. Ask vendors to walk you through each implementation phase and identify who they’ll need from your team. Estimate the internal hours involved, separating HR administrator time from IT time.

When we asked HR leaders how they overcome the do-nothing alternative, one challenged the premise:

That’s the right standard. If your case can’t beat the status quo honestly, it needs more work. Name DIY options yourself and evaluate them fairly instead of waiting for someone else to introduce them in the approval meeting.

And if the honest answer is “not yet,” set a date to revisit the decision. Improve what you have, keep measuring the problem, and return with stronger evidence. You’ll protect your credibility and leave the door open.

When the alternative is your HRIS, focus on fit.

You don’t need to argue that your HRIS is a bad product. It was built to run payroll, benefits, employee records, and other core processes accurately and at scale. Ask whether its talent capabilities were built with the same depth—and whether they support the decisions you’re trying to improve.

One invoice doesn’t guarantee one connected dataset. You can consolidate vendors and still leave engagement results, performance ratings, growth plans, and retention signals separated inside different products.

Decide where “good enough” is enough and where deeper capability matters. Most organizations can’t afford best-of-breed technology everywhere, and they shouldn't try. Your job is to show why this use case deserves greater investment.

When the alternative is generic AI tools, start with who’s asking.

Finance may want to know whether a tool you already pay for can do the job. Compare the options based on the data each tool can access, the consistency of its analysis, and whether leaders can trace and defend its outputs.

If a general AI tool can access only part of your people data, it can produce a confident answer from an incomplete picture. Without governed workflows and clear sourcing, small changes in how someone asks a question may also produce different answers. That may be acceptable for early exploration. The risk increases when the output informs a promotion, talent investment, or retention decision someone may question months later.

IT and legal will focus on a different set of questions: What can the model access? How does the vendor use that data? Where does it go? Who can view the output? Can the organization audit how employees use it?

Get those answers from your finalists in writing before they come up in an approval meeting. Ask which models power each feature, what data they access, whether customer data trains them, what controls and audit records are available, and what the contract guarantees.

Alignment now is adoption later.

It’s tempting to treat stakeholder alignment as a gate to clear before the real work begins. But many of the people you need to win over now will also determine whether the rollout succeeds: the managers who will use the process, the IT team that will support it, and the executive who must keep backing it when something slips.

That makes alignment the first stage of change management. When you bring people in early, they understand the decision and own part of the outcome. When you work around them, they have little reason to support the platform when adoption slows, or budgets tighten.

Gartner found that nearly half of HR staff believe HR technology has damaged HR’s reputation within their organization. That’s the risk when HR secures approval for a purchase without building shared ownership for what comes next.

The room isn’t only asking whether the software is good. Stakeholders want to know whether the value will justify the disruption—and whether you’ll be able to prove it.

That’s where Part 4 comes in. We’ll build the execution plan that belongs in the proposal: what happens in the first weeks and months, who owns each piece, and how you’ll show progress. Because getting the case approved is only useful if the organization can carry it through.