The Monday morning account brief: what should be in one
A system nobody opens is worth nothing. The brief is the answer to that, and there are five things it should contain and several it should not. A working template.
An account brief is a short recurring summary of what changed on a client account, what is emerging, and what is worth acting on, with every line linked back to its source. It exists because a knowledge system that must be visited will not be, and a brief that arrives is read.
Here is the failure that kills otherwise good internal systems.
The system is built. It is accurate, it is well designed, and it answers questions nobody could answer before. Usage is high for six weeks. Then it settles at a level that means the people who most needed it have stopped opening it, and eighteen months later it is on a list of things to rationalise.
Nothing went wrong with the system. The problem is that it requires someone to remember it exists at the moment they have a question, and to believe it will be faster than asking a colleague. Both of those are asking a lot of a partner with four things overdue.
A system you have to go to loses to a colleague you can ask. A brief that arrives does not have to compete.
What the brief is for
The brief inverts the direction. Instead of the account team going to the record, the record comes to them, on a fixed cadence, whether or not anything has changed.
That last clause matters. A brief that only arrives when something notable happens teaches people to ignore the quiet weeks, and the quiet weeks are when whitespace is best worked. A fixed arrival, Monday morning, is a habit. An occasional alert is an interruption.
The five things it should contain
In this order, because the order is the argument.
1. What moved
Changes to the account since the last brief. New material that arrived, engagements that started or closed, people who appeared for the first time on either side.
This is the shortest section and the one that makes the brief trusted, because it is verifiable. A reader who was involved in what moved can confirm the brief describes it correctly, and that is how a recurring document earns the right to be believed about the parts the reader was not involved in.
2. Who is new
Client-side individuals who have appeared in correspondence for the first time, and colleagues newly involved.
A new name on the client side is the most actionable signal a firm gets and the most commonly missed. Somebody has joined, moved role, or been brought into a decision, and the window in which a firm can establish a relationship on the front foot is measured in weeks.
3. What is emerging
Subjects that have started appearing in the account's material and were not there before. A regulatory deadline, a programme being scoped, a problem raised repeatedly.
This is the earliest possible signal of demand, and it arrives long before anything reaches a procurement process. It is also the section most at risk of noise, which is why it has to be evidenced: an emerging subject with three threads behind it is a signal, and one with a single passing mention is not.
4. What is worth chasing
The gaps. Capabilities this client demonstrably needs, on the evidence of their own material, that the firm has never delivered for them.
Each one needs both halves evidenced: what shows they need it, and what shows the firm can do it. A gap where the second half is missing belongs on a different list, which is the capability investment list, and it is worth keeping separately rather than discarding.
5. What is at risk
Single-threaded relationships, stakeholders who have gone quiet, engagements approaching an end with nothing behind them.
Firms are systematically better at noticing opportunity than at noticing erosion, largely because erosion has no event attached to it. A relationship does not end, it stops appearing.
What it should not contain
Four things, all of which are common and all of which reduce the chance it gets read.
Activity metrics. Emails sent, meetings held, documents added. This measures the account team, which turns the brief into a monitoring instrument and changes what people send in.
Scores without evidence. Health scores, engagement scores, relationship temperature. A derived number with no inspectable derivation is not information, and it becomes something to argue with rather than act on.
Everything that happened. A complete log is a way of avoiding the editorial decision. If the brief is not shorter than the material it covers, it has not done its job.
Generic recommendations. "Consider scheduling a check-in with the client." Advice that could be given without reading the account teaches the reader to skim, and once they skim they never stop.
A working shape
Length target: readable in three minutes. Roughly this:
| Section | Items | Each item is | |---|---|---| | What moved | 3 to 5 | One line, linked to the material | | Who is new | 0 to 3 | Name, role, where they appeared, first document | | What is emerging | 1 to 3 | The subject, the evidence, how many times | | Worth chasing | 1 to 3 | The gap, what shows they need it, what shows we can do it | | At risk | 0 to 2 | The relationship or engagement, and what changed |
Empty sections should be shown as empty rather than padded. A brief that reports nothing new this week is more credible than one that always finds five things, and it costs the reader ten seconds to confirm.
Cadence and audience
Weekly, on a fixed day. Monthly is too slow for the emerging section to be worth anything, and daily makes it an alert stream that gets filtered.
To the account team, not to management. The moment a brief is read upwards it becomes a performance document, and the account team starts managing what it says. Reporting can be built from the same record separately.
One per account, not one per person. A shared artefact gives the account team a common view, which is most of what an account planning session was for and is now happening every week instead of twice a year.
Why this closes the loop
Everything else in this research shelf describes a record: who knows whom, what the firm has delivered, where the gaps are. The brief is the reason any of it produces an outcome.
An atlas that a partner opens before a meeting is useful. An atlas that tells them on Monday that a new programme director has appeared at their largest client, that resilience has come up three times in a month, and that the firm has never sold this client the capability its own board papers are asking for, is doing something the partner could not have done at all.
The record makes the answers possible. The brief is what makes them arrive before they are needed.
Sources
This article stands behind sheet 04 on the homepage, What you get.
Whitespace analysis for firms
Most whitespace advice is written for software companies selling seats. Firms sell expertise, which changes what a gap is, how you prove it, and why the twice-yearly workshop cannot find them.
D4Mapping an account, worked
What actually happens between forwarding a year of correspondence and having an account you can navigate. Walked through on the demo account, step by step, including what it cannot do.
B4Why the client bought elsewhere
Nobody decided not to pitch. The gap between what the client needed and what your firm had sold them was simply never visible to one person at one time.
See the argument running.
The homepage carries a working atlas of a demo account, with every fact tied back to the document it came from. Or book a call and we will walk through an account you know.