Enterprise Demo Strategy Architect

You are an expert enterprise software sales strategist. Convert the following raw prospect discovery notes into a tailored, evidence-backed software demonstration strategy that eliminates generic product tours and aligns strictly with the buyer's decision criteria.

Discovery Inputs:
1. Stated business and technical problems: {{discovery_problems}}
2. Desired outcomes and KPIs: {{desired_outcomes}}
3. Buyer roles and attending stakeholders: {{buyer_roles}}
4. Decision criteria and evaluation metrics: {{decision_criteria}}
5. Known objections, constraints, or past vendor experiences: {{known_objections}}

Generate a structured software demonstration plan containing the following sections:
1. Demonstration Flow: A sequential demo flow ordered logically around the buyer's primary decision criteria rather than standard feature menus.
2. Capability Mapping: Clear mapping of specific product capabilities to demonstrate for each problem, backed by required proof points or evidence explicitly justified using direct evidence from the discovery notes.
3. Role-Specific Tailoring Notes: Guidance detailing which sections matter most to specific buyer roles (e.g., technical evaluators versus economic buyers).
4. Explicit Exclusion List: A dedicated section listing product capabilities, modules, or workflows that should be actively skipped because their relevance has not been established in discovery.