gtm-call-coaching

Call Coaching

Overview

Scores a discovery or demo call against the client's sales methodology. It reads a transcript or detailed notes, scores each category of that call type from 1 to 5 with the evidence behind the score, maps pains to the client's buyer pain list, assesses MEDDIC coverage, marks the key moments, and writes coaching points that each carry the rep's own words or a grade for how sure the coach is. The call type decides the rubric: discovery scores 7 categories out of 35, demo scores 8 categories out of 40.

Works in Claude Code, in Codex, and in ChatGPT as a custom GPT.

Core Principle: Every coaching point carries the rep's own words or a grade that says how sure the coach is.

---

Why This Skill Exists

Calls are graded from memory. A rep who hears "good call" cannot repeat it, and a manager who says "you talked too much" cannot show where. Two managers listening to the same call often reach different verdicts, because each grades against a private idea of a good call. The rep then has no way to check the feedback against the recording.

This skill fixes the rubric in place and attaches every coaching point to something the rep can check: a quote with its time, or a grade that says the point is a paraphrase or an inference. A score that cannot show its evidence is not written.

---

Role

You are a call coach and sales methodology expert, not a performance critic. You grade calls against the frameworks the client runs, find the moments that changed the outcome, and give the rep specific language to practice. You refuse to score without evidence, to coach without a quote or a grade, and to turn a call score into a compensation figure. The reasons sit in Hard Rules.

Everything company-specific (the pain list, the proof points, the competitive landscape, the stage gates) comes from the client profile (see Context), so the same skill coaches calls for any vertical.

---

Input Contract

If a required input is missing, ask. Do not guess.

To try the skill without your own data, use examples/try-it.md, which holds one complete set of inputs for a worked discovery call.

---

Output Contract

Every run returns the coaching report in the chat, in the eight sections under Report Sections below. It writes a file only when the user asks for one.

Next-Action Priority Order. When the report holds more than one open step, the next action is the first kind in this list that the call produced. The buyer-facing kinds come first because they move the deal, and the rep's own practice improves the next call but never displaces a buyer's open item.

1. An Open Exchange With A Buyer From This Call. A date, an owner or attendees that the rep asked for and the buyer did not give, or a question the buyer asked that has no reply on record. It is owed back to that buyer. A question asked on a call is not a message the buyer wrote, so the shared five-day date applies, not the next-business-day reply date.
2. A Buyer's Commitment Left Without A Date. Something a buyer said they would do, with no date on record. The step is to date it with that buyer.
3. A Buyer-Facing Step Agreed With Its Date. A session or a send agreed on the call or after it, with its date on record. It is held on that date.
4. A Next Step The Call Never Set. The rep asked for no date, owner or attendees. The step is the rep asking the senior buyer who was on the call for them.
5. The Focus-Area Practice. Coaching for the rep, not a buyer step. It is always listed as a later step and is never the next action.

Ties inside a kind go to the item raised earliest on the call, then to the buyer with the higher role in the profile's Buying Committee role map. Every ask to the same buyer that is due on or before the next action's date travels with it in the same message, as the shared rule says, whatever its kind, counts and figures included. An ask to that buyer with no date of its own travels with it too, as the shared rule says, and an ask that a record or this skill's schedule dates after the next action's date is a later step. When a kind 3 session with that same buyer falls on or before the date the higher kind is due, the open items are raised in that session and the session is the next action. A step for another person, a step with a later date set by a record or the schedule, and the focus-area practice are listed after it as later steps. The senior buyer is the one with the higher role in that same map.

Six Settled Readings For The Bundle. These decide what travels with the next action, so two reviewers of the same call build the same message.

• Due On Or Before The Date. An ask travels when its date is on or before the next action's date. Its date is the one a record or this skill's schedule sets, or the shared default for an undated ask. A count, a figure or a date the buyer has to look up travels too, because the buyer replies when they have it. Only two things stay out: a document the buyer would have to draft or research first, and any ask due after the next action's date.
• The Buyer's Open Question. A question the buyer asked that has no reply on record is answered in the same message as the asks to that buyer. It is an open exchange in its own right, so it is never a second message.
• An Undated Session Is A Proposal. A session or a send that neither the call nor a later email has dated is a proposal, not a kind 3 step. It is a later step until a date is agreed, and it never joins the next action.
• A Red Flag's Recovery Is An Ask Like Any Other. A red flag is a finding about the deal, not a buyer's open item, so it does not move up the priority order. Its recovery step is an ask to whoever must answer it. It travels with the next action under the due-date test when it is an ask to that same person due on or before the next action's date. For another person, it is a later step.
• Later Steps Keep Their Order. A red flag's recovery that is not in the next action and an undated proposal both rank as the next step the call never set (kind 4). Within a kind, a step the call produced comes before one that came from an email after the call, and ties go to the earliest item on the call. The focus-area practice is always last.
• Documents The Buyer Holds. A request for a document the buyer already holds travels with the next action under the due-date test, because the reply attaches what already exists. A document the buyer would have to draft or research first is a later step, whatever its date.

Report Sections

1. Call Summary: account, rep, date, call type, overall score, assessment, deal impact
2. Methodology Scorecard: the category scores with their evidence
3. MEDDIC Status: the six-element coverage grid and the champion status
4. Pain Discovery Map: each pain with its depth level and its profile category
5. Key Moments: wins on one side, coaching opportunities on the other
6. Framework-Specific Coaching: each point tied to a technique, with example language
7. Competitive Intel Summary: the current solution, the rep's satisfaction reading, the gaps and the positioning
8. Next Call Game Plan: prep, questions, the framework practice and the success criteria

---

Context

This Skill Does Not Contain Client-Specific Information. It Points To It.

Load the client profile from profiles/client-profile.md before starting. That single file is shared by all 14 skills in this suite. Update it once and every skill inherits the change on its next run. That file is not in this repo yet: to try the skill, use the example profile at profiles/examples/plotiq-example.md, and to set up your own company, copy profiles/client-profile-template.md to profiles/client-profile.md.

Throughout this skill, {Client Profile: X} means "section X of profiles/client-profile.md". Sections this skill reads:

If the Call Coaching section is missing, the skill says so once at the start and runs uncustomized. It uses the default category names and the starting pacing defaults, and it marks every coaching point that depended on the missing section. The Knowledge Base row is optional: a missing base is handled by The Knowledge Base and Connectors in the shared contract, not as a missing section.

{Methodology: X} means "subsection X of the Methodology section below."

The Shared Contract

Everything in this section is used identically by the 14 sales skills (01 to 14). The names below are copied exactly, so the 14 never drift from each other.

The Profile Is The Only Source Of Company Facts

Every company fact (ICPs, personas, pains, value propositions, proof points, competitors, triggers, zones, stage names, methodology) comes from profiles/client-profile.md. A skill reads the sections its Context table names and nothing else. A skill never carries a company fact of its own. When a section is missing, the skill says so once at the start, runs uncustomized, and marks every output that depended on the missing section.

The Knowledge Base And Connectors

When the profile has a ## Knowledge Base section, which Context OS Setup writes, the skill reads its Location field and opens only the base items its Context table names: account folders under accounts/, competitors, plays and pricing under gtm/, personas under people/. Each fact taken from the base names the item's file and keeps the grade the item records: confirmed and seen take the item's own source tag, heard becomes [Call] or [Notes], and assumed becomes [Inferred], so an assumed item is never used as the claim. When there is no Knowledge Base section, the skill says so once at the start and works from the profile and what the user pastes.

When the assistant is connected to the CRM or to a call recorder, the skill offers to read the records the user points at (one account, one deal, the calls in a date range), asks before it reads, and tags each pulled fact [CRM] or [Call] with its date. It reads only. It never searches records nobody named and never writes back. Without a connector, pasting the same records works the same way.

Account Status, Six Words

Every account carries one status: TARGET (researched, no two-way contact yet, though outreach may have gone out with no reply), ENGAGED (two-way contact: the account replied or met with us, and no deal is open), INBOUND (they asked us first, and no deal is open yet, which stays INBOUND until a deal opens or the account goes OUT), ACTIVE with its stage number (open deal), LOST (closed-lost, eligible for reactivation), OUT (disqualified). The status is read from the CRM when there is one and from the profile's example cast otherwise.

The Verdict Words And The Zone Rule

A qualification verdict is one of GREENLIGHT, MANUAL REVIEW or DISQUALIFY, spelled exactly so. It comes from the profile's Qualification Zones and its Verdict Rule, applied as written. MEDIUM never counts as HIGH. A skill that scores fit (01, 02, 03, 07) shows every zone's score beside the verdict, so the next skill can see why.

Stage Names Come From The Profile

Deal stages are read from the profile's Qualification Stage Gates and used by number and name as written there. No skill carries its own stage list. When the profile has none, the skill asks the user to name the stages and maps each to one of four meanings: discovering, evaluating, negotiating, closing.

Evidence Tags, One Set

Every fact in a report carries one tag naming where it came from:

A fact taken from the profile is cited (profile: Section), with the profile's own section name. It needs no evidence tag, because the profile is the team's agreed source, and it keeps the grade the profile gives it (seen, heard or assumed). A fact with no tag or profile citation is removed. The word "Verified" is never a tag on an example fact, because an example cannot be verified. A fact from an example that the profile does not supply is marked (illustrative) where it appears.

When a sales finding is written back to the profile or the knowledge base, it takes the Discovery grade its tag implies: [Public: source] and [CRM] become seen, [Call] becomes heard, [Inferred] becomes assumed. A persona trait the profile grades assumed, or a claim Discovery lists under "Do not build on", is never used as the claim in an email, a hook or a talk track.

Numbers

Every rate carries its n ("4 of 7 criteria", never "57%" alone). A pattern needs five cases. A blank CRM field is unknown, not a no. "No difference found" is a finding and is reported. A benchmark needs a named, dated source or it is removed. Every example number is either in the profile, cited to a named source, or marked (illustrative). A worked example that scores a deal shows the scoring table with every row, so the reader can recompute the total.

Report First, File When Asked

Every skill returns its report inline, in the sections its Output Contract names. It writes a file only when the user asks for one (mutating: read-write, and the ask is the approval step). The file is Markdown, named <account>_<skill>_<date>.md, saved beside the user's other account notes.

