Kraig had redlined the same clause a hundred times. Anti-assignment language, section 4.2, three paragraphs of boilerplate he could recite from memory. So when his analyst ran the draft through a new contract review tool and it flagged the same issue, plus two exposure points Kraig hadn't caught, in under four minutes, he didn't feel relief. He felt exposed.
His team had built its reputation on being the ones who caught what everyone else missed. That was the whole pitch, internally and externally. If a piece of software could catch it faster and cheaper, what was the pitch now?
That question is landing on desks across managed care departments this year, and most people are answering it the wrong way. They're treating it as an IT rollout to survive rather than a redefinition of the job to get ahead of. Those are not the same problem, and the difference is going to determine who's still negotiating contracts in five years and who's administering the software that replaced their function.
The part you don’t want to hear, and neither does Kraig
Here's the uncomfortable truth: a meaningful share of what fills a contract analyst's week, first-pass redlining, clause comparison, rate modeling, compliance checks against a preferred-language library, is exactly the kind of structured, repeatable work that AI tools are already good at. Not someday. Now. I've watched review cycles that used to take days get compressed into hours, with the software doing a more consistent job of flagging boilerplate risk than a tired analyst on their fourth contract of the day.
That's the external problem, and it's real. But it's not the one that actually threatens careers.
The one that threatens careers is internal. It's the analyst, the manager, even the VP, who quietly decides the tool is a threat to be resisted rather than a floor to build on. Who lets someone else on the team become the one who "gets" the AI stuff while they stay in their lane. Who mistakes speed at rote tasks for the whole job, forgets that the whole job was never just the redline, and lets that misunderstanding cost them the seat.
I've spent over thirty years in this field, five states, hundreds of contracts, and I have never once seen a negotiation won by whoever found the anti-assignment clause fastest. I've seen negotiations won by the person who understood what the payer actually needed, read the room when a stated position was a bluff, and knew which of eighty-five preferred provisions to trade away to protect the one that mattered. None of that shows up in a redline. All of it is still yours to own.
What actually changes, and what doesn't
The work that's automatable was never the differentiating work. It was the entry fee. AI is about to make that entry fee nearly free, which means the people who defined their value by how fast they could clear it are about to find that value gone. The people who defined their value by what they did after the redline was done are about to find themselves with more time to do more of it.
So the plan isn't to compete with the tool. It's to move up and out of the tool's lane, deliberately, before the decision gets made for you. That starts with learning the tools well enough to direct them instead of waiting on them, because whoever understands the tool's blind spots ends up managing whoever only knows its outputs. It continues with doubling down on the negotiation skills that were always human: reading counterparts, building the relationships that get a stalled negotiation unstuck with one phone call, and knowing when the data says one thing and the market says another. And it means going looking for the complexity AI can't touch yet, risk-based arrangements, novel partnership structures, the kind of contracting that requires judgment calls no training set has seen before, because that's where your seat gets more secure, not less.
Before you build a plan, run the honest version of this self-check:
Can you name, specifically, which parts of your current role are pattern-matching that a tool could learn this year?
Do you know how to direct an AI tool's output, or only how to receive it?
When was the last time you led a negotiation that required reading a person, not just a spreadsheet?
Are you the one your organization would ask to evaluate a new AI contracting tool, or the one it would explain the tool to?
If your routine tasks disappeared tomorrow, what would you spend that time on that a machine can't?
If more than one of those has an uncomfortable answer, that's not a verdict. It's the starting line.
What's actually at stake
Do nothing, and the risk isn't dramatic. It's quiet. It's the org chart redrawing itself over eighteen months, with the AI-fluent analyst getting pulled into the room for the complex renewal and you getting handed the routine ones. It's the slow realization that you've become the person who explains the old way of doing things to people who no longer need it explained.
Do something, and the upside is just as real. Six months after that redline moment, Kraig's team wasn't smaller. It was doing different work. The tool handled first-pass review on two hundred contracts a quarter that used to eat a third of his staff's time. Kraig spent that recovered time redesigning the value-based arrangements in his portfolio, work nobody was automating, and walked into his next executive committee meeting with a rate improvement story that had nothing to do with how fast anyone could find a clause.
The tools are not the threat. The refusal to change what you spend your time on is.
Start this week: pick one tool your organization already has access to, learn what it's actually good at, and hand it the most repetitive piece of your job. Then go spend the time you got back on the part of the work only you can do.
You were never valuable because you were fast. You were valuable because you knew what fast couldn't see.
Call to Action: If you've already started shifting how your team spends its time because of AI, or you're watching your organization get this wrong, tell me about it in the comments. I read every one, and the practitioner stories are what make this newsletter worth writing.
And forward this to the colleague who's still hoping this whole AI thing is a phase. It isn't, and neither is their contract review backlog.
About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Subscribe to his free weekly newsletter at https://www.KevinWatsonBarron.com
Disclaimer: This article is provided for general informational and educational purposes only. It reflects my personal views and observations based on professional experience in healthcare finance, managed care, payer relations, and revenue cycle operations. It should not be interpreted as legal, financial, regulatory, actuarial, or reimbursement advice. The content is not intended to represent the official position of my employer, any payer, provider, professional association, or other organization with which I may be affiliated. Readers should consult their own legal, financial, compliance, actuarial, or operational advisors before making decisions based on the issues discussed. Any references to payers, providers, regulations, market trends, or reimbursement practices are intended for discussion and education only and should not be construed as a statement about any specific contract, negotiation, patient matter, or confidential business arrangement.
