Executive Impact Strike Team

Pattern: Fork-Join | Team size: 4 agents

This team works in parallel on the most important demo ingredients, then joins them into one high-impact customer experience. The fork-join approach fits because business value, visual storytelling, conversational AI, and rebrandability can be developed separately before being combined into a single wow-factor demo.

Business Challenge

approach using Microsoft Fabric IQ and Copilot Studio as a business-value demo, not a technical demo. Something its built once but can be used as a compelling demo for other westfarmers sister concern companies just quickly by chnaging branding and skin it should be as compeliing yet simple enough to create a wow factor for the customer

Agent Roles

• C-Suite Outcome Lead — Identify the executive pain points and success metrics the demo should address in the first five minutes.
• Demo Moment Designer — Craft the memorable wow moments where Fabric IQ and Copilot Studio reveal insights, explain causes, and recommend actions.
• Reusable Template Engineer — Design the configurable demo structure so each sister company can be onboarded by changing branding, sample data, and terminology.
• Narrative Integration Producer — Merge the business story, branded interface, AI assistant, and insight dashboards into one smooth demo script.

Generated Prompt

Create an agent team to design a business-value demo using Microsoft Fabric IQ and Copilot Studio for Wesfarmers-style sister companies. Build a reusable, compelling, simple “wow factor” demo concept that is created once and quickly adapted for other group companies by changing branding, skin, terminology, and sample data. Focus on executive outcomes, business value, decision intelligence, conversational insight, and repeatable storytelling. Do not create a technical architecture demo. Do not overemphasize implementation details.

Project name: westfarmers_fabric_iq_copilot_value_demo

Use the Executive Impact Strike Team using a Fork-Join pattern.

Core business context:
- The demo must show how Microsoft Fabric IQ and Copilot Studio help business leaders make better decisions faster.
- The target audience is senior business stakeholders, not engineers.
- The demo should be compelling enough to reuse across Wesfarmers sister companies or similar diversified retail, industrial, healthcare, supply chain, or consumer businesses.
- The demo should feel customized for each company while requiring only light changes: logo, colors, business terminology, sample dataset, persona names, KPIs, and industry-specific labels.
- The demo should be simple enough to build and deliver reliably, but strong enough to create a “wow” moment.
- The recommended demo duration is 12–15 minutes, with executive value visible in the first 5 minutes.
- The demo must show a business problem, reveal hidden insight, explain root cause, recommend action, and generate a stakeholder-ready response using Copilot Studio.
- The demo should avoid deep technical talk about data pipelines, model configuration, schemas, or infrastructure unless directly tied to business value.

Team operating model:
- Work in fork-join mode.
- First, all agents read this full brief and align on the shared demo objective.
- Then Agents 1, 2, and 3 work in parallel on their specialized deliverables.
- Agent 4 begins only after Agents 1, 2, and 3 finish their core outputs.
- The final synthesis/review step begins only after Agent 4 finishes the integrated script.
- Each agent must explicitly challenge at least 3 assumptions from another angle: executive relevance, demo feasibility, repeatability, emotional impact, simplicity, or credibility.
- Agents must share handoff notes in their deliverables under a section named “Handoff Notes for Other Agents.”
- Keep all recommendations practical, buildable, and demo-ready.

Required output files:
1. outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/01_c_suite_outcome_map.md
2. outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/02_wow_moment_design.md
3. outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/03_reusable_template_blueprint.md
4. outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/04_integrated_demo_script.md
5. outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/05_synthesis_review.md

Agent 1: C-Suite Outcome Lead

Mission:
Identify the executive pain points, business outcomes, and success metrics the demo must address in the first five minutes. Make the demo feel urgent, commercially relevant, and boardroom-ready.

This task must complete before Narrative Integration Producer begins.

Create file:
outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/01_c_suite_outcome_map.md

Required length: 900–1,200 words.

Use exactly these section headings:
1. Executive Demo Premise
2. Target Executive Personas
3. First-Five-Minute Value Promise
4. Priority Business Pain Points
5. Success Metrics and KPIs
6. Recommended Demo Scenario
7. Assumptions to Challenge
8. Handoff Notes for Other Agents