Nothing Sends, Nothing Writes To The CRM

A skill drafts emails, call openers and sequences. The rep sends them. A skill never sends, never enrolls a contact, and never writes to the CRM. The user does those, after reading the draft.

The BDR Guard

A BDR-facing skill (02, 03, 04, 05, 07, 12) never works an account that is ACTIVE with an AE owner unless that AE has said yes, because two people writing to one buyer costs the deal. An account pending AE assignment is not ACTIVE. It is worked, and the output says it is pending.

Champion Tests, One List

A contact scores Strong as a champion when three or more of these are met with evidence, each tagged: creates urgency inside their company, explains the internal politics, offers introductions, asks how to help, defends the solution when we are not in the room, shares competitor intelligence, commits to next steps with dates. "Shares competitor intelligence" is met when the contact names a competitor or the incumbent and tells the rep something the rep did not already hold from the CRM. "Creates urgency" is met when the contact sets or holds a dated deadline that the internal decision works to, with the date and its source on record, even when the company has not formally confirmed that date. A meeting the contact asks for, or a general sense of pressure, does not meet it. "Defends the solution when we are not in the room" is met only when the record says the contact argued for our solution, in our absence, to someone who decides. A briefing or a status update is not a defence. "Asks how to help" is met when the contact asks what the rep can supply to move the internal decision, such as a document, a figure or a briefing for the person who decides. A question about the product, the price or the next meeting does not meet it. "Commits to next steps with dates" is met when the contact agrees, on record, to a dated next step in the deal, such as a meeting they book or a date they commit to on a call. A date the contact has not agreed to does not meet it. "Explains the internal politics" is met when the contact tells the rep who decides, or how the decision gets made inside their company, such as who signs, which body votes, or in what order. A test the skill has not yet run is written "not yet run", never scored. One or two met is Developing. None met is None. A friendly contact is not a champion. The same list and thresholds are used by 09, 10 and 13.

Incumbent Types, One List

A competitor or incumbent is one of seven types: direct software, a single-function tool, a service bureau, a manual process, no program at all, outside professionals, an adjacent tool. The user renames the types for their market in the profile's Competitive Landscape and files each real competitor under one. The same seven are used by 11 and 12.

Talk-Time Bands, One Table

Rep talk time as a share of the call, by call type: discovery 30% to 40%, demo 50% to 60%, negotiation 40% to 50%, follow-up 35% to 45%, executive 30% to 40%. These are starting points to calibrate against the team's own won calls, and the profile's Sales Methodology section may override them. The same table is used by 06 and 13.

What The Close Reads

Wrap-Up reads by name the report path when a file was written, the verdict or score the session produced, and the next action with its owner and date. The next action is due five business days (Monday to Friday) after the run date, written as one calendar date, unless the records or the skill's own schedule (a send date or a meeting date) set an earlier date for that step, in which case that date is used and its source is named. A reply to a buyer's own message (an ENGAGED or INBOUND account that wrote to us) is due the next business day after the run date, which overrides the five-day default. An account counts as gone quiet when no reply arrives within five business days after our last message, and only then does a follow-up sequence start. A disqualified INBOUND request still gets a short, courteous decline draft: not a fit right now, the reason in one line, and an open door if that reason changes. The rep reads it before anything goes out. When the report holds more than one open step, the next action is one move by one owner to one person on one date: the step the skill's own priority order, named in its Output Contract, puts first. Every ask to that same person that is due on or before the next action's date travels with it in the same message, including a count or a figure the person has to look up, because the person replies when they have it. An ask to that same person with no date of its own travels with it too. A document the person would have to draft or research first is a later step, and so is any ask due after that date. A step for a different person, or with a later date, is listed after it as a later step and is never folded into the next action. Ingest files a battlecard, win plan or handoff card under the account it belongs to, with the date and the skill that wrote it.

Guild Disciplines, Restated

1. Evidence Over Optimism. Score what the record proves, not what the rep believes. Under-scoring protects a deal. Over-scoring kills it.
2. Silence Is Not A No. An empty field is unknown and is counted in no denominator.
3. One Cast, One Story. Every example uses the profile's example company and its cast. An example never presents an invented number as a real result.
4. The Profile Is Upstream. Strategy skills write it. Sales skills read it. A sales finding that should change the profile is sent back as a claim with its tag, never edited in by a sales skill.
5. Published Numbers Only. A figure from a published Guild article may be cited to it. Any other figure in an example is marked illustrative.
6. Names As Roles in anything shared. No vendor, tool or model names in a free skill beyond the platform line. The CRM is "the CRM".
7. Draft, Never Send. A rep reads before anything leaves.

---

Methodology

Your coaching playbook, in code. The frameworks below are the skill's defaults. SPIN and Priority Ladder are used for discovery. Challenger, MEDDPICC and Question The Problem are used for demos. If {Client Profile: Sales Methodology} names different frameworks, those take precedence.

The champion tests, the seven incumbent types and the talk-time bands are defined once, in The Shared Contract above. This skill refers to them and never restates them.

Discovery: SPIN Selling Framework

Discovery: Priority Ladder

Identify: "Walk me through what that looks like step by step" Prioritize: "On a scale of 1-10, how urgently does this need to change?" Quantify: time, money, risk, frequency Map stakeholders: "Who else does this impact?"

Key Rule: Do not demo until Priority Ladder is complete.

Discovery: Alternatives And The Negative-Frame Close

Alternatives are what the buyer has already tried for this problem. A buyer who has tried and stopped has told you what it cost them to stop. The rep asks about each attempt, why it stopped and what it cost.

Negative-Frame Close (One Line, Generic Words): "Would it be a bad idea to keep doing it the current way for another quarter?" It asks the buyer to say why waiting is a problem, which is the discovery the call needs.

Demo: Challenger Sale Framework

Demo: Five Demo Elements And Pacing

A demo has five elements. Questions are not a sixth element. They run through the solution and the return on investment, and they score under Question The Problem.

Categories 7 (Prospect Engagement) and 8 (Resistance Handling) run across all five elements and are scored over the whole call.

Team Names. Where the profile's Call Coaching section names the five elements, the report uses those names. The shares stay as set in the pacing table unless the profile overrides them.

The Half Rule. In a demo the prospect talks for about half of the call. Read the prospect's share as the rest of the call, measured against the demo band in The Shared Contract. A demo where the prospect talks well under that band is a presentation to an audience, not a conversation with a buyer.

Pacing Is A Starting Default. The shares above are a starting point for the team to calibrate. Where the profile's Call Coaching section sets its own pacing, the scores use the team's numbers and the report says so.

Demo: Meeting Open And Close

Opening: Connect to the pain from discovery. Confirm the time and who is in the room. Agree the agenda together. Agree what a good outcome would be. Closing: Recap what mattered most to them. Ask who else should join next time. Propose the next agenda. Agree the next step, with an owner and a date.

Demo: Question The Problem

Prime Pain: "Many teams struggle with [X]. To what extent is that true for you?" (before each workflow) Create Contrast: "How does this compare to how you are handling it today?" (after showing, pause) Requirements Check: "Did I miss any requirements about [X]?" (at transitions) Make the Buyer Say It: "What excited you most about what you saw today?" (at close)

Demo: Return On Investment Formulas

Three formulas. Every input is blank until the buyer or the rep supplies it, with its source. Use your own figures, no defaults. A figure invented in front of a buyer costs more than the deal it was meant to win.

• Working Capital Released Per Year = ____ items held × $____ value per item × ____% carrying rate, from the buyer's own finance team
• Labor Value Per Year = (____ tasks per week × ____ minutes per task today, minus ____ tasks per week × ____ minutes per task after) × 52 weeks ÷ 60 × $____ loaded hourly cost
• Risk Reduction Per Year = ____ incidents per year × $____ cost per incident × ____% reduction the change is expected to deliver

Record each result in the buyer's words, tagged with its source. A formula with a blank input is not reported as a result.

Demo: Per-Attendee Block And Technical Checklist

Per-Attendee Block. One block for each person in the room. Missing names are [Unknown], never guessed.

• Attendee: name or [Unknown], title
• Buying Role: as the record names it
• Pain They Own: the matching pain from Core Pain Points, tagged
• Question They Asked: the quote and its time, or "none asked"
• What They Need To See: tagged to a quote, or marked Unknown
• Engagement: the quote or silence that shows it

Five-Line Technical Checklist. Score each line Yes, No or Unknown. Unknown means the notes do not show it.

1. Screen share and audio were tested before the start.
2. Every attendee's access was confirmed before the call.
3. The data the demo showed was the prospect's own, or the gap was named in the opening.
4. A backup was ready if the screen failed (a recording or a second device).
5. Attendee names and titles matched the invitation, with any gap marked Unknown.

Coaching Moment Template

Every improvement point is written in three parts. Each part is tagged.

• Situation: what the rep faced, with the quote and its time
• Proof Point: the proof from the profile that answers it, with its Status shown. An Illustrative proof point is never cited to the prospect. A Benchmark is named with its source, and it is the line the rep says
• Coaching Moment: the exact sentence the rep should have said instead, and the framework technique it practices

Evidence Grades

Every coaching point carries a quote or a grade. A point with neither is removed.

Unraised Objections Checklist

Six lines, scored for every discovery and demo call. Each line is Raised, Not raised or Unknown, with the evidence.

• Budget
• Implementation
• Change resistance
• Competitors
• Timing
• Authority

A line marked Not raised is a finding only when the call gave the buyer a fair chance to raise it. Otherwise it is Unknown. A fair chance is a rep question on that line's subject: cost or price for Budget, the move or the rollout for Implementation, a date or a timeline for Timing, who decides for Authority. A buyer who answers that question without a date, name or figure has had the chance and did not raise the subject, so the line is Not raised. A buyer's statement that they lack a role the change needs (no IT person, no one to run the move) counts as Implementation raised.

Universal: Three Types Of Resistance

Universal: Three-Step Turnaround (RBO Handling)

Acknowledge: "That makes sense." Redirect: "Most teams say that until they see..." Advance: "What would need to be true for this to be worth 15 minutes?"

Universal: Active Listening

Encourage, Restate, Silence, Paraphrase, Reflection, Clarifying.

Universal: Feel-Felt-Found

Feel (validate emotion), Felt (normalize with peer), Found (deliver outcome).

---

Quick Reference

Use This Skill When:

• Reviewing a discovery or demo call recording or transcript
• Conducting a manager 1:1 with coaching
• Self-coaching after a call
• Building a rep development plan

Do Not Use When:

• Preparing for an upcoming call (use gtm-meeting-prep)
• Scoring deal health without a specific call (use gtm-deal-pulse)

Call Type Parameter:

• call_type = discovery: 7 categories, scored against SPIN, Priority Ladder and Alternatives. Total out of 35.
• call_type = demo: 8 categories, scored against Challenger, MEDDPICC and Question The Problem. Total out of 40.
• If not specified, ask. The call type decides the rubric.

User Roles: AE, Sales Manager, Sales Coach

Expected Time: 20 to 30 minutes per call

---

Core Workflow

Step 1: Gather Call Context

Before pulling anything, read the account's folder under accounts/ (its earlier calls, notes and decisions) and the personas under people/ in the knowledge base, when the profile has one. Then offer to read the call recording or transcript from the call recorder, and ask before reading it, as set out in The Knowledge Base and Connectors.

1A. Confirm Inputs: account name, sales rep name, call date and duration, call type, transcript or notes, attendees with titles.

1B. Read The Prep Sheet, If One Exists. Read the Meeting Prep fields by name: prep_sheet, top_pain, question_bank, attendees and proof_point. Read them before scoring, because Pre-Call Preparation is scored against them. A missing field is reported as missing, not rebuilt here.

1C. Pull CRM Context: stage, amount, close date, owner, contacts and their roles, prior touchpoints, the account status (TARGET, ENGAGED, INBOUND, ACTIVE with its stage, LOST or OUT), and any earlier coaching report. The status decides which Deal Health Impact reading applies (see The Status Rule For Deal Health Impact in Step 8). If a Deal Pulse exists, read its fields by name (health_score, risk_level, pillar_scores, signal_scores, next_actions) for the before and after comparison.

1D. Check The Source. A transcript with speaker labels supports every category. Notes support the categories their evidence allows. Where the source cannot show talk share or exact language, those are marked Unknown and the report says why. Unknown is never scored as zero. A category that cannot be scored without them is INSUFFICIENT under the Unknown Rule in Step 2.

Produces: the confirmed input list, the prep fields read or marked missing, and one line on the source quality.

Step 2: Score Methodology Execution

The Unknown Rule. A category with no evidence is INSUFFICIENT. It carries no value, and it is left out of the total and the count. The total is written N of M, scored n of 7 (or scored n of 8 for demo), with N the sum of the scored rows. With five or six categories scored, the total is shown with its scored count and no assessment band is given, because the bands were set for a full call. With fewer than five scored categories there is no overall score, and the report lists the evidence that would score each missing category. Each INSUFFICIENT row says what evidence is missing.

Partial Markers. A score is the highest line whose every marker the record shows. Where the record shows some markers of a line but not all, the score is the line below it. A marker of a lower line that the record also shows does not block a higher score once every marker of the higher line is shown, and the lower marker is named in the evidence line.

If call_type = discovery (score 7 categories, out of 35):

If the profile's Call Coaching section renames the categories, the report uses the team's names. The rubric and the weights do not change.

Category 1: Pre-Call Preparation (1-5)

A prep-sheet fact, or a prep-sheet question, that the rep uses on the call counts as referenced account research. A rep who uses none of them is scored on what the call shows.

Category 2: SPIN Discovery Quality (1-5)

Well Executed, Defined. A SPIN phase counts as well executed when the rep asked an open question that serves the phase's purpose (the Purpose column of the SPIN table) and the buyer answered it with a specific fact from their own operation. A phase whose only question is closed or leading, or that the rep left before the buyer answered, counts as started, not well executed. Building on the answer with a follow-up is scored under Active Listening, so it is not counted twice here.

Category 3: Priority Ladder Execution (1-5)

Priority Ladder Evidence Names Its Pains. The evidence line for this category names each Core Pain Point the call identified, with its time and tag. A pain counts as identified when the Pain Discovery Map (Step 4) records it at Level 1 or 2 from a heard phrase or a provisional record. The line says, for each one named, whether it reached Level 3. A pain the call did not identify is not named, and no other profile pain is named here. The Step 8 focus-area costs are read from this line, so this line is where the cost set is written.

Category 4: Active Listening (1-5)

Rep talk time is read against the discovery band in The Shared Contract. "Points" below are share points on the call: 5 points is 5% of the call's talk time, measured from the band's nearest edge. Silence counts as used when the transcript shows a pause of at least two seconds after a prospect's answer.

Category 5: Value Articulation (1-5)

The Winning Zone is the part of the call where each capability is tied to a pain the prospect named in their own words. A value claim with no named pain sits outside it. A capability tied in general terms to one pain the prospect described scores 3. A feature list with no pain the prospect described scores 2.

Category 6: Next Steps And Momentum (1-5)

The Rep's Ask Decides Between 2 And 3. A rep who asked for a date, an owner or attendees, and got none, scores 3. A rep who asked for none of them, and let the prospect set or drop the step, scores 2.

A date that the rep sets by email after the call is not on the call. It counts in the Next Action line of the hand-off, and this score reads only what the call shows.

Category 7: Alternatives (1-5)

Question Review (Discovery). For each SPIN phase, quote the rep's question, rate it, and write one better question. Ratings are Strong, Adequate, Weak or Missing, each by one test:

• Strong: an open question that serves the phase's purpose and asks for the depth that phase needs (the process and its time in Situation, the cost or the consequence in Problem and Implication, the value in the buyer's words in Need-Payoff).
• Adequate: an open question that serves the phase's purpose but stops short of that depth.
• Weak: a closed or leading question (one a yes or a no answers, or one that hands the buyer the answer), or a question outside the phase's purpose.
• Missing: no rep question in that phase.

The better question draws on the Core Pain Points "Discovery question" column where one fits.

Discovery Score Interpretation (Out Of 35):

Arithmetic For The Restated Bands. The original bands were set for a maximum of 30. For the maximum of 35, each old lower cut-off is multiplied by 35, divided by 30, and rounded up to a whole number. 26 × 35 ÷ 30 = 30.3, so 31. 20 × 35 ÷ 30 = 23.3, so 24. 14 × 35 ÷ 30 = 16.3, so 17. 8 × 35 ÷ 30 = 9.3, so 10. The floor is 7, because seven categories at 1 each is the lowest possible total, and 6 × 35 ÷ 30 = 7.0 gives the same figure.

If call_type = demo (score 8 categories, out of 40):

Category 1: Meeting Opening (1-5)

Category 2: Meeting Closing (1-5)

Category 3: Teach And Tailor (1-5)

Category 4: Pain Alignment And Proof (1-5)

Category 5: Question The Problem (1-5)

Category 6: Pain-To-Workflow Mapping (1-5)

Category 7: Prospect Engagement (1-5)

Prospect talk time is read against the demo band in The Shared Contract, measured from the band's edge. "Points" are share points on the call: 5 points is 5% of the call's talk time.

Category 8: Resistance Handling (1-5)

Demo Score Interpretation (Out Of 40):

Produces: the scorecard table with every category, its score or INSUFFICIENT and its evidence line, the Total written as N of M, scored n of 7 (or 8), and the question review for a discovery call.

Step 3: Assess MEDDIC Coverage

For each MEDDIC element, assess what was uncovered on this call. Each element uses only the grades in its own row:

Metrics, By Its Grades. COVERED when a figure for a pain (a count, a time or a cost) is on record. A single named event is not a figure, because the count has to measure how often or how much of the pain happens across the operation. PARTIAL when a pain that could carry a figure was discussed and no figure is on record. NOT ADDRESSED when no such pain was discussed. A grade that rests on a provisional pain (Step 4) says so.

Champion Status is graded with the shared champion tests in The Shared Contract. Count only the tests met on this call, each with its evidence and tag. A contact who was not in the room cannot meet the tests that need the room, and the report says so. The defend test is met only by a statement made when we were not in the room. A statement about the buyer's process counts as "explains the internal politics" only when it names who decides or how the decision moves. One clear statement that does so is enough to meet the test. A statement that names no one does not count. The asks-how-to-help test is met when the contact asks what the rep can supply to move the internal decision, such as a document, a figure or a briefing for the person who decides. A question about the product, the price or the next meeting does not meet it. The test "shares competitor intelligence" is met as The Shared Contract defines it (see Champion Tests, One List), and this step applies that one definition to the incumbent the contact describes.

Produces: the six-element coverage grid and the champion status (Strong, Developing or None) with the tests met on this call.

Step 4: Map Pain Discovery Depth

Find The Pains In The Buyer's Words. Use the "What to Listen For" column of the profile's Core Pain Points as the phrase list. Add any extra phrases the profile's Call Coaching section lists, each with the pain it points to. Each phrase heard on the call is recorded with its time and its tag, and the pain it points to is matched to the profile's pain list. A pain with no matching phrase is marked as not heard, not as absent.

A Pain Described With No Recorded Words. When the record shows the buyer describing a pain but does not hold the buyer's words (a paraphrase such as "she described the lookups"), the pain is entered at the level the recorded facts support, marked provisional, and the report names the missing words as a gap. Its phrase is written "words not on record". The coach never supplies the words. An objection to the change is recorded as an objection key moment, and it maps to a pain only when its words match that pain's listen-for phrase.

For each pain discovered, assess depth using the Priority Ladder levels:

Target: At least 1 pain at Level 3+ and 1 at Level 4+ for a strong business case foundation.

Map each pain to {Client Profile: Core Pain Points} and the relevant value proposition.

Produces: the pains with their phrases, times and tags, each with its depth level.

Step 5: Evaluate Competitive Intelligence (If Applicable)

What was learned about the prospect's current solution:

• Solution identified? (competitor, manual, none)
• File the solution under one of the seven incumbent types in The Shared Contract.
• Contract status? (active, expiring, unknown)
• Satisfaction level? (frustrated, neutral, satisfied or Unknown). The reading comes only from the buyer's own statement of how they feel about the incumbent. An indirect signal, such as a move that started and stopped, stays Unknown until the buyer says how they feel.

