← Contents04 / 20

Module 4 — Methodology: Picking a Religion and Enforcing It

"A methodology is just a checklist a guru sold you for $40,000. The checklist still works. That's the part that should scare you." — my attorney, reviewing an invoice he did not approve, correctly.

It's somewhere past 3 a.m. and a man named Chip Brennan is on my screen telling forty thousand LinkedIn followers that "in 2026, qualification is dead." Behind him: a rented Lamborghini, a slide deck with the kerning of a ransom note, and the absolute diamond-hard confidence of a man who has never personally closed a six-figure enterprise deal under threat of a board meeting. He is wrong, of course — qualification is not dead, qualification is the only goddamn thing keeping his audience's pipelines from being a landfill of polite "maybes" and "sounds interesting, let's keep chatting." But here is the savage truth he's circling and monetizing at a markup: it does not matter which religion you pick. What matters is that you pick exactly ONE, write it into the CRM as structural law, burn the freelancers who deviate, and inspect against it until your reps dream about it. Five methodologies whispered at an offsite and then quietly abandoned will lose to one enforced mediocre framework, every quarter, forever. Consistency is the alpha. Enforcement is the sermon. Pick a god. Make them all fucking kneel.

THE JOB

A sales methodology is a shared language and a repeatable, inspectable checklist for answering one question on every deal: is this real, and what the hell do I do next to advance it? It standardizes how reps qualify prospects, what counts as a stage exit, and what "good discovery" means — so that a deal in Maria's pipeline means the same goddamn thing as a deal in Dave's, so the forecast isn't a collaborative fiction exercise that would embarrass a Magic 8-Ball, and so coaching has something real to grab onto beyond "do better, you're disappointing me." Without a methodology, every rep runs a private religion, the pipeline is a Tower of Babel built by people who don't speak the same language and don't know it, and your forecast is vibes wearing a necktie to a board meeting where people can fire you.

The CRM — that vengeful basement god, that insatiable data altar, that digital confessional booth where reps go to lie about their pipeline — demands to be fed structured, consistent deal information. Feed it garbage from five incompatible frameworks and it spits back garbage reports, a garbage forecast, and a garbage reason to miss plan in front of people who flew in from somewhere it wasn't raining. Feed it one enforced framework and it becomes, briefly, something approaching useful. This is the only miracle available to you. It's a shit miracle. Accept it anyway.

THE PLAYBOOK: THE MAJOR RELIGIONS, SPELLED OUT

MEDDIC / MEDDPICC — the enterprise gold standard, and the one framework worth tattooing on your reps if tattooing weren't a liability.

