Discovery And Demo Structure

Build practical discovery and demo structures that improve deal progression and buying confidence.

Confirm Inputs First

• If a current revenue-enablement-context exists, use it first for persona language, stage goals, and approved proof expectations.
• Confirm target audience: role, segment, and deal complexity.
• Confirm use case and product scope for the conversation.
• Confirm stage objective: qualification, evaluation, alignment, or commercial progression.
• Confirm known buyer risks: competition, timing, budget, technical constraints.
• Confirm current failure pattern if available: weak discovery depth, feature dumping, or poor next-step conversion.

Ask for only missing essentials. If details remain unknown, proceed with labeled assumptions.

Read The Right Reference

• Read references/discovery-demo-framework.md before building the structure.

Default Workflow

1. Define call outcome and decision quality required for this stage.
2. Build a question ladder that moves from context to impact to commitment.
3. Map stakeholder-specific concerns and value hypotheses.
4. Design demo sequence around buyer outcomes, proof, and risk handling.
5. Add transition language from discovery findings into tailored demo moments.
6. Select the right variant: executive discovery, technical demo, or multi-stakeholder decision meeting.
7. End with explicit next-step commitments, owners, and timeline.

Tool Notes

• Keep workflow tool-agnostic by default.
• If CRM fields or CI tags are available, align structure to those fields only when useful.

Output Contract

• Discovery Guide: objective, question ladder, and red-flag checks.
• Stakeholder Map: likely concerns and validation prompts by role.
• Demo Flow: sequence, proof points, and risk-handling moments.
• Transition Prompts: how to move from discovery to demo naturally.
• Next-Step Script: commitment language and meeting close structure.
• Variant Notes: adjustments for executive, technical, or multi-stakeholder contexts.

What To Avoid

• Using one discovery path for every stakeholder profile.
• Running feature-order demos disconnected from agreed buyer outcomes.
• Ending without clear owner/date commitments for the next decision step.

Quality Bar

• Tie every discovery and demo step to customer outcomes, not feature order.
• Keep questions layered, not checklist-style interrogation.
• Include explicit risk-handling paths for objections or uncertainty.
• Ensure final next step is concrete, owned, and time-bound.