Prepare questions for a first client conversation
Adapt an established sales method to your product and customer segment so the salesperson has a useful sequence of questions.
How this works
Adapt an established sales method to your product and customer segment so the salesperson has a useful sequence of questions.
Translate an established sales method into a usable question sequence for one call objective. Questions should reveal the buyer’s workflow and decision conditions without assuming a pain point or turning discovery into a scripted pitch.
Before you start
Defined operating scope
Salespeople need a consistent discovery method adapted to their product and deal stage.
Required source material
Obtain Sales methodology; Product description; Customer profile; Deal stage. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
A question presupposes an unconfirmed problem. Rewrite it to establish whether the problem exists.
Prepare the inputs
- methodology
- Required
Approved principles and question types
Preserve the intended sequence and definitions.
- offer
- Required
Product capabilities and exclusions
Use only approved claims.
- customer_context
- Required
Segment and confirmed facts
Separate observations from assumptions.
- call_goal
- Required
Stage, duration and desired learning
Define what must be understood by the end.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check methodology, offer, customer_context, call_goal before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected methodology and any missing required fields.
Add the original methodology materials
- Extract the method’s distinct discovery stages and the purpose of each rather than copying generic sales questions.
- Check each question’s learning objective and link to the chosen method.
Checkpoint: A saved intermediate result for: Add the original methodology materials.
Specify the product, audience, and call objective
- Map product relevance and customer context to hypotheses that the call should test.
- Rehearse the essential sequence within the time limit and remove leading or redundant prompts.
Checkpoint: A saved intermediate result for: Specify the product, audience, and call objective.
Draft questions and follow-up prompts
- Write open questions with follow-ups triggered by different answers, and select a realistic subset for the call duration.
- Check each question’s learning objective and link to the chosen method.
Checkpoint: A saved intermediate result for: Draft questions and follow-up prompts.
Add context from real customer problems
- Add relevant customer examples as optional probes, clearly labeled so they do not imply this buyer has the same problem.
- Rehearse the essential sequence within the time limit and remove leading or redundant prompts.
Checkpoint: A saved intermediate result for: Add context from real customer problems.
Package the result and unresolved work
- Check alignment with the methodology and remove questions that turn discovery into an early pitch.
- The guide supports a human conversation; it does not decide qualification from imagined answers.
Checkpoint: A concise discovery call guide. Unresolved items remain visible in the review record.
Decisions along the way
A question presupposes an unconfirmed problem.
Rewrite it to establish whether the problem exists.
The guide exceeds the available call time.
Prioritize essential learning and move optional probes to a reserve section.
A follow-up implies an unsupported product capability.
Remove the claim and ask a neutral process question instead.
What you will produce
discovery-call-question-guide-result.json
JSONA concise discovery call guide. Label proposed and completed states separately.
Include: call_goal · essential_questions · answer_branches · optional_probes · hypotheses · unsupported_assumptions · status · evidence_reference · review_note
discovery-call-question-guide-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving call_goal.
Include: source_reference · question · owner · next_action
Check the result
- Check each question’s learning objective and link to the chosen method.
- Rehearse the essential sequence within the time limit and remove leading or redundant prompts.
- Inspect methodology and offer in both the original and output; confirm that record identity and interpretation survived the transformation.
- Check alignment with the methodology and remove questions that turn discovery into an early pitch.
When something goes wrong
A question presupposes an unconfirmed problem.
Rewrite it to establish whether the problem exists. Retain the affected evidence and recovery status.
The guide exceeds the available call time.
Prioritize essential learning and move optional probes to a reserve section. Retain the affected evidence and recovery status.
A follow-up implies an unsupported product capability.
Remove the claim and ask a neutral process question instead. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Prepare questions for a first client conversation for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Offer automates invoice intake, not payments. A 20-minute first call should discover intake volume, exceptions and ownership; no pain point is yet confirmed.
Expected result
Synthetic expected result: Guide asks how invoices arrive, who handles exceptions and what happens when fields are missing. It does not promise automated payment or assume slow processing.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure preparation minutes; coverage of the agreed discovery topics in reviewed calls.
Stop or revise
A follow-up implies an unsupported product capability. Pause affected records and apply this recovery: Remove the claim and ask a neutral process question instead.
Keep the scope clear
- The guide supports a human conversation; it does not decide qualification from imagined answers.
- Do not insert fabricated customer facts or unsupported promises into role-specific prompts.
Check before using
Check alignment with the methodology and remove questions that turn discovery into an early pitch.
Business activities
- Run sales conversations and proposals
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Sales methodology · Product description · Customer profile · Deal stage
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow