What happens after your meeting

Your notetaker sends the call summary to the sales enablement ingest address. Everything else is reviewed against the standard taught in this course, and within the hour you receive coaching notes on the call: a one-line summary, what worked, what to sharpen, and the transcript moments that show it.

Your one hard operational rule: title tagging

The meeting title naming convention:

• For Discovery Calls: Discovery Call_<Company Name> (e.g. Discovery Call_Acme Corp)
• Presentation to new prospects: New Biz Presentation_Company Name (e.g. New Biz Presentation_Acme Corp)

Two fairness rules are built into the review:

• The deepest attention goes to MEDDPICC Evidence (D6), the buying picture. It is where deals are honestly won or lost, so if you improve one thing, improve the picture you walk out with.
• If no customer objection occurs, objection handling is simply not assessed for that call, and the same applies to any behavior that does not fit the meeting type. You are never marked down for a situation that never arose.

The three stages of skill

Every behavior in this course is described across three stages:

• Developing (present in part or inconsistent)
• Competent (the expected standard, and a pass)
• Elite (the stretch; what the behavior looks like at its best).

These are stages of skill, not verdicts on a person. The target is Competent, and wherever a behavior is Developing, the next concrete move up is always named.

Two situations never count against you: when a behavior does not apply to the meeting type at all, and when it applies but the occasion never arose, such as objection handling on a call where the customer raised no objection. The only miss is a behavior whose occasion arose and that was absent entirely, which is distinct from Developing, meaning you attempted it.

Flags

Your coaching notes flag two things when they occur: a deal risk (an anti-pattern was detected, or the call ended with no real commitment; Modules 8 and 9 cover both) and standout calls, which get surfaced as reinforcement moments for the team. A flag always comes with the transcript moment behind it, so you can see exactly what triggered it.

Gating behaviors: why a decent call can still be a miss

Three behaviors are gating:

• Quantifying the Cost of Inaction
• The Reveal (discovery)
• Landing a Buyer Signal at the close (both call types).

If a gating behavior is absent, the review surfaces it explicitly regardless of how everything else went, because the meeting missed its core job. A call can show many Competent behaviors and still be a miss if it never quantified the pain or never produced a next step. This is the honest way of saying some behaviors count more.

What the reviewer will never do

• Judge the customer. Whether the buyer was talkative, senior, or receptive is outside your control and is never part of the review.
• Judge without evidence. Every observation cites the transcript moment that justifies it. Feedback you cannot trace to your own words does not exist in this system.
• Assess talk-time or sentiment. These appear as context only, shown beside buyer engagement so neither is read in isolation.
• Infer things outside the transcript. A signed PoC that is merely mentioned is flagged for confirmation, nothing more.
• Mark you down on interpretation. Judgment calls (was your point of view “specific” enough?) are surfaced as notes for a human, never held against you.

The concept: why signals beat sentiment

Everything in the standard hangs on one idea: a strong meeting produces a Buyer Signal, not a good feeling. A Buyer Signal is something the customer did, visibly and by their own choice, that cost them something real: their time, their budget, or their standing with colleagues. It either happened or it did not, and someone else could confirm it.

The reason this matters is not philosophical. Buyers are polite. Enthusiasm costs a prospect nothing: it ends the meeting pleasantly, keeps their options open, and commits them to nothing.

Action costs something real. When a contact introduces you to their CIO, they are risking their own reputation; if the deal goes nowhere, that reflects on them. When they share an internal dashboard, they are trusting you with something not meant for outsiders. When they block time on an executive’s calendar, they are spending their company’s attention on you. People only pay these costs for things they actually intend to pursue. That is why one small action predicts deal progress better than an hour of warmth.

This is also why pipelines built on sentiment collapse late. “They loved the demo” survives every forecast review until the quarter it silently dies, because nothing real was ever holding it up.

The verification test

Before you tell yourself or anyone else that a deal moved forward, ask three questions about the meeting: What exactly did the customer do? When did they do it? What proof exists?

A real signal leaves a trace that someone who was not on the call can check on their own: a meeting invite now sits on the calendar, a document arrived in your inbox, a new stakeholder actually joined the session. If the only evidence is your impression that the call went well, you have a feeling, not a signal.

Compare these two claims about the same account. “Santos is really keen on our solution” has no trace behind it; it is your read of his tone, and nobody can check it. “Santos sent us their volume data on Tuesday” has a trace; the email exists, anyone on the team can open it. The first is sentiment. The second is a signal.

Notice the pattern in the strong column: every entry is customer-owned. You CCing the VP is your action; the VP joining a session is theirs. Signals are things the buyer does.

Designing meetings to produce signals

Signals rarely happen by accident; they are engineered.

Before every meeting, name the one signal this meeting should produce (that goes in your pre-meeting plan, Module 10).

During the meeting, listen for signal openings: a mention of another stakeholder is an introduction waiting to be asked for; a mention of internal data is an artifact waiting to be requested; enthusiasm is a dated commitment waiting to be proposed.

The skill is converting the opening on the spot:

Four ways sellers fool themselves about a deal

These four habits show up in your own head, in your CRM notes, and in what you tell your manager on a Monday. Each one makes a deal look healthier than it is. Each has a name, so the review can point at it, and a question that exposes it.

The concept: the Mantra and why replaying their words works

The Mantra is the short, customer-specific narrative you carry into every meeting on an account: what is forcing them to act (their Compelling Event), what the problem costs them (their Cost of Inaction), and what they said the solution must do (their Must-Have Capabilities), all in their own words. The strong open has two parts: a brief frame for the meeting, then a replay of the Mantra that invites correction.

Three mechanisms make this work on buyers:

• Feeling heard beats being agreed with. A buyer who hears their own situation, in their own phrasing, concludes you listened. That is rarer than it should be, and it buys you the right to ask harder questions later.
• The correction is free intelligence. “Actually, it’s gotten worse since we spoke” or “the CFO is now involved” is often the most valuable information of the whole meeting, and it only surfaces if you invite correction rather than agreement.
• New attendees align in under a minute. Anyone joining for the first time hears the whole deal context compressed, from you, framed your way.

Building your Mantra: the Value Pitch behind it

Where does the Mantra come from? It is your company’s general story, filled in with one customer’s specifics. Any version of that story, general or specific, has to answer four questions the buyer is silently asking: What problem does this remove for me, and what is that problem costing me? What do I get if it works? Why you and not the others? And why should I believe you?

Before any first meeting, run whatever you plan to say through three quick checks (call it the Triple A test):

• Articulate: Could the buyer repeat your message to a colleague an hour after the call, in one sentence? If your message needs a paragraph, they will not carry it anywhere, and a message that does not travel inside the account does not sell.
• Available: Does this buyer recognize the problem as their problem, today? You can be completely right about a problem they do not feel, and the message will bounce off. “Reconciliation eats your month-end” only lands on someone whose month-end actually hurts.
• Attainable: Does the buyer believe you can actually deliver what you are claiming? One claim that outruns your proof makes them discount everything else you said. Claim only what you can back with a named client, a number, or a demo.

A message failing any one of the three does not land, no matter how well delivered.

Worked example: first call from an inbound form

The prospect submitted a web form about finding a second fulfillment partner for deliveries to their retail clients. Same information, two opens:

The form is referenced but nothing is replayed; the customer’s situation stays inside the salesperson’s head, and the meeting slides into a company intro.

The correction just changed the deal: backup evaluation became a potential full switch, with a fresh compelling event attached. That is what inviting correction buys.

Language bank

• “In our 30 minutes I’d like to do three things: replay what we’ve heard and confirm it, walk through how we’d approach [issue] based on similar companies, and leave 10 minutes to agree on next steps. Does that work?”
• “What we’ve heard is that [compelling event] is forcing you to act this quarter; the current state costs roughly [quantified cost]; and what matters most is [must-have capabilities]. Did I get that right, and is anything different this week?”
• For a brand-new prospect with no prior conversation: replay whatever you do have (their form, their inquiry, their industry pattern) as a hypothesis to correct:“Companies like yours usually come to us when [pattern]. Before I assume that’s you, what actually prompted the call?”

The concept: diagnosis before prescription