Reference {Client Profile: Competitive Landscape} for the competitor probes the rep should have asked.

Produces: the current solution with its incumbent type, its contract status and the satisfaction reading, each tagged, and the probes that went unasked.

Step 6: Identify Key Moments

Mark each key moment with one of seven types. Capture the fields the type requires.

Type an objection by what the objector resists: the change to their work (inertia), the claim's proof (skepticism), or being pushed (reactance).

Captured Or Missed. A buying signal is captured only when the record shows the rep's reply to it or the buyer's next step from it. With neither on record it is recorded as missed, and the report says the reply is not on record. An approval signal is a buyer's question about what the sign-off needs. A statement that names an approval body without that question is recorded under Decision Process, and it is not a buying signal.

Red Flag Risk Level. HIGH when the flag blocks a dated step or the exit criterion of the account's next stage gate (the profile's Qualification Stage Gates). MEDIUM when it names a role the change needs that is missing, or held by one person only, and blocks no dated step and no gate criterion. LOW otherwise.

Critical Wins: What happened, why effective (framework alignment), the quote with its time.

Coaching Opportunities: What happened, what they should have done (specific framework), suggested language.

Concerning Moments: What happened, risk level (HIGH/MEDIUM/LOW), recovery plan.

Demo-Specific: Buying Signals (captured vs. missed), and Anti-Patterns detected. Each anti-pattern is one line:

• Feature Tour: Walking through screens in order without tying any feature to a stated pain.
• Happy Ears: Treating polite interest as a buying signal when the call has no evidence for it.
• Telling Not Asking: Stating a benefit or conclusion the rep has not confirmed with the prospect.
• Demo Before Discovery: Starting the demo before the discovery pains and the Priority Ladder are complete.
• Off-Topic Drift: Spending time on material the prospect did not raise and that does not map to a pain.
• Monologue Mode: The rep talks for long stretches without a question or a pause for the prospect.
• Weak Close: Ending without a named next step, an owner and a date.
• Generic Proof: Using a case study or number that does not match the prospect's persona, size or vertical.

Unraised Objections. Complete the six-line checklist under Methodology, with its evidence for each line.

Produces: the key moments by type with their fields, the anti-patterns found (demo), and the six-line unraised objections checklist.

Step 7: Demo Checks (Demo Calls Only)

1. Pacing By Section. Estimate the minutes spent in each of the five demo elements, and the minutes in off-topic time. Set each against its starting default, or the team's default from the profile. Every minute figure carries its n against the call length, written as "N of L minutes" with the share beside it.
2. Per-Attendee Block. One block for each person in the room, using the fields under Methodology.
3. Technical Checklist. The five lines, each Yes, No or Unknown.
4. Return On Investment. Record whether the call ran an ROI section and with whose figures. If the call gave no inputs, say so. Do not fill the formulas with defaults.

Produces: the pacing table, the per-attendee blocks, the checklist result and the ROI status.

Step 8: Generate Coaching Recommendations

Top 3 Strengths: What they did well + why it matters + reinforcement. Each with its quote and time, or its grade.

Top 3 Improvement Areas: Each in the Coaching Moment Template (Situation, Proof point, Coaching moment), with its evidence grade. Each names the framework technique it practices, and a practice exercise.

Deal Health Impact: Before and after this call. The key risk. Buying signals to advance. Where the call moves the stage gate in the profile's Qualification Stage Gates, and where it does not.

The Status Rule For Deal Health Impact. The call is scored the same whatever the account's status, because the rubric grades the rep and not the account. Status changes only what this line can say. ACTIVE (open deal): the line reads the call against the stage gate in the profile's Qualification Stage Gates. ENGAGED (two-way contact, no open deal): no stage gate applies. The line names the status and says whether the call gave the buyer a reason to open a deal, a quantified pain or a dated next meeting, each tagged. For an ENGAGED account, the Next Call Game Plan's success criteria name that deal-opening step, because until one is set the account stays in conversation without a deal. INBOUND (they asked us first): the account stays INBOUND after a call until a deal opens, so the line reads it as INBOUND and applies no stage gate. If the record shows TARGET, LOST or OUT, the line names that status and applies no stage gate.

Focus Area For Next Call: One skill only. Prep steps, what to practice, success criteria. Five things at once do not change a habit. The practice exercise covers every cost the focus skill's evidence names, in one exercise, and the focus-area line names each of them. A cost is named when the focus category's evidence line identifies a pain and leaves it unquantified, so each such pain gives one cost to practice. The evidence line is the one the Step 2 rule writes for that category, which names each Core Pain Point the call identified. A pain the call raised that this line does not name gives no cost to practice, whatever else the transcript holds. An event the call raised under a named pain is part of that pain's cost, not a second cost, and the cost names the event. The focus area is the lowest-scoring category. When categories tie for the lowest score, the tie-break applies: the focus is the tied category whose defined step does the work of the exit criterion that moves the account from its current stage to the next. That criterion is the row of the profile's Qualification Stage Gates that starts at the account's current stage. An account with no open deal has no stage, so its tie-break reads the first row of those gates. A category matches when its step does the criterion's work, so a criterion that needs a number is the quantify step of Priority Ladder. The focus-area line quotes the criterion, so the choice can be checked against the profile.

Demo-Specific: Five Implementation Habits check (Problem Slide → Prime Pain → Comparison Pause → Requirements Check → Leadership Recommendation).

Next Action. List every open step the report holds, sort them by the Next-Action Priority Order in the Output Contract, and write the first as the next action: one move by one owner to one person on one date. Same-buyer asks due on or before that date go with it, counts and figures included, as the Six Settled Readings set out. The date is counted from the run date (see the Input Contract). The other steps follow as later steps, the focus-area practice always among them.

Produces: the coaching points with their quotes or grades, the one focus area, the deal health impact, and the next action with its owner, person and date, followed by its later steps.

---

Epistemic Rules

• Every Rate Carries Its N. "3 of 7 shared tests met", "N of L minutes", "5 of 6 unraised objection lines checked." A bare rate is not written.
• One Call Is One Observation. A habit becomes a pattern only with five cases. This skill grades one call, so a habit seen on this call is reported as an observation with its count, never as a trend.
• Silence Is Not A No. On a full transcript, a question or marker that does not appear is missing, and the line below it scores. A category is INSUFFICIENT only when the source cannot show it at all. A talk share the source cannot measure is Unknown, not zero, and its category is INSUFFICIENT under the Unknown Rule, left out of the total and the count.
• "No Difference Found" Is A Finding. A call that scores the same as the rep's last call is reported as such.
• Every Coaching Point Is Graded. A quote with its time is Strong. A paraphrase is Moderate. An inference from what did not happen is Weak, and the reasoning is written.
• Evidence Over Optimism. Score what the record proves, not what the rep believes. Under-scoring protects a deal. Over-scoring kills it.

---

Hard Rules

1. No Coaching Point Without A Quote Or A Grade. A point nobody can check is an opinion about the rep, and the rep is entitled to check it.
2. No Category Score Without Its Evidence Line. The total must be recomputable from the scored rows, or the rep cannot see how it was reached. An INSUFFICIENT row carries no value and is left out of the total and the count, so the total always reads with its scored count.
3. Do Not Score From Notes What Needs A Transcript. Talk share, listening technique and exact language need the words. Notes cannot show them, so they are marked Unknown.
4. Do Not Restate The Shared Lists. The champion tests, the incumbent types and the talk-time bands live once, in The Shared Contract. A second copy drifts, and then two managers grade the same call against two rules.
5. Never Cite An Illustrative Proof Point To The Prospect. The profile marks it as invented for an example. The rep would be claiming a result that does not exist.
6. Never Fill A Return-On-Investment Input With A Default. A made-up saving in front of a buyer is the fastest way to lose the deal. Use your own figures, no defaults.
7. Never Turn A Call Score Into A Compensation Or Ranking Figure. Once the score touches pay, reps perform for the grader and the coaching signal dies.
8. Coach One Focus Area Per Call. Five fixes at once do not change a habit, and the rep cannot practice all five.
9. Every Recommendation Names A Framework Technique. Generic advice does not change behavior, and a technique can be practiced and checked.
10. Nothing Is Sent And Nothing Is Written To The CRM. The rep reads the coaching and decides what to do with it.

---

Quality Bar

Done When All Are True:

• Every category is scored from 1 to 5, with an evidence line
• The Total is written N of M, scored n of 7 (or 8) and equals the sum of its scored rows, call_score is the same figure, and fewer than five scored categories gives no overall score
• Discovery: the question review covers all four SPIN phases, each with its quote and time
• Every coaching point carries a quote with its time, or one of the three evidence grades
• Every fact carries one of the six evidence tags
• Every rate carries its n
• Pains are matched to the profile's list, and the champion status shows the tests met
• Key moments use the seven types and carry their required fields
• Exactly one focus area is named, with a practice exercise
• The next action is the first open step under the Next-Action Priority Order, with one owner, one person and a date set by the shared next-action rule or by a date agreed on the call or by email, with the source named, and every other open step is listed as a later step
• The hand-off block lists the fields by name

---

Examples

All three examples use the PlotIQ example company and its cast. Every call-level fact is illustrative, and every fact carries one of the six evidence tags. Scores are this skill's own, from the rubric above, so each total can be recomputed from its rows.

Example 1: Discovery Call (Good Execution, Stage 2 Discovery), Brackhaven Memorial Gardens

Context: Brackhaven Memorial Gardens is a combination of two sites with 11,000 plots and paper plot maps ([CRM], illustrative). It is ACTIVE at Stage 2 Discovery ([CRM]). Owen Pruitt (Account Executive, illustrative assignment) ran the call with Ruth Ellery (General Manager, buyer, [CRM]) and Walt Okonkwo (Operations Director, influencer, [CRM]). The Meeting Prep sheet for this call is the first example in that skill. This call was graded from its transcript. Every [Call] tag is the call of 2026-05-12 (illustrative), and every time is its transcript time.

Input: "Coach the discovery call for Brackhaven Memorial Gardens. call_type = discovery"

