# SaaS discovery call planning template

> Use a structured conversation to understand the problem, current process and buying constraints before prescribing a solution. Use the editable worksheet, example and review steps to turn it into a working document.

Source: https://saas-marketing.net/templates/saas-discovery-call-script/
Topic: SaaS Sales
Type: template
Published: 2026-09-17
Last updated: 2026-09-17
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/templates/saas-discovery-call-script/

## Short answer

SaaS discovery call planning template helps a SaaS team use a structured conversation to understand the problem, current process and buying constraints before prescribing a solution. The fields below define the required decisions and evidence. Download a CSV working copy, assign owners and replace the illustrative example with your own approved information.

## Key takeaways

- Use a structured conversation to understand the problem, current process and buying constraints before prescribing a solution.
- A script is a guide to listening, not a questionnaire to complete regardless of the answers.
- Every field needs a useful answer, supporting evidence or an explicit unresolved question.
- The download is an editable CSV file that opens in spreadsheet applications.

---

Use a structured conversation to understand the problem, current process and buying constraints before prescribing a solution. This worksheet supports the broader [saas sales plan](/saas-sales/).

## The working template

| Field | What to enter | Your answer | Owner |
| --- | --- | --- | --- |
| Opening | Agree on purpose and available time. | | |
| Current workflow | Ask how the task is done today. | | |
| Trigger | Ask why the issue matters now. | | |
| Impact | Explore consequences using the buyer's terms. | | |
| Stakeholders | Identify users, approvers and implementation owners. | | |
| Constraints | Ask about systems, timing and required controls. | | |
| Summary | Reflect what you heard and invite correction. | | |
| Next step | Agree on a useful action and owner. | | |

## A worked example

A buyer asking for analytics may actually need consistent definitions across departments. Explore the reporting process before demonstrating more charts.

The example is illustrative. It does not describe a measured customer result or create a promise about your own outcomes. Use it to understand the level of specificity the document needs.

## How to complete the worksheet

1. Choose one project, account segment or decision. A document that attempts to cover the whole company usually hides important differences.
2. Gather the evidence required by the fields above. Use approved customer research, current product information and the relevant business records.
3. Draft the answers with the person responsible for doing the work. Keep unresolved questions visible and assign a next action to each one.
4. Review the document with the people who depend on it. Confirm scope, responsibilities and any constraints before treating it as an operating agreement.
5. Save the version and review date. Update it when the underlying offer, process or customer evidence changes.

## Review before sharing

A script is a guide to listening, not a questionnaire to complete regardless of the answers.

A useful working document makes disagreements visible while there is still time to resolve them. Ask a colleague to explain the intended decision from the filled-in version without additional narration. If they cannot identify the next step or the evidence behind it, revise the relevant field.

Remove confidential customer details from any public copy. Keep names, prices and results only when you have permission and can explain their context. An empty evidence field is a signal to investigate, not an invitation to supply a plausible-sounding number.

## Continue the work

- [Choosing a SaaS sales model by ACV](/guides/saas-sales-models-by-acv/)
- [Self serve sales and when to add humans](/guides/self-serve-saas-sales/)
- [Inside sales for mid market SaaS](/guides/inside-sales-for-saas/)
- [The enterprise SaaS sales process](/guides/enterprise-saas-sales-process/)
- [Sales strategy for a SaaS startup](/playbooks/saas-startup-sales-strategy/)

Find more [templates](/templates/) and [checklists](/checklists/) for adjacent tasks.
{/* expanded-practice-2026-09 */}
## Apply saas discovery call planning template in a working review

Make a copy of the working file and complete one representative row before filling the entire document. Replace example values with evidence from the actual project. Add an owner and a review condition where the template calls for a decision. A blank marked unknown is more useful than an invented number that makes the file look finished.

For this topic, involve the sales owner and the buyer’s relevant decision participants and work from discovery notes, stage evidence and the next agreed action. The relevant unit is one qualified opportunity with a current buying process. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

### Evidence to prepare

Use buyer evidence to define progression. A completed seller task, such as a proposal or presentation, is not the same as a buyer commitment. Preserve the customer’s actual question and unresolved dependencies so follow-up can help rather than repeat the pitch.

| Review field | What to record |
| --- | --- |
| Topic | SaaS discovery call planning template |
| Decision | The specific action this explanation should help you choose |
| Working evidence | discovery notes, stage evidence and the next agreed action |
| Unit and scope | one qualified opportunity with a current buying process |
| Responsible people | sales owner and the buyer’s relevant decision participants |
| Remaining uncertainty | The missing fact that could change the decision |

### Two situations that can change the interpretation

#### When discovery turns into an early feature tour

A prospect asking about data migration needs a different session from one evaluating a new workflow with no existing system.

Use this check: Review the call notes for the current process, trigger, consequence and required outcome. Do not interrogate prospects with a long checklist unrelated to their request.

The [focused diagnostic guide](/guides/discovery-call-becomes-a-product-tour/) provides the correction process and a working evidence sheet.

#### When follow-up adds no new value

A verified migration answer is more useful than another generic message asking whether the prospect saw the proposal.

Use this check: Identify the last agreed question or dependency and the evidence needed next. Respect communication preferences and avoid escalating pressure after silence.

The [focused diagnostic guide](/guides/sales-follow-up-repeats-the-pitch/) provides the correction process and a working evidence sheet.

### Record the decision and the limit

An opportunity with a named technical review and an agreed next meeting is different from one with a favorable comment and no decision path. Both can remain in the CRM, but forecasting and follow-up should reflect the evidence actually available.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the [complete topic collection](/topics/saas-sales/) for related methods and the [category field guides](/industries/) when the product's buying situation or implementation requirements change how the method should be applied.

## Frequently asked questions

### What format is the downloadable template?

The working copy is a CSV file. Open it in your spreadsheet application, add owners and dates, and keep a separate copy of the original for reference.

### How should I fill in this template?

Use a structured conversation to understand the problem, current process and buying constraints before prescribing a solution. Start with one real project so that the decisions remain specific.

### What mistake should I avoid?

A script is a guide to listening, not a questionnaire to complete regardless of the answers.

### Do I need to complete every field before starting?

Identify the fields that change the decision or block safe execution. Mark unknowns with an owner and a review date rather than inventing an answer.