Slow Down to Go Fast: How First Command Moved 800 Reps Off a Legacy System Without Losing Their Trust

Most migration stories are told in one of two ways: the cutover was smooth, or the cutover was a disaster. Kay Davis's story is more useful than either, because it's not really about the migration at all. It's about what you do in the months before you flip the switch.

Kay is the VP of Financial Analysis and Transformation at First Command Financial Services, a company that serves active-duty and veteran military families, based out of Fort Worth, Texas, with additional offices all over the USA. Over the past year, her team moved roughly 800 reps off SAP Callidus and onto CaptivateIQ, while simultaneously simplifying the plan those reps had been running on for years. 

Two changes, one rollout, zero room for reps to lose confidence in their paycheck.

That's not a small bar to clear. CaptivateIQ's own 2026 State of Incentive Compensation Management report found that 91% of organizations report high payee trust today, but 64% experienced a payout error in the last year. Trust and accuracy aren't the same thing, and Kay built her team's rollout like she understood the difference.

Kay shared this story at Captivate 2026, our annual user conference, where the dominant message from the stage was, “Move fast.” So when she stood up and said the opposite, people listened. 

"I think I have a very unpopular opinion, or at least unpopular for this conference," she told the audience, "because the message we've been hearing from this stage is that you have to go fast, that it’s all about speed. And what I’ve found is that to go fast, we need to first slow down.” 

What "slowing down" actually looked like

The story of First Command's migration might have seemed slow to an outsider. In reality, it was deliberate — a specific sequence of moves, each one built to protect a rep's trust in the system.

1. The CEO went first. Before the project team said a word, the CEO signaled support for the change at the company's own sales conference. Reps heard it from the top before they heard it from anyone touching the system. That sequencing mattered: once the CEO had said it publicly, reps couldn't write the change off as something a middle manager was pushing on their own.
   
   
2. Communication cascaded down, not out. Updates moved through the leadership chain in order, monthly, so no rep ever heard about a change from someone two levels removed from their manager. This closed off the gap where rumors usually take hold — every rep heard it from the person they already reported to, not secondhand.
   
   
3. Sales leaders interviewed their own reps. The project team produced short video "podcasts" where sales leaders sat down with reps to talk through what the new plan actually meant for their business — with the questions coming from someone the rep already trusted. Reps open up differently to someone they already trust than to a new voice, so the concerns that came out of these conversations were the real ones, not the polished version people give a stranger.
   
   
4. They piloted with real stakes. More than 12% of the rep population ran the new plan before full rollout — large enough to surface real problems, not just a token test group. At that size, the pilot actually hit the weird commission scenarios and data edge cases, so the team was fixing them before full rollout instead of after.
   
   
5. The back office got the same briefing as the front line. This is the detail most rollout plans miss entirely. Reps call whichever back office person they already know, not whoever technically owns the answer — so if that person was left out of the briefing, the rep's confidence in the whole system would have taken the hit, math notwithstanding.

"Every rep out there has a favorite home office person," Kay said, "and they're going to call that home office person, whether or not the topic is within that person’s scope. What that means is we also had to make sure that our communication plan stretched over the home office and all of the back office teams."

This tracks with what CaptivateIQ's own research found: when rep inquiries spike, it's rarely curiosity. They're checking the math, and every unanswered question wears down trust before an actual error ever happens.

The unglamorous throughline: documentation

Kay's "slow down" philosophy wasn't just about change management theater. She connected it to something most comp teams haven't had to reckon with yet — and won't be able to put off much longer.

"Your AI agents, your AI support system – it runs on whatever you feed it," she said. "So if you don't have clear documentation of your process, if it's not well versioned or it's outdated, your AI won’t perform well and you won’t get the results you want."

Shared checklists. Dependency maps. Formulas that are actually written down somewhere rather than living in one person's head. It's not exciting work, but it's the same discipline that made the SAP Callidus migration hold together — and it's the same discipline that will determine whether AI helps a comp team or just adds a faster way to be wrong.

Three questions to steal from this playbook

• Does your executive team say something in public before your comp team says anything at all?
• If a rep called someone outside your comp team with a question tomorrow, would that person know what to say?
• If you handed your current process documentation to an AI agent today, would it actually work — or would it repeat whatever gaps already exist?

Kay has one more line worth keeping, from a leader she credits for shaping how her team thinks about setbacks: "Don't let a good disaster go to waste." Whether the disruption is a system migration or a government shutdown affecting the military families First Command serves, the instinct is the same — treat every outcome, good or bad, as something worth a real postmortem.

That instinct is exactly what the data says most comp teams are missing. High trust isn't a clean bill of health. It's a lag indicator: the errors happening now won't show up in a trust score until later, and by the time they do, the withdrawal has already been made.

First Command didn't wait to find that out. They spent months making the deposit before they needed it — the CEO's first public word, the cascade down the org chart, the back-office briefing most rollout plans skip entirely — so that when the switch is actually flipped, no trust was wasted.

Stories like this one are why the 2026 State of Incentive Compensation Report exists — to put numbers behind what practitioners like Kay Davis already know from experience. Download the full report to learn more.