Wins · Published 6 July 2026 · Claude · Rollout
Renalis: a team that improved real projects during the session itself
A Claude rollout that now saves the team over 30 hours a week, with several recurring processes partly automated.
Renalis came to us in the position most teams are in before a rollout: a few people had tried an assistant, most had not, and nobody was sure which of their tasks it was actually good at. The brief was a Claude rollout that would not stop at a tour of the interface.
What we did
We ran the session in English on the team’s own material. Rather than working through prepared examples, each person brought a live piece of work and we built against it. That changes the tone of a day quickly: the question stops being whether the tool is impressive and becomes whether it moved this specific task forward.
What they said
"It opened our eyes to how much we can do with AI. The delivery was clear, the English strong, and the hands-on tasks had us using it straight away. Several people improved a real project during the session itself."
That last sentence is the outcome we design for. A session where several people advance a real project before they leave is a session that survives contact with the following Monday. The team rated the day 4.8 out of 5.
Why it worked
- Real work in the room, not prepared demonstration material
- Delivered in the language the team actually works in
- Enough hands-on time that everyone produced something they kept
- A clear line on which tasks to hand over and which to keep
Where it stands now
The team currently saves over 30 hours a week. That figure is not one dramatic automation; it is a set of recurring jobs that each used to eat a morning. Drafting minutes and decisions from meeting recordings. Turning existing procedures and work instructions into plain, consistent language. Pulling data that lived in several different systems into one working file. Comparing supplier price lists instead of reading them one at a time.
None of those is glamorous, and that is rather the point. Thirty hours a week is what accumulates when a dozen unremarkable recurring tasks each get shorter, in a team that decided which ones to attack rather than waiting for one big idea.
Key takeaways
- Over 30 hours a week saved, spread across many recurring tasks rather than one big automation
- The wins were in minutes, procedures, cross-system data pulls and price comparisons
- Several people advancing real projects in-session is the signal adoption will hold
Related training
AI Foundations for Teams
Your whole team, front desk to board, does real work faster with ChatGPT, Copilot and Claude.
Book this training