AI adoptionClaude, rolled out across Teem’s internal team
Teem had nearly everyone using Claude every week, 12 weeks after kickoff
Teem had already bought the seats for its internal team. Our job was the setup behind the tool, and the support that got every one of those people actually using it.
Book a 30-min call →- Client
- Teem builds and runs hybrid healthcare teams, placing remote team members into optometry, veterinary and dental practices.
- The work
- Claude setup and coaching support for Teem’s internal team, not the healthcare VAs it places in practices. From May 2026.
- ~70
- Weekly users of ~75 internal seats
- 3–5 hrs
- Saved per week, per person
The goal was a little time back for everyone
Not a lot of time back for a few people. The founder set that target the day before kickoff, and it shaped every decision after it: a generalist tool for every role, rather than a handful of agents built for the few jobs that automate cleanly.
“We are not building agents that save one person four hours a day. We are building a generalist tool that saves 20 to 45 minutes a day for every person regardless of role or department.”
The second goal was cultural, and it came from Abby Hogan, who led the coaching and is now VP of Business Operations. A tool nobody admits to using is a tool nobody gets better at.
“We want to eliminate the stigma that you have to use it in secret, or you’re not doing your job as well if you are using it.”
What we built
First we interviewed department leaders and ran a baseline survey to measure how the team already used AI and where their time went. Then we built against what it said.
- 01Workspace-wide instructionsHow Teem talks, what it stands for, and the rule that a person reads every output before it goes out. Plus skills for the repeat jobs, like sales objections and compliance questions.
- 02An internal search projectAnswers questions from the SOP library in SharePoint and links back to the source document, so an answer can be checked rather than trusted.
- 03ConnectorsMicrosoft 365 and Asana for everyone, and the other systems by role, so Claude reaches the tools each team already works in.
- 04A getting-started guide, and a coaching prep toolOne guide written for every employee, and a tool that prepared the coach before each one-on-one call.
Then the coaching. Every person on the internal team got a one-on-one session, run in four cohorts, and it finished ahead of schedule on August 5. After it wrapped, we wrote per-department recommendations for using Claude with the tools that team already works in.
June baseline → after coaching
- Use only the company account for work
- 41%75%
- Using connectors to tools like HubSpot, Asana and Grain
- 8%88%
In June, 8% had ever set up an AI integration at all.
The results
- About 50 people using Claude daily and almost 70 weekly, out of about 75 internal seats
- Typical team member estimates Claude saves them 3 to 5 hours a week
- 90% have handed off or sped up at least one repetitive task
How this was measured
Usage counts are from Claude’s own analytics on July 29, twelve weeks after kickoff. Everything else is from a follow-up survey of the internal team after coaching wrapped, answered by 51 people. Time saved is what people estimate, not a measured figure.
What the team said about it
94% found their one-on-one coaching useful. These came back in the follow-up survey, which people answered without their names attached.
“After the 1:1 coaching, I realized I had so much power in my hands and just didn’t know how to use it to make my role easier and more efficient.”
“I think it is a strong move. The time savings are real.”
“This is such an impactful investment for the company.”
Want numbers like these on your team?
The seats are the easy part. The setup and coaching behind them is what gets people using the tool every week.
Book a call →Then leaders started building their own tools
Adrian Hora Filho, VP of Finance & Strategy, had been spending three to four hours a week assembling his leadership dashboard in Excel. In September he rebuilt it himself, in Claude, without us.
That is the point where an enablement program stops being a program. The capability sits in the team rather than in the vendor.
“I was finally able to build the dashboard the way I wanted it to.”
What’s next
With that baseline in place, Teem is hiring full-time AI staff of its own to keep building on it. Which is the right ending for this kind of engagement.
Bought the seats, and nobody’s using them?
That’s the normal outcome of buying a tool without the setup behind it. It is fixable.