# Discovery Call Questions Generator

> Discovery call questions are the open questions a seller asks before any demo to learn the buyer's situation, their pain, what it costs, who decides, and the next step. Gong's analysis of 519,000 discovery calls found success peaks at 11 to 14 of them. This free generator writes 15 to 20 for your product, so you can pick the best.

Use it at https://demopage.io/tools/discovery-call-questions. For sales teams and founders.

## How it works

1. **Enter your website.** Add who you're calling and what they want to solve, if you know.
2. **DemoPage reads your pages.** So the questions fit your product's problem, not a generic template.
3. **Run the call.** Five stages, situation to next step, three or four questions each, with an opener and a close.

## How do you run a discovery call?

A discovery call is where you learn whether you can help before you show anything. Start with how they work today, then find what hurts and what it costs, then who decides and by when. Only then propose a next step.

Good discovery questions are open, one at a time, and never a pitch in disguise. Listen more than you talk and write down their words: you'll use them in the demo and in the follow-up email.

Sources: [Gong Labs, analysis of 519,000 discovery calls](https://www.gong.io/blog/deal-closing-discovery-call).

## For AI agents

`POST https://demopage.io/api/tools/discovery-questions` with JSON `{"website": "example.com", "role": "Sales leader | Support leader | Marketing leader | Founder or CEO | Operations leader | IT or engineering | Someone else", "company": "optional", "goal": "optional"}`. The reply has `product`, `opener`, `groups` (Situation, Pain, Impact, Decision, Next step; each with `questions` of `q` and `listenFor`), and `close`. Up to 4 an hour from one place.

Send it with `Content-Type: application/json`. Requests made from another website's pages are refused.

## Questions

**What is a discovery call?**
The first real conversation with a prospect, where you learn their situation, their problem, what it costs them, and how they buy, before you demo anything.

**How many questions should you ask on a discovery call?**
Gong's analysis of 519,000 discovery calls found that asking 11 to 14 questions over the call went with the most success; fewer or more did worse. Plan 15 to 20, ask the ones the conversation needs, and spread them through the call.

**What are good discovery call questions?**
Open questions, asked one at a time, that follow the stages of the call: how they work today, what hurts, what it costs, who decides and by when, and what happens next. None of them should pitch a feature.

**Are the discovery questions specific to my product?**
Yes. DemoPage reads your homepage and product pages, so the questions fit your problem space, and the listen-for notes point to what your pages say you solve.

**Do you keep what I enter?**
No. Your website's text and what you type are sent to our AI provider to write the questions; DemoPage doesn't save either.