Guide

Our account manager quit and now everything lives in my head. How do I get it out?

You get it out by writing a one-page brief per client the same week: who actually decides, standing exceptions, how they like to be talked to, last promises, open asks, and the landmines. Those are the sentences you already say to yourself while you work the account. Karl Sakas puts a dedicated account manager at 4 to 8 accounts. That book is now sitting in one head.

By The Concrete team · Published

We make Concrete.

What the job actually is

You get it out by writing a one-page brief per client the same week. Who actually decides. Standing exceptions. How they like to be talked to. Last promises. Open asks. Landmines. Pin that brief where the next owner will look. Then turn every still-open line into named work in the channel.

The account manager already left. The remaining person, often the founder, absorbed the book. Wiro puts the leak this way: clients rarely leave because a person left. They leave because the handover showed them how much of the relationship lived in that one person's head, and the first weeks with someone new felt like starting again. The documents usually survive. Contracts, scopes, and invoices are on a drive. What walked out is the context around them.

Karl Sakas writes that a dedicated account manager typically holds 4 to 8 accounts, and that an AM or PM will ideally bill around 20 hours a week. Databox surveyed 48 agencies and found almost 70% keep each account manager under 10 clients. At a 3-to-30 person shop the owner is still that person for most clients. The departing AM's book is now sitting on top of that load.

The expensive leak is the Slack Connect channel. Slack has no native owner on a thread, so a 9pm ask can sit while three people each assume someone else has it. Shared channels sit on paid Slack plans on both sides. The Free plan only allows one-to-one external DMs, and keeps 90 days of message history. Pro is $7.25 per user per month billed annually, or $8.75 billed monthly, as of 10 November 2026. People in that channel can see messages from bots and apps. Keep the shop's brief off the thread the client can read.

Write a reply target into the channel. Mursa publishes 4 business hours for standard client Slack, 1 business hour for urgent, and the next business day after hours. Its July 2026 workspace audit logged about 3,100 client-side messages across 14 client channels over 27 weeks, and recorded zero after-hours escalations. ClearFeed's agency guide, updated 31 October 2026, says an account manager can usually keep 10 client channels straight, someone misses a ping around 40, and a practical SLA is 4 hours for standard clients, 1 hour for high-touch, and 30 minutes for VIPs or launches.

Panopto surveyed 1,001 US employees and found they spend an average of 5 hours every week waiting to get in touch with people who have the unique knowledge they need. Asana's Anatomy of Work Index, which surveyed over 10,000 knowledge workers, found they spend 60% of their time on work about work, including searching for information and chasing the status of work. The same index found the average employee uses 10 different apps every day. The brief has to live with the firm, or the next person spends those hours reconstructing it.

Open asks that sit overnight are a neighboring job, on the daily summary of open client asks. Promises typed in the thread are on the chief of staff page. The owed list before a check-in is on how to prepare for a client check-in. How a 10-person shop carries the book is on handling more clients without hiring an account manager. Silence after a handover is an early churn signal, on how to know which clients are unhappy.

What belongs on the one-page brief

Write the sentences you already say to yourself while you work the account. On r/CustomerSuccess in May 2026, operators said the layer that costs the most time is the stuff that never gets documented: who really makes decisions, who needs extra handling, and any ongoing frustrations. They ask three questions: who really makes decisions here, who needs extra handling and why, and what would you tell me in the first five minutes of a call. A blank notes field never unlocks that.

Karl Sakas, writing for owners who just lost an AM, says brief the new person internally on the client's situation, include them in meetings so the client becomes familiar, then stay in the background and push things to the new person before you respond. The brief is that internal dump. One page per client. If it does not fit, you are writing a handbook.

