Week 1
Buying Psychology
How buyers make decisions — and how top AEs engineer those decisions before demo day. Move from interrogator to trusted advisor in the first call.
Anchoring
Social Proof
Loss Aversion
Trust Acceleration
Consultative Stance
Slide Deck — 8 slides · click any to present
Slide 1
OPENING
Why 70% of Deals Are Lost Before Demo
- The buyer decides "is this worth my time?" in the first 4 minutes
- Most AEs spend those 4 minutes selling features, not earning trust
- The frame you set in call 1 determines whether you control the cycle
PRESENTER NOTE · Open with a story: pick a deal you lost where the buyer "went dark." Odds are the frame broke early. Let the room feel that.
Slide 2
FRAMEWORK
The Decision Stack: How Buyers Actually Buy
- Step 1: Safety — "Can I trust this person?"
- Step 2: Value — "Does this solve a real problem?"
- Step 3: Urgency — "Why now vs. do nothing?"
- Most AEs jump to Step 2. Winning AEs start at Step 1.
PRESENTER NOTE · Draw the stack live. Ask: where do you usually open? Watch hands go up for "value." That's the gap.
Slide 3
PSYCHOLOGY
Anchoring — Set the Frame or Lose It
- First number/reference mentioned anchors all future comparison
- Anchor high before you show price — or let the budget anchor you
- Example: "Our customers who replaced JumpCloud cut IT overhead by 40%…"
- Wrong: leading with your lowest tier to "seem accessible"
PRESENTER NOTE · Run the classic anchoring exercise: ask what they'd pay for a pizza. Then say "a $50 pizza." Watch estimates rise. Same thing happens with software.
Slide 4
PSYCHOLOGY
Social Proof — Borrow Credibility Fast
- "Companies like yours" signals: you've solved this before
- Name competitors already using your product (if you can)
- Peer pressure works on buyers: nobody wants to be the last mover
- Cadence: anchor → social proof → question (not: pitch → pitch → pitch)
PRESENTER NOTE · Have each rep write down 3 companies in their patch they can name-drop. This becomes their social proof arsenal.
Slide 5
PSYCHOLOGY
Loss Aversion — Pain Outweighs Gain
- Buyers feel losses 2× more intensely than equivalent gains (Kahneman)
- Frame around what they're losing every month they don't act
- "You're spending ~$X/month on manual IT provisioning right now"
- Don't threaten — quantify. Make the status quo expensive.
PRESENTER NOTE · Ask reps: in their last 3 deals, did they quantify the cost of doing nothing? Usually no. This is the habit to build.
Slide 6
MINDSET
Consultative vs. Interrogative — The 3-Sentence Test
- Interrogative: rapid questions with no connective tissue → feels like an audit
- Consultative: share an insight before every question → feels like advice
- Test: Can you say why you're asking before you ask it?
- "I ask because I see this a lot with teams your size…"
PRESENTER NOTE · Live drill: pair reps. One plays buyer, one plays AE. AE must frame every question with "I ask because…" before asking it. Debrief on how it felt.
Slide 7
TACTICS
Trust Accelerators — 5 Moves in 15 Minutes
- 1. Reflect back their world before talking about yours
- 2. Name their likely challenges before they say them
- 3. Challenge a safe assumption (shows you're not a yes-person)
- 4. Offer something of value with no ask attached
- 5. Be explicit about the outcome of the call
PRESENTER NOTE · Move #2 (naming challenges before they say them) is the biggest trust lever. It says: "I've been here before." Works especially well against enterprise incumbents.
Slide 8
ASSIGNMENT
This Week's Mission
- Map your next 3 discovery calls to the Decision Stack
- Write your 3 anchor statements before each call
- Record one call — find where you interrogated vs. consulted
- Bring: one trust moment that worked, one that fell flat
PRESENTER NOTE · The Gong recording review is non-negotiable. Self-awareness is the first skill. Can't improve what you don't see.
AE Playbook — Week 1 Self-Study
The Decision Stack Core Framework
Buyers don't make rational decisions. They make emotional decisions and justify them rationally. As an AE, your job in the first call is to move through three invisible layers before they'll give you anything real.
Layer 1 — Safety
- Can I trust this person?
- Have they solved this before?
- Are they going to waste my time?
Layer 2 — Value
- Does this solve a real problem?
- Is the ROI believable?
- Could this make me look good?
Layer 3 — Urgency
- Why now vs. next quarter?
- What's the cost of waiting?
- What happens if we do nothing?
Most AEs do this wrong
- Jump straight to Layer 2
- Never address trust explicitly
- Create urgency with discounts, not pain
"Earn the right to talk about your product by first proving you understand their world."
The rule before every first callThe 3 Biases Psychology
These three psychological principles are why certain AEs consistently win — and why others keep losing to "no decision."
Anchoring
The first reference point sets all future comparisons. If you let the buyer anchor on their current solution's cost, you'll fight that anchor forever. Set yours first.
Anchor Statement
"Most IT teams your size are spending 12–15 hours/week on manual provisioning. Before we look at anything else — is that range familiar to you?"
Why: anchors the problem cost before any solution is discussed.
Social Proof
Buyers look sideways (at peers) before they look forward (at your product). Use this. Name companies like theirs. Name the problems those companies had. Name what happened after.
Social Proof Template
"We work with a lot of [industry/size] teams — the pattern we keep seeing is [problem]. [Company type] usually comes to us after [trigger event]. Does any of that land for you?"
Why: three validation signals in one sentence. They're not alone. You've seen it. You know the trigger.
Loss Aversion
Buyers feel losses 2× more than gains. The status quo feels safe — but it has a hidden price. Your job is to make that price visible.
Cost of Status Quo
"If your team spends 2 hours/week on [manual task] × 5 people × 48 weeks — that's 480 hours/year. At $50 loaded cost, that's $24K you're spending on something you could automate. Does that math feel roughly right?"
Why: you're not threatening. You're quantifying what they're already losing.
Consultative Stance Skill Build
The difference between interrogation and consultation is connective tissue. Every question needs a "why I'm asking" frame. Without it, rapid questions feel like an audit — and the buyer shuts down.
The Formula
Structure
"I ask because [insight about their world] — [question]"
Example — Bad
"How many devices do you manage?"
Feels like a qualification form. No trust built.
Example — Good
"I ask because device sprawl is usually where the first big inefficiency hides — how many endpoints are you managing right now across macOS and Windows?"
Same data. Totally different frame. You're an expert, not a form-filler.
The 3-Sentence TestBefore your next call, write out your top 5 questions. For each one, write the "I ask because…" frame first. If you can't write it, you don't know why you're asking — and neither will the buyer.
Trust Accelerators First-Call Tactics
Exercise — Pre-Call Trust Plan
Before your next 3 discovery calls, write: (1) which trust accelerator you'll lead with, (2) what insight you'll offer for free, (3) how you'll challenge a safe assumption. Review with a peer before the call.
Week 1 Assignment
Buying Psychology
Complete before next session · Estimated time: 60–90 min
This Week's Tasks
Map your next 3 discovery calls to the Decision Stack
For each call: which layer are you starting at? Where does trust need to be built first?
Write 3 anchor statements before each upcoming call
Each anchor should reference a peer company, a relevant metric, and a pain pattern you've seen before.
Record one discovery or intro call this week
Listen back and mark: every question you asked without a "I ask because" frame. Count them.
Pick one trust accelerator to lead with on your next call
Write it out in advance. "What I'll say in the first 60 seconds to earn the right to ask questions."
Write the cost-of-status-quo for your top 2 open deals
Quantify it. Time × headcount × weeks. Make the math visible before your next call with them.
Bonus Challenge
Find one deal in your pipeline where you jumped straight to "value" without building trust first. Write out: what did you miss? What would you do differently on the next call? Bring this to the next session — we'll workshop it live.
Bring to Next Session
- One moment where a trust accelerator worked — what you said, how they responded
- One moment where interrogative questioning killed the energy — what happened next
- Your 3 anchor statements for your current ICP
Live Example — Week 1 · The First Call
Company
Verve AI · 150-person Series B SaaS
Your Buyer
Rohan Mehta · IT Manager
Current Tool
JumpCloud (renewal in 60d)
Situation
First call, 20 min, cold
Scenario: Rohan agreed to a 20-min intro call. He has another meeting after. You've never spoken. He asked your SDR "what does Rippling IT actually do differently?" This is everything.
AE
Interrogative
"Hi Rohan, thanks for taking the time. So — what does your IT setup look like today?"
Rohan
"We use JumpCloud for MDM, manage apps manually. Pretty standard setup."
AE
Audit Mode
"How many employees do you have?"
Rohan
"About 150."
AE
Still Auditing
"And how many people in IT?"
Rohan
"Two of us."
AE
Budget Too Early
"What's your budget looking like for something like this?"
Rohan
"We haven't really scoped that out yet."
AE
Generic Pitch
"Okay, well — Rippling IT is a unified platform. We handle MDM, app management, and identity all in one place. Most customers see big reductions in manual work. I can show you a demo…"
Rohan
"Sounds interesting. Can you send me some info and I'll take a look?"
❌ Outcome: "Send me some info" = dead deal. Rohan felt like a form to fill out, not a professional with real problems. He has no reason to prioritize a follow-up.
AE
AnchorSocial Proof
"Rohan, appreciate you making time. Before I say anything about us — I've been talking with a lot of IT leads at Series B companies lately, and the pattern I keep seeing is that the setup that worked at 80 people starts to crack around 150. Onboarding gets manual, apps proliferate outside IT's visibility, and then the first time a compliance requirement hits, everyone realizes the foundation isn't there. Does any of that land for you?"
Named their peer stage + described their likely pain before asking anything. You're not selling — you're reflecting their world back at them. If you're right, massive credibility. If wrong, they'll correct you — still useful.
Rohan
"Yeah, actually. We've definitely been feeling that pressure lately."
AE
Consultative
"I ask because teams at your stage usually reach out to us for one of two reasons — either a painful off-board experience, or a compliance deadline that put a spotlight on gaps. Which one is pulling you harder right now?"
"I ask because" frame + binary choice = consultative, not interrogative. Both answers are equally useful. Forces Rohan to name his own priority — which becomes your entire meeting agenda.
Rohan
"Honestly both. We had a rough off-board last month and we have a SOC2 audit coming up in Q3."
AE
Loss Aversion
"A rough off-board with a SOC2 audit on the horizon — that's a real pressure point. If access wasn't fully revoked and an auditor asks about it, that's not just an IT headache, that's a finding on the report. Is that a conversation that's made it up to your VP or CTO level yet?"
Elevated the pain from "ops inconvenience" to "compliance risk." Then threaded toward the economic buyer without asking directly — much warmer than "who's the decision-maker?"
Rohan
"Yes — Priya, our VP Eng, actually asked me to look at options after the incident. That's kind of why I'm on this call."
AE
Trust Accelerator
"Good — that means you have exec alignment on fixing this, which makes everything easier. Here's what I want to do: rather than pitching you on features, can I ask you 3–4 specific questions about your current setup? That way anything I show you will be directly relevant to what Priya cares about — not a standard tour."
Named the outcome before pitching. Reframed from vendor to advisor. "Relevant to what Priya cares about" shows you're already thinking about their internal stakeholder, not just the meeting. This is Trust Accelerator #5.
Rohan
"Yeah, that makes sense. Go ahead."
✓ Outcome: Rohan books a 45-minute discovery call for the following week and forwards the calendar invite to Priya with a note: "This is the vendor I mentioned."
Key Takeaways from This Call
- The first sentence anchored on their peer stage (Series B, 150 people) — not on Rippling's features. Frame before you pitch.
- The "I ask because" frame before every question made rapid questions feel like expert curiosity, not an intake form.
- Loss Aversion elevated the off-board from ops problem → compliance risk → career risk — three levels in one sentence.
- Threading to Priya happened naturally by asking "has this reached your VP?" — not by asking "who's the decision-maker?"
- The meeting ended with Rohan asking for next steps — you never had to push.
Field Plays — Week 1 · From the Field
Strong POV Opening — "Strong Opinion, Loosely Held"
Field Research · Sales StrategyTaught by Kyle Asay, RVP at MongoDB. The idea: never open a discovery call with "what are your priorities?" — arrive with a researched hypothesis and let them confirm or redirect you. It earns trust instantly.
The opening template:
Script
"I did my homework and it seems like an extremely exciting time to be at [Company]. [Person observation — e.g. you just joined as VP Sales 4 months ago] and you also [company observation — e.g. just announced a new Enterprise pricing model]. Is [company priority] you and your CEO [name]'s #1 focus over the coming months?"
Even when wrong, this opens a real conversation. "I'd rather have an informed but wrong opinion than show up with no point of view."
6 Cold Call Openers — A/B Tested
Field Research · Cold OutreachAll 6 were run for months. All performed equally — proving the key insight: tone and tempo matter more than the exact words you use.
"I'll be honest. This is a cold call, but it's extremely well researched and I'm confident it's worth your time. Cool if I share why I called you specifically?"→ Best single opener. Built $3M+ in pipeline.
"This is a cold call. Want to roll the dice?"→ Shortest. Highest pattern interrupt. Works on confident buyers.
"Is it fair if I give you a 27-second spiel — if it sounds interesting we can find time, if not you can tell me to go pound rock. Does that work?"→ Time-bounded. Removes pressure. Very high permission rate.
"I know nobody likes a cold call, honestly me included [laugh] — is it cool if I tell you why I'm calling and you can decide if it's worth a conversation?"→ Self-aware + collaborative. Works especially well mid-day.
"I'm hyper aware I'm literally cold calling you out of the blue — can I give you my reason for the call?"→ Most disarming. Good for senior buyers who get a lot of calls.
Key rule: Deliver slowly, clearly, with confident tone. Back up "well researched" with actual research you can deliver on immediately.
OPPS Email Framework — 28% More Replies from C-Suite
Field Research · Email StrategyC-level execs receive ~121 emails a day and allocate ~6 seconds per email. The P.S. line alone drives a 28% lift in reply rates — but only when it can't be AI-generated.
The Framework
- Observation — specific to their world
- Problem — the cost of the status quo
- P.S. — hyper-personal, human detail
- Simple CTA — one ask, low friction
P.S. Examples (human-only)
- Shared hometown connection
- Reference to their volunteer work
- Mention of their podcast/book
- "Saw you're hiring 3 SDRs — congrats"
P.S. included: 27% reply rate. P.S. omitted: 21% reply rate. A 28% lift from one line — and the P.S. has to feel human, not templated.
Personalization Over Automation — 7 Alternatives to Sequences
Field Research · Outbound"Instead of putting that new prospect in a 22-step, 36-day automated sequence..." — 7 things that actually work when you want a response from a specific person.
"If they smile or laugh reading your email, the odds of them responding increases." The tradeoff: you can optimise for volume or replies — but rarely both.
Week 2
Discovery Mastery
L1 → L2 → L3 → Trap. The four-layer question framework that surfaces real pain, builds urgency, and hands you the demo on a silver platter.
L1 Situation
L2 Problem
L3 Impact
Trap Questions
Discovery-to-Demo Bridge
Slide Deck — 8 slides
Slide 1
OPENING
The Discovery Lie: "We Had a Great Call"
- Great rapport ≠ great discovery. Buyers like people who don't push them.
- Surface-level answers → surface-level demo → "we'll think about it"
- The goal: make the buyer SELL THEMSELVES on why they need to change
PRESENTER NOTE · Ask: "Who's had a discovery call where you felt great about it — and the deal went nowhere?" Lots of hands. That's today's session.
Slide 2
FRAMEWORK
The 4-Layer Question Stack
- L1 — Situation: map the current state (facts, not feelings)
- L2 — Problem: where the current state is breaking down
- L3 — Impact: what that breakdown is costing (time, money, risk, career)
- Trap — Confirmation: buyer confirms their own pain in their words
PRESENTER NOTE · Draw the funnel on the whiteboard: wide at top (L1), narrowing to the point (Trap). Show how each layer earns the next.
Slide 3
L1
L1 — Situation Questions
- Purpose: understand the landscape without making them feel qualified
- "Walk me through how you currently handle [process]"
- "What does your stack look like today for [function]?"
- "How big is the team responsible for [area]?"
- Limit to 3–4 L1s. More = audit. Stop before you know everything.
PRESENTER NOTE · Common mistake: spending 30 minutes in L1 because it feels safe. L1 is table stakes. You need it, but don't live there.
Slide 4
L2
L2 — Problem Questions
- Purpose: find where the current state is causing friction
- "Where does that process break down most often?"
- "What's the most painful part of [L1 answer] for your team?"
- "If you could fix one thing about [current state], what would it be?"
- Don't suggest problems. Let them name it. Their words = their conviction.
PRESENTER NOTE · The moment they name the problem unprompted, lean in and slow down. That's where the real discovery begins.
Slide 5
L3
L3 — Impact Questions
- Purpose: attach emotional and financial weight to the problem
- "What does that cost you — in time, headcount, or actual dollars?"
- "How does [problem] affect your team's ability to hit [goal]?"
- "What's the risk if this doesn't get solved in the next 6 months?"
- "How is this showing up in your conversations with leadership?"
PRESENTER NOTE · L3 is where deals are won or lost. If you skip it, you can't create urgency. If you go too hard, you sound salesy. The key: let silence do the work after asking.
Slide 6
TRAP
Trap Questions — Make Them Commit
- Purpose: have the buyer confirm, in their own words, that the pain is real
- "So if I'm hearing you right — [restate pain] — is that the core issue?"
- "Would solving that change [L3 impact] meaningfully for you?"
- "If we could show you [specific outcome] today — would that be worth 30 more minutes?"
- Trap ≠ trick. It's a mirror that makes them own the problem.
PRESENTER NOTE · "Trap" is an internal label. To the buyer it feels like you're checking understanding. Done right, they're nodding enthusiastically before you've pitched anything.
Slide 7
BRIDGE
Discovery-to-Demo Bridge
- Never open your demo without this bridge sentence
- "Based on what you shared — [pain 1], [pain 2], [impact] — I want to show you specifically how we address that. Ready?"
- This sets the demo agenda and signals: we listened
- Bonus: "If we nail those three things, would you see a path forward?"
PRESENTER NOTE · Most reps just say "Great, let me show you the product!" and launch a generic tour. The bridge is the thing that makes your demo feel custom — even if it isn't.
Slide 8
ASSIGNMENT
This Week's Mission
- Build your personal L1–L2–L3–Trap question bank (min 3 per layer)
- Run the full framework on 2 live calls this week
- Review: did you get to L3? Did they name the pain or did you?
- Bring your Discovery Bridge sentence to next session
PRESENTER NOTE · The question bank is a living document. Update it every time a question surprises you — whether it landed or bombed.
AE Playbook — Week 2 Self-Study
The 4-Layer Framework Core Framework
Great discovery is not an interrogation. It's a guided conversation that helps the buyer articulate — in their own words — why the status quo is no longer acceptable. The L1→L2→L3→Trap framework is how you get there.
L1 — Situation (Map the Landscape)
L1 Question
"Walk me through how your team currently handles device provisioning when a new hire starts."
Maps the current process. Sets baseline for friction.
L1 Question
"What does your IT stack look like today — MDM, endpoint security, ticketing?"
Technical map. Reveals integration complexity.
L1 Question
"How big is the IT team responsible for all of this?"
Ratio check. 1 IT person per 100 employees = they're drowning.
L2 — Problem (Find the Friction)
L2 Question
"Where does that process break down most often for your team?"
Opens the complaint. Let them choose the pain point.
L2 Question
"What's the most painful part of your current onboarding flow for IT?"
"Most painful" signals you want the real answer, not the polished one.
L2 Question
"If you could change one thing about your current setup tomorrow, what would it be?"
Forces prioritization. Their answer is your demo focus.
L3 — Impact (Make the Pain Real)
L3 Question
"What does that actually cost you — in time, headcount, or dollars? Even a rough estimate."
Puts a number on pain. Their number > your estimate.
L3 Question
"How does this show up in conversations with your leadership?"
Connects to executive risk. Makes it a career problem, not just a process problem.
L3 Question
"What happens if this doesn't get solved in the next 6 months — what's the downstream risk?"
Creates future pain. Loss aversion activated.
Trap — Confirmation (Let Them Own It)
Trap Question
"So if I'm hearing you right — you're losing roughly X hours per onboard, the team's stretched thin, and leadership is asking why provisioning is still manual — is that the core issue?"
Summarize their pain in their words + slightly raise the stakes. They'll nod. That nod = deal momentum.
Trap Question
"If we could show you a way to cut that provisioning time by 80% and give your team a real audit trail — would that be worth an hour of your time?"
Turns trap into pre-close. You have permission to demo before demo starts.
Discovery-to-Demo Bridge Transition Script
The bridge is the most underused sentence in sales. Most AEs go from discovery straight into a product tour. The bridge makes the demo feel bespoke — even when it follows a standard flow.
Bridge Template
"Based on everything you shared — specifically [pain 1], [pain 2], and the impact on [L3 consequence] — I want to focus the next 20 minutes on exactly those three areas. If we nail those, what would that mean for your decision?"
Sets agenda. Signals listening. Gets pre-close buy-in before demo starts.
The Pre-Demo CommitmentGetting a "yes" to the bridge question is your first close. "If we nail those three things, would you see a path forward?" — this is the soft close before the demo. Most buyers will say yes. Now you know they're serious.
Week 2 Assignment
Discovery Mastery
Complete before next session · Estimated time: 90 min
This Week's Tasks
Build your personal L1–L2–L3–Trap question bank
Minimum 3 questions per layer, specific to your ICP. Write them for Rippling IT — not generic SaaS.
Run the full 4-layer framework on 2 live calls this week
Track: did you reach L3 on at least one pain? Did they name the pain — or did you suggest it?
Write the Discovery Bridge for your top 3 open deals
"Based on what you shared — [pain 1], [pain 2], [impact] — I want to show you specifically how we address that."
Ask the Trump Question on at least 2 calls
"What trumps that as an even bigger priority over the next quarter or two?" — note what surfaced.
Use Question 8 on one call this week
"What about this issue do others just not seem to understand?" — write down their exact answer.
Bonus Challenge
Pick a deal that stalled after discovery. Go back through your notes or call recording and identify: did you get to L3? Did you land a Trap question? Did you set the Bridge? Find the exact moment the discovery went shallow — and what you'd ask differently now.
Bring to Next Session
- Your completed question bank (L1/L2/L3/Trap) — we'll pressure-test it together
- One discovery call where you reached L3 — what did the buyer say?
- Your Discovery Bridge sentence for your current best deal
- The answer you got to Question 8 (the empathy question) — if you asked it
Live Example — Week 2 · Full Discovery Call
Company
Verve AI · 150-person Series B
Buyer
Rohan Mehta · IT Manager
Call #
Discovery — 45 minutes
Goal
Surface real pain → earn the right to demo
Scenario: Rohan booked a 45-min discovery. Priya (VP Eng) is CC'd on the invite but won't be on this call. Your job: get to L3 on at least two pains and land the Discovery Bridge before booking the demo.
AE
L1 — Situation
"Rohan, let's start with the current state. Walk me through what actually happens when a new hire starts at Verve — from the moment HR marks them active to when they have everything they need to do their job."
Open-ended, process-level question. "Walk me through" is better than "what do you do" — it implies a journey with multiple steps, which surfaces more friction.
Rohan
"So HR sends a Slack message to me. I manually create accounts — Google Workspace, GitHub, Slack, Notion, 1Password, a couple of security tools. Then I ship a laptop and enroll it in JumpCloud. The whole thing takes me 2–3 hours per person, sometimes more if they need specialized tools."
AE
L1 — Situation
"Got it. And how many people are you onboarding per month right now?"
Short, specific L1. Gets the math you need for the cost calculation you'll use in L3.
Rohan
"Eight to ten right now. We're growing pretty fast — might be 15 by Q3."
AE
L2 — Problem
"I ask because at 8–10 hires a month, you're already spending 20–25 hours just on provisioning — before you deal with anything else. Where does that process break down most often for your team?"
"I ask because" consultative frame. You did the math for them (20–25 hrs), which anchors the problem size before they've felt it. Then immediately drop to L2 — don't linger in L1.
Rohan
"Honestly, app provisioning is the nightmare. Every tool is a separate login process. And tools get added to the company stack without IT knowing. I found out we had 3 people using a new SaaS tool I'd never heard of — 6 months after they started using it."
AE
L2 — Deepen
"Shadow IT — that's usually where off-board exposure hides. The apps IT doesn't know about are the ones that don't get revoked when someone leaves. Is that what happened in the incident you mentioned last week?"
You connected his shadow IT answer to the off-board problem he raised in Week 1. This signals: I was paying attention. Also deepens L2 without adding a new question — you're building on what he gave you.
Rohan
"Exactly. The person still had access to three tools we didn't even know they were using. We only found out when they sent an email from one of those accounts a week after their last day."
AE
L3 — Impact
"Let's stay on that for a second. When that happened — what was the actual fallout? Not just the immediate scramble, but the downstream impact."
"Not just the immediate scramble" signals you want the real cost, not the sanitized version. The word "downstream" invites them to think beyond day 1 of the incident.
Rohan
"Leadership got involved. Priya had to explain it to the CEO. We spent two full days doing a manual audit of every tool across the company. And now there's a lot of pressure on me personally to make sure it doesn't happen again."
AE
L3 — Career Impact
"That 'pressure on me personally' — is that showing up in your next performance review? Or is it more of a day-to-day anxiety?"
This is the most important L3 question. You're attaching career risk to the problem. When the buyer feels personal stakes, urgency is real — not manufactured. Most AEs never go here.
Rohan
"Both, honestly. My review is in three months. And the SOC2 audit in Q3 is going to surface everything. If we can't produce a clean access log, we're going to fail a control — and that comes back to me."
AE
Trap — Confirmation
"Let me make sure I've got this right — because I want whatever I show you to be directly relevant to what Priya and the auditor are going to care about. You're spending 20–25 hours a month on manual provisioning. You have shadow IT you can't fully see or control. You had an off-board incident that went to the CEO and is now hanging over your review. And in Q3, a SOC2 auditor is going to ask for documentation you can't currently produce. Is that the problem you're trying to solve — or am I missing something?"
The Trap: a full summary of their pain, in their words, slightly elevated in stakes. Note "or am I missing something?" — this invites correction and shows confidence. The buyer almost always says "no, that's it" — and that confirmation is their first commitment to the deal.
Rohan
"No — that's it. That's exactly it. You've got it."
AE
Discovery Bridge
"Perfect. Then I want to build the demo around exactly those four things — provisioning time, app visibility, off-board control, and audit readiness. I'll skip everything else. Before I pull anything up — if we nail all four of those in the next 20 minutes, is this something you and Priya could move on before Q3?"
The Bridge: restate the 4 pains, promise a focused demo (not a tour), then do a soft pre-close. "Is this something you could move on before Q3?" — if yes, you have timeline and intent. If they hesitate, you've just uncovered the real blocker before wasting 2 more calls.
Rohan
"Yeah — I think so. I'd need to loop Priya in, but if it does what you're describing, yes."
✓ Outcome: Demo booked for next Tuesday. Rohan agrees to pull Priya in. You have four specific pains to demo against and a soft "yes" on timeline and intent — before showing a single screen.
What Made This Discovery Work
- Only 2 L1 questions — got to L2 fast. The math anchor ("20–25 hrs/month") was dropped at the L1→L2 transition, not later.
- L2 connected to shadow IT and then immediately tied it back to the off-board incident — continuity from Week 1 conversation built deep trust.
- L3 went to career impact ("your review is in 3 months") — that's where urgency lives. Most AEs stop at operational cost.
- The Trap summarized all 4 pains, then ended with "or am I missing something?" — open door for correction, signal of confidence.
- The Bridge got a soft pre-close before the demo was even scheduled. Rohan confirmed intent and named Priya as the next step — you didn't have to ask.
Field Plays — Week 2 · From the Field
The 8 Discovery Questions That Get AEs to President's Club
Field Research · Sales NewsletterAfter establishing their #1 priority with the POV opening, these 8 questions in order take the buyer from "aware of the problem" to "I need to solve this now." Questions 6, 7, 8 are where most AEs stop short — and where all the urgency lives.
Q8 is the unlock. When a buyer answers this, they're telling you exactly what their internal selling challenge is — and handing you your champion script.
4-Step First Discovery Call Framework
Field Research · Enterprise AE100+ closed logos, distilled into 4 moves. The framework works because it opens with a point of view — not a form — and uses the "Trump question" to surface the priority behind the stated priority.
Strong Point of View — share 2–3 research-based observations and make an educated guess at their #1 priority. Don't open with a blank question.
Listen and Repeat Back — "If I'm hearing you right — those are all important, but really it's X that's your biggest lever?" Then pause for 5+ seconds. Let them expand.
The Trump Question — "What trumps that as an even bigger priority you're focused on over the next quarter or two?" This surfaces the real #1, not the safe answer.
Pain Funnel — dig into why, what happens if it's not solved, failure scenarios. Understand the core business pain before discussing anything about your product.
The Trump question alone has turned single-team deals into company-wide initiatives. It finds the CEO-level priority hiding behind the manager-level answer.
The "What We've Learned" Slide — Growing a Deal from $15K → $90K
Field Research · DiscoveryOn call 3, show a slide summarising what you've learned about the prospect's world — their priorities, challenges, what they've shared. Then ask the Trump question at a higher altitude.
The Slide Opens This Question
"From your CEO's perspective, what trumps this as an even larger priority you're trying to solve for?"
The prospect revealed their CEO was focused on a new product launch to counter a competitive threat — and they'd been losing 70% of competitive deals for 6 months. The deal went from one team to the entire GTM organisation.
3 Lessons from This Deal
- Discovery is continuous, not a stage
- ROI quantification requires depth
- Strategic slides drive deeper conversations
What the Slide Contains
- Their stated #1 priority
- Pain points they've named
- What they've tried before
- Your hypothesis on the real problem
Week 3
The Art of the Demo
Stop touring the product. Start solving their problem. Pain-led demos that make buyers say "this is exactly what I need" — before you ask for next steps.
Pain-Led Structure
State→Show→Impact→Check
Buying Signals
Demo Close
Slide Deck — 7 slides
Slide 1
OPENING
Product Tour vs. Problem Demo
- Product tour: "Here's our dashboard, here's our reporting, here's our integrations…"
- Problem demo: "You said onboarding takes 3 hours. Let me show you why our customers get that to 20 minutes."
- The buyer doesn't care about features. They care about their problem disappearing.
PRESENTER NOTE · Ask the room: raise your hand if your last demo was a product tour. Most hands go up. Then ask: did it close? Most hands go down. That's the session.
Slide 2
FRAMEWORK
The Demo Engine: State → Show → Impact → Check
- State: "You mentioned [pain from discovery]…"
- Show: "Here's exactly how we solve that…" [demonstrate]
- Impact: "For teams like yours, this cuts [X] by [Y]…"
- Check: "Does this address what you were describing?"
- Repeat per pain point. Never show more than 3–4 pains.
PRESENTER NOTE · This is the gold-standard structure. Run it live with a rep volunteering a real deal from their pipeline. Do one full State→Show→Impact→Check loop together.
Slide 3
EXECUTION
Demo Agenda — Set It Before You Open Your Screen
- "I want to focus on [pain 1], [pain 2], and [pain 3] today — does that match what matters most?"
- Confirm the agenda. If they want to add something, add it now.
- This prevents: "Can you show me [thing you didn't plan for]" mid-demo
- Keeps you in control. Signals preparation.
PRESENTER NOTE · The demo agenda is the bridge from Week 2. If you set the bridge well, the agenda writes itself.
Slide 4
TECHNIQUE
Narrate Their World, Not Your Features
- Wrong: "This button triggers an automated workflow."
- Right: "So on Monday morning when your new hire shows up — instead of Sarah spending 2 hours setting up accounts — this triggers automatically the moment HR marks them active."
- Use their names, their tools, their timeline in the narration.
PRESENTER NOTE · The best demos feel like a story about the buyer's future. Feature language is present tense. Story language is future tense. "Imagine it's Monday and…"
Slide 5
READING ROOM
Buying Signals — When to Stop Showing
- "How would this work with [our specific tool]?" → integration curiosity = mental ownership
- "Can other people on my team see this?" → expanding the vision = multi-threading signal
- "What does implementation look like?" → buying signal, not stall
- "How long does it take to get up and running?" → timeline question = they're planning to buy
PRESENTER NOTE · When you hear a buying signal: STOP showing features. Answer the question fully, then pivot to next steps — not more demo.
Slide 6
CLOSE
The Demo Close — End with Momentum
- "We covered [pain 1], [pain 2], [pain 3]. Based on what you saw — how does this compare to what you were hoping for?"
- Let them answer. Then: "What would need to be true for you to see this as the right move?"
- This surfaces objections early — while you still have attention
- Never end with: "Any questions?" That's giving up control.
PRESENTER NOTE · The demo close is the most neglected step. Most reps say "Any questions?" and the meeting dies. Make your specific question a reflex.
Slide 7
ASSIGNMENT
This Week's Mission
- Map your next 2 demos to State→Show→Impact→Check per pain point
- Write a Demo Agenda template for your top 3 ICP use cases
- List the 5 buying signals you've heard — and what you did next
- Practice the Demo Close out loud 5 times before your next call
PRESENTER NOTE · Bonus: record your next demo. Count how many times you say a feature name without connecting it to a pain. Every feature mention without a pain context is lost time.
AE Playbook — Week 3 Self-Study
State → Show → Impact → Check Core Framework
Every pain point from discovery gets its own loop. Run the framework three times max per demo. More than four pains and you're a product tour again.
STATE
"You mentioned that onboarding a new hire manually takes your team 2–3 hours, and that it's caused issues with day-one access for new employees…"
Callback to their words. Shows you listened. Earns attention for the show.
SHOW
[Demonstrate the specific feature or workflow that solves that pain — nothing else]
Keep it tight. One pain = one demo sequence. Don't feature-creep.
IMPACT
"Teams in IT at your stage typically cut provisioning time from 3 hours to under 20 minutes within the first 30 days. And the audit trail is automatic — no more manual logging."
Quantified. Peer-referenced. Future-tense. Believable.
CHECK
"Does this match what you were looking for — or is there a nuance in your workflow I should account for?"
Invites pushback. Shows confidence. Advances the deal.
Placeholder NoteWeek 3 is also where your coach's specific demo slides live. If you have access to the Rippling IT demo deck — layer that into the State→Show→Impact→Check structure. The framework is the wrapper; your product is the content.
Buying Signals Reference Quick Reference
| Signal | What It Means | Right Response |
|---|---|---|
| "How would this work with [our tool]?" | Mental ownership. They're picturing integration. | Answer fully, then: "If we solve that — are you seeing a path forward?" |
| "Can my team also see this?" | Expanding the vision. Want to bring others in. | "Absolutely — who else on your team would care about this?" |
| "What does implementation look like?" | They're buying. Timeline question, not blocker. | Walk through your onboarding. Ask about their ideal go-live date. |
| "How long does it take to set up?" | Planning mindset. They're in. | Give timeline + ask: "Does that work with your timeline?" |
| They go quiet and take notes | Processing. Very good sign. | Let silence breathe. Don't fill it. Ask "What are you capturing?" |
Week 3 Assignment
The Art of the Demo
Complete before next session · Estimated time: 90 min
This Week's Tasks
Map your next 2 demos to State → Show → Impact → Check
Write out each pain point with its own SSIC loop before the call. 3 pains max per demo.
Write a Demo Agenda template for your top 3 ICP use cases
"I want to focus on [pain 1], [pain 2], and [pain 3] today — does that match what matters most?"
Ask the mid-demo multi-thread question on every demo this week
"When you see insights like this — who else on your team would get value from having visibility here?"
Use the Demo Close on every call — no more "Any questions?"
"Based on what you saw — how does this compare to what you were hoping for?" Then listen fully.
Record one demo and count feature mentions without pain context
Every time you describe a feature without tying it to a pain the buyer named — mark it. That's the gap.
Bonus Challenge
Send one value touch within 24 hours of your next demo — tied directly to something the buyer asked or said during the call. No ask. Subject line should reference their exact words. Track whether they reply.
Bring to Next Session
- One buying signal you heard this week — and what you did next
- Your SSIC plan for an upcoming demo — we'll review it live
- The Demo Close response you got — word for word
- Your feature-mention count from the recorded demo (honest number)
Live Example — Week 3 · The Demo Call
Company
Verve AI · 150-person Series B
Attendees
Rohan Mehta + Priya Singh (VP Eng)
Pains to Demo
Provisioning · Shadow IT · Off-board · SOC2
Goal
Get verbal "path forward" before end of call
Scenario: Priya joined at the last minute — Rohan looped her in. You have 40 minutes. Don't restart from scratch. Use the Bridge to anchor the demo to the 4 pains from discovery. Run State→Show→Impact→Check for each one.
AE
Demo Bridge
"Priya, great to have you on — Rohan and I did a deep dive last week. Based on that conversation, I want to focus the next 35 minutes on four specific things: manual provisioning time, shadow IT visibility, off-board access control, and what your SOC2 audit trail looks like today. I'm going to skip everything else. If we nail these four, I'll ask you both where this lands for you. Sound good?"
Bridge brings Priya up to speed in one sentence and signals you listened. Setting a tight agenda tells both buyers: this won't be a generic tour. "I'll ask you both where this lands" = pre-framing the demo close before the demo starts.
Priya
"That works. I've only got 30 minutes so let's keep it focused."
— Pain #1: Manual Provisioning —
AE
STATE
"Rohan, you mentioned your team is spending 2–3 hours per new hire — manually creating accounts across Google, GitHub, Slack, Notion, 1Password. At 8–10 hires a month, that's 20–25 hours of IT time just on provisioning. Let me show you what Monday morning looks like when a new hire starts in Rippling."
AE
[shares screen — shows Rippling IT workflow: HR marks new hire active → automated provisioning triggers → Google, GitHub, Slack all provisioned in under 2 minutes, device enrolled, apps assigned by role]
AE
IMPACT
"What you just saw takes 90 seconds. IT teams at your stage — Series B, 100–200 employees — typically go from 2–3 hours per hire to under 10 minutes. At your current hiring pace, that's about 20 hours a month back to Rohan. That's half a working week every month."
Quantified impact using their numbers. "Half a working week every month" is more visceral than "20 hours." Priya now hears this in dollars, not tasks.
AE
CHECK
"Rohan — does this cover the provisioning problem as you described it, or is there a step in your workflow I haven't accounted for?"
Rohan
"That covers it. Honestly that alone is huge."
Priya
"Quick question — how would this work with our Jira Service Management setup? We use Jira for IT ticketing."
AE
BUYING SIGNAL — Respond & Move
"Great question — there's a native Jira integration. You can trigger provisioning directly from a Jira ticket, so your IT workflow stays inside the same tool your team already uses. I can show you that specifically, or we can keep moving to shadow IT and come back to Jira at the end — whatever's more valuable to you."
Buying signal from the EB. Priya is mentally integrating Rippling into her stack — she's already picturing this. Don't dive deeper on Jira right now. Answer, offer choice, keep control of the demo agenda.
Priya
"Keep moving — we can come back."
— Pain #2: Shadow IT Visibility —
AE
STATE
"Rohan mentioned finding out about 3 tools employees were using 6 months after they started — apps IT never provisioned. The apps you can't see are the ones that don't get revoked. Let me show you what your app inventory looks like in Rippling."
AE
[shows app discovery dashboard — all SaaS tools connected to Google Workspace domain, flagged by provisioning status: IT-managed vs employee-added, usage data, risk level]
AE
IMPACT
"Everything here — whether IT provisioned it or an employee connected it themselves — shows up in one place. The yellow flags are shadow IT: tools added outside IT's visibility. You can set a policy so any new app connection triggers an approval flow before it's active. Teams that implement this typically get shadow IT under control within the first week."
AE
CHECK
"Priya — from a security posture standpoint, does this give you the visibility you'd want before a SOC2 audit?"
Directed the Check at Priya, not Rohan — she's the EB and the SOC2 decision-maker. Framing "before a SOC2 audit" connects directly to the urgency she cares about.
Priya
"Yes. This is actually what I was hoping to see. How does the offboarding work?"
AE
BUYING SIGNAL — EB is sold on Pain 2, asking about Pain 3
"That's exactly the next thing I want to show you."
Priya just asked about your next demo section unprompted. She's driving the demo now — that's the signal that she's bought in. Don't slow down, don't recap. Just move.
— Pain #3 & #4 covered — Demo Close —
AE
DEMO CLOSE
"We covered all four — provisioning, shadow IT, off-board, and the audit trail. Priya, Rohan — based on what you've seen, how does this compare to what you were hoping for when you got on this call?"
The demo close question. Open-ended, not "any questions?" Invites them to articulate value in their own words — which is the most powerful internal selling tool they have when Priya needs to explain this to the CEO.
Priya
"Honestly, this is more comprehensive than I expected. The SOC2 audit trail especially — that's what we've been missing. What does implementation look like?"
AE
BUYING SIGNAL — Timeline Question = They're Buying
"Most teams at your size are fully live in 3–4 weeks. We assign you a dedicated implementation manager and the first thing we tackle is the provisioning flows and app inventory — so you see impact in week one. Given your Q3 SOC2 timeline, going live by end of May would give you 6 weeks of clean audit data before any auditor asks. Does that timeline work for you both?"
Answered the implementation question with specifics + connected to their Q3 urgency. "Does that timeline work?" is the first direct close — and it's earned because Priya asked the question, not you.
Priya
"End of May works. Let's figure out next steps."
✓ Outcome: Priya says "let's figure out next steps" before you ask for anything. Deal moves to Stage 5. Rohan sends a follow-up in Slack 10 minutes after the call: "Priya is in. She's asking about budget process."
What Made This Demo Work
- The Bridge at the start was directed at Priya (new attendee) — brought her up to speed in 30 seconds without restarting discovery.
- Every State used Rohan's exact words from the discovery call. Not "provisioning is complex" — "2–3 hours per hire, 8–10 people a month."
- Buying signals from Priya (Jira question, off-board question) were answered cleanly then control was handed back to the agenda.
- Checks were directed at the right person: Rohan for operational pains, Priya for security and compliance pains.
- The demo close ("how does this compare to what you were hoping for?") got Priya to say "more comprehensive than I expected" — that's her selling herself.
Field Plays — Week 3 · From the Field
Mid-Demo Multi-Thread Seed — Plant It Before You Need It
Field Research · Demo StrategyThe easiest multi-threading move in existence. Ask it while they're engaged — when they're seeing value in the demo — not after, when you have to justify the ask.
The Question (mid-demo, while showing something impressive)
"When you see insights like this — who else on your team would get value from having visibility here?"
By end of call, you have implicit permission to add those people. Anthony Natoli's upgrade: name the person specifically — "How do you think Liz who leads your SDR org would react if she saw this?" — even more powerful because it personalises the question.
Plant this seed in every demo. You're not asking to expand the deal — you're asking who cares about what they're seeing. The expansion happens naturally.
Value Touches Between Meetings — Sell Without Asking
Field Playbook"Sell between meetings by offering value with no homework and no ask." The best follow-up emails don't ask for anything — they prove you were listening.
They asked about an integration? → Send a 90-second Loom walking through exactly how that integration works. Subject: "The Jira integration you asked about (90 sec)"
They mentioned a pain point? → Drop a relevant one-pager or case study tied to that exact pain. "Thought of your off-board situation when I found this."
They referenced a competitor? → Send a concise battle card — not to trash the competitor, but to help them evaluate the right criteria.
They mentioned a company initiative? → Send a relevant article, benchmark, or stat. Zero ask. Just: "Saw this and thought of what you mentioned."
Every value touch between meetings builds trust without pressure. By the time you ask for next steps, they've already received value 3 times. The ask feels easy.
Hook, Line, and Sinker — Demo Opening That Creates Urgency
Field FrameworkDon't just restate pains from discovery. Open the demo with the buying criteria in priority order — and connect the #1 priority to a metric that makes the cost of inaction visible.
Hook — Start with their top priority: "Based on what you shared, the thing that matters most is [#1 priority from discovery]."
Line — Reaffirm what they care about most: "And specifically, it's [exact pain in their words] that's creating the most friction right now."
Sinker — Connect to a critical metric: "Teams in your position are typically [quantified impact]. I want to show you exactly how we change that number."
This structure does three things before you show a single screen: confirms you listened, frames the demo around their world, and anchors the business case in a number they care about.
Week 4
Multi-Threading the Deal
Single-threaded deals die. Learn to map power, build champions, and get to the economic buyer before your competitor does.
Power Map
Champion 3-Test
Trigger Events
Exec Brief
Slide Deck — 7 slides
Slide 1
OPENING
The Single-Thread Death Spiral
- Champion goes quiet → deal stalls → "we're revisiting budget"
- 80% of stalled deals are single-threaded
- Your champion can't sell for you if they're the only one who knows you
PRESENTER NOTE · Ask: "Who has a deal right now where you only talk to one person?" Then: "How long has it been in that stage?" That's the ghost you're hunting.
Slide 2
FRAMEWORK
The Power Map — 4 Roles in Every Deal
- Economic Buyer: controls the budget. Must say yes.
- Champion: wants you to win. Has internal credibility.
- Influencer: shapes opinion but doesn't decide.
- Blocker: protecting status quo. Must be neutralized or won over.
PRESENTER NOTE · Have each rep draw a power map for their top deal right now. Which boxes are empty? That's where they're vulnerable.
Slide 3
CHAMPION
The Champion 3-Test
- Test 1 — Access: "Have they introduced me to anyone else?"
- Test 2 — Intel: "Do they give me info I couldn't find publicly?"
- Test 3 — Skin: "Do they have something to gain or lose from this decision?"
- If all 3 = no → they're a contact, not a champion
PRESENTER NOTE · Most reps mistake "friendly contact" for champion. The test is brutal but clarifying. Run it on every deal in the pipeline review.
Slide 4
EXECUTION
How to Get Introduced — The Champion Ask
- "Who else on your team has visibility into this problem?"
- "Typically, decisions like this involve [finance/IT/ops] — is that true here?"
- "I'd love to share a business case with [exec] — would you be comfortable facilitating that intro?"
- Never ask to "meet the decision-maker" — ask to solve a problem together
PRESENTER NOTE · The exec ask is the most skipped step. Most reps are afraid of seeming pushy. Reframe it as "helping your champion succeed" — because it is.
Slide 5
TRIGGERS
Trigger Events — When to Strike
- New hire in IT/Ops leadership → new pain ownership
- Funding round → budget unlocked, growth mandate
- Compliance audit → urgency created externally
- Competitor breach/outage → trust crisis with incumbent
- Headcount growth >20% → ops strain hitting now
PRESENTER NOTE · Trigger-based outreach converts 3× better than cold. Set LinkedIn/news alerts for your top accounts. Spend 10 min/day on trigger scanning.
Slide 6
EXEC
The 3-Minute Exec Brief
- Execs don't want a demo. They want: risk, cost, outcome.
- Open: "Here's the problem your team is solving for…"
- Middle: "Here's what the cost of doing nothing looks like…"
- Close: "Here's what a 90-day outcome looks like with us…"
- Ask: "Does that directionally match what you're trying to solve?"
PRESENTER NOTE · Execs will give you 3 minutes. Make them count. No features. No roadmap. Risk → cost → outcome. Practice this until it's 90 seconds.
Slide 7
ASSIGNMENT
This Week's Mission
- Draw a power map for your top 3 deals. Identify empty roles.
- Run the Champion 3-Test on every deal in Stage 3+
- Write your Champion Ask script — practice out loud
- Draft a 3-minute exec brief for one deal
PRESENTER NOTE · The power map exercise tends to be uncomfortable. That discomfort is signal. Empty boxes = deal risk you've been ignoring.
AE Playbook — Week 4 Self-Study
Power Map Template Core Tool
For every Stage 3+ deal, you should be able to fill in every box below. If you can't, the deal is at risk.
Economic Buyer
- Name + title
- Their top 2 priorities this quarter
- What success looks like for them
- Have you spoken with them directly?
Champion
- Name + title
- Their personal win from this deal
- Passed all 3 champion tests?
- Have they introduced you to others?
Influencers
- Who shapes the recommendation?
- What's their concern with the status quo?
- Have you spoken to them?
Blockers
- Who benefits from NOT changing?
- What's their objection?
- Plan to neutralize or win over?
Champion 3-Test Qualification Tool
"A champion is someone who sells for you when you're not in the room."
If they're not doing that, they're a contact — not a champion.Week 4 Assignment
Multi-Threading the Deal
Complete before next session · Estimated time: 60–90 min
This Week's Tasks
Draw a power map for your top 3 deals
Economic Buyer, Champion, Influencers, Blockers. Empty boxes = deal risk. Name the fix for each gap.
Run the Champion 3-Test on every Stage 3+ deal
Access, Intel, Skin. If a deal fails all 3 — you have a contact, not a champion. Decide what to do next.
Write your Champion Ask script and practice it out loud 3 times
Frame it as reducing their internal work — not "I need to meet your boss." Rehearse until it sounds natural.
Draft a 3-minute exec brief for one deal
Risk → cost of doing nothing → 90-day outcome. No features. No roadmap. Practice until it's 90 seconds.
Write out 2–3 reasons you'll lose each Stage 4+ deal
Then write the proactive fix for each risk. Address at least one before your next call on that deal.
Bonus Challenge
Set up a trigger alert (LinkedIn, Google News, or Crunchbase) for your top 5 accounts. Spend 10 minutes this week scanning for: new hires in IT/Ops leadership, funding news, compliance announcements. Use one trigger as your outreach reason on a prospecting or re-engagement touch.
Bring to Next Session
- Power maps for your top 3 deals — filled in, gaps marked
- One deal that failed the Champion 3-Test — what's the plan?
- Your exec brief (written or practised) — we'll give feedback live
- One deal risk you addressed proactively this week — what happened?
Live Example — Week 4 · Multi-Threading in Action
Deal Stage
Post-demo · Stage 4
Champion Candidate
Rohan Mehta · IT Manager
EB Status
Priya Singh — attended demo, engaged
Risk
Only talking to Rohan — single thread
Scenario: Great demo — Priya seemed interested but left early. Rohan is your only contact. You need to validate whether Rohan is a real champion, fill in the power map, and get a direct line to Priya before the deal can progress.
Step 1 — Run the Champion 3-Test on Rohan
✅
Test 1 — Access: Has Rohan introduced me to anyone else without being asked twice?
YES — He pulled Priya into the demo and sent her a pre-read note. He did this on his own initiative.
YES — He pulled Priya into the demo and sent her a pre-read note. He did this on his own initiative.
✅
Test 2 — Intel: Has he shared internal context I couldn't find publicly?
YES — Told me about the off-board incident, the CEO involvement, his performance review timeline, and that Priya is under pressure from legal on SOC2. None of this is public.
YES — Told me about the off-board incident, the CEO involvement, his performance review timeline, and that Priya is under pressure from legal on SOC2. None of this is public.
✅
Test 3 — Skin: Does Rohan have something to win or lose from this decision?
YES — His performance review is in 3 months. His manager (Priya) is watching. If Rippling fixes the SOC2 problem before Q3, Rohan is the hero. If it doesn't get fixed, he owns the failure.
YES — His performance review is in 3 months. His manager (Priya) is watching. If Rippling fixes the SOC2 problem before Q3, Rohan is the hero. If it doesn't get fixed, he owns the failure.
Rohan passes all 3 tests. He is a real champion — not just a friendly contact.
Step 2 — Power Map (Current State)
Champion
Rohan Mehta
IT Manager · Passed all 3 tests · Motivated by review + SOC2
Secured
Economic Buyer
Priya Singh
VP Engineering · Attended demo · Responded positively · Budget authority unclear
Engaged — needs direct conversation
Finance / Procurement
Unknown
Who approves SaaS purchases? Does it go through finance or can Priya self-approve?
Gap — ask Rohan
Blocker?
CTO / CEO?
Priya mentioned "I'll need to loop in leadership on budget." Is there anyone above Priya who could kill this?
Gap — ask Priya directly
Step 3 — The Champion Ask
AE (follow-up call with Rohan)
Multi-Thread Ask
"Rohan, based on the demo — it sounds like Priya is genuinely interested, and the SOC2 timeline makes this urgent for both of you. At this point, I want to make sure we're not creating extra work for you internally. Typically for a decision like this, Priya would want to see the security and compliance layer specifically, and finance would need to be in the loop on budget approval. Would you be comfortable making a direct intro over email this week? I'll send you a 3-line summary of where we are so you can just forward it — takes you 30 seconds."
The champion ask is framed as "reducing work for Rohan" — not "I need access to your boss." Giving him a pre-written summary to forward removes all friction. He becomes the messenger, you become the solution.
Rohan
"Yeah, that makes sense. Priya actually asked me for an update this morning. I'll intro you two over email today."
AE
"Perfect. One more thing — who else typically gets involved in a SaaS purchase at Verve? Does it go through finance or can Priya approve at her level?"
Mapping procurement path while Rohan is open. This question prevents a surprise blocker appearing in Week 5 when you try to close.
Rohan
"Under $25K Priya can approve directly. Above that it goes to the CFO. I think we're under that."
Step 4 — The 3-Minute Exec Brief (for Priya)
Email from Rohan → Priya (you provided the 3 lines)
"Priya — wanted to loop you in directly with [AE name] from Rippling.
Quick context: the problem we've been working on is provisioning (20–25 hrs/month of my time), shadow IT gaps that contributed to the March off-board incident, and getting audit-ready before Q3 SOC2. The demo last week showed all four solutions working together.
[AE] would like 20 minutes to walk you through the compliance layer specifically and talk about implementation timeline relative to Q3. I think it's worth your time."
Quick context: the problem we've been working on is provisioning (20–25 hrs/month of my time), shadow IT gaps that contributed to the March off-board incident, and getting audit-ready before Q3 SOC2. The demo last week showed all four solutions working together.
[AE] would like 20 minutes to walk you through the compliance layer specifically and talk about implementation timeline relative to Q3. I think it's worth your time."
Why this works: Rohan named the problem (not you), quantified it in his words, and gave Priya a reason to take the meeting — all in 3 lines. Your name isn't even on the selling sentences.
✓ Outcome: Priya replies in 2 hours: "I'm free Thursday at 2pm." Power map is now: Champion ✓, EB engaged ✓, procurement path mapped ✓. Deal moves to Stage 5.
Key Takeaways
- The champion 3-test on Rohan confirmed he was real — and revealed exactly which "skin" he has in the game (review + SOC2).
- The power map identified two gaps (procurement + potential blocker) that would have killed the deal in Week 5 if not uncovered now.
- The champion ask was framed as "reducing friction for Rohan" — not "I need to meet your boss." Same request, completely different dynamic.
- The 3-line exec brief was written in Rohan's voice, not yours. When Priya reads it, she hears her trusted report vouching for you — that's worth more than any pitch you could write.
Field Plays — Week 4 · From the Field
"Win One at a Time" — Multi-Threading Sequenced Right
Field PlaybookThe biggest mistake in multi-threading: trying to jump two levels at once. Buyers refer up through trust, not through cold introductions. Win the next level, then use them to earn the level above.
Discovery call → build the manager as your first champion. They're closest to the pain. Earn their trust completely.
Demo call → use the manager to get the director in the room. Their champion vouches for the meeting. Convert the director.
Team meeting → use the director to get VP/exec involvement. By now, two internal voices are advocating — you're not the one asking to meet leadership.
After every group meeting → send individual follow-ups to each person. Reference something specific they said. No ask — just reinforcing the relationship with each person independently.
Build an army of champions, not a single point of failure. If your one contact goes dark, you have two others. If all three go dark, the deal was never real.
Deal Risk Log — Write Out Why You'll Lose Before Every Call
Field Research · Deal Management"For each deal, I write out why I'll lose it. Usually there's 2–3 reasons." This is not pessimism — it's the most practical pre-call habit in sales. Every risk you name becomes something you can address before the buyer raises it.
Risk: Cheaper competitor in the mix → proactively show customers who upgraded from that tool and the outcomes they got. Do it before they bring up price.
Risk: Only talking to manager level → contractually build director involvement into the process: "If the first call goes well, I'll ask that we include your director in the next one."
Risk: Don't know their full tech stack → ask explicitly in discovery before the demo: "What else is in your stack that we'd need to connect with?"
Risk: No clear urgency driver → surface the cost of inaction at L3. If there's no urgency, it's not a deal — it's a conversation.
His #1 reason for losing deals: "no decision." The antidote is proactively introducing competitive context before the prospect decides to stay with the status quo.
CEO of Your Book of Business — Extreme Ownership Mindset
Field Research · Enterprise AEThe framing that separates AEs who build pipeline from AEs who wait for it: treat your territory like a business you own, not a book you inherit.
What CEOs do
- Set their own pipeline targets
- Build their own prospecting systems
- Don't wait for SDR support to act
- Identify risks before they become losses
- Review their "business" weekly
80/20 Weekly Time Split
- 80% → advancing + creating pipeline
- 20% → everything else
- Audit your calendar weekly against this
- "Do a little prospecting every day so you never have to do a lot"
72% of $1.2M closed won in a single year was self-sourced. The AEs who hit quota consistently are the ones who treat pipeline creation as a personal responsibility — not a shared function.
Week 5
The Close Blueprint
Closing isn't a moment — it's an architecture. Build the path to yes from Day 1 and you'll never need a closing technique.
Decision Infrastructure
Mutual Action Plan
Stall Handling
LOI Bridge
Pre-Close Checklist
Slide Deck — 7 slides
Slide 1
OPENING
Why Closing Techniques Don't Work
- The ABC mindset creates pressure → pressure kills trust
- Buyers who feel closed push back — or ghost
- The real close happens in Week 2 (discovery) and Week 4 (multi-thread)
- By Week 5, you're confirming — not convincing
PRESENTER NOTE · This reframe is the unlock. Closing is the outcome of everything before it. If you're relying on a close technique, something earlier broke.
Slide 2
FRAMEWORK
Decision Infrastructure — Map It Before Demo
- "How does your company typically evaluate and approve software purchases?"
- "Who needs to be involved for a decision like this?"
- "What does your approval process look like once the team is aligned?"
- "Have you done a purchase like this recently? What did that process look like?"
PRESENTER NOTE · Ask these in discovery — not in the close. By the time you're ready to close, the answers should be in your notes. Surprises in the close stage = lazy discovery.
Slide 3
TOOL
The Mutual Action Plan (MAP)
- A shared doc: your steps + their steps + dates
- Converts "thinking about it" into a collaborative project
- If they won't engage with the MAP → they're not serious
- Include: security review, legal, budget approval, go-live target
PRESENTER NOTE · The MAP is a qualification tool disguised as a project plan. If they won't fill it in with you, you don't have a real opportunity. Find out now, not at end of quarter.
Slide 4
LANGUAGE
Assumptive Language — The Soft Close
- "When you go live…" not "If you decide to move forward…"
- "As we onboard your team…" not "If this works for you…"
- "Your admin will be able to…" not "The admin role can…"
- Subtle shift from conditional to expectation. Mirrors buyer confidence.
PRESENTER NOTE · This is not manipulation — it's confidence. If the deal is real, assumptive language accelerates it. If it's not, it surfaces that too. Both outcomes are useful.
Slide 5
OBJECTIONS
The 4 Real Stall Types
- 1. Budget stall: "Need to check budget" → quantify ROI, connect to a live pain
- 2. Timing stall: "Let's revisit next quarter" → find the trigger that changes the clock
- 3. Stakeholder stall: "Need to get alignment" → you haven't multi-threaded enough
- 4. Trust stall: "We're evaluating options" → you haven't earned the right to win
PRESENTER NOTE · Almost every stall falls into one of these four. The treatment for each is different. "Needs more time" is not a category — it's a symptom. Diagnose the root cause.
Slide 6
BRIDGE
The LOI Bridge — Create Commitment Before Contract
- Letter of Intent: non-binding, written commitment to move to legal/procurement
- "Can we put a short LOI in place so legal/procurement can start in parallel?"
- Filters real deals from tire-kickers instantly
- If they won't sign an LOI → contract won't come either
PRESENTER NOTE · Not all companies use LOIs. But the concept works: any low-friction written commitment (even a confirmed email with a timeline) creates psychological ownership and accelerates legal.
Slide 7
CHECKLIST
Pre-Close Checklist — 8 Questions
- Is the economic buyer bought in? Have I spoken to them directly?
- Is the pain quantified in their words?
- Is the MAP agreed with dates and owners?
- Are all blockers identified and addressed?
PRESENTER NOTE · If you can't answer yes to all 8 questions (see playbook for full list), you're not ready to close — you're hoping. Hope is not a strategy.
AE Playbook — Week 5 Self-Study
Stall Diagnostic & Treatment Objection Handling
| Stall Type | What They Say | Root Cause | Treatment |
|---|---|---|---|
| Budget | "Need to check on budget" | ROI unclear or not compelling | Quantify the cost of doing nothing. Tie to a live business pain they named. |
| Timing | "Let's revisit Q3" | No urgency driver | Find what changes in Q3. If nothing — the stall is real. If something — use it. |
| Stakeholder | "Need to get everyone aligned" | Single-threaded deal | Ask your champion: "Who needs to be in the room? Can we get them in this week?" |
| Trust | "We're still evaluating" | Not differentiated / rapport low | Name the competitor. Ask: "What would it take for us to win?" Listen hard. |
Pre-Close Checklist Deal Qualification
RuleIf you can't check all 8 boxes, don't send the proposal yet. Sending a proposal to an unqualified deal creates work for you and false urgency that evaporates the moment the PDF lands.
Week 5 Assignment
The Close Blueprint
Complete before next session · Estimated time: 90 min
This Week's Tasks
Map the decision infrastructure for every Stage 4+ deal
Who approves? What's the process? What's the threshold? If you don't know — ask this week.
Create or send a Mutual Action Plan for your top 2 deals
Your steps + their steps + dates. If they won't fill it in — that tells you something. Both outcomes are useful.
Audit your last 5 follow-up emails for conditional vs. assumptive language
Highlight every "if you decide" and "in the event that." Rewrite each one with assumptive language.
Diagnose every stalled deal using the 4 stall types
Budget, Timing, Stakeholder, or Trust? Write the root cause and the specific treatment for each one.
Run the 8-question pre-close checklist on your top deal
If any box is unchecked — don't send the proposal yet. Fix the gap first.
Bonus Challenge
Pick one deal where the competitor is a factor. Proactively name the competitor on your next call before the buyer does. Use the reframe: "I'd actually encourage you to evaluate them — here's how I'd suggest comparing the two so you're looking at the right things." Bring what happened.
Bring to Next Session
- One stall you diagnosed correctly — what type, what you did, what happened
- One stall you diagnosed wrong — what you thought it was vs. what it actually was
- Your MAP for a current deal — filled in or attempted
- The pre-close checklist result on your top deal — how many boxes are green?
Live Example — Week 5 · Diagnosing the Stall
Deal Stage
Stage 5 → trying to close
Situation
Post Priya call — felt great — 5 days of silence
Stall Message
Rohan: "Let me chat with Priya and circle back"
Your Job
Diagnose the stall type → apply the right treatment
Scenario: The Priya call went well — she said "this is more comprehensive than I expected." Then 5 days of silence. You followed up and Rohan replied: "This looks great. Let me chat with Priya and we'll circle back next week." You have 60 seconds to decide what type of stall this is.
Diagnose: Which Stall Type Is This?
❌ Budget Stall?
Nothing about budget has come up. Priya confirmed they're under her $25K approval threshold. Not this.
❌ Timing Stall?
They have an urgent Q3 SOC2 deadline. Timing is working in your favour. Not this.
⚠️ Stakeholder Stall?
Rohan says "let me chat with Priya" — but Priya was on the demo. Why does he need to re-brief her? Possible: there's a new person involved (CFO?). Partially.
⚠️ Trust / Comparison Stall?
Priya said it was good — but also their JumpCloud renewal is coming up. Are they using the Rippling demo to get a better JumpCloud renewal price? Most likely.
Verdict: This is a Stakeholder + Comparison stall. Priya is interested, but she may be using this evaluation to leverage JumpCloud on renewal. "Let me chat with Priya" is delay language — they've already spoken. Rohan is running interference while something gets sorted internally.
The Right Response — Call, Not Email
AE (call with Rohan)
Diagnose First
"Rohan, appreciate the reply. Before I add anything to your plate — help me understand what's happening on your side. Priya seemed really positive after the demo. What's the conversation internally looking like right now?"
Don't assume. Ask. "What's the conversation internally" invites Rohan to share what's actually blocking progress — without putting him on the defensive.
Rohan
"Yeah, she liked it. But she mentioned JumpCloud reached out this week about our renewal and she wants to see their updated offer before making a decision. Doesn't want to leave money on the table."
AE
Reframe the Comparison
"That makes sense — and I'd actually encourage that. But here's the thing: comparing JumpCloud's renewal to Rippling is apples to oranges. JumpCloud is MDM and identity. What you saw with us covers provisioning, app lifecycle, off-board, and the audit trail — all in one place. If Priya wants to compare on price, she should compare total cost of what you currently have stitched together versus one platform. I can put together a quick cost comparison that makes that clear. Would that be useful to send her before she sits with JumpCloud?"
Don't panic at the JumpCloud comparison. Reframe the comparison criteria — you're not competing on MDM price, you're competing on total platform cost vs. fragmented stack. Offering a cost comparison puts you in the deal, not on the sideline.
Rohan
"That would actually be really helpful. Yeah, send that over."
AE
MAP + Timeline
"I'll send it today. While I have you — I want to put together a quick Mutual Action Plan so we both know what needs to happen to get you live before Q3. It's a 5-line doc: your steps, our steps, dates. Takes 10 minutes to fill in together. Can we do that on a quick call this week, or should I draft it and you fill in your side?"
The MAP ask does two things: (1) it advances the deal even while Priya is evaluating JumpCloud, (2) it qualifies Rohan's seriousness. If he won't engage with a MAP, the deal is softer than it looks.
Rohan
"Draft it and send it over. I'll fill in our side and loop Priya in on the timeline."
✓ Outcome: You send the cost comparison and draft MAP same day. Rohan fills in the MAP with Priya. JumpCloud comes back with a 15% renewal discount. Priya looks at the MAP and tells Rohan: "The Rippling scope is bigger — let's go with them."
Assumptive Language — See the Difference
❌ Conditional Language
- "If you decide to move forward…"
- "If this works for you…"
- "In the event that you choose Rippling…"
- "If we end up working together…"
Signals: I'm not sure you're buying. Creates psychological distance.
✓ Assumptive Language
- "When you go live in May…"
- "As we onboard your team…"
- "Your admin will be able to…"
- "When Rohan runs his first audit…"
Signals: I'm confident this is happening. Mirrors buyer certainty. Accelerates the deal.
Key Takeaways
- Diagnose before you respond. "Let me think about it" is not a category — it's a symptom. Find the root cause before applying a treatment.
- The JumpCloud comparison was a Trojan horse. Reframe the comparison criteria — you control what they're comparing if you move fast enough.
- The MAP closes the gap between "interested" and "committed." If they fill it in, the deal is real. If they won't, find out why now.
- Assumptive language is confidence, not manipulation. Use it only on deals that are real — it accelerates what's already moving.
Field Plays — Week 5 · From the Field
Mutual Success Plan — >90% Pilot Win Rate
Field Research · Enterprise AEEvery pilot he runs includes a Mutual Success Plan. It's the difference between "we'll try it out" and "we're committed to making this work." The plan turns a trial into a project — with owners and dates on both sides.
Success criteria — what does "this worked" look like? Define it with them before the pilot starts, not after.
Session schedule — weekly check-ins, who attends, what gets reviewed. No pilot runs without a cadence.
Pilot resources — what you're providing, what they're responsible for, implementation milestones.
3 sign-off lines — security sign-off, legal sign-off, commercial signer identified. Get these named before the pilot starts or you'll hit them as surprises at close.
"Never begin a pilot without executive alignment — ideally with the economic buyer already engaged." Win rate on pilots: north of 90%.
Proactive Competitive Positioning — Beat "No Decision"
Field PlaybookThe #1 reason for losing deals isn't a competitor — it's "no decision." The prospect defaults to doing nothing. The fix: introduce competitor context proactively before they use it as an exit ramp.
The Proactive Competitor Frame
"I want to be transparent — you're probably also evaluating [competitor], and I'd encourage that. What I'd suggest is making sure you're comparing on the right dimensions. Here's what teams who've moved from [competitor] to us typically say about the differences that mattered…"
Why This Works
- You control the comparison criteria
- Shows confidence, not fear
- Names the competitor before they do
- Frames their story around your strengths
What to Prepare
- 1-2 customer stories per main competitor
- Key differentiators that matter to this buyer
- The one thing the competitor genuinely does better (credibility)
Introducing the competitor yourself removes their ability to use it as a stall. "We're also looking at X" becomes a conversation you're already having — not a surprise blocker at close.
3 Strategies for Keeping Momentum — Between Every Meeting
Field Research · Enterprise AEMost deals don't die from a single objection — they bleed out from lost momentum between meetings. These three habits keep the deal moving when you're not in the room.
Set a specific next step before you leave every call — not "I'll follow up next week." A date, a time, and what will happen on that call. Mutual commitment before you hang up.
Send a value touch within 24 hours — something tied directly to what was discussed. No ask. Just proof you were listening. Subject line: reference their exact words.
Give your champion something to use internally — a one-liner they can use when their manager asks "where are we on this?" The easier you make it for them to sell internally, the faster the deal moves.
The gap between meetings is where deals go cold. Momentum is a habit — not a reaction to deal risk. Build these three touches into every cycle, automatically.
Week 6
Pipeline Architecture
Top AEs don't wait for pipeline to happen to them. They engineer it. Build the system that generates consistent, qualified deals — and the OS to run it sustainably.
Pipeline Audit
Stage Exit Criteria
3-2-1 Commit
Personal Sales OS
90-Day Plan
Slide Deck — 7 slides
Slide 1
OPENING
The Pipeline Illusion — Full Funnel, Dry Close Rate
- Most reps have "a lot in the funnel" — but close <15% of it
- Volume is not a strategy. Quality velocity is.
- You can't manage a pipeline you haven't audited
PRESENTER NOTE · Ask: "What's your current close rate on opportunities in Stage 4+?" Most won't know. Then: "What should it be?" That gap is what today solves.
Slide 2
AUDIT
The 3-Question Deal Audit
- Q1: "Is the pain real and quantified?" If no → back to discovery
- Q2: "Is the economic buyer engaged?" If no → multi-thread now
- Q3: "Is there a clear next step with a date?" If no → stall or ghost risk
- Any "no" = deal needs action before it moves in your forecast
PRESENTER NOTE · Run this audit live on the room's deals. Pick 3 volunteers. Use their real pipeline. Every "no" gets a plan in the next 48 hours.
Slide 3
FRAMEWORK
Stage Exit Criteria — What Actually Moves a Deal
- Stage 3 → 4: Champion identified + pain quantified + decision process mapped
- Stage 4 → 5: EB engaged + MAP agreed + timeline confirmed
- Stage 5 → 6: Legal/procurement in + no open blockers + LOI / verbal commit
- Stage drift = activity without progress. Audit weekly.
PRESENTER NOTE · Many AEs move deals forward based on "it feels good." Stage exit criteria make it objective. If the criteria aren't met, the stage is wrong — and the forecast is lying.
Slide 4
FORECASTING
The 3-2-1 Commit Framework
- 3 = Total pipeline (all active opportunities)
- 2 = Best case (deals with EB engaged + MAP in place)
- 1 = Commit (deals that pass ALL stage criteria + close date confirmed)
- Commit must be deals you'd bet your month on, not just "looks good"
PRESENTER NOTE · Most reps inflate their commit because they're afraid to look light. Accurate forecast = trusted AE. Over-forecast = lose manager trust + bad self-awareness loop.
Slide 5
RHYTHM
The Weekly Pipeline Rhythm
- Monday: review every Stage 4+ deal against 3-question audit
- Wednesday: prospect block — 2 hours minimum, no exceptions
- Friday: update CRM, review commit vs. pipeline, plan next week's outreach
- Daily: 30 min trigger scanning + 5 personalized touches
PRESENTER NOTE · The reps who hit quota consistently are boring. They do the same things every week. Discipline beats inspiration every quarter.
Slide 6
OS
Your Personal Sales OS
- ICP doc: 3 sentences on who your best buyer is, in your words
- Outreach library: 10 battle-tested openers, updated monthly
- Discovery bank: L1/L2/L3/Trap questions, live doc
- Win/loss log: one-pager per deal closed or lost — what worked, what didn't
PRESENTER NOTE · Top AEs treat their sales process like a product. They iterate, document, and share. Your OS is your edge — build it deliberately, not accidentally.
Slide 7
CLOSE
Your 90-Day Plan from Here
- Month 1: run the full 6-week framework on every new deal
- Month 2: audit your pipeline with the 3-question test. Kill the ghosts.
- Month 3: track close rate by stage. Set a new benchmark. Beat it.
- PClub isn't luck. It's reps of a system, executed consistently.
PRESENTER NOTE · End the session here. Let the room sit with the 90-day plan. Ask: "What's the one thing from this program you'll do differently tomorrow?" Go around the room.
AE Playbook — Week 6 Self-Study
Stage Exit Criteria Reference Core Tool
| Stage | Exit Criteria — Must Have ALL |
|---|---|
| Stage 3 → 4 | Champion identified (passed 3-test) · Pain quantified in buyer's words · Decision process mapped · EB named (even if not engaged yet) |
| Stage 4 → 5 | EB directly engaged · Mutual Action Plan agreed · Demo completed with Check confirmation · Timeline and go-live date established |
| Stage 5 → 6 | Legal/procurement introduced · No open blockers · LOI or verbal commit in hand · All pre-close checklist items green |
Personal Sales OS Template Build This
Your ICP (3 Sentences)
Template
"My best buyer is [role] at [company type, size, stage]. They're usually triggered by [event or pain]. They buy when [condition]."
Write yours. If you can't, you don't know your ICP well enough to qualify fast.
Win/Loss Log Format
Win Log
- What triggered their buying decision?
- Who was the real champion?
- What moment won the deal?
- What would have lost it?
Loss Log
- At what stage did it actually die?
- What was the real objection?
- Where did I not multi-thread?
- What would I do differently?
90-Day Sprint
Month 1: Apply all 6 frameworks to every new deal. Month 2: Pipeline audit — kill anything that fails the 3-question test. Month 3: Track your close rate by stage, set a new personal benchmark, and build one new element of your Sales OS. Then do it again.
"The best AEs don't grind harder. They run better systems."
PClub is a process. Build yours.Field Plays — Week 6 · From the Field
Self-Sourced Pipeline System — 72% of $1.2M Closed Won
Field Research · Pipeline72% of $1.2M in closed won revenue in a single year was self-sourced. The premise: orgs run everyone through a generic 2-week onboarding then expect pipeline. Top AEs build their own system instead of waiting for it.
Narrow your account list — cut from 300 to 50 focus accounts. Depth beats breadth. Know your 50 accounts the way a founder knows their customers.
Non-negotiable prospecting block — time-blocked, every week, no exceptions. "Do a little prospecting every day so you never have to do a lot."
Study → Imitate → Iterate — find the top rep at your company. Run their openers, emails, sequences first. Only customise after you know why something works.
Multi-channel every prospect — email + cold call + LinkedIn + voicemail. Each touch builds on the last. One channel alone is too easy to ignore.
AEs who keep the prospecting discipline from their SDR days consistently outperform those who rely on inbound + SDR support. Pipeline is a personal responsibility, not a shared function.
AE of the Year — 4-Bucket Territory Strategy
Field Research · Territory PlanningNot inspiration — a literal territory plan in four buckets. Steal this structure for quarterly planning. "Treating AE of the Year like a campaign, not a hope."
Bucket 1 — Top of Funnel
- 7 unpenetrated focus accounts
- Full new plan of attack per account
- Multi-channel from day 1
Bucket 2 — Late-Stage
- ~7 deals in advanced stages
- Onsite visits to minimise risk
- Exec engagement on every deal
Bucket 3 — Renewals
- Major renewals at year-end
- Customer satisfaction + training first
- Turn them into active advocates
Bucket 4 — Closed-Lost
- Revisit when budget cycles change
- Map new leadership since the loss
- Changed priorities = new opening
Treat your territory like a product launch, not a waiting game. Every quarter has four distinct pipeline sources — most AEs only work two of them.
Winning Back a Churned Account — 7-Step Framework
Field Research · Account Strategy"You cannot be relevant in your outreach if you are only looking at basic notes from a CRM dropdown." Churn intelligence comes from call transcripts and institutional memory. Treat re-engagement like a new closed-lost motion.
Most AEs inherit a churned account with a CRM dropdown and a hunch. The ones who win it back come in with a real intelligence brief. That's the gap.
Week 6 Assignment
Pipeline Architecture
Complete before next session · Estimated time: 75–100 min
This Week's Tasks
Run the 3-question deal audit on every Stage 4+ deal in your pipelineFor each: What's the risk? What's the next step? What's my confidence? Write it down — don't just think it.
Build your personal stage exit criteria for Stages 3, 4, and 5List 3 hard criteria per stage that must be true before you move a deal forward. No handwaving.
Draft your 3-2-1 forecast for this week3 commit deals (close this week), 2 best-case deals (likely this month), 1 pipeline deal (next 30–45 days). Add one line of reasoning per deal.
Write your ICP in exactly 3 sentencesWho is the ideal customer, what problem do they have, and what makes them buy? No more, no less. Bring it to share.
Build a Win/Loss log entry for your most recently closed deal (won or lost)Include: what stage it moved fast, what stalled it, what you'd do differently, and one thing the competitor did well.
Bonus Challenge
Pick your single highest-risk open deal. Write a 1-page internal deal brief: deal context, power map, champion health score (1–5), risks, and your close plan with specific dates. Share it in your next 1:1 and ask your manager to poke holes in it.
Bring to Next Session
- Your completed 3-question audit results — we'll go deal by deal as a team
- Your stage exit criteria doc — we'll compare across reps and align on a shared standard
- Your 3-2-1 forecast — we'll pressure-test each deal together
- Your Win/Loss log entry — one rep will present theirs to the group
Live Example — Week 6 · Pipeline Audit
Exercise
3-Question Audit on 3 real deals
Questions
Pain quantified? · EB engaged? · Next step with date?
Rule
Any "No" = action required before this moves in forecast
Format
Run each deal in class — volunteers use their real pipeline
How to run this: Pick 3 deals from the class's real pipeline. Run the 3-question audit live. Every "No" gets a specific action in the next 48 hours. No deal moves in the forecast until all 3 are green.
Deal 1: Verve AI (Rohan Mehta) PASSES
✅
Q1 — Is the pain real and quantified?
Yes. "20–25 hrs/month provisioning, off-board incident that reached CEO, SOC2 audit in Q3." Said in their words. Priya confirmed it.
Yes. "20–25 hrs/month provisioning, off-board incident that reached CEO, SOC2 audit in Q3." Said in their words. Priya confirmed it.
✅
Q2 — Is the economic buyer engaged?
Yes. Priya attended the demo, responded positively, reviewing the MAP. Budget is under her approval threshold.
Yes. Priya attended the demo, responded positively, reviewing the MAP. Budget is under her approval threshold.
✅
Q3 — Clear next step with a date?
Yes. MAP review call Thursday. Close target end of month. Go-live end of May.
Yes. MAP review call Thursday. Close target end of month. Go-live end of May.
All 3 green. Commit deal. Forecast it.
Deal 2: FinStackCo (Arjun Sharma, IT Lead) FAILS Q2
✅
Q1 — Pain quantified?
Yes. "300 devices managed manually, 4 security incidents this quarter."
Yes. "300 devices managed manually, 4 security incidents this quarter."
❌
Q2 — Economic buyer engaged?
No. Arjun says "I handle IT decisions" — but they're 300 people, Series C. A $20K+ purchase doesn't get approved by an IT Lead alone.
No. Arjun says "I handle IT decisions" — but they're 300 people, Series C. A $20K+ purchase doesn't get approved by an IT Lead alone.
Action (48h): "Arjun, for a decision at this scale I want to make sure we're not creating a surprise in your approval process. Is there a finance or ops leader who typically gets looped in on vendor decisions?" Do not advance in forecast until EB is named.
⚠️
Q3 — Next step with date?
Soft. "Will circle back end of month" — no specific call, no MAP.
Soft. "Will circle back end of month" — no specific call, no MAP.
Action (48h): Send draft MAP and ask Arjun to confirm the EB before scheduling the next call. Two gaps, one move.
Q2 fails. Best Case only — not a commit until EB is engaged and confirmed.
Deal 3: MedPulse (Neha Kapoor, IT Manager) FAILS Q3
✅
Q1 — Pain quantified?
Yes. "12 hires/month × 3 hrs each = 36 hrs/month. HIPAA audit coming."
Yes. "12 hires/month × 3 hrs each = 36 hrs/month. HIPAA audit coming."
✅
Q2 — EB engaged?
Yes. CTO (Vijay) was on the first demo call, said "this looks like what we need."
Yes. CTO (Vijay) was on the first demo call, said "this looks like what we need."
❌
Q3 — Next step with date?
No. Last reply was 14 days ago: "we'll circle back next week." Two unanswered follow-ups. No MAP. No date.
No. Last reply was 14 days ago: "we'll circle back next week." Two unanswered follow-ups. No MAP. No date.
Action (48h): One value-add touch — don't chase. "Neha, put together a quick HIPAA access control checklist based on what you shared — wanted to send it before your audit prep kicks in. Happy to walk through it if there's a 20-min window this week." If no reply in 3 business days: move to at-risk. Stop forecasting as commit.
Q3 fails — ghost risk. One more value touch. No response = remove from commit, don't let wishful thinking distort your pipeline.
3-2-1 Forecast Summary
3 — Total Pipeline
₹54L
All 3 active deals
2 — Best Case
₹36L
Verve AI + FinStackCo (EB pending)
1 — Commit
₹18L
Verve AI only — all 3 criteria green
Key Takeaways
- Verve AI passes because the full 6-week system was executed — each week built on the last. No stage was skipped.
- FinStackCo fails Q2 because multi-threading was skipped. "Arjun handles IT decisions" is never true at 300 people. This surfaces in procurement and kills the deal late if not fixed now.
- MedPulse is ghosting. 14 days of silence after "we'll circle back" = deal is not real yet. One value touch. Then remove from commit — do not let it rot in the pipeline and distort your forecast.
- The 3-2-1 forces honesty. Most reps forecast all 3 as commit. Only Verve AI passes. Accurate forecast = trusted AE. Inflate it every quarter = the one thing that kills your credibility with your manager faster than a lost deal.