Discovery is business diagnosis aimed at producing two things: quantified pain and a verifiable next commitment. It is not a warm-up for the demo, and it is where experienced sellers lose the most ground, for a specific reason: experience makes you fast at pattern-matching. You hear two sentences of the problem and you already know the answer, so you jump to it. The pattern-match is usually right about the product fit and usually wrong about the deal, because the deal is not built on whether you understood the problem. It is built on whether the customer articulated it, sized it, and owned it out loud. A pain the customer never quantified is a pain they will not pay to remove.

Two of the behaviors in this module are gating: Quantifying the Cost of Inaction, and the Reveal. A call can show many Competent behaviors and still be a miss if it never quantified the pain.

Open, diagnostic questioning

Open questions (“how”, “what”, “walk me through”) make the customer describe reality; closed and leading questions make them confirm your guess. The difference matters because a customer explaining their own process discovers things while talking, commits to what they say, and gives you their vocabulary to reuse. Useful stems:

• “Walk me through how [process] works today, step by step.”
• “What happens when [failure mode] occurs? Who gets the call?”
• “What have you already tried, and why didn’t it hold?”
• “What’s forcing the timing? Why now rather than next quarter?”

Following up: three levels of why, and silence

First answers are canned. Every buyer has a rehearsed one-liner for “what’s the problem” that they have given every vendor. The real answer sits two or three layers down, and two tools get you there:

The three-levels-of-why. Follow the first answer with why (or “say more”, “what’s behind that”), then follow that answer again.

• Layer one is the symptom (“reconciliation is slow”). Layer two is the consequence (“finance closes late”). Layer three is the stake (“if close slips past the 5th, we breach a covenant”).

Deals are built at layer three.

Deliberate silence. After a hard question, count three seconds before speaking. The pause feels long to you and thoughtful to them, and what a buyer says to fill a silence is almost always less rehearsed than their first answer. Filling your own silences is the single most common follow-up failure.

Quantifying the Cost of Inaction (gating)

Climb toward the number one rung at a time.

1. Time“how many hours does that take?”
2. Money“what does that cost in a year?”
3. Risk“what’s at risk if it stays this way?”
4. Owner“who feels that most?”

Each rung is a harder question than the last, and each answer makes the next one natural to ask. You do not need all four on every call, but before you start talking about your product you need two things: a number the customer stated or agreed to, and a named person who owns the problem.

Resist the pivot to product even when you can already see the answer; especially then, because your certainty is exactly what tempts you to skip the customer saying it themselves.

Worked example: from vague pain to a number

Five questions, no product mentioned, and the deal now has a customer-stated $400K churn exposure, a monthly frequency, and a named executive owner. That is a gated pivot earned.

The Reveal: surfacing the capability gap (gating)

The Reveal is where the customer discovers, out loud, that they cannot currently do the thing that would remove the pain.

It must be their discovery. If you assert the gap (“you don’t really have a backup plan for that, do you?”), the customer’s ego defends the status quo; if they surface it answering an honest question about how things work today, the gap is theirs and they own fixing it.

The mechanics: take a Must-Have Capability, and ask how they currently execute the situation that requires it.

Bringing a point of view

A point of view is how you earn the right to ask hard questions: you offer a pattern from similar companies and test it. “Teams at your stage usually find reconciliation cost compounds as volume grows. Does that match what you’re seeing?” Two failure modes: no hypothesis at all (“what are your biggest challenges?” reads as a vendor who did no homework), and generic commentary every vendor gives. The test of a good point of view is that the customer engages with it rather than politely agreeing.

The concept: the buying picture, not the framework

MEDDPICC is the eight things you must know to forecast a deal honestly:

• Metrics
• Economic Buyer
• Decision Criteria
• Decision Process
• Identify Pain
• Champion
• Competition
• Paper Process

It is where the review focuses hardest on both call types, and the bar is specific: it does not credit you for knowing the framework or using its vocabulary. It credits evidence, meaning the element actually surfaced or progressed in this call, in the customer’s words.

