Loading...
customer service

Sales Discovery Call SOP

A sales discovery call SOP template for preparing, running, and documenting a qualification call. Use it to keep questions consistent, capture next steps, and log clean CRM notes.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Saas · B2b Services · It Services · Manufacturing · Healthcare

Overview

This Sales Discovery Call SOP template covers the full workflow for a qualification call: reviewing the prospect record, preparing the agenda and question framework, opening the meeting, uncovering needs and pain points, qualifying the opportunity, confirming next steps, documenting the call in the CRM, and sending a follow-up summary.

Use it when you want every rep to run discovery in a consistent way and capture the same decision-making details. It is especially useful for inbound leads, first meetings with outbound prospects, SDR-to-AE handoffs, and any situation where you need a clear record of fit, urgency, stakeholders, and buying process. The template helps prevent vague notes, missed follow-up, and deals advancing without enough evidence.

Do not use it as a rigid script for support calls, implementation reviews, or renewal discussions. It is also not the right fit when the conversation is already deep in technical validation and the team needs a solution workshop instead of basic discovery. If your sales motion is highly regulated or safety-sensitive, adapt the question set to include required approvals, claims restrictions, and escalation paths before using it live.

Standards & compliance context

  • This SOP supports ISO 9001-style documented information practices by creating a repeatable record of the call, outcome, and follow-up actions.
  • It aligns with PMI process group thinking by separating preparation, execution, monitoring, and closing activities into clear steps.
  • For regulated industries, the template can be adapted to capture approved claims, required disclosures, and escalation notes without changing the core workflow.
  • If the call touches on customer data, security, or contractual terms, the CRM notes should follow your organization’s retention and access-control rules.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Steps

This section matters because it turns a discovery call into a repeatable workflow with clear ownership from prep through follow-up.

  • Review the prospect record and meeting context
    The sales representative reviews the prospect's company profile, prior interactions, meeting attendees, and stated objectives before the call. The representative confirms the prospect's industry, role, current stage in the buying process, and any known pain points. Capture any open questions, prior commitments, and relevant account history that may affect the discovery conversation.
  • Prepare the discovery call agenda and question framework
    The sales representative prepares a concise agenda that includes introductions, business context, pain points, current process, decision criteria, timeline, and next steps. The representative selects open-ended questions that cover needs, impact, stakeholders, budget range, authority, and urgency. The representative tailors the question set to the prospect's industry and likely use case.
  • Join the call and confirm the meeting purpose
    The sales representative joins the call on time, confirms audio and video quality, and greets the prospect professionally. The representative states the purpose of the meeting, confirms the expected duration, and aligns on the agenda. If additional attendees are present, the representative asks each participant to briefly introduce themselves and their role.
  • Discover the prospect's business needs and pain points
    The sales representative asks open-ended discovery questions to understand the prospect's current process, challenges, desired outcomes, and the business impact of the problem. The representative probes for frequency, severity, current workaround, and consequences of inaction. The representative listens for measurable pain points, operational constraints, and triggers that indicate urgency.
  • Qualify the opportunity against agreed criteria
    The sales representative qualifies the opportunity using the team's agreed framework, such as budget, authority, need, timeline, and fit. The representative confirms decision-makers, buying process, implementation constraints, and any non-negotiable requirements. If the prospect does not meet minimum qualification criteria, the representative documents the gap and determines whether to nurture, disqualify, or escalate.
  • Confirm next steps and mutual action items
    The sales representative summarizes the key takeaways, confirms the prospect's priorities, and agrees on the next step. The representative assigns clear owners and due dates for any follow-up actions, such as sending materials, scheduling a demo, or involving another stakeholder. The representative confirms the date and purpose of the next meeting before ending the call.
  • Document the call in the CRM
    The sales representative logs the call outcome in the CRM immediately after the meeting. The representative records the prospect's pain points, qualification status, stakeholders, timeline, objections, next steps, and follow-up commitments. The representative updates the opportunity stage, adds relevant notes, and attaches any supporting documents or call recordings if applicable.
  • Send the follow-up summary to the prospect
    The sales representative sends a concise follow-up email that summarizes the prospect's goals, key pain points, agreed next steps, and any promised resources. The representative includes the date and purpose of the next meeting or action item. The representative ensures the message matches the CRM record and does not introduce new commitments that were not discussed on the call.

How to use this template

  1. 1. The rep reviews the prospect record, meeting context, and prior touchpoints so the call starts with relevant background and no duplicate questions.
  2. 2. The rep prepares the discovery agenda, custom question framework, and qualification criteria so the conversation stays focused on fit, need, timing, and stakeholders.
  3. 3. The rep joins the call, confirms the meeting purpose, and sets expectations for timing, outcomes, and any follow-up needed.
  4. 4. The rep asks one discovery question at a time, verifies each answer, and records business pain, current process, decision criteria, and known constraints.
  5. 5. The rep qualifies the opportunity against the agreed criteria, confirms next steps and owners, and logs the outcome, notes, and tasks in the CRM before sending the summary email.

