Sales Interview Questions for AEs and BDRs

Key things to listen for:

• Buyer-centric framing — the answer should be about what they learned about the prospect, not what they pitched
• Pain → impact → metric → economic buyer chain surfaces naturally
• MEDDICC (or equivalent) discipline — even if they don't name the framework, the structure should show through
• Specificity — concrete deal size, industry, role of the buyer, timeline

Good approach:

1. Names the company, ICP fit, and how the deal was sourced
2. Identifies the compelling event (why now, not Q4)
3. Describes the economic buyer and their personal/business metrics
4. Walks through the decision criteria and decision process they uncovered
5. Names one thing they got wrong and corrected mid-cycle

Red flags:

• Describes the pitch, not the discovery — "I showed them our integration with Slack…"
• Cannot name the economic buyer or the compelling event
• Every deal sounds the same — no specifics
• Takes full credit and never mentions the champion or SE

Key things to listen for:

• Names a framework — MEDDICC, MEDDPICC, SPICED, BANT, GPCT, Sandler — and explains it in their own words
• Application over recitation — they can show how they actually use it on a live call, not just spell out the letters
• Knows when to compress or skip steps — a self-serve $5k deal doesn't need full MEDDICC

Good approach:

• MEDDICC (enterprise default): Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion, Competition
• SPICED (modern SaaS): Situation, Pain, Impact, Critical Event, Decision
• BANT (transactional): Budget, Authority, Need, Timeline — fast but shallow

Strong AEs treat the framework as a checklist for risk, not a script. They surface gaps ("I don't know the economic buyer yet") and turn each gap into a next-call objective.

Red flags:

• Cannot name a framework at all
• Recites letters but cannot demonstrate application
• Uses the framework as an interrogation list during discovery calls
• Believes the framework alone qualifies a deal — never updates it after kickoff

Key things to listen for:

• Disqualifies fast — the best AEs treat their pipeline like a portfolio and aggressively cut deals that won't close
• Has explicit kill criteria — "no economic buyer = no deal," "no compelling event = parking lot"
• Comfort with pushing back on internal pressure to keep weak deals in the forecast

Good approach:

1. Define the disqualification triggers up front: missing economic buyer access by call 3, no quantified pain, no competitive displacement story, no compelling event tied to a date
2. Apply them at fixed milestones, not whenever the deal feels stuck
3. Move disqualified deals to a nurture cadence rather than killing the relationship — many come back
4. Re-qualify aggressively after every stage transition — fresh information should change the score

Red flags:

• "I never disqualify, I always find a way" — this AE's forecast will rot
• Confuses 'haven't replied in 2 weeks' with 'disqualified' — they're not the same
• Has no explicit criteria, just gut feel
• Keeps deals in Commit out of habit or fear of pipeline coverage conversations

Key things to listen for:

• Does not accept the timeline at face value — explores whether 'no urgency' is real or rehearsed
• Probes the compelling event — what changes between now and Q3?
• Creates urgency through cost of inaction, competitive pressure, or quantified pain — not artificial deadlines

Good approach:

1. Acknowledge the timeline: "Got it, Q3 is the budget window."
2. Probe the cost of doing nothing for the next 4 months — what does that translate to in lost revenue, churn, manual hours, or competitive exposure?
3. Surface the status quo cost: "What's it costing you today to operate without this?"
4. Test for a silent compelling event — board meeting, hiring plan, contract renewal, regulatory deadline
5. If urgency truly doesn't exist, set a clear next step tied to the buyer's calendar ("Let's reconnect mid-Q2 with a build-out plan") and move on without forcing it

Red flags:

• Manufactures fake discount deadlines to force a close
• Walks away on the first "no urgency" without probing
• Promises EOQ pricing for a deal that has no chance of closing in EOQ

Key things to listen for:

• Multi-threading discipline — never relies on a single champion to relay information up the chain
• Asks the champion directly with a structured question, not vaguely about "who's involved"
• Uses external signals — org charts, LinkedIn, press releases, hiring patterns — to triangulate the EB

Good approach:

1. Ask the champion directly: "Walk me through how a decision of this size typically gets approved here. Who signs the contract?"
2. Use a mutual close plan as the artifact that surfaces the EB — every milestone needs an owner, including the signature step
3. Multi-thread early: ask the champion to introduce you to the EB's direct report, peer in finance/procurement, or end-user team lead — three contacts beats one champion every time
4. Validate via independent sources: LinkedIn org chart, recent press, internal hiring announcements, conference speaker lists
5. If the champion blocks access, treat that as a qualification signal — the champion may not actually have influence

Red flags:

• Emails the CEO cold without the champion's knowledge — torches the deal
• Accepts "my boss will sign off" without ever talking to the boss
• Conflates 'the person sponsoring the project' with 'the person with budget authority' — often different people in enterprise

Key things to listen for:

• Intellectual honesty — they updated their qualification in real time rather than forcing the deal into a template
• Curiosity over confirmation bias — they kept asking questions even when the answers stopped supporting their hypothesis
• Self-awareness — names what they almost missed and why