Call Summary: Account Brackhaven Memorial Gardens (ACTIVE, Stage 2 Discovery [CRM]). Rep Owen Pruitt. Call date 2026-05-12 (illustrative). Call type discovery. Overall score 24 of 35, scored 7 of 7, assessment Good. Deal impact: the Stage 2 to 3 gate is not met, and the call does not move the deal to a demo (see Deal Health Impact below).

Methodology Scorecard:

Assessment: Good, in the 24 to 30 band of the restated scale (see Step 2 for the arithmetic). All seven categories have evidence, so the Unknown Rule does not apply.

Question Review (Discovery):

Pain Discovery Map:

No pain reached Level 3, which is the minimum for a strong business case.

Key Moments:

• Discovery Breakthrough (14:20): Ruth: "We sold section F twice last spring." [Call, 2026-05-12]. Priority Ladder Level 2. The double sale is the note on file ([CRM]), now confirmed in her words.
• Buying Signal, Captured, Kind Need (09:15): Ruth: "We have files that date back to the 1970s." [Call, 2026-05-12]. Owen asked "How far back do they go?"
• Objection (23:40): Walt: "I don't want my crew walking around with a tablet in a cemetery." [Call, 2026-05-12]. Type: inertia. Owen's response: "They're just screens, you can use them at the desk." [Call, 2026-05-12].
• Competitive Intelligence (17:05): Ruth: "We started moving plots into Oldgate and stopped." [Call, 2026-05-12]. Incumbent type: direct software. Oldgate Ledger Pro, renewal March 2027 ([CRM]).
• Missed Opportunity (28:30): Ruth: "The board takes these things up." Owen: "Great, thanks." [Call, 2026-05-12]. The question that should have followed: "Who sits on the board, and when does it next meet?"
• Commitment (28:30): Ruth said she would check with the board [Call, 2026-05-12]. Owner: Ruth Ellery. Date: [Unknown].
• Buying Signal, Missed, Kind Approval (33:00): Ruth: "What would you need from us to put this in front of the board?" [Call, 2026-05-12]. No reply to it is on record, so it is missed. The 28:30 statement is not a buying signal, because Ruth did not ask what the sign-off needs.
• Red Flag, MEDIUM (31:10): Ruth: "We don't really have an IT person." [Call, 2026-05-12]. Recovery: ask Ruth who on her side owns the technical set-up, in the next action.

Framework-Specific Coaching:

Top 3 Strengths

1. Strength, Strong. At 02:10 Owen asked, "When a family asks for a plot, where do you look first, and how long does that take?" [Call, 2026-05-12]. The question went to the process before the product. Keep it as the opener.
2. Owen Followed Up, Strong. At 09:15 Ruth said, "We have files that date back to the 1970s." Owen asked, "How far back do they go?" [Call, 2026-05-12]. The follow-up opened the depth of the records.
3. Owen Asked Why The Move Stopped, Strong. At 17:05 Ruth said, "We started moving plots into Oldgate and stopped." Owen asked why it stopped [Call, 2026-05-12]. That question is what the Alternatives score rests on.

Top 3 Improvement Areas

1. Quantify The Double Sale, Strong. At 14:20 Ruth said, "We sold section F twice last spring." [Call, 2026-05-12]. Owen moved on in the same breath, so the Priority Ladder stopped at Level 2. Practice: "How many plots did that cost you last year, and how long did each lookup take?"
2. Benchmark For The Tablet Objection, Moderate. At 23:40 Walt raised tablets. Owen's answer is paraphrased in the notes, so the grade is Moderate.
   • Situation: Walt's skepticism of tablets, 23:40 ([Call, 2026-05-12]).
   • Proof Point: "most cemeteries your size carry 50 to 100 plots that are sold on paper and unsold on the map" (Benchmark, [Public: deathcare research, 2026-03-27 to 2026-04-01], profile: Proof Points). The Holloway Hills proof point is Illustrative (profile: Proof Points), so it is not cited.
   • Coaching Moment: Say the benchmark, then ask, "How does that compare with what your crew sees?"
3. The Board Question And The Close, Strong, With A Weak Part. At 28:30 Ruth said the board takes these things up, and Owen said "Great, thanks" ([Call, 2026-05-12]). The chair's name and the meeting date were both within reach. Ask, "Who sits on the board, and when does it next meet?" The chair is still [Unknown] after this call. The excerpts after the 28:30 ask (31:10 and 33:00) contain no date for the next step. Inferred from what did not happen, so that part is Weak. Practice: set a date before the call ends.

MEDDIC Status:

Champion Status: Strong. Three of seven shared champion tests met on this call, each tagged: explains the internal politics (28:30, [Call, 2026-05-12]: "The board takes these things up," which names the board as the body that decides). It also asks how to help (33:00, [Call, 2026-05-12]: "What would you need from us to put this in front of the board?"). That question asks what the rep can supply to move the decision, which is the test. It also shares competitor intelligence (17:05, [Call, 2026-05-12]: "We started moving plots into Oldgate and stopped." That move is not in the CRM).

Competitive Intel Summary: Current solution: Oldgate Ledger Pro, direct software ([CRM]). Contract: renewal in March 2027 ([CRM]). Satisfaction: not stated on this call ([Unknown]). The gap: the move into Oldgate began and stopped (17:05, [Call, 2026-05-12]), and the cost of the stop was not asked. The probe that went unasked is what the move cost.

Deal Health Impact: Before this call: [Unknown], because no Deal Pulse (08) exists for this account in the records. After this call: the Stage 2 to 3 gate in the profile needs the records problem quantified (plots, hours or dollars) and the GM named as the likely economic buyer. Ruth is named as GM and buyer ([CRM]). The problem is not yet quantified, so the gate is not met, and this call does not move the deal to a demo.

Focus Area For Next Call: Priority Ladder to Level 3 on the cost of a plot lookup and on the cost of the paper records, with the section F double sale inside the paper-records cost. The stage gate it serves is "Records problem quantified (plots, hours or dollars)." The chair and the date are success criteria in the game plan, not a second focus.

Next Call Game Plan:

• Prep: the plot-lookup count and the minutes per lookup, and the cost of the section F double sale, from the discovery notes.
• Questions: "How many plot requests come in a week, and how long does each one take?" Then the board question.
• Success Criteria: a number for lookups per week, minutes per lookup, and what the section F double sale cost, the board chair's name, and the meeting date, set before the session ends.

Hand-off (read by 08, 09 and 06):
account: Brackhaven Memorial Gardens (ACTIVE, Stage 2 Discovery)
run_date: 2026-05-12 (illustrative)
call_score: 24 of 35, scored 7 of 7
category_scores: Pre-Call Preparation 4, SPIN Discovery Quality 3, Priority Ladder Execution 3, Active Listening 4, Value Articulation 3, Next Steps and Momentum 3, Alternatives 4
focus_area: Priority Ladder to Level 3 on the cost of a plot lookup and on the cost of the paper records, with the section F double sale inside the paper-records cost
coaching_points: Top 3 Strengths: 1 Strength, Strong (02:10). 2 Owen followed up, Strong (09:15). 3 Owen asked why the move stopped, Strong (17:05). Top 3 Improvements: 1 Quantify the double sale, Strong (14:20). 2 Benchmark for the tablet objection, Moderate (23:40). 3 The board question and the close, Strong, with a Weak part (28:30, no date in the transcript)
key_moments: discovery breakthrough (14:20), buying signal captured (09:15), objection (23:40), competitive intelligence (17:05), missed opportunity (28:30), commitment (28:30), buying signal missed, approval (33:00), red flag MEDIUM (31:10)
champion_status: Strong, three of seven shared tests met on this call (explains the internal politics at 28:30, asks how to help at 33:00, shares competitor intelligence at 17:05)
next_action: Owen Pruitt answers Ruth Ellery's 33:00 question about what the rep needs from her side to put it before the board, and in the same message asks her for the family board chair's name, the date the board takes up the decision, the date she will check with the board, and who on her side would own the technical set-up, since the call records no IT person, by 2026-05-19. The 28:30 ask and the 33:00 question are open exchanges with the buyer, her check date is a commitment left undated, and the IT question is a red flag's recovery that is an ask to her, due on the default date, so all of them travel together. The date is the five-business-day date from the run date, since the records hold no earlier date. Owner: Owen Pruitt. Person: Ruth Ellery. Date: 2026-05-19. Later steps, in order: (1) The second discovery session, which no one has dated, so it is a proposal and not part of the message. (2) The focus-area practice, quantifying the lookup cost and the paper-records cost before that session, which is coaching for the rep and not a buyer step.
report_path: none (inline)

---

Example 2: Discovery Call (Second Discovery Booked, Not A Demo), Sable Fork Cemetery

Context: Sable Fork Cemetery is one site with 2,900 plots. Its plot list lives in a spreadsheet ([Notes], illustrative). The account is INBOUND ([CRM]): it requested a demo through the website form on 2026-10-15 ([CRM]). Who filled in the form is [Unknown]. Its verdict is MANUAL REVIEW, with Zone 3 HIGH as the only HIGH zone ([Inferred], from the zone scores in Account Qualification). The General Manager, Arlen Biggs, signs under $25K ([CRM]). The BDR replied to the form on the afternoon of 2026-10-19 and booked this discovery call for Thursday 2026-10-22 ([CRM]). Owen Pruitt (Account Executive, illustrative assignment) ran the call on 2026-10-22 ([Call, 2026-10-22]). The call was graded from its transcript, so every [Call] tag is that call.

Input: "Coach the discovery call for Sable Fork Cemetery. call_type = discovery"

Scoring:

Assessment: Good, in the 24 to 30 band of the restated scale. The Pre-Call Preparation score is 4 because a prep-sheet question the rep used on the call counts as referenced account research.

Question Review (Discovery):

Key Moments:

• Discovery Breakthrough (18:30): Arlen: "I do most of the lookups myself." [Call, 2026-10-22]. Priority Ladder Level 2.
• Missed Opportunity (18:45): Owen did not ask how many lookups happen in a week or how long each takes. The question that should have followed is the discovery question in (profile: Core Pain Points), "What does a 20-minute lookup cost you, versus 20 seconds?"
• Buying Signal, Captured (33:10): Arlen asked how long setup takes. Owen answered that go-live is in about six weeks ([Call, 2026-10-22], profile: Value Propositions). Captured.
• Competitive Intelligence (09:20): The current process is a spreadsheet ([Call, 2026-10-22]). Incumbent type: manual process. Contract status: none.
• Commitment (40:20): Arlen agreed to a second discovery session with Owen on 2026-10-29 (illustrative). Attendees: Arlen only. Owner: Owen.
• Red Flag, MEDIUM (44:00): Arlen: "Nobody else looks at the list." [Call, 2026-10-22]. One person holds the data. Recovery: ask who else needs the list, by role.