DocumentInclude or leave outWhy
Who actually decides, and who is day-to-dayIncludeThe champion who hired you may already be gone. The person who pings Slack may not sign the retainer.
Standing exceptionsIncludeWho hates Monday calls. Which CMO wants a one-line summary. Which account has a standing exception on revisions. The replacement arrives with clean process and zero history without this line.
How they like to be talked toIncludeRecap length, emoji, who sees the draft before their director, the color they will never accept. Wiro names these as preferences nobody recorded.
Last two promises the agency madeIncludeThe discount mentioned on a call. The extra video agreed in passing. The report format they were told would change next month. From the client's side, that was the agency's word.
Open asks still sitting in Slack or emailIncludeChannel history hides thread replies unless you open them. A catch-up that reads only top-level messages drops the actual ask.
Landmines, politics, ongoing frustrationsIncludeWhy the last campaign was pulled. Which competitor they are sensitive about. What went wrong with the previous agency. The first five minutes of a call.
Access still in the leaver's nameIncludeAd accounts, pages, and client chats set up on a personal login or phone. Wiro says this is the point that causes the most immediate damage.
Named owner and backup for the channelIncludeA group in the channel recreates the bystander effect. One person owns the inbound queue and the send button. The backup is named in the same pinned note.
A full Slack export of the channelLeave outSearch finds the thread if you remember a phrase. The next owner will not read 18 months of scrollback before the first client ping.
A process encyclopedia or 40-page SOPLeave outOn r/agencynewbies, an owner who spent weekends on SOPs, Notion databases, and Loom videos found nobody used any of it. Finding the doc took longer than asking.
Contracts, scopes, and invoices already on the driveLeave outThose documents usually survive. Point to them. The brief stays one page.
A recap of everything that already shippedLeave outThat is catch-up. The brief is the open work and the unwritten rules. Mix them and the why dies the first time someone checks a box.

Which method wins which job

Fund the row that matches the leak. A one-page brief, a catch-up, and a 12-week transfer plan are neighboring jobs. The account manager already quit, so the overlap plan is often already gone.

JobWins itWhy
Get the tacit stuff out of one head this weekOne-page client briefWrite who decides, exceptions, last promises, open asks, and landmines. One page per client. The sentences you already say to yourself.
A durable document in the internal channelSlack canvasAdd a canvas as a tab on the internal twin of the client channel. Right-click the tab and select Show canvas by default. Canvases sit on paid Slack plans. Keep it off Slack Connect.
Catch up on a thread you already openedSlack summariesConversation summaries ship with Pro at $7.25 per user per month billed annually, as of 10 November 2026. Daily recaps ship with Business+ at $15 per user per month billed annually, or $18 billed monthly. They shorten the thread. A brief is a separate page.
A planned departure with the leaver still in the buildingA 12-week knowledge transfer planShiftFlow splits easy stuff from the hard stuff that lives only in their head: unwritten rules, who to ask, why we do it this way. That plan needs the leaver. Two weeks' notice compresses it to essentials.
Contacts, org chart, and an account plan in one productKaptaKapta keeps contacts, stakeholder maps, account plans, and notes so the next KAM can pick up. Built for a key-account team. Public pricing is quote-only.
Projects, approvals, invoices, and notes on one client recordWiroWiro is built around the client record so a resignation is a staffing question. Waitlist as of 10 November 2026. The aim is the same on any system: attach the notes to the client as the work happens.
The client meets the new owner before the old one is goneA joint intro callSakas: include the new person in meetings, then tell the client they are the primary contact. Wiro wants two calls, one where the leaver leads and one where the successor leads. The leaver is often already gone on this prompt.
Open asks and promises, a person still sendsConcreteEach morning it nudges the owner of every open follow-up. Send / Edit / Skip cards; no auto-send mode. Follow-ups survive reboots. Design-partner preview; see what it is.
Judgment, the live call, and the relationshipA personSoftware stores the brief and the open work. The client still needs a named owner who can say yes.

The caveat that should decide the setup

The failure shops name first is making the client start over. Wiro's line is the one to pin: they leave because the handover showed them how much lived in one head. A 12-week plan after they have already quit is a plan for a person who is gone. Write the brief this week from the sentences in your own head. Pull Slack threads, pins, and email for the lines you forgot. Ask coworkers what they watched the AM do. Accept you will miss some of it.

The second failure is a wiki dump nobody opens. Operators on r/agencynewbies spent weekends on SOPs, Notion, and Loom. Nobody used any of it. The docs were too long. Finding them took longer than asking. One page, in the internal channel, shown by default, is the address. New people read that. Eighteen months of scrollback stays unread.

The third failure is an AI that talks to the client unsupervised, or a bot that posts the shop's internals in Slack Connect. People in that channel can see messages from bots and apps. A digest of open asks in the shared thread shows the client your backlog. Treat an AI extract of the channel as a draft. The outgoing person, or the remaining owner, still confirms who decides, the last promises, and the landmines. A half-joking never send them a long recap can read like a real rule. Put the send gate in writing before you install anything in a shared channel. How to run an agent there is on using an AI agent in a Slack channel shared with a client.

Karl Sakas, on sudden AM turnover, says assign the client to an existing person the client has already met, tell them you are working on a long-term contact, and keep the extra load temporary so the remaining AMs do not burn out. Stay in the background and push things to the new person before you respond. Clients only keep asking for the founder when the founder is the only one allowed to say yes.

