Picture Friday at nine in a finance team of three. Every overdue invoice already has its next step. The routine reminders are drafted in the firm’s own wording. The firmer notes wait for the account leads whose names go on them. The invoices that should not be chased are held, each with its reason. It looks like this every Friday, whoever is at the desk.
That team has an AI capability. The same three people, on the same AI subscription, now do something that used to depend on one person’s memory. Put a few capabilities like it side by side and you 10X what the team can do.
A capability is something your team can do.
Most firms describe their AI by what they bought: licences, an assistant, a chat window. A capability describes what the team can do with it. “Everyone has an AI licence” is a purchase. “Every overdue invoice has a reviewed next step by Friday at nine” is a capability.
You know a capability by three signs. It has a name your team uses. It produces the same quality whoever starts it. And one role owns it and approves every change. A clever prompt has none of these. A prompt, a capability template and a capability shows the difference on one task.
The five parts.
Every capability, in any department, has the same five parts. If one is missing, the work falls back on whoever happens to know.
- Outcome. The result the business gets, written so anyone can tell whether it happened.
- Method. The steps and decision rules your best person follows, including the cases where they stop.
- Context. What only your firm knows: your records, your wording, this week’s notes and promises.
- Tools. Where the work runs, what the AI can read and what it cannot touch.
- Review. Who checks the output, who decides and who owns the capability itself.
One capability, laid out.
Here is overdue-invoice follow-up preparation at an invented firm, with one week’s records.
Illustrative example with invented data. An invented 60-person professional-services firm. Aging as of 25 September 2026.
Capability: overdue-invoice follow-up preparation
- 1. Outcome
- By Friday at nine, every overdue invoice is either ready to follow up, with a draft in the firm’s tone for its age and the right sender named, or held with the reason and the person who can release it. This week: six overdue invoices, two drafts, four held.
- 2. Method
- Check the aging report is current. Apply the holds before drafting: nothing disputed is chased, and nothing a payment may already have settled. Skip any invoice reminded in the last seven days or still inside a promised date. Set the tone by age: 1 to 30 days, a short reminder; 31 to 60, a request for a payment date; over 60 or after a missed promise, a direct note from the account lead. Draft from the approved message for that bracket. Offer no discount, credit or payment plan. Send nothing.
- 3. Context
- The firm’s tone guide and its three approved messages. The account leads’ notes: Client C promised payment of Invoice 1031 ($6,400) by 11 September and missed it; Client E disputed Invoice 1035 ($3,800) on 2 September. The exception list: a $5,600 wire on 23 September with no reference fits Invoice 1044 or Invoice 1045; Invoice 1042 shows $200 open after a short payment nobody has explained. Past correspondence: Client G paid Invoice 1047 on 24 September, and Invoice 1036 ($1,850, 37 days) is still open.
- 4. Tools
- The firm’s approved AI workspace, on the platform it already pays for. The billing coordinator supplies the aging report export, the notes and the exception list. Drafts land in a shared follow-up folder. The capability has no connection to the mailbox or the accounting system, so it cannot send a message or post a payment.
- 5. Review
- The billing coordinator reviews the plan and sends the draft for Invoice 1036. The account lead for Client C edits and sends the note on Invoice 1031, with the finance lead copied. The account lead releases Invoice 1035 once the dispute is resolved. The controller releases Invoices 1042, 1044 and 1045 once the balance and the wire are explained. The controller owns the capability and approves every rule change.
Nothing has been sent and nothing has been posted. Any credit or payment plan is the controller’s decision.
The method stopped four messages that read well and should not go out this week. The context turned a polite reminder to Client C into a note that cites the missed promise. The week this belongs to is in What a fully powered finance team knows before month end.
What stays with people.
A capability prepares; people decide. Sending a message is a separate action, taken by the person whose name is on it. So is posting a payment, in the accounting system. Releasing a hold, settling a dispute and agreeing a credit stay with a named role. AI prepares, people decide sets out that line for every department.
A capability is proved on the hard cases before anyone relies on it: a missed promise, or two invoices that could match one wire. What we test before we call an AI workflow ready shows that record, and Who owns an AI capability after the pilot? covers the owner’s job once it is in weekly use.
Write down your own.
Pick one piece of recurring work and answer five questions:
- What is true when this work is done well, and by when?
- What does your best person check, in what order, and when do they stop?
- Which records, notes and approved wording do they rely on?
- Where will the work run, and what must the AI never be able to do?
- Who reviews each output, who decides, and who owns the rules?
Five answers are the first draft of a capability. From there, map the work that crosses teams, land the capability on the roles that do it, prove it on real work, then roll it out. You can also start from ours: the Capabilities Directory holds capability templates, each a reusable starting version you adapt to your rules.
A capability runs on the platform you already have: ChatGPT, Claude, Copilot or Gemini. You set the pace, and your organization keeps control of how the work gets done.
Bring one recurring piece of work and the name of the person who does it best.