Discovery
AuraScore 77/100

Enterprise Omnichannel Fulfillment Discovery Plan

Formulate a multi-stakeholder discovery plan to diagnose retail supply chain and store-level fulfillment bottlenecks.

Use this plan when preparing to lead exploratory discovery sessions with retail operations and supply chain executives. It establishes an investigative roadmap across store fulfillment, inventory visibility, and distributed order management.

Template

Role: Senior Enterprise Account Executive specializing in retail supply chain and omnichannel store operations.

Context

  • Retail Account: {{retailer_name}}
  • Store Network Scale: {{store_footprint}}
  • Current Enterprise Architecture: {{core_erp_pos_stack}}
  • Primary Executive Champion: {{target_executive_sponsor}}
  • Stated Operational Challenge: {{stated_inventory_pain_point}}
  • Planned Session Length: {{discovery_session_length}}

Task

Generate a structured, stakeholder-aligned discovery execution plan designed to uncover root causes of inventory distortion, evaluate operational friction across stores and fulfillment nodes, and quantify the business impact for {{retailer_name}}.

Method

  1. Analyze {{stated_inventory_pain_point}} across both distribution center networks and physical retail tiers using {{store_footprint}} as baseline context.
  2. Map known architecture constraints based on {{core_erp_pos_stack}} to isolate potential latency points between online cart reservations and store inventory feeds.
  3. Frame targeted discovery inquiries tailored specifically to {{target_executive_sponsor}} regarding working capital tied up in safety stock and markdowns.
  4. Structure a time-boxed agenda allocating appropriate depth across operational, financial, and technical tracks within {{discovery_session_length}}.
  5. Draft probing question sequences across three dimensions: unified stock visibility, ship-from-store labor overhead, and buy-online-pickup-in-store (BOPIS) exception handling.
  6. Formulate hypothesis-driven impact prompts that guide the client to quantify revenue loss from phantom inventory and stockouts.
  7. Define explicit qualification milestones required to advance the opportunity to a collaborative technical architecture review.

Constraints

  • Focus strictly on physical store operations, warehouse synchronization, and digital fulfillment channels.
  • MUST include role-specific question phrasing tailored to store operations, IT, and merchandising leads.
  • MUST NOT recommend specific vendor products or pitch solution features during this discovery phase.
  • Maintain an investigative, consultative tone centered on business risk and margin protection.

Output format

Provide the plan across the following designated sections:

  1. Executive Context & Discovery Objectives (max 150 words)
  2. Time-Allocated Session Agenda (broken down by minute intervals for {{discovery_session_length}})
  3. Stakeholder Question Matrix (table with columns: Stakeholder Role, Operational Focus Area, Primary Probing Question, Financial Impact Metric)
  4. Risk and Objection Contingency Guide (3 anticipated friction points with counter-prompts)
  5. Session Exit Criteria & Next-Step Governance (bulleted list of 4 concrete qualification outcomes)

Self-review

  • Are all questions uniquely relevant to {{retailer_name}}'s scale of {{store_footprint}} and technology stack {{core_erp_pos_stack}}?
  • Does the agenda fit realistically within {{discovery_session_length}} without rushing high-value financial impact topics?
  • Is the deliverable completely free of pre-mature product positioning?
AuraScore breakdown
77/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering8/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-discovery
retail-consumer-goods
retail
omnichannel
fulfillment