This is where experienced sellers most often coast, because instinct fills the gaps that questions should. You have seen a hundred deals like this one, so you assume the CFO signs, the process runs six weeks, and your engaged contact will carry it internally. Each assumption is usually right, and one wrong assumption per deal is what kills forecasts.

The discipline is separating what you know (the customer said it or did it) from what you infer.

The eight elements, what counts, and how to ask without jargon

Never use MEDDPICC vocabulary with a customer; it triggers the Vocabulary Theater flag when the evidence is thin, and it sounds like process, not conversation. Ask in plain language:

Sequencing: pain first, structure second

Do not run the eight elements as a checklist; interrogation kills discovery.

The natural order: pain and metrics first (Module 3 gets you there), because a customer who has just sized their own problem will happily tell you how a fix would get bought. Then process and people (“who signs, what are the steps”). Save for last the incumbent (what would the current provider have to break for them to move?) and the paperwork (legal review, security review, procurement, and how long each takes on their side). On a first call, walking out with pain quantified, the EB named, and the decision process sketched is a strong D6.

The rest can progress across calls; the review credits what surfaced or progressed, not completeness.

Worked example: the NDA moment

A prospect agrees to sign your NDA so they can review your technical documentation. Two ways to handle the same moment:

The NDA gets signed and the deal enters the pipeline as progressing. Nobody knows who approves the vendor relationship, what the internal steps are, or whether the contact can carry it.

Same NDA, but the deal now has two named stakeholders, a sketched process, and a pending introduction: three MEDDPICC elements progressed in ninety seconds, at the exact moment the prospect was most engaged.

The concept: a champion is shown by action, not warmth

A champion is someone with influence who is actively selling for you when you are not in the room. That last clause is the whole definition: most of the deal’s life happens in meetings you are not invited to, and a champion is your presence in them. Enthusiasm, responsiveness, and friendliness are personality, not proof; plenty of warm contacts have no influence, and plenty of influential ones are brisk.

Distinguish a coach from a champion. A coach likes you and shares helpful information, but it costs them nothing to do it. A champion pays a real price: they attach their own name to yours in front of their colleagues, and if you fail, some of that failure lands on them. The evidence rule is behavior over words. A stated intent is weak evidence; an action is strong.

Actions that validate a champion

• They introduce you to another stakeholder, especially the economic buyer.
• They share an internal artifact: a deck, a dashboard, a process document.
• They warn you about a blocker, a competing initiative, or a competitor’s move.
• They take an internal step on their own initiative, on a date.

The three tests you can run in a meeting

• The introduction test. “Who else needs to be part of this, and could you bring them into our next conversation?” A champion commits with a name and a date. A coach says “I’ll see.”
• The information test. Ask for something internal but reasonable: the criteria doc, current volumes, the incumbent’s pain points. Sharing something internal costs them a little trust, and paying that cost is exactly what makes it evidence.
• The stake test. “If this goes ahead, what does it do for you and your team?” A champion has a personal answer: they win something. Someone with no stake in the outcome will not fight for it.

Building a champion, not just finding one

Champions are usually made, not found. The making has two parts:

First, give them the win: connect the project explicitly to their outcome, so advocating for you advances them.

Second, equip them: a champion sells your story internally in your absence, so the story must survive without you.

That is what the Mantra is for; a contact who can repeat “this costs us roughly $400K a year in churn exposure, and this vendor removes the missed deliveries that drive it” to their COO is armed. A contact who can only say “they seemed good” is not.

Before any meeting where your contact will carry the message onward, arm them. Ask what their COO is likely to want to know, then make their job easy: “What questions do you expect from her side? Happy to put the two numbers that matter on one page, so you are not reconstructing it from memory.” A champion who walks in with a crisp one-pager wins the internal conversation; a champion left to improvise says “they seemed good.”

Worked example: converting a hedge

The conversion does two things at once:

• The vague offer becomes a dated commitment (an action, hence champion evidence when kept)
• The introduction test is run in the same breath.

The concept: objections are information surfacing under pressure

A buyer who voices an objection is usually telling you what they need to hear to advance. The buyers to worry about are the ones who raise nothing and go quiet. Two facts shape the whole architecture:

• The surface objection is rarely the real one. “Too expensive” usually means “I can’t justify this internally yet.” “Bad timing” usually means “nothing is forcing me to act.” Answering the surface objection with a surface answer (a discount, a delay) treats the symptom and leaves the disease.
• An objection answered but not converted is a stall. The arc must end in a forward step, or you have merely returned to neutral.

Hence the arc every objection runs: acknowledge, diagnose deeper, reframe to value, test, advance. Three behaviors carry the rating.

1. Diagnosing the real objection

The move is acknowledge-then-question. First, say back what you heard without agreeing with it: “it sounds like the price is landing high.” This lowers the temperature, because a buyer who feels heard stops pushing.

Then ask what is sometimes called a calibrated question: an open question that gets the buyer to explain their objection rather than defend it, usually starting with how or what. “What number were you expecting, and how did you get there?” cannot be answered with yes or no; answering it forces the buyer to show you their reasoning, and inside that reasoning is the real objection.

Never respond to an objection you have not diagnosed; your first sentence after an objection should almost always end in a question mark.

2. Reframing to value

A reframe changes what the objection is measured against. Price measured against zero is always too high; price measured against the customer’s own quantified Cost of Inaction is a comparison you can win, which is why Module 3’s quantification is the setup for every reframe you will ever run.

Offering options rather than a single concession keeps you out of a haggle: the conversation becomes “which structure fits” instead of “how much will you drop.”

3. Converting the objection into an advance

The taxonomy, with reframe language

What usually sits under each surface category, and a line you can adapt for the reframe:

Concessions: never give without a get

If a concession becomes unavoidable, pair it with a commitment of equal weight: “we can move on price if you commit to a three-year term and become a public reference.”

A concession given free teaches the buyer that pushing produces discounts; a concession traded holds the price floor and produces a Buyer Signal at the same time.

Useful gets: longer term, reference or case study rights, an introduction to the economic buyer, a signed evaluation plan, expanded scope.

The concept: validation, not exploration

A presentation or demo proves that the Must-Have Capabilities the customer named are deliverable, in the customer’s context. Read that definition against its opposite: a feature tour proves that your product has features, which the customer already assumed. The difference in the room is who the demo is about. A tour is about you; a validation is about them, and every screen you show either proves something they said they need or it is filler.

This is also why a demo is earned by discovery rather than a substitute for it: you cannot validate capabilities nobody has named. If you find yourself demoing without a list of the customer’s stated must-haves, you are in Module 9’s Demo-as-Discovery territory.

Planning: the capability map

Before any presentation, build a three-column map: the capability the customer named (in their words), the feature or flow that proves it, and the proof point that lands it (a comparable client, a number, a live action). The demo path follows the map in the customer’s priority order, highest first, because meetings get cut short from the end. Everything in the product that is not on the map is out of the demo.

Pitching at the right altitude

Match language to the stakeholders present. A cheat sheet for the rooms you actually sell into:

Elite altitude control connects layers in one breath: “the automatic alert your engineer needs is exactly what gives your COO same-day visibility of exceptions.” When the room is mixed, default to the most senior altitude and dip down on request, not the reverse.

Tying each feature to a named capability

Introduce every feature by the capability it serves, before showing it: “This addresses what you called real-time reconciliation. Here’s how.” Then, after showing it, check it landed: “does that match what you’d need to trust it?” The introduce-show-check rhythm keeps the demo two-way. Showing features for their own sake (“here’s our reporting module, lots of options”) is Developing.

Handling “can it do X?” honestly

Capability questions are trust tests wearing technical clothes. The buyer usually knows or will discover the true answer; what they are really measuring is whether you tell it to them. A truthful no, delivered plainly, buys credibility that carries the other nine yeses. Two honest-handling moves worth naming because they are exactly what the review credits, and they feel counterintuitive:

• Proactive disclosure. Naming a real limitation before being asked (“I’ll be upfront: we connect to one accounting system per account, not several, so let’s validate early whether that works for you”) prevents a late-stage blocker and reads as confidence, not weakness.
• The specific escalation. When you cannot fully answer a technical question, commit to a named internal expert and a date (“let me confirm with our CIO how we deployed that, and I’ll come back to you by Thursday”) rather than guessing or overselling.

