Pattern: Advisory Debate | Team size: 4 agents
Two competing strategic perspectives and a compliance/risk voice debate tradeoffs, then a moderator synthesizes a balanced corporate-travel playbook. This approach fits because winning business travellers often involves hard choices (premium vs. cost focus, perks vs. simplicity, flexibility vs. yield), and structured debate surfaces blind spots early.
Win business travellers for the airline I am working fore
Create an agent team to win business travellers for the airline I am working for by running an “Advisory Debate” between three strategic voices (Premium Experience Advocate, Cost & Procurement Advocate, Distribution & Travel-Tech Specialist) and concluding with a Moderator & Synthesis Lead who produces a balanced corporate-travel playbook, prioritized roadmap, and decision framework.
PROJECT_NAME: win-business-travellers
GLOBAL CONTEXT (READ FIRST)
- Objective: Produce a practical, channel-realistic, CFO/procurement-ready corporate travel strategy that increases share of business travellers while protecting yield and operational feasibility.
- Scope: Network/schedule strategy, onboard product and airport experience, loyalty and corporate contracting, disruption recovery, sales motions, distribution (TMC/OBT/NDC/GDS), reporting/analytics, and measurement.
- Constraints: You do NOT know the airline’s current position. Make explicit assumptions and provide “if/then” branches where assumptions materially affect recommendations.
- Output must be decision-ready: clear tradeoffs, financial/logical rationale, implementation steps, dependencies, and measurable KPIs.
WORKING ASSUMPTIONS TO USE (AND CHALLENGE)
- Airline competes in at least one business-heavy corridor (hub-to-hub, capital cities, major commercial centers).
- The airline can influence: fare products/rules, bundles/ancillaries, loyalty levers, servicing policies, sales approach, and distribution content.
- The airline has limited capex in the near term; recommend both “0–90 day,” “3–9 month,” and “9–18 month” initiatives with capex vs. opex notes.
TEAM SETUP AND COLLABORATION MECHANICS
- Each agent writes their own memo to a separate file (paths below) and must:
- State 8–12 assumptions (numbered) relevant to their lens.
- Provide 10–15 concrete recommendations with “Why it matters,” “Implementation notes,” “Risks/downsides,” and “KPIs.”
- Identify 5 non-obvious failure modes (e.g., channel leakage, corporate policy conflicts, union/ops constraints, revenue dilution, content parity issues).
- Provide 8–10 questions they would ask leadership to validate/adjust the plan.
- Debate protocol:
1) Agents produce first-pass memos independently.
2) Agents read each other’s memos and then produce a “Challenges & Rebuttals” section appended to their own file:
- 6–10 direct challenges to other agents’ recommendations (quote the recommendation name/phrase you’re challenging).
- 3–5 concessions where the other side is correct, plus how you’d incorporate it.
- 3 “deal-breaker” risks that would cause you to halt or redesign parts of the plan.
3) Agents then produce a short “Aligned Moves” section: 5 actions they agree are robust across perspectives.
- Coordination rules:
- Use consistent terminology for corporate travel: TMC (Travel Management Company), OBT (Online Booking Tool), GDS, NDC, policy compliance, duty of care, SLAs, traveler vs. booker.
- Make channel feasibility explicit: any offer must specify how it is bought (direct, TMC/OBT, GDS, NDC API, aggregators) and whether content parity is required.
- Quantify where possible: include ballpark ranges (not fabricated precise numbers). Use relative/benchmark logic (e.g., “top quartile Wi‑Fi NPS improvements typically correlate with…”).
- No hand-wavy statements. If unsure, label as assumption and provide validation steps.
- Hard dependencies:
- No synthesis document can be drafted until all three advocate memos (including rebuttals) are complete.
- The Moderator must explicitly resolve disagreements and document tradeoffs; do not average them away.
DELIVERABLES AND FILE OUTPUTS (WRITE EXACTLY THESE FILES)
1) Premium Experience Advocate memo
- File: outputs/agent_teams_demo/win-business-travellers/01_premium_experience_advocate.md
- Length: 1,200–1,600 words
- Required sections (use these headings exactly):
1. Executive stance (max 120 words)
2. Key assumptions (8–12 bullets)
3. Target segments & jobs-to-be-done (3–5 segments)
4. Recommendations (10–15, each with Why / How / Risks / KPIs)
5. Disruption recovery & service model (specific policies + SLAs)
6. Competitive differentiation (what we’ll be known for)
7. Failure modes (5)
8. Questions for leadership (8–10)
9. Challenges & rebuttals (added after reading others)
10. Aligned moves (5)
2) Cost & Procurement Advocate memo
- File: outputs/agent_teams_demo/win-business-travellers/02_cost_procurement_advocate.md
- Length: 1,200–1,600 words
- Required sections (use these headings exactly):
1. Executive stance (max 120 words)
2. Key assumptions (8–12 bullets)
3. Buying center map (traveler vs. booker vs. procurement vs. finance)
4. Recommendations (10–15, each with Why / How / Risks / KPIs)
5. Corporate fare architecture (bundles, rules, compliance, leakage control)
6. Reporting, invoicing & VAT/tax considerations (where applicable)
7. Failure modes (5)
8. Questions for leadership (8–10)
9. Challenges & rebuttals (added after reading others)
10. Aligned moves (5)
3) Distribution & Travel-Tech Specialist memo
- File: outputs/agent_teams_demo/win-business-travellers/03_distribution_traveltech_specialist.md
- Length: 1,200–1,600 words
- Required sections (use these headings exactly):
1. Executive stance (max 120 words)
2. Key assumptions (8–12 bullets)
3. Channel reality check (TMC/OBT/GDS/NDC/direct) — what breaks where
4. Recommendations (10–15, each with Why / How / Risks / KPIs)
5. Content parity & offer/order strategy (practical steps)
6. Servicing & disruptions in-channel (exchanges, refunds, credits)
7. Data & measurement plan (attribution, corporate ID, mid-office)
8. Failure modes (5)
9. Questions for leadership (8–10)
10. Challenges & rebuttals (added after reading others)
11. Aligned moves (5)
4) Moderator & Synthesis Lead master playbook (FINAL)
- File: outputs/agent_teams_demo/win-business-travellers/04_master_corporate_travel_playbook.md
- Length: 2,000–2,600 words
- This file must be written only after files 01–03 are complete with their rebuttals.
- Required sections (use these headings exactly):
1. One-page executive summary (max 350 words)
2. What we’re optimizing for (yield, share, loyalty, cost-to-serve) + explicit tradeoffs
3. Decision framework: Premium-led vs. Procurement-led (when to choose which, with triggers)
4. Unified corporate traveller value proposition (3 pillars + proof points)
5. Offer architecture (fare families, bundles, flexibility, ancillaries) with channel notes
6. Corporate contracting & sales motion (SMB to global) + sample negotiation levers
7. Distribution execution plan (GDS/NDC/OBT/TMC): content parity, servicing, and friction removal
8. Operations & service design for road warriors (disruption playbook + SLAs)
9. 90-day / 3–9 month / 9–18 month roadmap (table with owners, dependencies, capex/opex, risks)
10. KPI tree & measurement (leading vs. lagging indicators, targets as ranges, instrumentation plan)
11. Risk register & mitigations (top 12 risks; include compliance, reputational, channel, dilution, ops)
12. Open questions to resolve (top 15) + how to validate quickly
13. Synthesis review: how debate changed the plan (explicitly cite 6–10 debate points resolved)
5) Cross-agent alignment artifacts (SHORT)
- File: outputs/agent_teams_demo/win-business-travellers/05_alignment_summary.md
- Length: 600–900 words
- Required sections (use these headings exactly):
1. Points of agreement (10 bullets)
2. Key disagreements (8 bullets) + “resolution in master playbook”
3. Critical assumptions to test first (10 bullets)
4. Immediate next actions for leadership workshop (agenda, 60 minutes)
WORKPLAN (EXECUTION ORDER WITH DEPENDENCIES)
1) Premium Experience Advocate: Draft file 01 (sections 1–8 only).
2) Cost & Procurement Advocate: Draft file 02 (sections 1–8 only).
3) Distribution & Travel-Tech Specialist: Draft file 03 (sections 1–9 only).
4) Cross-read step (mandatory):
- Each advocate reads the other two memos and appends their “Challenges & rebuttals” and “Aligned moves” sections.
- Dependency: This step must complete before Moderator begins the master playbook.
5) Moderator & Synthesis Lead:
- Read files 01–03 end-to-end.
- Draft file 04 with explicit reconciliation of conflicts and a prioritized roadmap.
6) Final synthesis/review step (mandatory, last):
- Moderator produces file 05, ensuring:
- All major disagreements are either resolved or explicitly parked with tests.
- Roadmap dependencies are consistent with channel/ops constraints.
- KPIs are measurable with a clear data source owner (e.g., Sales Ops, Revenue Mgmt, Digital, Loyalty, Contact Center).
- The full package is internally coherent (no contradictory promises across product, contracting, and distribution).
CONTENT REQUIREMENTS (NON-NEGOTIABLE DETAILS)
- Every recommendation must include:
- Name (short label)
- Target persona (traveler/booker/procurement/finance)
- Buying/booking path (direct/TMC/OBT/GDS/NDC) and servicing path
- Expected impact (qualitative + range if possible)
- Primary cost type (capex/opex/mixed) and major dependency
- Include at least:
- 6 recommendations focused on irregular operations (IROPS) and disruption recovery for business travellers.
- 6 recommendations focused on corporate fare/rule simplification and policy compliance.
- 6 recommendations focused on distribution/servicing (NDC/GDS parity, exchanges/refunds, mid-office).
- Avoid airline-specific brand claims; make it adaptable. When offering examples, label them “Example wording” and keep them generic.
Now execute the plan and write the files to the specified paths.
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.