The dominant methodology for complex, multi-stakeholder deals. Not a stage gate — a scorecard. Every letter is something you must know and have documented evidence for. Opinions don't count. Feelings don't count. "I think they have budget" is worth exactly nothing when the deal dies in procurement and your quarter goes with it. Write it down or it didn't happen — the CRM doesn't give a damn about your gut.

  • M — Metrics. The quantified economic impact, in their currency, their math, their fiscal year. Not "improve efficiency" — "cut onboarding from 14 days to 3, worth $1.2M annually at their volume, confirmed by the VP of Operations on a recorded call." If you cannot state the number — a specific, defensible, buyer-verified number — you do not have a business case. You have a brochure. Brochures don't close. Brochures get filed and forgotten. If your rep can't give you the Metrics in thirty seconds, you have a science project masquerading as a deal, and you need to stop forecasting it as a real thing before you embarrass yourself in front of someone who matters.

  • E — Economic Buyer. The single person with discretionary authority to say yes and release the budget — not your champion, not the VP who likes your demo, not the enthusiastic Director who sends you Slack messages at all hours. The EB. Have you met them? Does your rep know their name and title and what they actually care about? If the answer is "we haven't gotten there yet" in week six of a deal, that is a fucking alarm, not a to-do item.

  • D — Decision Criteria. The formal checklist — technical requirements, business requirements, relationship factors, political considerations, and whatever other bullshit they've packaged into an RFP — that the buyer will use to judge you against the alternatives. If you're not actively shaping these criteria early in the deal, the competitor who showed up before you is shaping them against you, and you're walking into a beauty contest whose judge has already picked the winner. Get in the room. Shape the damn criteria. Win or lose on your own terms.

  • D — Decision Process. The actual sequence of events, approvals, signatories, and dates between "we like you" and a fully executed contract with cash moving in your direction. Legal review. Security review. Procurement. Executive sign-off. Finance approval. Who has to bless this thing and in what order? The deal your rep describes as "just waiting on signature" — and then it sits undead in your forecast for six weeks while you tell the board it's "in legal" — died right here in this stage, of a Process that was never mapped. Nail this letter or get surprised at the worst possible time. The board does not enjoy surprises.

  • P — Paper Process. (The second P; MEDDPICC's most underestimated letter.) The specific contracting and legal gauntlet that exists entirely separate from the business decision. Who drafts the MSA? Which party's paper do you use? Are there redlines from legal that require executive escalation? Who in procurement owns vendor onboarding and what's their queue? The deal that "just needs signature" is the deal that meets Paper Process for the first time at the worst possible moment and slips your quarter. Map it early. Every single time.

  • I — Identify Pain. The compelling, quantified, urgent business pain driving the purchase — not a wish, not intellectual curiosity, not "someday we should probably look into this." A hurt that has a dollar figure, a deadline, and a named human being who is personally and professionally measured against fixing it. No pain means no urgency. No urgency means no budget release. No budget release means you have been running a free consulting engagement for three months and calling it a deal, you poor bastard. Identify the pain, get the number, get the sponsor, or stop forecasting it and move on.

  • C — Champion. A person inside the account with genuine power and influence who wants you to win and will spend real political capital selling internally for you when you're not in the room. The test: will they give you the decision process without being asked? Will they arrange an introduction to the Economic Buyer? Will they tell you when you're about to lose? If not, they are a Coach — someone who gives you information but has no power and no skin in the game. Coaches are useful. Coaches are not champions. Forecasting on a coach is how you hit 31% of plan and spend a lot of time on calls with the board.

  • C — Competition. Who else is in this deal — including, critically, "do nothing" and "build it internally," which win more deals than Salesforce, Hubspot, or your actual competitors combined. Know your competition, know their narrative, know where you beat them and where you don't. The competitive analysis that lives in a Notion doc nobody reads is not a competitive strategy. Know it or lose to it while confused.

MEDDPICC is not a questionnaire you run once in discovery and check off like a grocery list. It's a living, inspected scorecard that should be revisited every pipeline review without exception. Score each letter red/yellow/green on every material deal. The reds are your fucking work list. The yellows are the risk you will pretend isn't risk until it becomes a miss. The greens are the story you're currently telling yourself and the board — inspect them hardest, because the greens are where happy ears live. Inspect all three.

BANT — the classic, fast, blunt disqualifier. Born at IBM. Still useful. Also not enough by itself.

Four gates, fast to run, brutal to fail:

  • B — Budget. Do they have money allocated, accessible, and real? Not "we think we could find it." Real.
  • A — Authority. Are you talking to someone who can actually make a decision, or someone who will enthusiastically describe how decisions get made to someone else?
  • N — Need. Documented, specific pain — or curiosity?
  • T — Timeline. A compelling event with a real date, or a vague "probably H2"?

BANT is excellent for high-velocity SMB and inbound triage. Run it fast; disqualify hard; kill the tire-kickers quickly and move to the next one. What BANT absolutely cannot do is run a six-figure enterprise deal — "Budget" as a yes/no binary misses the entire Economic Buyer conversation, the business case architecture, the paper process gauntlet, and the political shitstorm that actually decides whether the money releases. Use BANT to disqualify fast in velocity motions. Do not use BANT to run enterprise and then stand in a post-mortem asking why your commit evaporated in procurement with eleven days left in the quarter. That's not the framework failing — that's you applying a sprint tool to a marathon and getting surprised by the finish line's location. BANT is a scalpel. Don't use it for surgery that needs a different instrument.

Challenger — a selling motion, not just a qualifier. This is how you sell, not just whether you should.

From The Challenger Sale (Dixon and Adamson). The research showed that the best enterprise reps aren't the relationship-builders everybody was training — they're Challengers who run a three-part motion called Teach–Tailor–Take Control, and it looked like this:

  • Teach the customer something new, surprising, and frankly uncomfortable about their own business — a Commercial Insight that reframes their problem in a direction that plays to your strength and makes the status quo look like a burning building they've been calmly rearranging furniture in. If you're teaching them something they already knew, you're not Challenging — you're pitching, and they will feel the difference, and the deal will stall. If you're teaching them something they didn't know that is actively costing them money, you're Challenging, and you've earned the next meeting.

  • Tailor that message to the specific economic and emotional reality of each individual stakeholder. The CFO has a different set of nightmares than the CIO. The VP of Engineering has different nightmares than both. One size fits nobody in an enterprise deal. Obvious to say, apparently goddamn impossible for most reps to actually execute in the room.

  • Take Control — drive the deal like you have somewhere to be. Talk about money early, because the rep who waits for the buyer to bring up budget is the rep who gets a gentle "we'll circle back" six weeks before end of quarter. Create constructive tension. Name the status quo cost. Don't be a nice, agreeable, accommodating presence who floats along on the buyer's timeline and then gets surprised when the deal "goes quiet." You are not here to be comfortable. You are here to close.

Challenger pairs with a qualification framework — it does not replace one. It is a motion, not a scorecard. Use Challenger to shape the deal and earn the right to advance it. Use MEDDPICC to know whether the deal is actually real or just feels real, which is a different and more expensive thing. They're not the same tool and you need both, you impatient bastard. Using only one is how you run a great discovery on a deal that was never going to buy.

SPIN — a discovery questioning framework, and the best one ever written. Rackham spent twelve years and thirty-five thousand sales calls on this. You should probably read the damn book.

The SPIN sequence, used in discovery calls to surface pain and build a compelling business case without pitching:

  • S — Situation questions. Current state. Context. "How do you handle X today? What does your current process look like?" Establish the landscape without boring the prospect to death. Reps spend too long here. Get in, get context, move on.

  • P — Problem questions. Surface the pain. "Where does the current process break down? What happens when X doesn't work?" Make the buyer articulate the problem in their own words. Their words are the words that will matter in the internal business case. Your words are the words of a vendor.

  • I — Implication questions. This is where SPIN makes its money, and where most reps chicken out and pivot to pitching because the silence is uncomfortable. Do not pivot. Take the problem and run it forward — make the buyer feel the downstream blast radius of what they've been tolerating. "When that breaks, what does it actually cost the team? What do people have to do manually instead? How does it show up in your numbers? What happens to your customers when it fails?" The implication is the blade. Used correctly, it does not need to be wielded — the buyer picks it up themselves and does the work. Shut up and let them.

  • N — Need-payoff questions. Let them sell themselves. "If that were solved, what would be different? What would you be able to do that you can't do now? What would that be worth?" The buyer who articulates the value of solving their own problem is a buyer who can go build an internal business case. You've just done the work of three follow-up calls in one conversation, you brilliant, patient, question-asking son of a bitch.

SPIN is the best discovery-call operating system ever constructed, and it was built on actual research, not a guru's intuition and a two-day certification program. Bolt it onto whatever primary methodology you run to force your reps to stop pitching features at minute three and start asking questions that build a real, buyer-owned business case. Reps who pitch in discovery are reps who lose to the competitor who asked better questions. Stop pitching. Start asking. The silence after a good Implication question is not failure — it's the sound of a deal advancing.

Sandler — a buyer-disqualifying, psychology-first system for reps who keep getting strung along by prospects who will never buy.

The Sandler Selling System inverts the relationship: the rep is a trusted equal, not a supplicant, and the system is built to disqualify tire-kickers rather than chase them. Core structural moves:

The Up-Front Contract — at the start of every meeting, you mutually agree to the agenda, the expected outcome, and what happens at the end: "By the close of this call, we'll both know whether it makes sense to go to a next step — if it does, here's what I'd propose; if it doesn't, that's a legitimate outcome and we'll say so." This single move eliminates the vague, cowardly "thanks, we'll be in touch!" that rots pipelines, pads stage-two deal counts, and gives reps something to forecast that has no chance of closing. Every meeting has a contract. Every meeting has a defined exit. If your rep can't tell you what the defined exit was, the meeting was a social call and a waste of everyone's goddamn calendar.

Pain–Budget–Decision qualification — three gates in the rep's order, not the buyer's order, because this is not a guided tour of the prospect's org chart: Confirm the pain is real, urgent, and owned by someone with skin in the game. Confirm the budget exists or can demonstrably be found. Understand the decision process end to end. No pain, no fucking conversation. No budget reality, no proposal — you're not writing custom SOWs for tire-kickers. No decision clarity, no timeline. Sandler reps disqualify bad deals fast and brutally, which means they have time for good ones. The average non-Sandler rep is carrying twelve zombie deals that will never close and forecasting four of them as commit. Sandler fixes this problem before it metastasizes.

No free consulting. Sandler reps do not produce detailed, custom proposals for prospects who haven't committed to a process. They do not run proof-of-concepts for buyers who haven't established urgency and authority. They do not write SOWs for companies that are gathering information. This sounds obvious. It is apparently not obvious, because your pipeline is full of deals where the rep has produced enormous amounts of work for buyers who have every intention of using it internally and never signing a goddamn thing. Sandler fixes this. Use it.

Champion vs. Economic Buyer vs. Blocker — the three roles that decide every deal, and the two you confuse most often

  • Champion: has real power AND real influence, actively wants you to win, and will spend political capital selling internally when you are literally not there. Will give you the internal decision process unprompted. Will arrange the EB meeting. Will tell you when something changed that you need to know about. The test — will they do something difficult for you? If not, you have a Coach.

  • Coach: gives you information, access, and enthusiasm, and is genuinely useful for navigating the account's org chart. Has no real power and will not — cannot — spend political capital on your behalf. Catastrophic when confused with a Champion and forecasted as one, which happens all the time, which is why pipelines are full of bullshit. The difference between a Champion and a Coach is the difference between a commit and a 31% quarter and an emergency all-hands where everyone pretends to be surprised.

  • Economic Buyer: controls the budget. Can say yes when everyone else has said no. Can say no when everyone else has said yes. The deal you "won" without ever meeting the Economic Buyer is the deal that disappears in "final approvals" at a moment that ensures maximum forecast damage. Meet the Economic Buyer or acknowledge you're forecasting a prayer.

  • Blocker: actively wants you to lose, and has their reasons, and those reasons don't matter — what matters is that they exist and they're operating while you pretend they don't. The incumbent's embedded ally who staked their reputation on the competitor. The threatened IT lead who chose the other vendor two years ago and cannot afford to be proven wrong. A procurement officer who is, for reasons that may be personal, political, historical, or simply baroque, personally opposed to your company's existence. The rival VP sponsoring your competitor because a competitive win makes their org look indispensable. Identify the Blocker early. Understand their specific motivation. Either neutralize them through your Champion or route around them at a higher level. The Blocker you never identified — the one you decided to pretend wasn't real because your Champion said "don't worry about Karen" — is the autopsy finding on the majority of your inexplicable losses. They were not inexplicable. You just never did the uncomfortable work of looking.

How to operationalize a methodology in the CRM — because a poster is not a system, and a system is not enforced until the CRM enforces it

A methodology that lives only in a PDF, a two-day offsite, and the memory of the reps who were awake for it is a $60,000 poster with excellent production values. It decorates the wall and changes nothing. You make it structural in the CRM or you make it meaningless — there is no middle ground and no partial credit. Here is how:

  1. Translate every letter into a required CRM field — not a text note, not a "see activity log," an actual structured field. MEDDPICC → actual fields: Metrics (text field with the number, required at Qualified), Economic Buyer (a contact record with the role "Economic Buyer" assigned, required at Proposal — not a rep's interpretation of who "basically" controls the budget), Pain (text field, required at Discovery exit), Champion (a contact record with the Champion role flagged, required at Qualified), Competition (multi-select, required at Proposal), Paper Process (text field, required at Commit). If the field isn't in the CRM with a requirement, the letter doesn't fucking exist. That's the rule. The field is the methodology. The methodology is the field. No field, no methodology, no matter what's in the SKO slides.

  2. Build stage gate exit criteria and enforce them in the system — not by asking the rep nicely during a 1:1, not by posting a slide at the SKO, in the actual CRM workflow that won't advance the stage without the required fields populated. Discovery → Qualified requires Pain, Metrics, and Economic Buyer contact record populated. Qualified → Proposal requires Decision Criteria, Decision Process, and Champion confirmed as a contact record. Proposal → Commit requires Paper Process and Competition documented. The stage means something when it requires documented evidence to enter. Without exit criteria, stages are vibes with numbers and the pipeline report is a work of speculative fiction. Beautiful. Useless.

  3. Add a qualification scorecard field. Roll the letters into a 0–8 score (one point per letter with documented evidence) or a red/yellow/green aggregate, surfaced on both the deal view and the pipeline report. Now you can sort your pipeline by how qualified it actually is. Now the forecast can reflect deal quality, not deal volume. Now you can walk into a forecast call and spend your time on the yellows and reds instead of the lies.

  4. Inspect against the methodology in every 1:1 and every pipeline review, out loud, in the CRM, in front of the rep. Every deal discussion runs in the language of the methodology — "Walk me through the Economic Buyer. Show me the Metrics field. Who is the Champion and what have they actually done for you this week — not what you think they'll do, what they've done?" If the rep cannot answer in the CRM with documented evidence, the deal is not real — regardless of the close date typed into that field, the stage displayed, or the rep's personal conviction about how great the relationship is. Conviction is noted. Documented evidence is what gets committed. A rep who can tell you everything about a deal verbally and nothing in the CRM has a deal that will vanish the moment they're not here to narrate it. Do not accept oral tradition as pipeline management.

  5. Make methodology adoption a coached, inspected, consequenced behavior. Reps do what's inspected, not what's expected — and if you have never once pulled up a rep's CRM and asked "where's your Champion contact record" in a 1:1, you have not inspected it. If you mention the methodology at kickoff and let it wither in the first week of January, you adopted it in name and abandoned it in practice, and the floor knows, and they're acting accordingly. If you run every pipeline review in the language of the methodology — "show me the Metrics, walk me through the Decision Process, who's the Blocker and what's the plan" — and gate stage advancement on field completion, you have a living system that compounds. One of these produces a forecast you can trust and coach against. The other produces a Salesforce org that is technically populated and profoundly full of shit. Choose before someone from the board chooses for you.

Why ONE enforced beats FIVE ignored — this is not a philosophy, it is an operational fact

Three reasons, no wiggle room:

1. Common language. Coaching, deal handoffs, and forecast calls only function when "Qualified" means the same goddamn thing to every person in the room at the same time. If Maria's qualified deal has a confirmed EB and documented pain and Dave's qualified deal is a guy who responded positively to a cold email once, "Qualified" is a meaningless category, and your pipeline report is a category error dressed up as data. You cannot coach against a standard that doesn't exist. You cannot forecast against categories you cannot define. You cannot inspect deals you cannot compare.

2. Clean, reportable data. Five frameworks running simultaneously means five incompatible field sets, a fill rate of approximately zero percent on anything consistent, and a CRM that cannot be queried for insight because nobody agreed on what the hell to put where. The CRM becomes an administrative burden rather than a reporting tool. The RevOps Martyr is manually reconciling five different pipeline views in a spreadsheet at midnight before the board deck goes out. She is not happy. The data is still wrong. Fix this at the source.

3. Inspectability. You can only identify a weak deal if you're measuring it against a known, shared, enforced standard. Without a standard, every deal is an essay submitted by a rep who wrote their own rubric, and pipeline review becomes you reading forty different essays instead of running a consistent inspection process. Pick the religion that fits your sales motion — BANT and Sandler for velocity and SMB; MEDDPICC layered with Challenger and SPIN for complex enterprise — and enforce it with the righteous fervor of someone whose bonus and employment depend on forecast accuracy. Because both of them do, and the universe does not grade on a curve.

HOW IT GOES TO HELL

The Guru — Lance "The Closer" DiMarVo sells your VP a $60,000 Challenger rollout. Two-day offsite at a Marriott that doesn't have a bar within walking distance but has excellent branded notebooks and a forty-minute energy session involving audience clapping and a phrase about "reframing the customer's universe" that sounds profound and means nothing. Certificates printed on thick cardstock, suitable for framing. Three weeks later, not one CRM field has changed. Not one stage gate has been updated. Not one rep has asked a Commercial Insight question in a live discovery call. The floor is selling exactly how it sold before the offsite, except now everyone can recite Teach–Tailor–Take Control when directly asked, which nobody ever does except Lance, for $60,000. You bought a feeling and two days of catered protein bowls and called it a systems transformation. The methodology you did not operationalize — did not build into stages, fields, inspection cadences, or 1:1 accountability — is the methodology you did not buy. It was theater. Lance thanks you for your business and your check. Chip Brennan is on LinkedIn announcing a new cohort.

The VP of Vibes announces "we're a MEDDIC shop now!" at the SKO with the energy of a man who just read the Wikipedia summary. He defines nothing. He builds no CRM fields. He updates no stage gates. He never once asks about the Economic Buyer in a 1:1 because he's managing the energy in the room, not the evidence in the system. Reps, understanding immediately that this is performative, fill whatever new required fields get created with "TBD," "see notes in activity log," "N/A," "asked at call," and — in one instance that is seared into my memory and my therapy — a single period. Just a period. The fields now look like data and contain none, which means the pipeline reports look populated and tell you absolutely nothing, which is a more expensive version of the same shit problem you already had before the SKO. Congratulations, you've added administrative overhead to your existing dishonesty. The VP of Vibes is solving problems aesthetically, cosmetically, performatively. The Number does not care about the aesthetic. The Number is coming regardless.

The Brilliant Jerk refuses the methodology entirely and with contempt. "I close on instinct. The letters are for reps who need training wheels." His pipeline is a black box — a private, undocumented relationship-map that exists only in his head and his phone contacts. When he leaves — and he will, because he always does, because The Brilliant Jerk is constitutionally unable to stay anywhere long enough to be managed — you discover that three of his four Q4 "commits" had never had a confirmed Economic Buyer meeting on record. One deal had been "in legal" for four months with zero paper process documentation. His entire deal history in the CRM is a sequence of stage changes and a handful of optimistic call notes that say "great call, very excited" with no evidence of anything. Instinct is just undocumented MEDDIC that dies the day the rep does, walks out the door, or goes to the competitor. The methodology exists so the institutional knowledge doesn't leave with the person. Make the Brilliant Jerk use it. Document it. Inspect it. This is not a preference and it is not optional and his close rate does not exempt him.

The floor running five methodologies simultaneously — one rep doing BANT, another doing half-remembered Sandler from a podcast they listened to three months ago, a third doing something they're calling Challenger but is actually just being aggressive in demos, and a fourth who is doing nothing but vibes and expense reports — produces a forecast where no two deals mean the same thing, where every pipeline review has to start from scratch because there's no shared framework and no shared language, where the RevOps team is trying to map four incompatible field sets onto a single stage definition and failing at all four, and where the CRO reads the weekly pipeline report like tarot cards spread on a conference room table. The cards look like data. They smell like data. They are fiction printed in a table format. The board is on a plane. They are bringing questions.

FIELD RULES

  • RULE: One enforced methodology beats five admired ones, every single quarter, forever. Consistency is the alpha. Pick a god and make them all fucking pray to it.
  • RULE: If it's not a required field with a stage gate enforced in the CRM, it is not your methodology — it's your wallpaper. Wallpaper doesn't close deals. Wallpaper doesn't make forecast calls less painful.
  • RULE: No Economic Buyer met, no commit. A deal you cannot trace to the person with budget authority is a wish dressed in stage clothing and it will miss the quarter and take your credibility with it.
  • RULE: A champion has power, has influence, and acts on your behalf when you're not in the room. Anyone who doesn't do all three is a coach. Useful. Not a champion. Don't forecast on a coach.
  • RULE: Qualify to disqualify. The fastest path to making quota is to stop burning hours, goodwill, and RevOps capacity on deals that were never real. Disqualify hard and early. The pipeline purge is an act of sanity.
  • RULE: Coaching requires a standard. Without the methodology enforced in the system, you're not coaching — you're yelling into a vacuum with authority. The methodology is the ruler. Without it, you're guessing. The board doesn't care that you were guessing elegantly.

From the field, 3:48 a.m.: I have a recurring nightmare about a Salesforce field named Champion__c that every rep on the floor had filled with the name of a person who had no budget authority, no organizational influence, and apparently no awareness that there was a sales process occurring around them. The field said Champion. The field lied. The entire forecast was built on forty people who could not, under any circumstances, sign a check or survive a vendor review meeting. We hit 31% of plan. I explained this to the board. It was a long call. Expense line: one (1) methodology implementation, performed retroactively on the post-mortem. Pick a religion. Enforce it like your quarter depends on it. Because it fucking does.