The mid-demo capability check

Pause at least once, partway through, to confirm the demo is hitting what matters and redirect time: “Based on what you’ve seen, are we hitting what matters most? Anything to spend more time on?” The check exists because your demo plan was a hypothesis about their priorities, and the room’s reaction is data. Elite is reading disengagement and reallocating visibly: “reporting clearly matters more than I planned; let’s drop the admin tour and go deep there.” Running the full scripted demo regardless of engagement is Developing.

The concept: the last two minutes decide the meeting

This is the behavior most likely to flag a deal as at risk, and it is entirely in your control.

The close must produce a verifiable forward commitment: a specific date, named attendees, and an agenda or deliverable, affirmed by the customer in the call. An engaged, positive prospect who leaves without those three things is a weak signal, however good the conversation felt.

The psychology of why this gets skipped is worth naming, because knowing it is half the fix. When a call has gone well, asking for a hard commitment feels like risking the warmth: the buyer is happy, why introduce friction? But the ask is not friction, it is the receipt. A buyer genuinely moving forward finds a date in seconds; a buyer who was being pleasant hesitates, and that hesitation is information you want now, not in three weeks of unanswered follow-ups.

Enthusiasm is the moment to ask, not the reason to skip asking.

The close sequence

Five beats, thirty seconds, learnable as a single habit:

1. Summarize“So today we confirmed [pain and number], and the open question is [X].”
2. Propose“The right next step is [specific meeting or action with an agenda].”
3. People“Who on your side should be in it? You mentioned [stakeholder]; should they join?”
4. Date“Does [specific day] work? What does [stakeholder]’s calendar look like that week?”
5. Confirm“So: [date], [names], [agenda]. I’ll send the invite before we hang up. Anything I should have asked that I didn’t?”

Sending the calendar invite during the call, not after, is the strongest single move available: the commitment becomes an artifact while everyone is still in the room.

Converting hedges

Buyers hedge reflexively, not deceptively; a hedge is an almost-commitment waiting for one more question. Convert on the spot:

When the customer resists dating

Sometimes the honest answer is that they cannot commit yet: a board meeting pending, a budget cycle, a reorganization. Do not force a fake date; convert to a conditional one and secure the trigger: “Understood. Your board meets on the 12th; can we pencil the 14th, and you’ll confirm or move it once you know the outcome?”

A conditional date with a named trigger is far stronger than no date, and stronger than a soft date neither side believes.

Language bank

• Discovery close“Is there anything I should have asked that I didn’t? What I’d like to do is come back next Tuesday and walk through what a solution could look like, how we do it, and where we’ve done it before.”
• Demo close“What’s the next thing your team needs to do internally to advance this? Who should be in that conversation? What date works?”
• After a document exchange (NDA, technical documentation):“Once you’ve had a chance to review the docs, when would make sense to reconnect, and who else on your side should be part of that conversation?”Then hold for a specific date and a stakeholder name before accepting “sounds good” as a close.

1. Demo as Discovery

Flagged when a presentation runs for a prospect with no prior discovery call, or whose prior discovery was weak. The pattern: pain gets named in the first minutes, and the seller pivots to a walkthrough and commercials before quantifying the cost, confirming the economic buyer, or establishing a decision process. It comes from a good instinct, showing rather than telling, but a demo before quantified pain has nothing to validate against, so it becomes a tour, and tours produce “looks interesting, send us a proposal” pipelines.

The pressure usually comes from the customer: “can you just show us the platform?” The Competent counter is the trade:

2. Reverse-Engineered Qualification

Flagged on leading-question patterns (“would you say...”, “do you agree that...”, “so it sounds like you really need...”, “wouldn’t it be fair to say...”) followed by brief customer affirmatives (“yes”, “right”, “mm-hm”). This manufactures qualification instead of surfacing it: the pain is yours, the customer merely didn’t argue. A deal file full of your assertions and their nods is a deal file full of nothing, and it collapses the first time a stakeholder you haven’t met asks your contact to explain the problem.