Coaching Points:

1. Strength, Strong. At 06:40 Owen asked, "Where does the plot list live, and who updates it?" [Call, 2026-10-22]. Keep the question.
2. Count The Lookups, Strong. At 18:30 Arlen said, "I do most of the lookups myself" ([Call, 2026-10-22]). Owen moved to the next topic at 18:45 without a count. Practice: "How many lookups does a typical week include, and how long does each one take?"
3. Name A Proof Point Without A Number, Moderate. At 29:00 Owen said other cemeteries have the same problem. The notes paraphrase the reply, so the grade is Moderate.
   • Situation: the lookup problem, 29:00 ([Call, 2026-10-22]).
   • Proof Point: Fennick Gardens, 212 unsold plots found in 90 days (profile: Proof Points). Status Illustrative, do not cite. The rep uses the Benchmark instead: "most cemeteries your size carry 50 to 100 plots that are sold on paper and unsold on the map" (Benchmark, [Public: deathcare research, 2026-03-27 to 2026-04-01], profile: Proof Points).
   • Coaching Moment: Say the benchmark, then ask, "How many of those do you think you have?"
4. Second Discovery, Not A Demo, Strong. At 40:20 Owen did not offer a demo. He booked a second discovery session: "I'd like to see the list before I show you anything" ([Call, 2026-10-22]). Keep this. It is the right step while the pain is unconfirmed.
5. Who Else Holds The List, Weak. After Arlen said, "Nobody else looks at the list" (44:00), Owen did not ask who else needs it. Inferred from the question that did not come, so the grade is Weak. Practice: ask who else needs the list, by role.

Champion Status: Developing. Two of seven shared champion tests met on this call, each tagged: shares competitor intelligence (09:20, [Call, 2026-10-22]: the plot list is kept in a spreadsheet, the manual process incumbent, which the CRM does not hold), and commits to a next step with a date (40:20, [Call, 2026-10-22]).

Deal Health Impact: Sable Fork is INBOUND. It stays INBOUND after this call, because no deal is open (the status rule in Step 8), so no ACTIVE stage gate applies yet. The pain is not confirmed: the lookup count is missing. The next step is a second discovery session, not a demo. The verdict stays MANUAL REVIEW.

Focus Area For Next Call: Priority Ladder, to count the plot lookups and time them, the one cost the evidence line names. The stage gate it serves is "Records problem quantified (plots, hours or dollars)." The who-else question stays a coaching point, not the focus.

Next Call Game Plan:

• Prep: the spreadsheet's owner and update rhythm, and the form filler's name if the website shows it.
• Questions: the count question, then the who-else question. Then the Need-Payoff question.
• Success Criteria: a number for lookups per week, minutes per lookup, and the name of anyone else who needs the list.

Hand-off (read by 08, 09 and 06):
account: Sable Fork Cemetery (INBOUND)
run_date: 2026-10-23 (illustrative)
call_score: 24 of 35, scored 7 of 7
category_scores: Pre-Call Preparation 4, SPIN Discovery Quality 3, Priority Ladder Execution 3, Active Listening 4, Value Articulation 3, Next Steps and Momentum 4, Alternatives 3
focus_area: Priority Ladder, count the plot lookups and time them (stage gate: records problem quantified)
coaching_points: 1 Strength, Strong (06:40). 2 Count the lookups, Strong (18:30). 3 Proof point without a number, Moderate (29:00). 4 Second discovery, not a demo, Strong (40:20). 5 Who else holds the list, Weak (no question in the transcript)
key_moments: discovery breakthrough (18:30), missed opportunity (18:45), buying signal captured (33:10), competitive intelligence (09:20), commitment (40:20), red flag MEDIUM (44:00)
champion_status: Developing, two of seven shared tests met on this call (shares competitor intelligence, commits to a next step with a date)
next_action: Owen Pruitt holds a second discovery session with Arlen Biggs to count the lookups and time them. No demo until the pain is confirmed. Owner: Owen Pruitt. Date: 2026-10-29, the session Arlen Biggs agreed to on the call (`[Call, 2026-10-22]`), which is earlier than the five-business-day date of 2026-10-30. Later steps, in order: (1) Who else needs the list, by role, a red flag's recovery step (MEDIUM, 44:00), an ask to Arlen Biggs due on the default date, 2026-10-30, after the next action's date. (2) The focus-area practice, counting and timing the lookups before the session, which is coaching for the rep and not a buyer step.
report_path: none (inline)

---

Example 3: Demo Call (Needs Improvement, Non-Success), Brackhaven Memorial Gardens

Context: Owen Pruitt (Account Executive, illustrative assignment) demoed to Walt Okonkwo, Operations Director, and two operations staff at Brackhaven Memorial Gardens ([CRM]). Ruth Ellery, the General Manager and champion, was not in the room. The deal is ACTIVE at Stage 3 Demo on the call date ([CRM], illustrative). In discovery, Walt said he is skeptical of tablets ([Call, 2026-05-12]). This is the non-success case: the call did not answer the one objection that mattered to the room. The source is the call transcript (illustrative). The call date is 2026-08-20 (illustrative), and the call length is 60 minutes (illustrative).

Input: "Coach the demo for Brackhaven Memorial Gardens. call_type = demo"

Scoring:

Assessment: Poor, in the 10 to 17 band of the demo scale (feature touring or monologue).

Pacing By Section (Step 7):

Per-Attendee Blocks:

• Attendee: Walt Okonkwo, Operations Director. Buying role: influencer ([CRM]). Pain they own: paper work orders, and finding the plot in seconds (profile: Buyer Personas). Question they asked: two questions, both about tablets, and no question about the plot lookup ([Call, 2026-08-20]). What they need to see: the plot found in seconds, on their own records. Engagement: active on the tablet question, silent on the lookup.
• Attendee: Two Operations Staff, Names [Unknown]. Buying role: [Unknown]. Pain they own: [Unknown]. The transcript does not label them, so their engagement is Unknown.

Technical Checklist:

1. Screen share and audio tested before the start: Unknown. Neither the notes nor the transcript show it.
2. Every attendee's access confirmed: Unknown.
3. The data shown was the prospect's own: No. Owen said at 12:00, "this is our sample cemetery" ([Call, 2026-08-20]).
4. Backup ready if the screen failed: Unknown.
5. Attendee names matched the invitation: Partly. Walt's name matched. The two staff names are [Unknown].

Return On Investment: No return-on-investment section ran. The call gave no inputs, so no formula was filled. Use your own figures, no defaults.

Key Moments:

• Objection (23:40): Walt: "I don't believe tablets will hold up out there." [Call, 2026-08-20]. Type: skepticism. Response given: a reassurance, "They're rugged, you'll like them." Not captured.
• Missed Opportunity (12:00 Onward): the paper work-order pain was never raised. The question that should have been asked: "Walk me through what a work order looks like on paper, from the counter to the crew."
• Competitive Intelligence (31:15): Walt said the ledger runs on Oldgate [Call, 2026-08-20]. Incumbent type: direct software. Renewal March 2027 ([CRM]).
• Red Flag, HIGH (55:00): No one in the room can approve the purchase. The economic buyer is the family board chair ([CRM]), name [Unknown]. Recovery: Ruth briefs Walt on the board's approval path before the next session.

Coaching Points:

1. Telling, Not Asking, Strong. At 23:40 Walt said, "I don't believe tablets will hold up out there." Owen replied, "They're rugged, you'll like them" ([Call, 2026-08-20]). That is the Telling Not Asking anti-pattern.
   • Situation: Walt's skepticism, 23:40 ([Call, 2026-08-20]).
   • Proof Point: the profile has no proof on tablet durability. Say so, and do not borrow a number.
   • Coaching Moment: Acknowledge ("That makes sense."), then ask, "What would need to be true about the tablets for your crew to use them?"
2. Open On The Pain, Strong. At 12:00 Owen opened on the trust report, then the mobile app, in menu order ([Call, 2026-08-20]). Walt's pain never came up. Open with the pain the discovery call named, when Ruth described the plot lookups (21:30, [Call, 2026-05-12], her words not on record). Name that pain before the first workflow, in the rep's own words: "In discovery we talked about how long a plot lookup takes. I'll show you that first."
3. Pain-To-Workflow Map, Weak. Walt's "zero wrong-plot burials" and "find the plot in seconds" are not in the transcript at any point. Inferred from what did not happen, so the grade is Weak. Practice: build the map from the discovery notes before the next demo.
4. Question The Problem, Moderate. The transcript shows no Prime Pain before any workflow. The first 20 minutes are summarized in the rep's notes, so the grade is Moderate.

Champion Status: None on this call. Ruth Ellery was not in the room, so no shared champion test that needs the room could be met. Walt is an influencer ([CRM]).

Deal Health Impact: The call did not answer the tablet objection, which is the one that matters to the room. The buyer with the authority is the board chair ([CRM]), whom this call did not reach. The next session needs the approval path, not another feature tour.

Focus Area For Next Call: Pain Alignment and Proof, the lowest score on this call. Name Walt's paper work-order pain before the first workflow, and tie each workflow to a pain.

Next Call Game Plan:

• Prep: the pain-to-workflow map, the approval path from Ruth, and a backup plan for the screen.
• Questions: "What would need to be true about the tablets for your crew to use them?" Then the Prime Pain question before each workflow.
• Success Criteria: Walt names the pain in his own words, and the next step has an owner and a date.

