Deal notes that update themselves after every call, and a follow-up that waits for the AE.

A B2B sales team ran MEDDPICC properly, which is rarer than it sounds. Every deal had a document tracking the metrics, the economic buyer, the decision criteria and process, the paper process, the pain, the champion and the competition. The discipline was real. So was the cost of keeping it up.

After every prospect call an account executive was expected to update the document, write up the call, and send a follow-up. Three pieces of admin, each small, each competing with the next call for the same hour.

The team named it plainly: the documentation was time-intensive, the updates were late and uneven in quality, and the admin was slowing deals down. What sits underneath that is familiar to anyone who has run a methodology. A good follow-up takes longer than an AE has between meetings, so it goes out late or generic. The document gets updated when there is a gap in the calendar, from memory, rather than when the call ends. The record lags the deal.

That lag is not a documentation problem. A forecast built on stale fields is a stale forecast. A manager coaching from the document is coaching last week’s deal. And a prospect who has just spent an hour with the AE waits for the follow-up while the AE is in other calls. Deal velocity is the sum of small delays like that.

The other option was to loosen the method. Nobody wanted that. MEDDPICC was working. The problem was that a person had to do the transcription.

We mapped what an AE does between the end of one call and the start of the next. Most of it is reading and transcription: what was said, what changed, what the CRM already knows. Three decisions sit inside it. What did this call tell us about the deal? What should happen next? And what do we say to the prospect?

The first takes judgment, but it is low-stakes and fully reversible: the MEDDPICC document is read by the AE and their manager, and a wrong inference gets corrected at the next review, not by a customer. A coworker can own that, on the condition that the AE can see and correct what it wrote. The second is a recommendation, and a recommendation is exactly as far as a coworker should go on deal strategy: it proposes, the AE decides. The third goes to a prospect and cannot be unsent, so the coworker drafts it and the AE is the one who sends it.

When a call ends, the coworker collects everything the deal has produced: the transcript, meeting notes, the email thread, task updates, and the deal’s properties in the CRM. It reads all of it against the eight MEDDPICC fields and updates the document with what changed: a newly named economic buyer, a procurement step that appeared in an email, a decision criterion the prospect mentioned on the call. Then it writes a short playbook for the AE: what this call moved, what is still unknown, and what to do about it before the next one.

It also summarises the call and drafts the follow-up from the actual conversation: what was discussed, what was promised, what the next step is. The draft lands in the AE’s queue in the CRM they already work in. The AE reads it, edits or approves, and only then does it go out.

The AE walks out of one call and into the next. By the time they are back at their desk, the MEDDPICC document reflects what was just said, there is a note on what to do next, and a follow-up is waiting for a read and a click. The document is current when the pipeline review happens, not because someone remembered to update it but because the call ending is what updates it.

We have not measured this one in deal velocity, and we would rather say so than guess. The time is easier to estimate, and we will show the arithmetic so you can substitute your own numbers. Done properly, the three tasks after a call — update the document, write up the call, write a real follow-up — take somewhere between thirty and forty-five minutes. An AE running ten prospect calls a week was spending five to seven hours on them, or most of a working day, and getting it back is most of a day per AE per week. Across a team of ten that is a rep’s worth of selling time that was going into paperwork. What the team reports alongside that is the shape of the change: follow-ups going out the same day, documentation that no longer depends on who is diligent, and the gap between calls spent preparing for the next one rather than writing up the last.

What we watch is disagreement. When an AE overrides a MEDDPICC update, either the coworker read the sources wrong or the AE knows something that was in none of them, and the two need different fixes: one is a change to how evidence is weighed, the other is a missing source. When AEs edit follow-ups the same way over and over, the draft is wrong, not the AE.

The document update runs on its own because it is reversible and somebody reads it anyway; that is authority it holds because the AEs keep agreeing with it. The follow-up stays behind approval because a prospect reads it, and no run of good drafts changes what a bad one costs. If the overrides on the document ever climbed, it would go back to proposing field changes rather than making them. Authority moves on the record, and it moves both ways.