Go-live day usually feels good.

The system is live. The vendor's team is on-site or on the call. Everyone's logged in. The demo data is gone and your real accounts are in there. You made it.

Then the vendor team wraps up. Training calls end. The project manager who knew your agency and answered questions within the hour is replaced by a support ticket queue.

And real life resumes.

This is where most AMS projects quietly start to fall apart. Not because the system doesn't work. Because adoption doesn't get the same attention after go-live that implementation did before it.

Here's what I've seen happen, and what to do about it.

Workarounds happen fast

Within the first two weeks, your staff starts finding friction points. Steps that take longer than they expected. Workflows that don't quite match how they used to handle something.

Some of that friction is normal. New systems take adjustment.

But when friction doesn't get addressed, people find workarounds. They keep a spreadsheet for the things the AMS doesn't do easily. They text each other for status updates instead of checking the system. They enter data quickly and mean to update the AMS later, which means later never happens.

These workarounds aren't laziness. They're your staff adapting to get through the day. The problem is that once a workaround becomes a habit, it becomes invisible — and over time it becomes the actual workflow, running parallel to the system you're paying for.

Six months in, you can have a perfectly functional AMS that your team has quietly routed around in a half-dozen places without anyone naming it as a problem.

Adoption concentrates in the wrong places

In most agencies after go-live, one or two people become the AMS people. Usually the most tech-comfortable members of the team. They know the system well. Everyone else learns that if they need something done in the AMS, they can ask one of those two people.

This isn't a disaster, but it's a risk. The AMS people become a bottleneck. And if either of them leaves, the institutional knowledge of how your agency actually uses the system goes with them.

The agency owner often has a different relationship with the system than the rest of the team. Usually a shallower one — looking at reports, checking pipelines. But the day-to-day transactional work is handled by CSRs, and if those CSRs are working around the system in ways nobody's tracking, the reports the owner sees aren't fully accurate.

Nobody audits adoption at 90 days

I've been in agencies where, six months after implementation, the agency owner thought the AMS was running well. And technically it was. The data was in there. Policies were being entered. The system was on.

Then you'd ask someone to walk you through how they process a renewal. You'd watch them do half of it in the AMS and half of it in a spreadsheet that nobody mentioned in any of the implementation conversations.

The audit is simple. Pick 5 to 10 workflows your team runs daily — renewals, mid-term changes, new business, COI requests, claims follow-up. Ask someone to walk you through how they actually do each one. Watch, don't just listen.

If they're using the AMS for the whole workflow, great. If they're routing around it at any step, that's the thing to fix.

This is worth doing at 30, 60, and 90 days. By then, patterns are set. Catching it at 90 days means you're fixing workarounds before they become permanent.

The person who needs to own this isn't the vendor

The vendor's job ends when implementation ends. Maybe with a check-in call at 30 days. After that, adoption is your problem to manage internally.

Someone in your agency needs to own ongoing usage. This doesn't have to be a formal role. It just needs to be a person who's accountable for watching how the system is being used and raising problems when they see them.

In a 5-person agency, that might be the owner or the most experienced CSR. In a larger agency, it might be an operations manager. The specific person matters less than whether the responsibility actually belongs to someone.

Without a named owner, adoption problems get noticed when they've already been baked in for months. With one, you're catching friction early enough to do something about it.

The math on partial adoption

A system that's fully adopted delivers its full value. A system that's 60% adopted — because 40% of the workflow still runs outside it — delivers partial value at full cost.

The license fee is the same. The implementation cost is the same. The only variable is how consistently your team uses the thing you bought.

I've been in agencies paying for a comprehensive AMS while their CSRs are still doing significant work in Excel and email because the handoff between "we went live" and "we actually use this" never got finished.

Go-live is not the finish line. It's the starting line for adoption. Plan for what comes after it.