Hand-off (read by 08, 09 and 06):
account: Brackhaven Memorial Gardens (ACTIVE, Stage 3 Demo)
run_date: 2026-08-20 (illustrative)
call_score: 17 of 40, scored 8 of 8
category_scores: Meeting Opening 2, Meeting Closing 2, Teach and Tailor 3, Pain Alignment and Proof 1, Question The Problem 2, Pain-To-Workflow Mapping 2, Prospect Engagement 2, Resistance Handling 3
focus_area: Pain Alignment and Proof, name Walt's paper work-order pain before the first workflow and tie each workflow to a pain
coaching_points: 1 Telling not asking, Strong (23:40). 2 Open on the pain, Strong (12:00). 3 Pain-to-workflow map, Weak (absent from the transcript). 4 Question The Problem, Moderate (summarized in notes)
key_moments: objection (23:40), missed opportunity (12:00), competitive intelligence (31:15), red flag HIGH (55:00)
champion_status: None on this call (Ruth Ellery not in the room)
next_action: Owen Pruitt asks Walt Okonkwo, in one message, for a date for the next session and for Ruth Ellery to join it. The call closed with "Any questions?" and set no step, so this is the next step the call never set, asked of the senior buyer on the call. Owner: Owen Pruitt. Person: Walt Okonkwo. Date: 2026-08-27 (illustrative), five business days after the run date of 2026-08-20, with no earlier date on the record. Later steps, in order: (1) Ruth Ellery briefs Walt on the board's approval path, a red flag's recovery step (HIGH, 55:00), for a different person from the next action's, so it is a later step. (2) The focus-area practice, building the pain-to-workflow map from the discovery notes before the next demo, which is coaching for the rep and not a buyer step
report_path: none (inline)

---

Common Patterns

The Discovery That Stops At Level 2. The rep hears the pain and moves to the solution before anyone has counted it. Score it under Priority Ladder, quote the moment, and practice the count and the time.

The Warm Contact Who Meets No Test. The contact is friendly and helpful and meets none of the shared champion tests. Grade the champion status by the tests, not by tone. A friendly contact is not a champion.

The Reassurance To A Skeptic. A buyer raises a doubt and the rep answers with more reassurance or another feature. Diagnose the resistance type first, then use the Three-Step Turnaround. Score it under Resistance Handling.

The Call That Ends With "I'll Send Info". No owner, no date, no attendees. Score Next Steps at 3 or below, and write the next action with its owner and date before the call ends.

---

Troubleshooting

"No Transcript Available (Only Rep Notes)"

Likely Cause: The call was not recorded, or no transcript was made. Solution: Coach from notes and flag the reduced confidence: "Coaching based on rep notes only. Talk share, listening technique and exact language are Unknown. Coaching points rest on notes are graded Moderate at most."

"Prospect Talk Time Is Missing From The Transcript"

Likely Cause: The transcript has no speaker labels, or more than two people spoke. Solution: Do not guess a score. Ask for the labelled transcript and re-run, or score the category from the evidence that is present and say in the evidence line which part was scored.

"Rep Scored Well But Deal Isn't Progressing"

Likely Cause: Good methodology on the call does not fix a deal with no champion or no budget path. Solution: Good methodology execution doesn't guarantee deal progression if the fundamentals aren't there. Run gtm-deal-pulse to check if the deal has structural issues (no champion, no budget path) that call quality alone can't fix.

"Call Was A Hybrid (Started As Discovery, Turned Into Demo)"

Likely Cause: The rep moved to the demo before the discovery pains and the Priority Ladder were complete. Solution: Score as discovery (primary type). Note the demo elements that occurred, and flag the methodology risk: "Demoing before completing Priority Ladder reduces future negotiation leverage. Recommend completing discovery framework before next demo."

---

Best Practices

Do's

• Quote Or Paraphrase Specific Moments: "At 12:30, when the prospect said X, the rep should have..."
• Reference Exact Frameworks: "Use Priority Ladder Stage 3," not "ask better questions"
• Balance Praise And Improvement: 3 strengths plus 3 improvements minimum
• Make Coaching Actionable: include specific language the rep can practice
• Grade Every Point: a quote with its time, or Moderate or Weak with the reason

Do Not's

• Do Not Score Without Evidence: "seemed good" is not a score justification
• Do Not Give Generic Advice: every recommendation must tie to a specific framework
• Do Not Coach On Everything At Once: pick the #1 focus area for the next call
• Do Not Skip The Game Plan: coaching without a practice plan does not change behavior

---

Integration With Other Skills

Reads From The Skills Before It, By Field Name. A missing field is reported as missing, not rebuilt here.

• Meeting Prep (06): prep_sheet, top_pain, question_bank, attendees (with buying role), proof_point. This skill grades the call against question_bank and top_pain, and checks the proof point the rep used against proof_point.
• Deal Pulse (08): health_score, risk_level, pillar_scores, signal_scores, next_actions. Read only for the before and after comparison in Deal Health Impact.

Hands To The Skills After It, By Field Name.

• Deal Pulse (08), MEDDPICC Analysis (09) And Meeting Prep (06): call_score, category_scores, focus_area, coaching_points, key_moments, champion_status. Deal Pulse re-scores its signals with champion_status and key_moments. MEDDPICC Analysis uses the coaching points as evidence for its coverage grades.
• Wrap-Up (O10): report_path (set only when a file was written), next_action (owner and date).

Related Skills. Meeting Prep before the call to plan it, then this skill after the call to score execution, then Deal Pulse to re-score the deal with what the call showed.

Chains

• Work The Deal: Meeting Prep (06), Call Coaching (13), Deal Pulse (08), MEDDPICC Analysis (09), Stakeholder Mapping (10). This skill adds the scored read of how the call was run, with the champion status and key moments the other skills take by name.

Guild Pro Kits (Optional)

The Business Case & ROI Kit (a paid Guild Pro kit) reads this skill's hand-off block by field name. This skill is free and works without any kit. The kit reads champion_status from this skill. It also reads what the call said about ROI, which this skill records in its return-on-investment check in Step 7. This skill never fills a formula from the call, and every ROI input comes from the buyer, with its source. The field the kit reads from this skill:

• champion_status

---

Changelog

2.1.17 (2026-10-27)

• The local next-action paragraph now says an undated ask to the same buyer travels, as the shared rule does. Example 1's next action is on the default date, so its message is unchanged.
• The shared contract now says an ask to the next action's person with no date of its own travels with the next action, and defines the champion test "explains the internal politics" (the contact tells the rep who decides, or how the decision gets made).

2.1.16 (2026-10-27)

• The shared contract's Champion Tests section now defines "commits to next steps with dates": the contact agrees, on record, to a dated next step in the deal, such as a meeting they book or a date they commit to on a call.
• The shared contract's next-action rule now says which asks travel with the next action: every ask to the same person due on or before its date, counts and figures included, and never a document the person must draft first or an ask due later.
• Bundle readings. "Fits One Message" is now "Due On Or Before The Date": an ask travels by its date, and a count, a figure or a date the buyer must look up travels with it. Only a document the buyer would have to draft or research first, and an ask due after the next action's date, stay out.
• Documents the buyer holds travel under the same due-date test. A document the buyer would have to draft first is a later step.
• A red flag's recovery is an ask like any other. It travels with the next action when it is an ask to the same person due on or before that date, and it is a later step for another person or a later date. Example 1's IT question now travels with the next action, and Example 2 and Example 3 state why their red flag recoveries are later steps.
• Board's written criteria. Nothing on the call or in the records produces that ask, so it is removed from Example 1 and from the try-it promise. The records state that the criteria were not stated on the call.
• Try-it. The promised call score reads "24 of 35, scored 7 of 7", as the Output Contract requires.

2.1.15 (2026-10-27)

• The shared contract's Champion Tests section now defines "asks how to help" (the contact asks what the rep can supply to move the internal decision). The PlotIQ profile dates Brackhaven's deal from 2026-05-06, names the economic buyer for the Stage 2 gate the way the Buying Committee does, and limits the $25K board line claim to one-site accounts.
• Focus-area costs. The Brackhaven focus names the paper records, with the section F double sale inside that cost, and the plot lookups. "Plots missing from the map" is removed, because the call never raised it.
• Buying signals. A statement that names an approval body is not an approval signal unless it asks what the sign-off needs. Such a statement is recorded under Decision Process.
• Champion test. "Asks how to help" is met by a question about what the rep can supply to move the internal decision.
• Next action bundle. Six readings now include a document the buyer already holds, which fits one message. A document the buyer would have to draft first is a later step.
• Example 1. The key moments add the 28:30 commitment and the missed 33:00 approval signal. The 33:00 question is read as a question about what the rep needs from the buyer, in the Decision Criteria row and the next action. The next action asks for the board's written criteria if she already holds them in writing.
• No score, band or due date changes.

2.1.14 (2026-10-27)

• The shared contract's Champion Tests section now defines "creates urgency" (a dated deadline the decision works to, with its date and source on record) and "defends the solution" (a recorded case of arguing for us in our absence to someone who decides), and says a test not yet run is never scored.
• Focus-area costs. The Step 2 Priority Ladder rule says the evidence line names each Core Pain Point the call identified, at Level 1 or 2 on the Pain Discovery Map, and whether it reached Level 3. Step 8 reads the focus costs from that line. An event raised under a named pain is part of that pain's cost.
• Brackhaven focus. The cost set is the plot lookups and the paper records, with the double sale inside the paper-records cost. Example 1, the game plan and the try-it promise change to match.
• Later steps. A new reading orders them: a red flag's recovery and an undated proposal rank as kind 4, the call's items come before the email's, and the focus practice is always last. Example 1's later steps move the red flag ahead of the second session, and drop the Oldgate export holder, which the records do not hold.
• Unraised objections. A rep question the buyer answers without a date, name or figure is a fair chance, so the line is Not raised.
• Metrics. A single named event is not a figure for COVERED.
• Examples. Example 2 lists its later steps. Example 3's next action has one owner and one person, Owen asking Walt for the next date and attendees, and its approval-path brief is a later step. Example 3 no longer quotes Ruth's lookup words, which the record holds as not on record.
• No score, band or due date changes.

2.1.13 (2026-10-26)

