Capability template for customer success and account management
Client-status update preparation
Every client gets an accurate status update on schedule, drafted from the notes and the task list, with confirmed dates kept apart from estimates and the client’s open decisions in plain view.
The outcome
A fully powered client team sends every client a clear update on the day it is due, and every line in it is true. The client sees what moved, which dates are committed, which are still estimates and which decisions only the client can make. Each lead can run 10X the client relationships with the same care.
This capability drafts that update from the matter or project notes, the task list and the last update sent. The person who owns the client relationship reviews, edits and sends it. The draft never goes out on its own and never turns an estimate into a promise.
Who starts the work, and when
A project manager, responsible attorney, account director or engagement lead starts it on the agreed update day, and again between updates when a date moves or a new decision lands on the client’s side.
What they supply
- The notes since the last update. Meeting notes, call notes and internal comments.
- The task list or plan. Each date with its status: confirmed, estimated or at risk.
- The last update sent. What the client was told to expect.
- The update standard. Length, greeting, sign-off, section order and what never goes in.
What comes out
A draft message covering progress, confirmed dates, labelled estimates, client decisions with a needed-by date and the next step, plus a note for the reviewer. The example is an invented 30-person civil engineering firm designing site drainage for a client’s warehouse expansion.
Good means the client knows what to do after one read, and the project manager sees every judgment the draft left for them.
An invented example
Illustrative example with invented data. The sources on update day.
| Source | What it says |
|---|---|
| Last update, 2 November | Drainage layout to Client C on 6 November. Planning submission targeted for 20 November. |
| Task list, 9 November | Layout sent 6 November. Planning submission 20 November: confirmed with Client C’s planning consultant. Final drawings 11 December: estimate. |
| Project notes, 9 November | Both detention-tank locations work. Client C must choose by 13 November to hold the 11 December estimate. Internal: drafting team shared with another project in December. |
Illustrative example with invented data. The draft update.
Subject: Project 7731 status, week of 9 November
Since our update on 2 November, we sent the drainage
layout on 6 November, as planned.
Confirmed: the planning submission goes in on
20 November. Your planning consultant has agreed it.
Estimate: final construction drawings by 11 December.
This date depends on the decision below.
Your decision, needed by 13 November: which of the two
detention-tank locations to use. Both work. A choice by
13 November keeps the 11 December estimate.
Next step: we prepare the planning submission and
confirm the drawings date once you choose.
[Project manager]
Illustrative example with invented data. The note for the reviewer.
Reviewer note: Project 7731 update
- Changed: Layout delivered on the promised date. Planning submission moved from target to confirmed.
- Dates: 20 November: confirmed. 11 December: estimate. 13 November: from project notes; confirm before sending.
- Left out on purpose: The shared drafting team, an internal note. It bears on the 11 December estimate; decide whether the client should hear it.
Nothing has been sent. The project manager reviews, edits and sends.
Where it fits
- Law firms: matter status drafted for the responsible attorney.
- Professional services: engagement updates that keep client inputs visible.
- Engineering firms: design dates that depend on client choices.
- Customer success and account management: the update is the relationship between meetings.
- Project and delivery: the plan and the client’s view of it agree.
- Growth & scaling: more clients per lead without updates slipping.
What has to change for your company
- What counts as confirmed. For example, only a date the client agreed in writing.
- Cadence and triggers. The update day for each client, and what calls for one in between.
- What never goes in. Internal staffing and fee discussions. In a law firm, advice and legal deadlines stay with the responsible attorney.
- Review and sending. Who reviews each client’s update and who sends it.
We start from what the client should know after reading, map the work from notes to sent message, and land each step on its owner. This capability template is written for ChatGPT, Claude, Copilot and Gemini, and your firm keeps control of how the work gets done.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 9 November 2026. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your firm means drafting updates for recent weeks and comparing them with what was sent, including a week where a date slipped and one where the notes and the task list disagree. Pilot acceptance-test preparation builds that test set, and What we test before we call an AI workflow ready shows the record we keep.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Bring a real piece of this work to a call. We’ll walk through what it takes to fit this capability to your rules, prove it on your work and put it in the hands of the roles that own it.