Content requirements:
- Define one primary demo scenario that can work across multiple Wesfarmers-style companies. Example themes may include: margin leakage, inventory imbalance, supplier disruption, store performance variation, workforce cost pressure, customer demand shifts, or promotion effectiveness.
- Select one scenario as the strongest and justify why it creates broad executive relevance.
- Define 3–5 executive personas, such as CEO, CFO, COO, Chief Customer Officer, Store Operations Head, Supply Chain Head, or Digital/Data Leader.
- For each persona, specify:
  - Their concern
  - The business question they ask
  - What Copilot should help them decide
  - The KPI they care about
- Define the “first five minutes” of value: what the audience sees, understands, and feels before any technical explanation.
- Include 6–8 KPIs that are easy to visualize and meaningful across sister companies.
- Include at least 3 assumptions that could weaken executive credibility and how to avoid them.
- Keep language executive-friendly and avoid technical jargon.

Agent 2: Demo Moment Designer

Mission:
Craft the memorable “wow moments” where Fabric IQ and Copilot Studio reveal insights, explain causes, recommend actions, and produce an executive-ready response. Design moments that are emotionally compelling but feasible to build.

This task must complete before Narrative Integration Producer begins.

Create file:
outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/02_wow_moment_design.md

Required length: 1,000–1,300 words.

Use exactly these section headings:
1. Demo Experience Goal
2. Signature Wow Moments
3. Conversational AI Flow
4. Insight Reveal Sequence
5. Recommended Actions
6. Executive Output Moment
7. Simplicity and Feasibility Guardrails
8. Assumptions to Challenge
9. Handoff Notes for Other Agents

Content requirements:
- Design 4–6 demo moments. Each moment must include:
  - Moment name
  - What the audience sees
  - What the presenter says
  - What the Copilot user asks
  - What Fabric IQ/Copilot appears to infer or explain
  - Why it creates business impact
- Include at least one moment where the AI explains “why this happened,” not just “what happened.”
- Include at least one moment where the AI recommends a decision or action.
- Include at least one moment where Copilot Studio generates an executive communication, such as a store manager action brief, supplier escalation note, CFO summary, or board update.
- Include one “brand switch” moment showing how the same demo can be skinned for a different sister company.
- Make the wow moments simple enough to create with mocked or sample data if needed.
- Avoid magic that would seem unrealistic. Ensure every wow moment feels plausible to business users.

Agent 3: Reusable Template Engineer

Mission:
Design the configurable demo structure so the same demo can be reused across sister companies by changing branding, sample data, industry terminology, and KPI labels. Prioritize speed of adaptation and consistency of experience.

This task must complete before Narrative Integration Producer begins.

Create file:
outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/03_reusable_template_blueprint.md

Required length: 1,000–1,300 words.

Use exactly these section headings:
1. Reusable Demo Design Principle
2. Configurable Demo Components
3. Branding and Skinning Model
4. Sample Data Model
5. Industry Terminology Swap Table
6. Copilot Prompt and Response Template
7. Dashboard and Insight Template
8. Onboarding Checklist for a New Sister Company
9. Assumptions to Challenge
10. Handoff Notes for Other Agents

Content requirements:
- Define a reusable demo “shell” that can support multiple companies without rebuilding the whole experience.
- Specify exactly what should be configurable:
  - Company name
  - Logo
  - Color palette
  - Persona names
  - Business units or locations
  - KPI labels
  - Product/category names
  - Supplier/customer labels
  - Sample data values
  - Copilot tone and terminology
- Include a concise sample data model with 6–10 business entities, such as Location, Product Category, Supplier, Promotion, Inventory, Sales, Margin, Forecast, Workforce, Customer Segment, or Incident.
- Provide a terminology swap table with at least 5 rows showing how the same demo could be adapted for different sister companies or industries.
- Include a Copilot prompt template with placeholders, such as [CompanyName], [BusinessUnit], [KPI], [Region], [DecisionNeeded].
- Include a 1-day, 3-day, and 5-day adaptation plan for rebranding the demo for a new company.
- Do not over-engineer. Make it suitable for a fast, reusable business demo.

Agent 4: Narrative Integration Producer

Mission:
Merge the executive outcome map, wow moments, reusable template, branded interface concept, AI assistant flow, and insight dashboard story into one smooth 12–15 minute demo script.