Concrete is an AI employee that works in existing Slack channels. Every incoming message gets a receipt mark. Drafts land as Send / Edit / Skip cards. There is no auto-send mode. Every substantive answer is logged with the person's verdict, and the verdicts become written rules overnight, so a correction does not have to be repeated. Follow-ups survive reboots. Each morning it nudges the owner of every open task or ask. After downtime it sweeps channel history, thread replies included. It starts from a ready-made role such as Customer Success or Chief of Staff, then adapts. It is in design-partner preview; the longer thesis is on the vision page. It does not replace the account manager. It does not write the brief for you. The brief still needs a page. Concrete keeps the work that page created. Drafting the client-facing reply is a neighboring job, on the approval-before-send page.

Step by step: get the knowledge out this week

This is the boring version that holds when the owner just absorbed the book. Pin it in the internal channel, before the first call where you have to explain the account again.

  • Step 1: Rank the book by who would feel they are starting over. Start with the clients where a missed exception would cost the account, only one person has ever touched the file, or the client already pings you by name. Karl Sakas puts a dedicated account manager at 4 to 8 accounts. That is a handful of pages this week.
  • Step 2: Write the one-page brief from the sentences you already say. Who actually decides. Standing exceptions. How they like to be talked to. Last two promises. Open asks. Landmines. Access still in the leaver's name. Finish the sentences you already use while you work: every month I have to remember to, never send them, if this is missing I.
  • Step 3: Pull open promises and asks out of Slack the same day. Open Threads. Channel history hides thread replies unless you open them. Name an owner and a date on every still-open line. A promise to send it Friday is the leak if Friday has passed. Spoken promises in a thread are a neighboring job, on the commitments-from-threads page.
  • Step 4: Pin the brief on the internal channel, name an owner and a backup. Add the canvas as a tab on the internal twin, not the Slack Connect channel. Show canvas by default. One person owns the inbound queue and the send button. The backup is named in the same note. A group in the channel recreates the bystander effect.
  • Step 5: Tell the client with a plan, keep send as a tap. Name who is taking over and when. Frame it around continuity. Write the reply target into the channel: 4 business hours standard, 1 business hour urgent, next business day after hours. Draft the intro. Send stays a tap. A bot message in Slack Connect is visible to the client.
  • Step 6: Sweep threads in the morning and keep the brief current. A catch-up that reads only top-level messages drops the actual ask. Watch for slower replies, skipped meetings, and a champion who left the thread. Those are the early signs the relationship is being re-evaluated. Update the brief the same day a rule changes, or it dies the first week.

Questions people ask

What should I write down first after an account manager leaves?

Start with the clients who would feel they are starting over. For each, write who actually decides, standing exceptions, how they like to be talked to, the last two promises, open asks, and the landmines. A dedicated account manager typically holds 4 to 8 accounts. That is a handful of pages.

Is a wiki enough to hold what the account manager knew?

A wiki is a durable address. Teams skip it when the thread is still moving. Pin a one-page brief on the internal Slack canvas, and keep open asks as named follow-ups in the channel. Asana's Anatomy of Work Index found knowledge workers spend 60% of their time on work about work, including searching for information.

Should I tell clients the account manager left before I have a replacement?

Tell them with a plan. Name who is taking over and when. Karl Sakas says assign the client to an existing person they have already met, then stay in the background and push work to that person. Wiro says the worst way for a client to learn is from an automatic email reply after they have gone.

Can I dump Slack threads into an AI and call that the handover?

Use the model as a draft. On r/CustomerSuccess, operators let AI pull raw material, then made the outgoing person confirm five fields: what they care about, recent promises, real stakeholders, next action, and landmines. A half-joking never send them a long recap can read like a real rule. A named owner still confirms the record.

Does an AI teammate replace the account manager's tribal knowledge?

An AI teammate marks messages seen, drafts the reply, and follows up on open work. A person still writes the brief, owns the client, and taps send. Concrete has no auto-send mode. Verdicts on drafts become written rules overnight, so a correction does not have to be repeated. The relationship stays with a person.

What if the departing account manager already left and I cannot ask them?

Write the brief from your own head this week. Pull Slack threads, pins, and email for the lines you forgot. Ask coworkers what they watched the AM do. ShiftFlow's emergency path is the same: piece together knowledge from what is left, assign temporary owners, and document as you go. A 12-week plan needs the leaver in the building.

Sources

If your team already runs its work in Slack, start with one role in one channel. Concrete is an AI teammate that works in your Slack channels and asks a person to approve before anything goes out. It is not a chatbot builder, and it never sends on its own.