Traverse StaffingTraverse Staffing
← Operations hiring tips
OperationsFor employers4 min read

Who Belongs in the Room Before You Buy New Business Software

Traverse Staffing · Nov 19, 2026

Most mid-sized employers have lived through this. Leadership approves a new ERP, scheduling platform, CRM or analytics tool. IT scopes it, finance signs off, and three months later the people doing the daily work are finding ways around it.

The technology rarely causes that failure. The order of conversations does.

Treat it as a change in how people work

A system purchase is usually framed as a technology decision. It is better understood as a decision about how dozens or hundreds of people will spend their days. IT should lead the technical evaluation, because it knows the existing environment and what it will have to support. But IT cannot speak for the plant floor, the sales team or the accounting close.

A workable rule: if a group's daily work will change materially, someone from that group is in the room before the decision, not after it.

For most Canadian and US employers, that means some mix of:

  • Operations or plant leadership, who know where work actually stalls
  • Finance, who will test the cost and the return
  • Sales leadership, if the tool touches pipeline, quoting or customer data
  • HR, who will see the hiring, training and turnover effects
  • A frontline supervisor or two, who can say what a shift really looks like
  • IT, for fit, security and support load

The frontline voice is the one most often missing, and it is the one that catches the most expensive mistakes.

Give each group its own reason to care

One business case will not persuade everyone. Each function judges the same purchase by a different measure.

Group What they will ask
Finance Is the cost realistic, and when does it pay back?
Operations Which processes get faster or cleaner?
Frontline teams Does this take work off my plate or add to it?

Vague promises of efficiency do not hold up. A supervisor can respond to "this removes a manual re-entry step that takes each planner about 20 minutes a day." Nobody can respond to "this will streamline operations." Be specific about where the value comes from, then let the people closest to the work test whether the number is believable.

Expect the scope to grow

Early estimates are usually low. Once integrations, data clean-up, training time and process redesign are mapped, the real cost often lands well above the first figure. That is normal, and it is a good reason to have finance and operations involved from the start. A bigger number that the whole group understands is far easier to approve than a surprise discovered mid-project.

The same applies to people. A new platform needs someone to configure it, someone to clean the data, and someone to train users. If those roles are not in the plan, the project stalls or pulls your best people off their real jobs.

Questions to settle before anyone signs

Put these to the whole group and write down the answers:

  1. What problem are we solving, and where does it show up today?
  2. Which workflows change if we go ahead?
  3. What are we assuming about savings or output, and who has checked it?
  4. What will this ask of the people who use it every day?
  5. Do the people closest to the work think the benefit is realistic?
  6. Who will own it after launch, and do we have that person?

The last question matters more than it looks. Many implementations hit their go-live date and then drift, because nobody was hired or assigned to run the system afterward.

Plan the talent alongside the technology

A system purchase often creates demand for skills you do not have in house: a systems analyst, a data specialist, a project lead, a contract implementation resource, or a finance person who can model the return. Deciding this early gives you time to hire well. Deciding it at go-live means paying a premium to fill the gap in a hurry.

Contract talent can cover the peak of an implementation without adding permanent headcount. A permanent hire is better for the role that will own the system for years. Knowing which is which should be part of the plan, not an afterthought.

What to do next

Before your next significant system decision, list every group whose work will change and check that each has a named voice in the room. Then list the roles the project will need, and decide which are contract and which are permanent. If you want help sizing that talent plan or filling those roles, a Traverse recruiter can help.

Your hiring guide

Hiring in operations? See your market the way we see it.

Built for your business alone: who competes with you for the same people and what they pay, where the candidates who would want to work for you live, and how you stack up. It comes from our own weekly index of your market, so you will not find it anywhere else.

Get my hiring guide
My hiring guideBookCall