Revenue Enablement report
Discovery Question Bank: your result
This answer uses a made up example company. Change the details above and press Run to see your own result.
Discovery Question Bank
For SDRs and account executives. The decision: what do we ask on the discovery call?
Give it the discovery framework you use, such as MEDDPICC, BANT or SPICED, and get questions for each part of it, with advice for the stage of the conversation.
This sample is a made up example, built from the inputs behind Fill in an example. It shows part of one section of the answer.
Owner: the account owner with Head of Last-Mile Operations. At the next discovery meeting about our product, ask the questions below and record the buyer’s own answer, its source and the person who can approve the next step. Check: a dated answer to the first unresolved buyer question.
See the full example answer or run it with your own details.
Revenue Enablement report
This answer uses a made up example company. Change the details above and press Run to see your own result.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
What next? Work with Shashwat Try another tool See all 85 tools and skills
Generated on 2 November 2026 from this branch, with the inputs behind Fill in an example. Your own inputs give a different result.
Revenue Enablement report
No explicit unanswered metric or information gap was supplied. Confirm the next missing decision with the buyer before selecting questions from the optional bank.
Sector: not clear from your inputs (name the industry for sector notes). Business model: not stated. Tell us how you charge and the plan will adjust.
Use only the sections needed after the unanswered questions above.
Say it in your own voice:
Owner: the account owner with Head of Last-Mile Operations. At the next discovery meeting about our product, ask the questions below and record the buyer’s own answer, its source and the person who can approve the next step. Check: a dated answer to the first unresolved buyer question.
To sharpen this, give: known pain points (it would turn the questions from the area to the pain, one statement at a time); your solution (list the parts of the product with a few words on what each does; it would add a question on each part); known metrics (it would replace the sector's usual measure with the number the prospect gave).
Suggested timings, lengths and counts: adjust them to your own.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
The bank opens with Unanswered questions first (reminding you to confirm the next missing decision or metric gap before picking from the full list), followed by an Opening for a discovery conversation, role-specific questions (Questions for <Prospect role>), framework questions for every letter of your chosen method (MEDDPICC, BANT, SPICED, Challenger, Gap Selling, or All), and Closing the call. If you leave Known pain points and Known metrics blank, the questions use placeholders like "the problem you came to fix" and "the number this problem moves" so you remember to ask the buyer to name them first.
Come back before every next-stage call (First call, Discovery, Deep dive, Technical, or Executive) and paste the pain points and metrics the buyer just shared so the bank generates targeted follow-up questions on what is still missing. The tool applies the same fixed rules every time. It does not call an AI model, and this site does not keep what you enter.
Add Revenue Enablement once (see Use it in Claude, ChatGPT or Gemini), then ask in plain words. Here is a prompt built from the tested example:
My role is not stated. Ask me for my role first. Use Revenue Enablement's Discovery Question Bank tool. framework: MEDDPICC; deal stage: Discovery; prospect industry: Third-party logistics; prospect role: Head of Last-Mile Operations; your solution: our product. If this tool is unavailable, ask me to open its web page; do not invent its output. In Gemini CLI or Antigravity, use the Helix GTM Suite skills package for related guidance, without claiming to run this connector.
You do not need to sign in. A web browser is enough, and the answer comes back in a second or two.
It applies fixed rules in the Revenue Enablement code to the inputs above and returns text. It does not call an AI model, does not look anything up, and does not store what you type. The web form and the AI assistant connector run the same tool code, so the same input gives the same answer in both.
Previous: Deal Strategy CoachNext: ROI Business Case Builder
MCP tool name: discovery_question_bank. REST: POST https://revenue-enablement.gtmhelix.com/api/tools/discovery_question_bank with this JSON body (see How it works):
{
"input": {
"framework": "meddpicc",
"deal_stage": "discovery",
"prospect_industry": "Third-party logistics",
"prospect_role": "Head of Last-Mile Operations",
"your_solution": "our product"
}
}
Run a Helix tool in your browser, then take the result to ChatGPT, Claude or Gemini. Connectors work with supported plans in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Each plugin has its own installation steps, below or on its own page.
Connector setup guides · Skills package setup guide · Find the skills on skills.sh