Post-sale teams rarely run out of time because one task is unusually difficult. They run out of time because hundreds of small pieces of coordination accumulate around the customer.
A TAM checks three systems before an executive review. A CSM asks Product for an update that Support already has. An escalation creates a Slack thread, a meeting and two follow-ups because nobody has the full context. A renewal review becomes a weekly ritual for reconstructing what happened.
Individually, each activity looks reasonable. Together, they create what I call the post-sale coordination tax: the capacity consumed simply moving information, ownership and decisions between people and systems.
Why this matters
The tax is easy to miss because it does not appear as one line in a budget. It appears as senior people carrying fewer accounts, more management layers, increasing meeting load, slow escalations, inconsistent customer context and headcount that rises with customer growth.
This is also why many AI programmes disappoint. They optimise visible tasks such as note-taking, email drafting and summary generation while leaving the coordination system untouched. Saving five minutes on an email does not matter much if the person still spends an hour finding the right information, deciding who owns the issue and chasing the next update.
Before choosing another tool, I would map the coordination tax across five places.
1. Routing
Routing is the work of deciding where something should go. Who owns this customer question? Is it Support, Product, Engineering, Services or the TAM? Does it need escalation? Which queue or channel should it enter?
Routing tax shows up when the customer-facing person becomes the default front door. The organisation has specialist teams, but the TAM or CSM still receives the request, translates it and carries it to the correct destination.
A useful measure is the share of inbound work that requires manual triage by the account team before it reaches its true owner.
2. Context rebuilding
Customer context often exists, but not in a form the next person can use. It is spread across CRM notes, support tickets, product requests, meeting transcripts, email and someone's memory.
So every important interaction starts with reconstruction. What was promised? What changed? Who is waiting on whom? Which issue matters to the customer and why?
Context rebuilding is expensive because it usually consumes experienced people. It can also create customer risk when different internal teams operate from different versions of the story.
Measures might include preparation time for account reviews, the number of systems checked, or the time required for a new owner to understand a live customer issue.
3. Handoffs
Every handoff creates a chance for delay, ambiguity or loss of ownership. The problem is not that handoffs exist. Enterprise technology companies need specialist teams. The problem is when each transfer requires a person to restate the request, attach the evidence, explain the business impact and then remain involved because ownership is not clear.
A good handoff has an explicit owner, required context and a visible next step. A bad handoff creates another coordination loop.
Look at how many people remain copied on work after responsibility should have moved elsewhere, and how often the account team has to ask whether something is still progressing.
4. Synchronisation
Meetings are often the mechanism organisations use when information does not move reliably on its own.
That does not make meetings inherently wasteful. Some decisions need discussion. But recurring calls whose main purpose is "get everyone up to date" are a useful signal. They often exist because the underlying systems cannot provide a shared view of customer state.
Measure the recurring internal meeting hours attached to an account or workflow and ask a harder question: if the information were already assembled and trusted, which of these meetings would still need to happen?
5. Reporting
Reporting tax appears when the same customer information is repeatedly reshaped for different audiences. The account plan, executive brief, renewal review, product escalation and leadership update may all use overlapping facts, but each is manually rebuilt.
This is a good place for AI when the source information is reliable. AI is strong at synthesis: gathering known information, reducing it and presenting it for a specific decision. It is much less valuable when it simply creates another document that someone must maintain.
Measure how often the same underlying information is manually copied, summarised or reformatted.
From activity to business value
The point of measuring coordination is not to produce a prettier productivity dashboard. The useful question is what the recovered capacity changes for the business.
That may be fewer hires required as the customer base grows. It may be more accounts per TAM without reducing service quality. It may be lower cost-to-serve, faster escalation resolution, earlier visibility of renewal risk, or more senior time spent on adoption and expansion.
Those outcomes matter more than "hours saved". Recovered hours only become valuable when the organisation knows what it will do with them.
A simple starting map
Pick one recurring post-sale workflow. Do not map the whole customer lifecycle. Choose something people complain about today: product-status requests, escalations, executive reviews, renewal preparation or customer health reporting.
For that workflow, record five things: where the request enters, who touches it, what information they need, where they wait, and what must be reconstructed manually.
Then classify the work into routing, context rebuilding, handoffs, synchronisation and reporting. Estimate volume and time conservatively. The result does not need to be perfect. It needs to show where coordination is consuming experienced capacity.
Only then ask where AI belongs.
AI should attack the coordination tax
The strongest post-sale AI use cases are often less glamorous than a new customer-facing agent. They are the systems that classify incoming work, assemble account context, detect missing information, route requests, prepare decision-ready briefs and surface the next owner without requiring a TAM to carry the process manually.
The goal is not to make a busy person process more coordination. It is to remove coordination from the person in the first place.
That is the distinction I use when looking at post-sale AI: does this make an existing task faster, or does it change the operating model enough that the task, handoff or meeting is no longer needed?
The Post-Sale Coordination Tax is an Opscale working model for analysing post-sale workflow friction. It will evolve as the model is tested against real engagements.