Coaching a team that had already bet on Claude
Four ninety-minute workshops for a founding team whose product already ran on the model.
- Services
- Team coaching
- Format
- Four ninety-minute workshops over five weeks
- Group
- Six people: five founders and an acting CFO
The tool was already chosen
Wellth Group is a pre-launch wealth-tech company. Its product is built on Claude and the founding team had already bought a team plan. Six people had never worked in it together.
The sponsor set out four things he wanted: to understand what the tool could actually do, to get both the individual and the team setup right, to agree how people would collaborate and where documents would end up, and to find the capability they were not using. Starting points varied widely. One founder rated his own experience as low; two were using Claude every day.
The problems that surfaced in the sessions were about the team, not the model. Work was being created in silos, so useful things existed that nobody knew about. Output drifted towards the generic without a codified house template. And there were no written ground rules for a team that will handle other people's money.
Four Tuesday mornings on their own work
The program was rewritten from a one-to-one coaching format into a team one, with the agenda built around the documents this team actually produces. Participants were asked to bring a real example to each session.
Session one covered the landscape, individual and team setup, and governance. Session two covered the desktop and Office surfaces and skills, including a house meeting-agenda skill built live in the session. Session three introduced Claude Code and agentic workflows. Session four ran as office hours: demonstrations, an honest account of what the team plan does not share well, and what each person would do next. Written answers followed each of the first two sessions.
A team setup rather than six personal ones
The output of the program was an operating model the group agreed to, plus the written material to run it without us.
- Setup
- Standard connectors deployed centrally through organisation settings, experimental ones left to individuals, and organisation-level instructions agreed.
- Skills
- A branded meeting-agenda skill built live, and personal skills moved into the shared library so useful work stops being invisible.
- Where work lives
- Draft in Claude, finish in the Office add-ins, save to SharePoint. SharePoint stays the record.
- Materials
- A four-session playbook published as a web deck, a quick start guide, a plugin deployment guide and fifteen written answers to questions raised in sessions.
A small engagement, honestly
Workshops delivered over five weeks, with email support in between.
One founder used Claude to build a three-year forecast broken down by general ledger and sub-ledger account, pulled from the accounting system, and used it for planning.
The sponsor set up the Outlook add-in to refile and recategorise mail and to write his own rules for the rest.
The team left with one setup instead of six, and agreement on which system holds the finished document.
This was coaching, not a build. Nothing was measured before and after, and no hours-saved figure is claimed.
Thanks again for the session today, as well as the follow-up emails and items. It was most useful.
Have a problem shaped like this one?
Fixed-scope discovery to start.
Strata: Sue Winston — Unsplash