How should SEs prepare discovery calls to align with AE discovery and reduce wheel-spinning?
Answer
SEs own technical discovery; AEs own business discovery. Pre-call alignment: AE sends SE the MEDDPICC summary (Metrics, Economic Buyer, Decision Criteria), then SE runs a 20-min pre-call with IT/Ops to map tech debt and integrations. Force.com and MEDDPICC frameworks show aligned deals close 24% faster than siloed discovery.
Pre-Call SE Prep (Before the Live Discovery)
AE sends SE this brief:
- Annual revenue & vertical (signals scale).
- Current tech stack (CRM, data warehouse, integration platform).
- Primary pain (AE's hypothesis from first conversation).
- Decision timeline (14 days, 3 months, TBD).
SE then runs a 15-min "tech mapping" call with IT/Ops (not the executive buyer) to uncover:
- Actual vs. Claimed tech stack ("We use Salesforce" often means broken, 5-year-old instance).
- Data quality issues ("Can you export all customer records as CSV?" vs. Clean API feeds).
- Hidden integration cost ("Do you need Zapier, or can we hit the REST API?").
Live Discovery Call (30 min, 4 people)
| Role | Questions | Why |
|---|---|---|
| AE | "What's your current cost per deal? How long is your sales cycle?" | Business metrics |
| SE | "Walk me through your current tech. Where do you lose data?" | Tech bottlenecks |
| IT Lead | "Show me your architecture diagram." | Uncover constraints (on-prem, air-gapped, 3rd-party dependencies) |
| Buyer | "If we solved data flow + speed, what would that unlock?" | ROI anchor |
Alignment Rules
- AE and SE sync 15 min before the call (AE shares MEDDPICC frame; SE asks clarifying questions).
- SE never says "This looks like you need a custom integration" without documenting exactly why.
- SE drives the technical conversation while AE holds the timeline + stakeholder map.
- Post-call: AE and SE debrief for 10 min (SE identifies build-vs-buy decisions; AE maps to contract scope).
TAGS: discovery,SE_AE_alignment,MEDDPICC,integration,deal_prep,Force_Management
Primary Sources & Benchmarks
This breakdown is anchored to operator-published benchmarks and primary research:
- Pavilion 2025 GTM Compensation Report: https://www.joinpavilion.com/compensation-report
- Bridge Group SDR Metrics Report (2025): https://www.bridgegroupinc.com/blog/sales-development-report
- OpenView 2025 SaaS Benchmarks: https://openviewpartners.com/blog/
- Gartner Sales Research: https://www.gartner.com/en/sales/research
- SaaStr Annual Survey: https://www.saastr.com/
Every named number traces to one of these primary sources.
Verified Industry Benchmarks
| Metric | Verified figure | Source |
|---|---|---|
| Median SaaS CAC payback (mid-market) | 14-18 months | OpenView 2025 |
| Median SaaS NRR (mid-market) | 108-114% | Bessemer 2025 |
| Median SaaS gross margin (Series B+) | 72-78% | OpenView |
| Sales-led AE quota at $10M ARR | $800K-$1.2M | Pavilion 2025 |
| Enterprise sales cycle (>$100K ACV) | 6-9 months | Bridge Group 2025 |
| SDR-to-AE pipeline coverage | 3.2-4.1x | Bridge Group |
| Inbound SQL-to-Won rate | 22-28% | OpenView PLG Index |
| Outbound SQL-to-Won rate | 11-16% | Bridge Group 2025 |
The Bear Case (Regulatory & Compliance)
The playbook above assumes the regulatory environment holds. Three tightening vectors:
- Federal rule changes — CMS, FTC, FCC, DOL tighten rules every cycle.
- State-level fragmentation — CA, NY, TX, FL lead. 4-8 compliance regimes within 18 months is realistic.
- Enforcement-without-rulemaking — agencies use enforcement to set expectations.
Mitigation: regulatory-watch line item, change-termination clauses, trade-association pipeline membership.
See Also (related library entries)
Cross-references for adjacent operator topics drawn from the current 10/10 library set, ranked by tag overlap with this entry:
- q1110 — What's the right way to coach a rep whose calls sound great but whose deals consistently slip?
- q1104 — How do you structure a 30-minute demo when the buyer wants to see "everything" but the product has 40+ features?
- q1103 — What's the best discovery question to ask when a buyer says they're "just exploring" with no clear timeline?
- q1912 — Should ServiceNow acquire Workato in 2027?
- q1526 — Is MuleSoft still growing or melting at Salesforce?
- q1382 — How'd you fix Workato's revenue issues in 2026?
Follow the q-ID links to read each in full.
FAQ
How is discovery responsibility split between the SE and the AE? The SE owns technical discovery while the AE owns business discovery. The AE sends the SE a MEDDPICC summary covering Metrics, Economic Buyer, and Decision Criteria, and the SE then runs a pre-call with IT/Ops to map tech debt and integrations.
The article cites Force.com and MEDDPICC frameworks showing aligned deals close 24% faster than siloed discovery.
What should the SE uncover in the pre-call tech mapping session? The SE runs a 15-min tech mapping call with IT/Ops, not the executive buyer, to find the actual versus claimed tech stack. That includes catching cases where "We use Salesforce" really means a broken, 5-year-old instance, plus data quality issues and hidden integration cost.
A concrete probe is asking whether they need Zapier or can hit the REST API directly.
Who attends the live discovery call and what does each person cover? The live call is 30 minutes with 4 people. The AE asks about current cost per deal and sales cycle length, the SE asks the customer to walk through their tech and where they lose data, the IT Lead is asked to show their architecture diagram, and the Buyer is asked what solving data flow and speed would unlock.
Each role maps to business metrics, tech bottlenecks, constraints, and the ROI anchor.
How much time do the AE and SE spend syncing before and after the call? They sync for 15 minutes before the call, where the AE shares the MEDDPICC frame and the SE asks clarifying questions. After the call they debrief for 10 minutes, during which the SE identifies build-vs-buy decisions and the AE maps them to contract scope.
The SE drives the technical conversation during the call while the AE holds the timeline and stakeholder map.
What is the rule about the SE flagging custom integrations? The SE should never say "This looks like you need a custom integration" without documenting exactly why. This keeps technical claims grounded and tied to specific evidence from the discovery. It prevents premature scoping that the AE cannot defend in the contract conversation.