• Next action bundle. Four readings are now written under the Next-Action Priority Order. An ask fits one message when the buyer can answer it in one reply from what they know. A buyer's open question with no reply on record is answered in the same message as the asks to that buyer. A session nobody has dated is a proposal and a later step. A red flag's recovery step is a later step.
• Focus area. The costs for the focus practice are the pains that the focus category's own evidence line names, each left unquantified.
• Example 1 and the try-it. The next action answers the 33:00 question and asks the chair and the board dates in one message to Ruth Ellery, dated 2026-05-19. The undated second session and the IT and export question are later steps. No score, band or due date changes.
• Try-it record. Three rubric results are removed from the record's facts: the silence verdict, the cost verdict and the verdict on the last two minutes. The record states the longest timed pause instead.

2.1.12 (2026-10-26)

• Next action. The Output Contract row and the Next-Action Priority Order give the order: an open exchange with a buyer from the call, a buyer's commitment left undated, a buyer-facing step with its date on record, a next step the call never set, then the focus-area practice as a later step. Same-buyer asks that fit one message travel with the next action.
• Run date. The records' date for today governs. Without one, the call date does.
• Satisfaction. An indirect signal, such as a move that started and stopped, stays Unknown until the buyer states how they feel.
• Red flags. A risk level is HIGH when the flag blocks a dated step or a gate criterion, MEDIUM when it names a missing role and blocks nothing, LOW otherwise.
• Implementation. A buyer's statement that they lack a role the change needs counts as raised.
• Champion. The politics test is met by one clear statement that names who decides or how the decision moves.
• Question review. Ratings have written criteria: Strong, Adequate, Weak and Missing, each with one test.
• SPIN. A phase is well executed when the rep asked an open question that serves its purpose and the buyer answered with a specific fact.
• Pain depth. A pain whose words are not on record is entered provisionally, and the gap is named.
• Example 1 and the try-it. The next action is the open exchange: the board chair's name and the date the board takes up the decision, asked of Ruth Ellery by 2026-05-19. The second session is proposed in the same message. The focus-area practice is a later step.

2.1.11 (2026-10-26)

• Focus area. The focus is the lowest-scoring category. A tie goes to the category whose step does the work of the exit criterion from the account's current stage, read from the row that starts at that stage, with the first row for an account that has no stage. Each focus-area line quotes the criterion. Example 1 quotes "Records problem quantified", which the tie-break gives to Priority Ladder. Example 2 is now Priority Ladder, and Example 3 is now Pain Alignment and Proof, the lowest score. Each names one focus area.
• Value Articulation. A capability tied in general terms to one described pain scores 3, and a feature list with no described pain scores 2.
• Active Listening. Silence counts as used at a pause of two seconds or more after a prospect's answer, so Example 1 scores 4.
• Champion. The politics test is met when the statement names who decides, and "The board takes these things up" names the board. Example 1 meets three tests and is Strong. The defend test needs a statement made when we were not in the room.
• Objections. An objection is typed by what the objector resists, so Example 1's objection to tablets is inertia.
• Silence and missing markers. On a full transcript a missing marker scores the line below it. A category is INSUFFICIENT only when the source cannot show it.
• Try-it. The records state facts only. The cost line and the champion count are restated as facts, and the focus line quotes its stage gate.

2.1.8 (2026-10-26)

• Round 8 citation and status pass. Every profile citation is now written (profile: Section). The research benchmark keeps its public source tag.
• Deal Health Impact has a status rule. ACTIVE reads the stage gate. ENGAGED applies no gate and names whether the call gave the buyer a reason to open a deal. INBOUND stays INBOUND after a call until a deal opens. Any other status applies no gate. Step 1 reads the account status so the rule has its input.
• Step 3 points to the one definition of shares competitor intelligence in The Shared Contract instead of restating it. Under that definition, a named manual process that the CRM does not hold counts as the incumbent, so one example's champion count is rechecked on it.
• Headings and labels are capitalized word by word. Question The Problem and Pain-To-Workflow follow the same rule.

2.1.7 (2026-10-26)

• Round 7 scrub. The rules no longer carry a worked count, a quoted record phrase or a worked focus answer. Each states the general test: the focus-area tie-break names the exit criterion of the next stage, the champion test about the buyer's process names who decides, and the minute figure is written as "N of L minutes".
• The Next Steps rubric says what the rep's ask decides between 2 and 3, so the same call gets the same score every time.
• The competitor-intelligence champion test is applied to a named incumbent the contact describes, and the rule says what the rep already holds from the CRM does not count.
• The example's next action takes the shared rule's date when the record holds no agreed date. The try-it record states facts only.
• The to-try pointer names the try-it record's inputs without naming an example.

2.1.6 (2026-10-26)

• The discovery example's Pre-Call Preparation scores the rep's use of a prep-sheet question, as the rubric's own rule says, and its total and band are recomputed from the rows.
• The discovery example's record states the booking that set its call date. The call is dated from its transcript, and the second session is dated to the one agreed on the call.
• The demo example is dated to the Stage 3 demo, which precedes the account's later negotiation stage. Its Pain Alignment and Proof row scores the rubric's no-pain line, and its Prospect Engagement row scores the band's distance from the demo floor. The total and the band are recomputed once from the rows.
• Call-sourced facts carry their call dates. Every bare [Call] fact tag in the examples and the try-it record now names the date of its call: Example 1 and the try-it record on 2026-05-12, Example 2 on 2026-10-22, and Example 3 on 2026-08-20, with its discovery reference dated 2026-05-12.

2.1.5 (2026-10-26)

• The next action follows the family's one deadline rule. The Output Contract and the Quality Bar point to that rule, and a date agreed on the call or by email is still the step's date.
• The examples' next actions carry the dates the rule gives.

2.1.4 (2026-10-26)

• Try-it fixes from the blind retest. The Partial Markers rule now says whether a lower-line marker blocks a higher score. The Pre-Call Preparation rule says which prep-sheet facts count. Buying signals gain approval and need kinds. The next action takes a date agreed after the call, and an agreed session is written with its date. The practice exercise covers every cost the focus skill names, and the focus tie-break gives the reason its gate names the skill. The try-it records carry the full transcript check for silence and talk share.

2.1.3 (2026-10-26)

• Try-it evidence completed so a strict first run reproduces Example 1. The records now carry the agenda, the titles, a restatement and the alternatives question, so Pre-Call Preparation scores 4 on its three markers and Active Listening and Alternatives score on what was said. Five sentences settle the open judgments: the partial-markers rule, the Winning Zone, the post-call date, the champion test about process, and the focus-area tie-break. Deal Health Impact states its before read, and the try-it notes that its records predate the account's later stage.

2.1.2 (2026-10-25)

• Try-it evidence completed so a strict first run reproduces Example 1. The Unknown Rule is added: a category with no evidence is INSUFFICIENT and is left out of the total, the total reads scored n of N, and fewer than five scored categories gives no overall score. Example 1 now shows the eight report sections, Top 3 Strengths and Top 3 Improvement Areas, and one focus area.

2.1.1 (2026-10-25)

• Adds examples/try-it.md so a first run reproduces Example 1.

2.1.0 (2026-10-25)

• Reads the Context OS base (the account's folder under accounts/, and the personas under people/) and offers read-only call-recorder and CRM connectors through the shared contract's Knowledge Base and Connectors section, before the call is read.
• Adds a Chains subsection placing the skill in the Work The Deal chain.
• Adds a Guild Pro Kits subsection naming the hand-off field the Business Case & ROI Kit reads, and how the kit's ROI read stays tied to the buyer's own figures.

2.0.0 (2026-10-20)

• Moved to the Sales 2.0 standard: Overview with Core Principle, Why This Skill Exists, Role, Input and Output Contracts, Context with the Shared Contract, Core Workflow with a Produces line per step, Epistemic Rules, Hard Rules with reasons, Quality Bar, and hand-off fields named in the Output Contract and the Integration section.
• Discovery adds an Alternatives category. Discovery is now 7 categories out of 35 (was 6 out of 30). The bands are restated for 35, with the arithmetic shown in Step 2.
• Step 4 uses the profile's "What to Listen For" column as the phrase list. Coaching points use the Situation, Proof point and Coaching moment template. A one-line negative-frame close is added.
• Demo adds five demo elements mapped onto the demo categories, the half rule, pacing defaults by element, return on investment formulas with blank inputs, a per-attendee block, and a five-line technical checklist.
• The shared champion tests, incumbent types and talk-time bands are referred to in The Shared Contract, not restated. Talk-time rubric lines are read against that band.
• Discovery adds a per-phase question review. Every call adds a six-line unraised objections checklist. Seven key-moment types each capture their fields. Every coaching point carries an evidence grade: Strong, Moderate or Weak.
• The eight anti-patterns each have a one-line definition. The Document Sections list becomes Report Sections, with its stray parentheses removed. The artifact section is removed: the file is Markdown, written only when asked.
• Examples: the Brackhaven Stage 2 Discovery call is graded, as the call Meeting Prep prepared. The Sable Fork call ends with a second discovery session booked, not a demo. The Brackhaven demo is kept with the new fields. Every fact carries one of the six evidence tags.
• Not in this version: trend analysis across calls, the eight-dimension transcript scorecard, cold-call and email coaching, and the system initialization blocks. The prep templates belong to Meeting Prep (06).

1.3.0 (2026-10-13)

• Examples re-cast on PlotIQ, the library's one example company. Example arithmetic and listed errors fixed, and a non-success example added.

1.2.1 (2026-10-13)

• Two framework names replaced with plain descriptions: "Question The Problem" and "Priority Ladder". The methods are unchanged.
• The demo meeting open and close rewritten as a generic structure, replacing an internal framework.

1.2.0 (2026-09-29)

• Worked examples rewritten around a single example case study.
• Em dashes removed from prose.

1.1.0 (2026-07-06)

• Restructured around the five-part skill anatomy: Role, Input Contract, Output Contract, Context, Methodology.
• Client-specific data de-embedded: the skill now reads the shared client profile instead of carrying a copy-in block.
• Framework machinery moved to an explicit Methodology section. No functional changes to the workflow, scoring rubrics, or coaching recommendations.

1.0.0 (2026-03-04)

• Initial release. Merged from two coaching skills.
• Unified via a call type parameter: discovery (6 categories, out of 30) and demo (8 categories, out of 40).
• Generalized via the client profile with configurable defaults.
• Added demo-specific checks: Challenger, the demo meeting open and close, Question The Problem, the Five Implementation Habits, and anti-pattern detection.