The tell in your own speech: your “questions” contain the answer. The fix is mechanical: strip the assertion, keep the topic, reopen the question. “So it sounds like you really need a second supplier?” becomes “how do you handle it today when a supplier lets you down?” Same topic, but now whatever comes back is evidence.

3. Vocabulary Theater

Flagged when methodology terminology (Champion, Economic Buyer, Decision Criteria) appears in your dialogue while the actual evidence behind it in the call is thin or absent. Saying the words is not doing the work, and the pattern usually appears in internal recaps too: “strong champion, EB identified” over a deal where neither has a name attached to an action. The fix is always the same: attach a specific name, number, or date to the concept, or do not invoke it. “We have a champion” becomes “Marco is introducing me to their COO on Thursday,” or it becomes silence.

4. Happy Ears

Flagged when customer sentiment in the transcript is highly positive but the call produced no real commitment. An engaged, enthusiastic prospect who leaves without a dated, named, agreed next step is precisely the deal that stalls, and the enthusiasm is exactly what makes the miss invisible: everything about the call said yes except the one thing that counts. Module 8’s discipline is the antidote: enthusiasm is the moment to ask for the commitment, not the reason to skip asking.

Reading your own flags

When a deal risk flag appears in your coaching notes, it includes the timestamp and your quote. Go to that moment in the transcript and ask one question: what was the open question I could have asked instead? Write it down; it becomes the first move of your next call on that account. Module 11 walks a full example.

The concept: the invisible 95 percent

The meeting is the visible 5 percent; the prep and the capture are the invisible 95 percent, and skipping them shows up weeks later in the pipeline, not in the meeting itself, which is why the habit is hard to keep and worth keeping. Both rituals produce a written artifact, and the two artifacts feed each other: the capture from this meeting becomes the Mantra you replay at the next one, and the reviewer can check the meeting against the plan.

The pre-meeting plan

Five lines, five minutes, done before every external meeting. A calendar invite or a logistics note is not a plan. Copy this template:

Elite adds three prepared questions tied to the capability gap, the point of view you will bring, and what you intend to walk out with, and the meeting visibly follows the plan.

The post-meeting capture

Same day, while the transcript is still warm in your head. Record what the customer did, not how it felt. Copy this template:

Why same-day matters: Your capture feeds the Mantra you replay at the next open (Module 2), and the reviewer checks the meeting against it. A stale or missing capture degrades every subsequent call on the account: you open the next meeting on old information, the customer corrects you on facts you should have had, and the trust the replay was supposed to build leaks away.

A rated discovery excerpt

A short discovery exchange, then how the reviewer rates it. The point is to see how a transcript becomes ratings with evidence, not to model a perfect call.

Result: 4 of 5 applicable behaviors at Competent or above; all three gating behaviors demonstrated. Coaching focus: follow-up depth, drilling one layer into the $400K breakdown rather than moving on. Notice what the rating did not do: it did not punish the short call for lacking a demo behavior (N/A), and it named the next move on every non-Elite line.

How to work your coaching notes in ten minutes

When coaching notes land, especially with a flag on them, resist the two reflexes: defending the call from memory, and skimming past it. The notes are built to be worked:

1. Start with the one coaching focus and any flags. Thirty seconds.
2. Open the transcript link at the flagged timestamps, not from the top. Read two minutes around each. The quote in the email always has context; sometimes the context softens it, and if you genuinely disagree with a rating, reply and say so; that feedback is reviewed and sharpens future reviews.
3. For each gap, write the question you could have asked at that moment. Not a justification, a question. This is the single highest-value habit in the whole system.
4. Fold those questions into the pre-meeting plan for your next call on that account. A risk flag on the account clears the way it arrived: through behavior in the next transcript.

Where the dimensions meet

The modules were taught separately; on a call they are one motion. The Mantra replay (M2) sets up quantified pain (M3), which arms every reframe you will need (M6) and every altitude choice in the demo (M7). The buying picture (M4) tells you who the close must include, the champion tests (M5) tell you who will carry it, and the close (M8) converts the whole call into the one thing the pipeline can trust: a signal (M1). Master the close first; it is the behavior that pays on every call, this week.