Nearly every firm in the room at Engage Boston 2026 had bought an AI tool in the last 12 months. The results were all over the map. Same category of tool. Wildly different outcomes. One firm cut time-to-submit by a third. The firm sitting two tables over saw almost nothing change.

When the practitioners started comparing notes, the pattern was obvious. The tool was not the variable. The manager was.

This matters because most VPs are still shopping like the software is the deciding factor. They run demos, compare feature lists, and negotiate price. Then they sign, roll it out, and wait for the numbers to move. When the numbers do not move, they blame the tool and start shopping again. That cycle burns money and time, and it never fixes the actual problem.

The Binding Constraint Is the Person, Not the Product

Here is what the room agreed on by the end of that session. The AI tools available to staffing firms right now are good enough. Sourcing, matching, note-taking, outreach drafts, resume parsing. The core products work. The gap between a firm that gets results and a firm that does not is almost never the software.

The gap is manager readiness. Whether the frontline manager understands what the tool does, has rebuilt the team's daily workflow around it, and holds recruiters accountable for using it the new way.

Think about how a tool usually lands. IT flips it on. There is a 45-minute training webinar. A few reps watch it. Then everyone goes back to doing their job exactly the way they did it last week, except now there is an extra tab open that nobody opens.

That is not an adoption problem. That is a workflow problem wearing an adoption costume.

The recruiter still starts the day the same way. Still sources the same way. Still writes notes the same way. The tool is sitting right there, capable of doing three of those steps faster, and it does not get used because nobody changed the steps. The manager never redesigned the work. So the work stayed the same.

Why This Is Good News for Your P&L

The best part of this framing is what it means for your budget. If the binding constraint were the software, you would be stuck buying and rebuying until you found the magic tool. That tool does not exist.

But the constraint is manager readiness. You can fix that without changing your tech stack. You already own the tool. You already pay the licenses. The value is sitting there waiting for someone to redesign the workflow and hold the team to it.

This is the core of how I think about making change stick. Build. Change. Adopt. Most firms nail Build. They pick and install the tool. They skip Change, which is redesigning the actual work. Then they act shocked when Adopt never happens. Adoption is not a phase you get to. It is the result of doing the Change work first.

Let me be specific about what Change looks like. Take a recruiter's morning. Today it might be: check email, review the ATS queue, source three candidates, screen two, log notes. If your AI tool handles sourcing and note drafting, the new workflow is not the old workflow plus a tool. It is a different sequence.

  • Recruiter opens the AI-sourced shortlist first, already built overnight.
  • Recruiter reviews and rejects in 10 minutes instead of sourcing from scratch in 90.
  • Recruiter spends the saved time on candidate calls, which is the part a human has to do.
  • The tool drafts the notes. The recruiter edits and approves in two minutes.

That is a redesigned workflow. It names what the tool does, what the human does, and what the human stops doing. Without that redesign, the tool is a feature nobody asked for.

What Manager Readiness Actually Requires

Manager readiness is not a personality trait. It is a set of concrete things a manager can do. You can build it in weeks.

First, the manager has to understand the tool at the workflow level, not the feature level. Not "it does AI sourcing." Instead, "it replaces the first 90 minutes of my recruiter's morning and here is what they do with that time."

Second, the manager has to own the redesign. Not IT. Not the vendor. The person who runs the team rewrites the daily steps, because they are the only one who knows how the work really flows.

Third, the manager has to inspect the new behavior. If the old workflow is still allowed, recruiters will drift back to it in a week. People do what gets checked. The manager checks that the new steps are the steps.

Firms that got results at Engage Boston did these three things, whether they used that language or not. Firms that did not get results skipped all three and pointed at the software.

There is a hard truth in here for owners and PE ops leaders. If your rollout failed, the tool did not fail you. Your change process failed. That is uncomfortable, but it is also the reason you can fix it. You control the change process. You do not control whether the vendor ships a better model next quarter.

The Move This Week

Pick one team. Not the whole firm. One team with a manager who is willing.

Sit with that manager for 30 minutes and map the recruiter's current daily workflow, step by step, on paper. Then mark every step your AI tool could do. Now rewrite the daily steps so the tool owns those and the recruiter's time shifts to the human work.

Give that new workflow to the team as the required process, not a suggestion. Have the manager inspect it every day for two weeks. Track one number that matters, like time-to-submit or calls per recruiter per day.

In 30 days you will know more about your AI investment than a year of dashboards told you. And you will have proof of what a real rollout looks like, ready to run on the next team.

You do not need a new tool. You need a redesigned workflow and a manager who owns it. That is the whole game.