Good approach:

A strong story has three parts:

1. The starting hypothesis — "I thought this was a 50-seat mid-market deal, ICP-perfect, 6-week cycle."
2. The pivot moment — "On the call the VP mentioned a parallel evaluation with [competitor] that was further along than I knew, and budget was already 80% allocated to a different line item."
3. The response — they reframed the deal: "I deprioritized it from Commit, kept the relationship warm, and refocused effort on three other late-stage deals."

The best version shows the AE asking one more question instead of pitching when the deal started to look weaker.

Red flags:

• Cannot recall a deal where their view changed — implies confirmation bias
• 'Pivot' is just discovering a new use case for the same pitch
• Frames the new information as 'the prospect being difficult' rather than as data they should have surfaced sooner

Key things to listen for:

• Pain = the root business problem that costs the company money, time, customers, or risk
• Symptom = the surface complaint the buyer leads with — "our onboarding takes too long," "our reports are wrong"
• Strong AEs always dig from symptom → pain → quantified impact

Good approach:

Example chain:

• Symptom: "Our sales team complains the CRM is slow."
• Question: "What does slow CRM cost you?"
• Pain: "Reps log activity at the end of the week instead of after each call, so pipeline data is 5 days stale."
• Question: "What decisions do you make on that data?"
• Quantified impact: "Our weekly forecast call is wrong 30% of the time, and that's pushed two end-of-quarter misses into red."

The pain isn't 'slow CRM' — it's forecast accuracy at the board level, which is a CRO-level priority worth a multi-six-figure spend.

Red flags:

• Sells against the symptom — "we'll make your CRM faster"
• Never asks the second or third 'why' to dig past the surface complaint
• Cannot quantify impact in dollars, hours, or risk

Key things to listen for:

• Reads the room — notices disengagement signals (short answers, screen-off, distracted)
• Reframes the conversation rather than doubling down on the script
• Swaps to peer-style dialogue — shares a customer story, asks for their reaction, makes it two-way

Good approach:

1. Name what's happening, gently: "I'm asking a lot. Let me share what I'm trying to understand and why — and you can tell me if there's a faster way."
2. Trade information for information — share an anonymized customer story or a benchmark that earns the next question
3. Compress — collapse three questions into one, signal you respect their time
4. Reset the agenda mid-call if needed: "Want me to walk you through what I'm seeing in similar companies instead?"
5. Offer a follow-up async — "Would it work if I sent two short questions over email after this?"

Red flags:

• Keeps drilling through the script while the prospect visibly checks out
• Blames the prospect afterward ("they wouldn't open up") instead of owning the call
• Sends a 9-question form after the call as a recovery — makes it worse

Key things to listen for:

• Time-blocking — prospecting is calendared, not squeezed in between meetings
• Channel balance — calls, emails, LinkedIn, video, referrals — not just one channel
• Concrete numbers — "50 dials, 100 emails, 30 LinkedIn touches" — quantified, not 'I work my list'
• Triaging discipline — replies, demo prep, and admin live in different time blocks than fresh prospecting

Good approach:

A strong BDR day looks roughly like:

• 8:00 – 9:30 — research and list prep for the day's accounts
• 9:30 – 11:30 — power hour: cold calls, no email tab open
• 11:30 – 12:30 — LinkedIn engagement, voice notes, video DMs
• 1:30 – 3:30 — second call block + same-day replies to morning outreach
• 3:30 – 4:30 — cold email sequencing for tomorrow's list
• 4:30 – 5:00 — CRM hygiene, next-step logging, manager 1:1 prep

Red flags:

• 'Whatever the day looks like' — no structure
• Replies dominate the day — never leaves time for net-new prospecting
• Spends 4 hours/day researching, 1 hour calling — research is procrastination

Key things to look for:

• Short — under 90 words. Mobile-readable in one screen
• Specific — references something only that VP would care about (recent hire, tech stack signal, conference talk)
• One clear CTA — a single 15-minute call, or one question to reply to
• No filler — no "Hope this finds you well," no 5-sentence company pitch
• Subject line earns the open — outcome-focused, 4–7 words, no clickbait

Strong example:

Subject: Cutting deploy time at 200-eng orgs

Hi Priya — saw your team posted three SRE roles last week. Companies your size that go from 8 to 25 engineers usually hit the same wall: deploys still funnel through a handful of senior people, and CI minutes balloon 3–5x.

We helped [Customer A] cut deploy time from 14 min to 90 sec across 180 engineers in 6 weeks.

Worth a 15-min look at how they did it? Or if you've already solved it, I'd love to know what worked — happy to swap notes.

— Alex

Red flags:

• 6-paragraph email with three CTAs ("book a call OR reply OR check our pricing page")
• Generic personalization ("loved your recent post!") with no specifics
• Mentions only product features, not buyer outcomes
• 'Just checking in' subject line

Key things to listen for:

• Time-boxed — 5 to 10 minutes per prospect for outbound, not 30
• Repeatable checklist rather than ad-hoc scrolling
• Trigger-event awareness — funding, hiring, leadership changes, product launches, earnings
• Connects research to a hook, not just "facts I know about them"

Good approach (5-minute version):

1. LinkedIn (90 sec): title, tenure, recent posts they've authored, recent role changes in the team
2. Company news (60 sec): funding announcements, exec hires, press releases, 10-Q if public
3. Tech stack signals (60 sec): BuiltWith, job postings (great for tech tells), Stack Share
4. Hiring patterns (45 sec): how many job posts open for the prospect's function? Direction of headcount?
5. Hook synthesis (45 sec): write one sentence — the compelling hook — before opening Gmail

Red flags:

• 30 minutes scrolling LinkedIn = procrastination disguised as preparation
• Cannot articulate the hook in one sentence after research
• Uses the same hook ("I saw you're hiring") for every prospect — not personalized
• Skips research entirely on tier-1 ICP accounts

Key things to listen for:

• Diagnoses systematically — list, message, channel, timing — rather than just rewriting copy
• Asks for help — listens to peer call recordings, requests manager feedback, looks at top performers' sequences
• A/B tests rather than swapping everything at once

Good approach:

1. Audit the list first — bad list quality kills reply rates more than bad copy. Are these in-ICP? Right level? Right industry segment?
2. Compare against a top performer's sequence in the same role — subject lines, openers, CTAs, send timing
3. Test one variable at a time — change the subject line for one cohort, keep the body. Then change the opener. Then the CTA.
4. Listen to peers' calls — top BDRs often run a wildly different opener than what their sequence implies
5. Switch channels for half the list — pure email → email + call + LinkedIn touch
6. Set a 2-week target — "I want to be at 2% by end of next sprint and 3% by month's end. Here's my plan."

Red flags:

• 'The list is bad' — blames inputs without proving it
• Rewrites everything at once with no way to measure what helped
• Goes silent and waits to be reassigned
• Asks for help only after a quarter of missed numbers

Key things to listen for:

• Does not send the deck blindly — unqualified collateral kills more deals than it opens
• Asks one qualifying question or proposes a 15-min call instead
• Treats 'send me info' as a soft brush-off worth one more probe

Good approach:

Strong BDRs reply with something like:

Happy to send the right thing. We work with three different angles — [outcome 1] for [persona A], [outcome 2] for [persona B], and [outcome 3] for [persona C]. Which one is closest to what you're looking into? Or if 15 minutes is easier, I can show you the relevant slice live this week.

This does three things:

1. Anchors specificity — they have to pick a use case, which surfaces their pain
2. Trades a question for the deck — they can't get info without telling you something
3. Offers a low-friction alternative — the call is a softer ask than the deck

If they truly insist on a deck, send a 2-page customer-story PDF, not the 40-slide corporate deck. It carries the buyer further down the funnel without leaking your full pitch.

Red flags:

• Attaches the 30-slide deck on the first reply
• Asks no qualifying question — pure send-and-pray
• Sends the deck and then disappears for a week

Key things to listen for:

• Two-tier (or three-tier) approach — not one-size-fits-all
• Ties tier to deal size and win-rate math, not gut feel
• Templates exist — but at the right layer (middle of the email, not the opener)

Good approach:

• Tier 1 (top 50 ICP accounts): hand-crafted, multi-channel, account-based sequences. Often 30+ minutes per prospect. Reserved for accounts where a single win is worth 10x average ACV.
• Tier 2 (in-ICP, medium fit): semi-personalized — strong opener and CTA, templatized body, 5–10 minutes per prospect. The bulk of an AE's outbound day.
• Tier 3 (broad ICP, top-of-funnel awareness): automated sequences with light variable insertion. Heavy volume, low expectation per prospect — designed to keep the brand in front of the market.

In SMB the mix tilts toward Tier 3 (volume wins). In Enterprise it tilts to Tier 1 (a single logo justifies the time). The mistake is using the same mix for both.

Red flags:

• Pure spray-and-pray with no tiering
• Hand-crafts every email — burns 4 hours/day on prospecting math that doesn't pay
• Cannot articulate the math: 'how many touches per closed deal at each tier?'

Key things to listen for:

• Acknowledges the objection without panic-discounting
• Probes — "compared to what?" — surfaces whether the comparison is competitor pricing, internal budget, ROI hurdle, or anchoring tactic
• Re-anchors on value before any pricing discussion
• Never discounts first — discount is the last lever, not the first

Good approach:

1. Acknowledge: "I appreciate you raising this — I'd rather hear it now than at signature."
2. Probe: "Help me understand — too high compared to what? Another vendor, your internal budget, or the ROI we've discussed?"
3. Listen for the real concern — three different problems require three different responses
4. Re-anchor on quantified value: "We agreed the impact was $X. The investment is Y. That's an 8x return in year one. Where's the disconnect?"
5. Offer trade-offs, not price cuts: longer term length, deferred payment, scoped pilot, case-study consent in exchange for a lower price
6. Hold the line — confidence under price pressure separates senior AEs

