ImplementationAutomationAdoption
I work the part of the deal that comes after the signature — implementation, adoption data, and applied AI — so teams actually use the systems they buy.
I design implementation around how the team actually works — milestones, stakeholders, integrations — and stay through the messy middle until the new system is just how work gets done.
See it in practice →We define good adoption in numbers on day one. I track it, find the drop-off, and fix it — no vanity metrics.
See it in practice →I put AI to work in post-sale workflows — training, support, content — where it earns its keep, and keep it out of where it doesn’t.
What I’m exploring →I managed a $3M book of business where accounts were churning quietly — the kind you only notice at renewal. I built a Health Check program: regular education and platform tune-ups that reached accounts before they were at risk.
The call I made: run it on a cadence — education and tune-ups up front, instead of rescue missions at renewal time.
The limit: it only worked where someone on the client side engaged. No program fixes an empty chair.
Want this for your team? →What stuck: people adopt what they understand. I’ve been building every rollout like a curriculum ever since.
What stuck: why accounts stay — health metrics read honestly, education before the renewal, showing up early.
What stuck: why rollouts stick — design around the team as it is, lead the people through the change, measure adoption or lose it.
If they don’t use it, you didn’t ship it. I learned this watching renewals die on unused licenses.
Documentation nobody reads is the same as no documentation. If the team can’t explain it back, the rollout isn’t done.
If we can’t agree what good adoption looks like before kickoff, we’ll argue about it after.
If it can’t point to a number it moved, it was a demo, not a deployment. No hype, no pilots to nowhere.
I head implementation at Sandler — onboarding and enabling our franchisees. My spare cycles go to applied AI — the unglamorous side of post-sale.
I’m Ben Breaux, a post-sale solution architect in Denver. I started with a degree in education and spent 10+ years in customer success and implementation, learning why software gets adopted — or doesn’t.
Now I design what happens after the sale: the architecture, the data behind adoption, and AI with a clear job to do.
Hiring for implementation, adoption, or applied AI roles? I’d like to hear what you’re building.