Two days of prep, done in thirty minutes
Executive business reviews are where the real conversation with a customer happens. They were costing one to two full days each, so they were being rationed.
- Context
- Enterprise customer success
- Role
- Designed and built
- Type
- AI skills and agents
- Built so far
- Around nine
01 / The problem
The most valuable meeting was the one we could least afford to run
An executive business review isn't a status update. It's the meeting where you sit down with a customer, look honestly at the last quarter, and agree what the next one is for. It's where success plans get made and where renewals get protected long before anyone says the word renewal.
Preparing one properly meant pulling together three months of data, working out what the numbers actually said, deciding what was going well and what was quietly breaking, choosing what deserved time in the room, and drafting the follow-ups that would carry the commitments forward.
That was one to two days of work per customer, which put a hard ceiling of around three reviews a week on the whole team.
When the strategic conversation costs two days, you ration it. The accounts that get skipped are rarely the ones that needed it least.
02 / The insight
The bottleneck was never the slides
Most attempts to speed this up automate the formatting. A template, a data connector, a chart that fills itself in. That saves the cheapest part of the job.
The expensive part is judgement. Reading three months of signal and deciding what it means. What's working, what's breaking, what the customer needs to hear even though they haven't asked. That's the part people assume can't be encoded, and it's exactly the part worth encoding, because it varies between one person and another and between a good week and a bad one.
03 / What I built
A skill that runs the sequence a good CSM runs
You give it the client information. It works through the same steps, in the same order:
- Pull the quarter together. Three months of numbers as one picture, not a folder of exports.
- Read what the numbers say. What moved, what stalled, what's quietly going wrong.
- Sort it honestly. The good, the bad, the ugly and the genuinely positive, kept separate instead of blended into a comfortable average.
- Set the agenda. What deserves time in the room, and in what order.
- Build the deck. Straight into the template I defined up front, so it arrives in a shape the team already trusts.
- Draft the follow-ups. The emails that turn a good conversation into commitments.
Under thirty minutes, from a standing start.
04 / The rest of the set
Around nine, and counting
The review skill was the first. Once it was clear the approach worked, the same question got asked of everything else that ate hours without producing judgement.
- Account segmentation. I define the indicators that matter and the agent segments the book against them. It used to be an annual exercise because it was too slow to be anything else, which meant the tiers always described a business that had already moved on. Now it runs quarterly, giving a focus set that rotates with the year and a tier one held steadily so renewals are protected long before the date.
- Meeting actions. An agent that sits in on a call, or works from it afterwards, and comes out with the action items, the timelines, and who owns each one. The follow-up nobody has time to write properly.
- Inbox control. A skill that keeps a CSM on top of their email rather than the other way round, which in this job is not a small thing.
- Project proposals. Built for the implementation team. It takes our input, follows our instructions and our template, and produces the proposal.
- Cross-channel reporting. Connecting Slack, Teams and email so notifications reach the right places and data can be aggregated from all of them at once instead of chased across three.
None of these replace a customer success manager. They delete the part of the week that was never the job.
05 / Results
A rationed ritual became a routine one
The time saving is the obvious result and the least interesting one. What changed is what the function could do. When every account can have a real quarterly conversation, success planning stops being something reserved for the top ten accounts and becomes how the team works.
06 / Why this one matters
The same method, pointed at a new problem
This is the QHSE habit again. Find the step where the failure actually happens and design it out. The failure here wasn't a bad business review. It was the review that never happened because there wasn't time, and an account nobody has had a real conversation with for two quarters is an account you lose without seeing it coming.