Red flags:

• Immediate 10–15% discount without probing
• Cannot articulate ROI — relies on "we're worth it"
• Apologizes for the price
• Caves to the first objection and then has nothing left for procurement

Key things to listen for:

• Validates the choice — never trashes the competitor
• Curiosity over bashing — asks what's working and where the gap is
• Plays the long game — comfortable nurturing through a renewal window

Good approach:

1. Validate: "Makes sense — they're a solid choice for [use case]. A lot of teams start there."
2. Probe usage: "What do you love about it? What do you wish it did differently?"
3. Find the gap — every competitor has weak spots. Their gap is your wedge.
4. Quantify the cost of the gap — "You said the reporting is manual. What does that cost the team in time per week?"
5. Plant a seed, don't force a switch: "When are you reviewing the renewal? Worth a 20-minute look 90 days before, so you have leverage either way."
6. Track the renewal date in CRM and re-engage 90–120 days out — that's when buyers actually shop

Red flags:

• Bashes the competitor — torches credibility and the relationship
• Drops the deal as soon as 'we use someone else' is mentioned
• Doesn't track the renewal date — loses the only realistic window
• Tries to displace mid-contract without a compelling event

Key things to listen for:

• Multi-channel re-engagement — email, LinkedIn, phone, video DM — not just 'just checking in' emails
• Delivers new value each touch — not the same nudge five times
• Comfortable with a clean break-up email as the last step

Good approach:

A disciplined re-engagement plan over 14–21 days:

1. Day 2: short email with a relevant resource (case study from a similar customer, benchmark report). No CTA, just value.
2. Day 5: LinkedIn voice note or video DM — different channel, different format
3. Day 8: phone call — many ghosts are inbox triage casualties, not real silence
4. Day 12: email to the champion's peer or boss — multi-thread the deal
5. Day 18: break-up email — "Closing the loop. Should I assume now isn't the right time, or did this slip through your inbox?" Often gets a reply when nothing else does.
6. If still silent: move to a quarterly nurture cadence with industry value drops

Red flags:

• Seven 'just checking in' emails in ten days — desperate and annoying
• Same channel and same script every time
• Gives up after one follow-up
• Sends a guilt-trip email ("I've reached out three times and you haven't replied")

Key things to listen for:

• Does not negotiate alone — pulls in the champion immediately
• Trades concessions — discount only in exchange for something measurable (term length, multi-year, payment terms, case study, reference call)
• Has a walk-away point — knows what discount level breaks the deal economics
• Anticipates procurement rather than being surprised by them

Good approach:

1. Loop the champion in fast: "Procurement is asking for 30%. Before I respond, I want to understand — is this their standard opening ask, or is there a budget constraint I should know about?"
2. Reframe the conversation: procurement is paid to negotiate, not to evaluate value. The champion already bought the value.
3. Trade, don't concede:
   • Discount for 3-year commit instead of 1
   • Discount for payment annually upfront instead of quarterly
   • Discount for case-study consent and 2 reference calls
   • Discount for legal turnaround in 5 days with the standard MSA
4. Stagger the trades — never offer the full discount in one move
5. Have a walk-away — if the deal economics break, kill it cleanly. A bad deal hurts ramp and renewal more than no deal.

Red flags:

• Caves to the full discount in the first reply
• Negotiates alone without engaging the champion
• Gives discounts with nothing in return
• Doesn't know the floor — discounts past what the business can absorb

Key things to listen for:

• Probes the real reason — budget freeze, headcount freeze, priority shift, M&A, or simply a soft "no" wrapped in a corporate excuse
• Doesn't immediately accept the freeze at face value
• Looks for alternate champions at the budget-approving level
• Pauses the deal cleanly if it really is dead — doesn't burn it

Good approach:

1. Empathize first: "Got it — that happens a lot right now. Let me make sure I'm reading this right."
2. Probe the scope of the freeze: "Is it all new vendors, or just new tooling categories? What about existing relationships expanding scope?"
3. Probe the duration: "Is this through end of quarter, end of fiscal year, or open-ended?"
4. Probe the level: "Who initiated this — CFO, CEO, board?" The answer tells you whether to escalate or wait.
5. Find the budget-approver: if the freeze is real, the only person who can override it is whoever ordered it. Multi-threading or a peer-customer reference call may help.
6. If genuine: pause the deal cleanly with a re-engagement date, deliver value during the pause (industry reports, customer intros), and revisit when the freeze lifts.

Red flags:

• Pushes harder against the freeze, alienating the champion
• Goes silent and lets the deal die without re-engagement plan
• Doesn't probe — accepts the freeze and moves on
• Tries to circumvent the freeze through unauthorized channels and gets the champion in trouble

Key things to listen for:

• Clear, defensible definitions for each forecast category
• Honest admission that the most common discipline failure is moving hope-deals into Commit to look good
• Explicit criteria for moving between categories — not gut feel

