The buyer asked for a dashboard. What work needs to change?

SaaS Discovery checklist

Prepare questions that uncover the work behind a buyer’s request. Leave the conversation with a shared understanding of the problem, the evidence and a useful next step.

10 steps · 30 practical checks

Illustration of a sales team meeting remote customers by video.
SaaS sales & customer conversations · Preparation for real work.

Prepare the next conversation, session or decision.

Work through these 10 steps and choose the actions relevant to your situation. The pitfalls are illustrative examples, not customer quotations. Use the checklist on screen or print it for your preparation.

Review what is known

Illustrative pitfall

“We asked the buyer to repeat information already shared.”

  • Read authorised account and meeting notes.
  • Separate facts, assumptions and gaps.
  • Choose the most useful gaps to explore.

Agree the conversation

Illustrative pitfall

“The buyer expected a short call and received an interrogation.”

  • Confirm purpose, time and participants.
  • Ask what would make the conversation useful for them.
  • Explain how the discussion will shape any next step.

Explore the current work

Illustrative pitfall

“We accepted the requested feature as the complete need.”

  • Ask the buyer to describe the current workflow.
  • Identify the people, tools and handoffs involved.
  • Request a specific example of the difficulty.

Understand the impact

Illustrative pitfall

“The problem sounded important but nobody could explain its effect.”

  • Ask who is affected and how often it happens.
  • Explore time, effort, risk or customer impact.
  • Distinguish evidenced impact from an initial estimate.

Clarify the desired change

Illustrative pitfall

“A vague wish became a promised solution.”

  • Ask what a better working situation would look like.
  • Identify the outcome that matters most.
  • Check what should remain unchanged.

Follow the answer

Illustrative pitfall

“We followed the question list and missed the important clue.”

  • Listen for incomplete or unexpected information.
  • Ask a relevant follow-up before changing topic.
  • Summarise what you heard and invite correction.

Map the stakeholders

Illustrative pitfall

“One enthusiastic contact was treated as the whole buying group.”

  • Ask who uses, evaluates and approves the solution.
  • Explore different priorities and concerns.
  • Agree how missing perspectives can be included.

Check constraints

Illustrative pitfall

“The proposed next step ignored the team's technical limits.”

  • Ask about relevant systems, resources and timescales.
  • Identify required security or integration reviews.
  • Keep unknown constraints visible for specialist follow-up.

Test your understanding

Illustrative pitfall

“Our summary described the product we wanted to sell.”

  • Restate the problem in the buyer's language.
  • Check the priority and evidence with them.
  • Acknowledge where fit is still unproven.

Agree a useful next step

Illustrative pitfall

“We booked a demo without deciding what it should prove.”

  • Choose the next action around the remaining question.
  • Agree participants, owner and date.
  • Record the buyer context for anyone joining later.

Put it to work

Turn the checklist into focused practice.

NewSkilz shapes practical training around your people, goals, real working situations and approved content.