Best practices

  • Review the prospect record before the call so you can ask informed questions instead of repeating information already captured.
  • Use a consistent qualification framework, but tailor the wording to the prospect’s industry, role, and buying stage.
  • Ask for concrete examples of the current process, pain points, and impact so the notes contain evidence, not vague interest.
  • Confirm decision makers, influencers, and the expected approval path before ending the call.
  • Capture objections, risks, and unresolved questions in the CRM while the call is still fresh.
  • Send the follow-up summary the same day and include the agreed next step, owner, and due date.
  • Escalate immediately if the prospect describes a compliance, security, or implementation constraint that could block the deal.

What this template typically catches

Issues teams running this template most often surface in practice:

The rep skips the pre-call review and misses context that was already available in the CRM.
The agenda is too generic, so the prospect leaves without a clear understanding of the call purpose.
Discovery questions are asked in a script-like way and fail to uncover real business pain or urgency.
Qualification criteria are not applied consistently, so weak opportunities stay in the pipeline.
Next steps are discussed loosely but not assigned to a specific owner or date.
CRM notes capture a summary but omit objections, stakeholders, and decision criteria.
The follow-up summary is delayed, which reduces momentum and creates confusion about the agreed actions.

Common use cases

SDR qualification for a SaaS pipeline
An SDR uses the SOP to confirm need, timing, authority, and fit before booking a demo. The structured notes make the handoff to the AE cleaner and reduce back-and-forth after the call.
Founder-led discovery for early-stage sales
A founder uses the template to keep discovery focused while still sounding conversational. It helps capture repeatable notes and prevents important qualification details from being lost between calls.
Enterprise account discovery with multiple stakeholders
An AE uses the SOP to identify the economic buyer, technical evaluator, and operational owner in a complex deal. The template helps the team track stakeholder roles, constraints, and follow-up actions in one place.
IT services discovery before a scoping workshop
A services team uses the SOP to gather current-state process details, pain points, and implementation constraints before moving into solution design. That reduces scope gaps and improves the quality of the next meeting.

Frequently asked questions

What is included in this Sales Discovery Call SOP template?

This template covers pre-call review, agenda preparation, opening the call, discovery questions, qualification, next-step confirmation, CRM documentation, and the follow-up summary. It is designed for a single discovery call, not a full sales process or account plan. The structure helps a rep capture the same core information every time so handoffs and pipeline reviews are easier. You can customize the question framework to match your product, ICP, and qualification model.

Who should use this SOP?

It is typically used by sales development reps, account executives, founders handling early sales, and sales managers coaching call quality. A sales ops or revenue ops owner can also adapt it as the standard for note-taking and CRM hygiene. If your team uses different roles for prospecting and closing, this SOP still works as the common discovery format. It is especially useful when multiple reps need to ask comparable questions and document answers consistently.

How often should this SOP be used?

Use it for every first discovery call and for any follow-up qualification call where scope, need, timing, or fit is still being evaluated. It is not meant for every customer meeting, such as implementation check-ins or support escalations. Teams often keep the same SOP in place until the qualification criteria or product positioning changes. If you update your ICP or pricing model, review the template before the next call cycle.

How does this template help with qualification?

The SOP forces the rep to compare the prospect’s answers against agreed criteria instead of relying on memory or gut feel. That reduces vague pipeline entries and makes it easier to decide whether to advance, nurture, or disqualify the opportunity. It also creates a clear record of the business problem, stakeholders, timeline, and decision process. That record is useful for forecasting and for later handoff to a closer or solutions consultant.

Does this template align with any formal process or documentation standards?

Yes, it supports ISO 9001-style documented information practices by making the call record repeatable, traceable, and easy to review. It also fits PMI process group thinking by separating preparation, execution, monitoring, and closing actions. For regulated or safety-related sales, the template can be adapted to capture required approvals, controlled claims, or escalation notes. It is not a legal form, but it does help standardize the evidence you keep.

What are the most common mistakes when using a discovery call SOP?

Common mistakes include asking every prospect the same script without adapting to the account, skipping the pre-call review, and failing to confirm next steps before ending the meeting. Another frequent issue is logging only a summary instead of the actual qualification evidence and objections. Reps also sometimes forget to send the follow-up note promptly, which weakens momentum. This template is meant to prevent those gaps by making each step explicit.

Can I customize the question framework and qualification criteria?

Yes, and you should. The question framework should reflect your product category, buying committee, deal size, and qualification method, such as MEDDICC, BANT, or a custom scorecard. You can also add industry-specific prompts, security questions, or implementation constraints. Keep the structure of the SOP intact, but tailor the content so the notes are actually useful to your team.

How does this work with CRM and sales tools?

The SOP is built to end with CRM logging, so it works well with Salesforce, HubSpot, or any system where call notes, fields, tasks, and next steps need to be recorded. You can also link it to meeting tools, call recording, and task automation so the rep does less manual follow-up. The important part is that the CRM captures the qualification outcome, not just a transcript. If your team uses call intelligence software, this SOP can define what still needs human review.

Is this better than an ad-hoc discovery call approach?

Yes, if you need consistency, coaching, and cleaner pipeline data. Ad-hoc calls often miss key questions, produce uneven notes, and leave next steps vague. A SOP gives the rep a repeatable sequence so the conversation stays focused while still sounding natural. It also makes it easier for managers to review calls and spot where deals are stalling.

Ready to use this template?

Get started with MangoApps and use Sales Discovery Call SOP with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?