Good approach:

• Commit — will close this period with high confidence. Mutual close plan signed, procurement engaged, legal in motion, EB verbalized intent. If anything in the deal slipped, it would surprise you.
• Best Case — meaningful upside. Everything is qualified but at least one critical milestone is unresolved (procurement still circling, signature blocked on internal approval, EB not yet looped in this cycle).
• Pipeline — qualified opportunities that could realistically close in the next 1–2 periods. Not committed to this one.

Where discipline breaks:

1. AEs put hope-deals in Commit to manage their manager's perception — looks great until the deal slips and the credibility tax compounds
2. "Slipped from last quarter" deals get auto-recategorized as Commit because they were 'almost done' — usually a sign they were never close
3. Loose definitions across the team — Commit means something different per AE

Resisting pressure to misrepresent: Strong AEs respond — "I'd rather report this honestly and recover with the next deal than burn forecast credibility. Here's what would have to happen for this to move to Commit."

Red flags:

• Every deal magically lands in Commit two weeks before EOQ
• Forecast is based on gut, not on stage criteria
• AE inflates to please the manager — flags later when it's too late

Key things to listen for:

• The hard work was done in weeks 1–10, not weeks 11–12. EOQ should be execution, not heroics.
• Mutual close plans with milestone-level visibility
• Procurement and legal engaged early — not on day 75
• Daily stakeholder syncs in the last 7–10 days

Good approach:

Weeks 9–10:

• Mutual close plan signed for every Commit deal — "by Date X, signature; Date X-3, procurement; Date X-6, redlines back"
• Pre-negotiate redlines with legal so contract isn't the bottleneck
• Procurement intro made for any deal >$50k ACV

Weeks 11–12:

• Daily 15-min sync with each champion — "What's the next blocker?"
• Weekly stakeholder roll-up to manager — color-coded against the close plan
• Pre-built fallback paths — what scope cut still gets us signed?

Final 3 days:

• Stop opening new fronts; finish what's qualified
• No panic discounts — discount discipline matters most here
• Verbal commits get a written confirmation — "Just to confirm I heard you: signature by Friday EOD."

Red flags:

• Panic-discounting on the Friday of the last week of the quarter
• Discovering procurement exists in the last 5 days
• 'Last-minute hero' deals that close on the 31st — usually rebooked back to next quarter as churn or buyer's remorse
• New logos brought into Commit in the final week

Key things to listen for:

• Joint document — both sides own it, both sides sign off
• Reverse-engineered from the desired signature date back to today
• Milestone-level detail — owner, date, dependency
• Used as a qualification test, not just project management

Good approach:

A strong mutual close plan includes:

1. Target signature date — agreed by champion and EB
2. Backward-planned milestones — security review, legal redline, procurement intake, EB approval, signature
3. Owners — name, not 'their team' or 'us'
4. Dates — committed, not 'sometime in March'
5. Open risks — explicitly listed (e.g., 'CFO out of office last week of March')
6. Success criteria for the pilot/POC if applicable

Share it as a Google Doc, walk through it on a call, get the champion to commit to it on record. Use it as a forecasting truth-teller — if a milestone slips by 2+ days without an updated plan, the deal is sliding.

Refusing to engage — if the champion won't engage with the close plan, that's a strong qualification signal. Either the champion doesn't have the influence to align stakeholders, or the deal isn't real yet.

Red flags:

• Close plan is unilateral — the AE built it without the buyer's input
• No owners, no dates, just "work back from end of quarter"
• Plan never updated after kickoff
• Used as a pressure tool rather than a coordination artifact

Key things to listen for:

• Has explicit re-qualification criteria — not gut feel
• Identifies the rotting metric — what specifically has gotten worse since first qualified?
• Willing to demote or kill rather than keep slipping

Good approach:

When a deal slips a third time, run a hard re-qualification:

1. MEDDICC audit — score every letter today versus when first qualified. Where's the regression?
2. Identify the rotting metric:
   • Lost champion access? — usually fatal
   • Compelling event evaporated? — demote to Pipeline
   • Budget pushed to next FY? — re-stage to next quarter, don't kill
   • Competitor selected? — usually dead; ask for the post-mortem
3. Test the champion's commitment — "What's the realistic path to signature in the next 30 days? If you were in my seat, would you keep this in Commit?"
4. Make a call — demote to Best Case, demote to Pipeline, or close-lost with reason
5. Document the decision and reasoning in CRM — future you will thank present you

Communicating the demote: "I demoted [Deal X] from Commit to Best Case. Champion has slipped twice on procurement intro and I can't get an EB call. I'd rather report this honestly now than miss the number cold next month."

Red flags:

• Keeps the deal in Commit on the basis of 'they said next month'
• Has no explicit criteria for demoting
• Never closes deals as 'closed lost' — perpetual late-stage zombies
• Slips quietly without telling the manager until the deadline

Key things to listen for:

• Discount is earned, not offered
• Trades concessions for the discount — never gives it away
• Knows the floor — has a clear walk-away point
• Recognizes that discounting an unqualified deal doesn't save it — it just moves the close-lost from this month to next

Acceptable discounts:

• Multi-year commitment — 3-year locks justify 10–15% off list
• Payment terms — annual upfront vs quarterly
• Reference call or case study consent — measurable marketing value
• Expansion commitment — pilot to enterprise rollout in 12 months
• Pioneer customer pricing for a new product line — they take risk, you discount

Red flag scenarios:

• Discount to 'save' a deal that isn't qualified — the discount won't close it
• Discount before the EB has verbalized commitment — burns the lever before you need it
• Discount given without a trade — sets the precedent for renewal and expansion
• Discount because the buyer asked, with no business reason — trains them to ask harder

Strong AEs respond to a discount ask with: "What about the proposal isn't working? Let's solve the actual issue before we touch price."

Red flags:

• Defaults to discount as the first negotiating lever
• Cannot articulate when a discount is okay vs. not
• Discounts every deal at EOQ — predictable to procurement, kills future leverage

Key things to listen for:

• Has a clear menu of trades — not improvising on the call
• Knows which trades have real value to the business and which are cosmetic
• Sequences trades — never offers the best one first

Common trades, ranked by usefulness:

1. Multi-year commit (highest value) — locks revenue, reduces churn risk, justifies the largest discount
2. Annual upfront payment — cash flow + reduces collections friction. Often worth 5–8% off list
3. Pioneer-customer / case-study consent — marketing gets a named logo and a quote. Worth 3–5%
4. Reference calls — 2–3 calls/year with prospects. Worth 2–3%
5. Expansion commitment — written intent to expand to other teams or modules at a defined date
6. Faster legal turnaround — accept your standard MSA without redlines = saves 4–6 weeks of cycle time
7. Co-marketing — joint webinar, conference appearance — softer, harder to enforce

Lower-value but still useful:

• Pilot scope reduction (start with X seats, expand at Y)
• Quarterly payment instead of monthly
• Beta access feedback commitment

Avoid trading away:

• Termination-for-convenience clauses — eats forecast confidence
• Most-favored-nation pricing — handcuffs you for the entire customer life
• Custom SLAs you can't measure — operational nightmare

Red flags:

• Improvises trades on the call without manager guidance
• Treats every trade as equal — gives away the most valuable lever first
• Trades for cosmetic concessions (a logo on a slide) instead of real ones

Key things to listen for:

• Confidence under pressure — separates senior AEs from mid-level
• Value re-anchoring — pulls the conversation back to outcomes
• Willingness to walk — credible only if real
• The buyer felt they 'won' something — even if it wasn't price

Strong story shape:

1. Setup — deal size, buyer profile, the discount ask
2. The pivot moment — the moment they decided not to discount and why (usually: "the quantified ROI was 6x, discounting would have signalled we didn't believe our own number")
3. The trades — what they offered instead (term length, payment terms, faster onboarding, reference logo, scoped pilot extension)
4. The close — what the buyer said when they signed without the discount ("You're the first vendor that didn't immediately fold. We needed to see that.")
5. The follow-up impact — renewal a year later was higher, no discount precedent set

Why deals close at full price:

• The AE built enough value certainty that the discount felt cosmetic
• The competitive alternatives were weaker once compared head-to-head
• The cost-of-inaction was higher than the discount would have offset
• The buyer felt respected, not nickel-and-dimed

Red flags:

• Cannot recall ever holding price — either inexperienced or undisciplined
• 'I just refused to discount' with no value re-anchor or trades — usually means they got lucky once
• Claims to never discount, ever — equally unrealistic in B2B

Key things to listen for:

• Does not promise the roadmap — vague 'yes' commitments destroy renewal and breed customer success burnout
• Quantifies the gap — what's the actual size of the feature, and what does the buyer want it for?
• Scopes a workaround if the deal is meaningful
• Gets product/engineering on a call if the deal warrants it

Good approach:

1. Probe the underlying need: "What's the use case driving this? Tell me what the workflow looks like today." Often the buyer wants an outcome that can be achieved another way.
2. Quantify the gap honestly: "This is a 3-month build, not 3 weeks. I won't pretend otherwise."
3. Scope a workaround: integration via Zapier, manual process for the first 60 days, services engagement to bridge
4. Loop in product if the deal is >$100k ACV — a 20-minute call with PM can change the buyer's perception completely
5. Trade for early-access design partnership if the feature is genuinely on the roadmap and the buyer is influential
6. If the gap is fundamental and the workaround doesn't hold — walk. A bad-fit deal damages CSAT, renewal, and reference value

Red flags:

• Promises the feature is 'coming next quarter' to close — even if PM has never heard of it
• Buries the gap in a contract clause hoping the buyer doesn't notice
• Says yes verbally, no in writing — sets up a renewal disaster
• Never escalates to product even when the deal warrants it

Key things to listen for:

• Specific diagnosis — what was the actual breakage? (pipeline coverage, win rate, ASP, cycle time)
• Specific change — what did they do differently in the next quarter?
• Measurable outcome — did the change work? With numbers, not vibes.
• Takes responsibility — doesn't blame the territory, the product, marketing, or the comp plan

Strong story shape:

1. The miss — "I closed 65% of quota in Q2. Coverage was 2.4x, should have been 3.5x."
2. The diagnosis — "My win rate held at 28%, but I didn't have enough pipeline to absorb the normal slippage."
3. The change — "I rebuilt my outbound cadence with 2 hours of blocked prospecting daily, and I asked my BDR to lift my coverage to 4x."
4. The result — "I hit 112% in Q3 and 96% in Q4 — coverage held at 3.8x."

The AE owns the diagnosis without theatrical self-flagellation. The lesson is operationally specific, not motivational.

Red flags:

• Blames the market, the product, marketing leads, the comp plan, the territory
• Cannot diagnose specifically — 'I just needed to work harder'
• The 'change' is vague ('I refocused on activity')
• Never measured whether the change worked
• Has never missed quota — either too junior to have been tested, or evasive

Key things to listen for:

• Remembers the feedback specifically — not in vague terms
• Can name the behavior change they made in response
• Credits the manager — doesn't minimize the feedback or paint themselves as already knowing
• Time has passed — they can describe the result, not just intent

Strong response shape:

1. The feedback: "My manager told me I was talking too much in discovery calls — I was answering questions before they were asked, which was killing the buyer's chance to articulate pain."
2. The initial sting: "It hit hard because I'd been getting compliments on rapport, and I conflated rapport with talking. I sat with it for a couple of days."
3. The change: "I started recording calls and tracking my talk-time ratio. Goal: under 40% in discovery. I shared the metric with my manager weekly."
4. The result: "Talk time dropped from 65% to 38% over two months. My conversion from discovery to demo went from 45% to 62%."

Notice the structure: feedback, reaction, action, outcome — all specific.

Red flags:

• "I don't really get critical feedback" — either evasive or coachable to nobody
• Frames the feedback as the manager's misunderstanding, not their behavior
• Cannot name the change they made
• 'I disagreed but I tried' — passive compliance is not coachability

Key things to listen for:

• Empathy for the other team's incentives — understands why marketing/CS see things differently
• Data-driven resolution — uses pipeline data, NPS data, churn data rather than gut
• Escalates constructively when needed — not 'going around' the other team
• No us-vs-them framing

Common conflict types:

• AE vs. Marketing — "the leads you sent are unqualified" / "sales doesn't follow up"
• AE vs. CS — "this customer is unhappy because the AE oversold" / "CS isn't supporting expansion"
• AE vs. SE/Product — "we promised something we can't build" / "sales is fabricating the roadmap"

Good approach (example: AE vs. Marketing):

1. Acknowledge the other team's pressure — "I know your MQL targets are tight this quarter."
2. Bring data — "I worked 47 of the 62 MQLs from your last campaign. Conversion to SQL was 8%, vs. the 18% we see from the [other campaign]. Here's the pattern I'm seeing in the unqualified ones."
3. Co-design a fix — "Could we add a job-title filter on the form, and could I review 10 randoms before the next campaign goes live?"
4. Loop the leader in only if escalation is needed — and frame it as a process question, not a finger-point

Red flags:

• Blames marketing publicly — torches the relationship
• Ignores the other team's incentives — "that's their problem"
• Won't share their own data when asked
• Escalates to leadership without trying to resolve directly first

Key things to listen for:

• Structured 30/60/90 plan — not 'ramp up and start selling'
• Product mastery is a deliberate effort, not background absorption
• ICP study — they learn the customer, not just the product
• Peer shadowing — they call out specific people they want to learn from
• Manager alignment on what success looks like at each milestone

Strong 30/60/90:

Days 1–30 (Learn):

• Product walkthrough with every PM and SE
• Read the last 20 won-deal call recordings and last 10 lost-deal post-mortems
• Shadow 5 calls with top performers (discovery, demo, negotiation, close, churn save)
• Build their own deck — never use someone else's word-for-word
• Memorize the ICP and the top 3 competitive landmines

Days 31–60 (Run):

• Run their first 20 discovery calls with weekly manager review of recordings
• Build pipeline coverage to 3x quota
• Establish a personal outbound cadence and stick to it
• Get their first deal into proposal stage

Days 61–90 (Close):

• Close their first deal (or two)
• Calibrate forecasting with the manager — first Commit attempt
• Identify one process improvement they want to own (e.g., competitive battlecards)

Red flags:

• 'I'll figure it out as I go' — no plan = no ramp
• Spends 90 days in training and never picks up a phone
• Skips reading lost-deal post-mortems
• No manager alignment on expectations

Key things to listen for:

• Tests ethics under quota pressure — the best AEs walk away from deals that would damage the customer or the company
• Specific reasoning — bad fit, can't deliver value, post-sale cost too high
• Comfort with short-term miss in exchange for long-term integrity