Do not begin until these files are complete:
- outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/01_c_suite_outcome_map.md
- outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/02_wow_moment_design.md
- outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/03_reusable_template_blueprint.md

Create file:
outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/04_integrated_demo_script.md

Required length: 1,400–1,800 words.

Use exactly these section headings:
1. Demo Title and Positioning
2. Audience and Setup
3. 15-Minute Run of Show
4. Presenter Script
5. Copilot Conversation Script
6. Dashboard and Insight Cues
7. Brand Switch Segment
8. Business Value Close
9. Risks and Recovery Lines
10. Handoff Notes for Final Review

Content requirements:
- Create a demo title that sounds business-led, not technical.
- Write a 12–15 minute run of show with timestamps. Use this structure:
  - 0:00–1:00 opening business challenge
  - 1:00–3:00 executive dashboard view
  - 3:00–6:00 Copilot insight discovery
  - 6:00–9:00 root cause and recommended action
  - 9:00–11:00 generated executive or operational communication
  - 11:00–13:00 brand/skin switch for another sister company
  - 13:00–15:00 business value close and next step
- Include exact presenter talk track lines for each segment.
- Include exact Copilot user questions and idealized Copilot responses.
- Include at least 5 dashboard/visual cues that the presenter can point to.
- Include a “brand switch” sequence where the presenter says how the same demo becomes relevant to another company by changing brand, sample data, and terminology.
- Include 5 risks and recovery lines, such as Copilot latency, unclear response, skeptical executive question, data credibility concern, or “is this just a chatbot?” objection.
- The script must not sound like a product feature tour. It must sound like a business decision story.

Final Synthesis/Review Step

Mission:
Review all outputs as a single demo package. Identify gaps, contradictions, over-complexity, weak business value, weak wow factor, or poor reusability. Produce a concise final package review and recommended next actions.

Do not begin until this file is complete:
- outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/04_integrated_demo_script.md

Create file:
outputs/agent_teams_demo/westfarmers_fabric_iq_copilot_value_demo/05_synthesis_review.md

Required length: 900–1,200 words.

Use exactly these section headings:
1. Overall Demo Assessment
2. Strongest Business Value Points
3. Strongest Wow Moments
4. Reusability Assessment
5. Simplicity and Build Feasibility Review
6. Gaps, Risks, and Fixes
7. Final Recommended Demo Package
8. Immediate Next Actions

Content requirements:
- Score the demo from 1–10 on:
  - Executive relevance
  - Wow factor
  - Simplicity
  - Rebrandability
  - Build feasibility
  - Business-value clarity
- Provide a brief reason for each score.
- Identify the top 5 changes that would make the demo more compelling.
- Identify the top 5 things to remove or simplify.
- Recommend the final “hero scenario” to build first.
- Recommend the minimum viable demo assets to create:
  - Dashboard screens
  - Copilot conversation prompts
  - Sample data tables
  - Brand configuration file or checklist
  - Presenter script
- End with a clear go/no-go recommendation and the next 3 actions.

Collaboration mechanics:
- Before writing final files, each agent must inspect the business problem and selected team design.
- Agents 1, 2, and 3 must work independently first, then cross-check their assumptions through their “Assumptions to Challenge” sections.
- Agent 4 must explicitly reconcile:
  - Executive priorities from Agent 1
  - Wow moments from Agent 2
  - Reusable template constraints from Agent 3
- The final synthesis must challenge the whole package and remove anything that feels too technical, too generic, too complex, or too hard to reuse.
- If two agents conflict, choose the option that maximizes business impact while keeping the demo simple and reusable.
- Prefer plain business language over platform terminology.
- Use Microsoft Fabric IQ and Copilot Studio as enablers of business decisions, not as the story itself.

Quality bar:
- The final package must be compelling to a senior executive within 5 minutes.
- The demo must be reusable for another sister company with light rebranding.
- The story must include insight, explanation, action, and communication.
- The demo must feel plausible, not like science fiction.
- The deliverables must be copy-paste ready for a team planning the actual build.
- Every file must be written in Markdown and saved to the exact specified path.

Build Your Own

Create your own AI agent team at Build Agents Store. Describe your business problem and get specialized agent teams with ready-to-use prompts for Claude Code.