The AE playbook

Discovery is where most deals are won or lost — and most reps under-invest. The winning structure layers two frameworks:

• SPIN for the conversation shape: Situation → Problem → Implication → Need-payoff. Situation questions establish context (sparingly). Problem questions surface pain. Implication questions amplify the cost of the pain. Need-payoff questions get the buyer articulating their own value case.
• MEDDIC for the qualification spine: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion. Used as a diagnostic — what's missing? — not as a deal-stage gate.

The single highest-leverage discovery question: "What does it cost you today to not solve this?". The number the buyer gives you becomes the value math for the rest of the deal. Without it, you're selling features.

The demo is where most AEs accidentally talk themselves out of deals. Three rules that survive every deal review:

• Lead with one specific use case, not the platform tour. The platform tour is for the marketing site. The demo should solve the prospect's exact problem in front of them — and stop.
• Mirror their language. If they call it "pipeline coverage", you call it pipeline coverage. If they say "forecast accuracy", that's the term. Reusing their words signals you heard them.
• Build in a moment of intentional silence. After the key use case lands, stop talking. Let them react. The best questions come from this silence — and the demo turns into a working conversation instead of a one-way pitch.

Demos longer than 30 minutes lose deals more often than they win them. If the demo is structurally going to run longer, split it into two sessions with different stakeholders. The buyer's attention is the constraint, not your feature surface.

Single-thread deals die when the champion leaves, the priority shifts, or procurement asks for another bid. Multi-threading is how AEs prevent this. The working rule: every deal over $50k needs at least three stakeholders engaged before proposal.

• The Champion — believes in your product and will sell internally for you. Identified through MEDDIC discovery.
• The Economic Buyer — owns the budget. Often not the Champion. Must be reached before pricing conversations.
• The Coach — gives you internal information about how the deal will be evaluated. Often an unexpected role: an IT analyst, a procurement person, a peer of the Champion.

How to get there: ask the Champion. Direct request: "Who else needs to be comfortable with this for you to move forward?". Most Champions answer honestly when the question is asked respectfully. Then book the meetings.

Negotiation belongs at the end of the deal, not the middle. AEs who discuss discounts before pricing has been formally proposed lose margin every time. Three rules:

• Anchor with value, not price. The cost-of-inaction number from discovery is your anchor. Reference it before pricing. The deal value is set BY the customer in their own words — your pricing is the secondary number.
• Trade, never give. If the buyer asks for a discount, the rep asks what they'd give in return — a longer commitment, a faster timeline, multi-year terms, paid case study, executive sponsorship. Discounts without trades signal that your pricing wasn't real.
• Procurement is solvable. Most procurement objections are about process compliance, not price. Engage procurement early, give them what they need (security questionnaire, vendor onboarding form, etc.) — and the price negotiation gets easier because procurement's job feels respected.

The single highest-leverage closing question: "If we agree on the terms we've discussed, are you ready to move forward on Friday?". Specific date, clear ask, no ambiguity. Most close attempts fail because the ask is too vague.

AEs who can't forecast accurately get coached out. The two practices that fix it:

• Weekly pipeline pruning. Every deal stuck in the same stage for 60+ days either moves or comes out. Holding zombie deals to make the pipeline look fuller pollutes the forecast and burns rep time.
• Stage-weighted probability with calibrated rates. Don't use Salesforce's defaults. Pull your own historical close rate by stage and apply it — the generic defaults are usually well off from what your own pipeline actually converts at.

Use the Pipeline Calculatorto model best-case + commit + most-likely against your own historical conversion rates. Commit is what you'd say in a manager 1:1; best-case is the dream; most-likely is what your manager will judge you against.