Strong story shape:

1. The setup — "Deal was a $180k ACV, mid-Q3, would have closed me at 96% to quota."
2. The red flag they spotted — "In the final pricing call, the champion was framing internal expectations very differently from what our product actually does. Reporting capabilities he was selling internally weren't going to ship for another 9 months."
3. The decision — "I called my manager, walked through the gap, and recommended we either descope to what we could actually deliver in 90 days or pause the deal. The buyer wasn't willing to descope."
4. The outcome — "We pulled out. I missed the quarter by 7 points. A year later they came back, re-engaged with the right scope, and we closed a cleaner $240k deal that renewed at 130%."

The point: the AE traded a missed quarter for a healthier renewal book and a referenceable customer.

Red flags:

• "I never walk away" — either junior, or willing to ship bad deals
• Walks away too easily — never engages with descoping or champion conversations first
• Frames the walk-away as the buyer's fault, not their own qualification gap
• Has no story at all — never had the situation, or never recognized it

Key things to listen for:

• Updates the CRM in real-time or end-of-day, not end-of-week
• Knows which fields matter — next step + date, MEDDICC fields, stage rationale, competition, champion contact
• Updates are decision-relevant, not box-checking

Good approach — after every call, log:

1. Next step and date — the single most important field. If there's no next step, the deal is stuck.
2. MEDDICC fields: any new info on metrics, EB access, decision criteria, decision process, identified pain, champion strength, competition
3. Contacts touched — name, role, sentiment
4. Stage transition rationale — why this deal moved (or didn't) — three bullets max
5. Risks — what could still derail this?
6. Champion-test indicators — did the champion do what they said they'd do since the last call?

Time budget: 5–8 minutes of CRM update per 30-minute call. Anything more is over-engineering; anything less is decay.

Why hygiene matters:

• The manager's forecast review is only as good as the CRM
• Pattern recognition over time depends on consistent data — you'll know your average cycle time, common loss reasons, and conversion math only if you log it
• Account handoffs (to CS, to the next AE) are smooth only with a clean trail

Red flags:

• 'I update at end of week' — by then half the call detail is lost
• Only updates the fields the manager checks — gaming the process
• Doesn't log next-step date — forecast becomes hope
• Updates take 30 minutes per call — perfectionism kills selling time

Key things to listen for:

• Personalizes the opener and the close, templatizes the middle
• Audits reply patterns and rotates language periodically
• Treats sequences as a starting point, not a finished product
• Listens to peers for what's working in the field, not just what the marketing team built

Good approach:

1. The opener is always personalized — a specific reference to the prospect, their company, a recent event, or a peer-customer outcome. This is the make-or-break sentence.
2. The body can be templated — the value prop, the customer outcome, the proof point. These rarely change per prospect.
3. The CTA is personalized to the persona — a CFO gets a different CTA than a VP of Engineering.
4. Audit your reply rate weekly:
   • Are subject lines getting opens?
   • Is the first sentence holding attention (reverse-engineer from delivery / reply rates)?
   • Are CTAs converting to bookings?
5. Refresh templates monthly — the moment a sequence starts feeling stale to you, it's already stale to recipients
6. A/B test one variable at a time — never rewrite a whole sequence at once

The rule of thumb: if a recipient could find the same email in their inbox sent to 20 other people, the opener wasn't personalized enough.

Red flags:

• 'I just use the template as-is' — guaranteed mediocre reply rates
• Never audits reply patterns — runs the same sequence for a year
• Personalization variable is {{first_name}} only — buyers see through this instantly
• Sounds the same as every other BDR at the company

Key things to listen for:

• Adoption discipline — tries the tool in good faith before judging
• Captures concrete friction rather than gut-reacting
• Escalates with data, not feelings
• Recognizes that initial discomfort isn't the same as a bad tool

Good approach:

1. Try it for two weeks in good faith — the first week of any tool feels worse than the workflow it replaces, simply because it's unfamiliar
2. Track concrete friction — log the moments where the tool slows you down or duplicates work. Don't generalize ('it's clunky'); be specific ('it takes 4 clicks to do what used to take 1, on this specific workflow').
3. Look for the why — usually the rollout is solving a problem that's invisible to you (reporting, audit trail, manager visibility). Ask your manager what the win condition for the rollout is.
4. Escalate constructively — if the tool genuinely hurts performance after 2 weeks, raise it with data: "I logged X hours of extra work per week across these 3 workflows. Here's what I'd propose instead."
5. Don't lone-wolf around it — sales teams need a single source of truth; opting out of tools breaks reporting and creates internal friction

Legitimate pushback is rare but real — usually when the tool was procured without input from the people who use it daily, and there's a measurable productivity hit.

Red flags:

• Refuses to try the tool — "I've seen this before, it never works"
• Pretends to use it for reporting but actually works in the old system
• Complains in the team Slack channel without ever escalating constructively
• Cannot articulate the friction beyond 'I don't like it'