Tier-One OEM Joint Business Review Presentation Script
Generate a high-stakes executive dialogue script for presenting a multi-year industrial OEM account growth plan.
Use this template when orchestrating an annual strategic review with Tier-1 manufacturing executives. It turns operational metrics, joint cost-down targets, and modernization roadmaps into an executive-level spoken script.
Role: Principal Global Strategic Account Director specializing in Tier-1 industrial and automotive OEM enterprise partnerships.
Context
- Target Account: {{oem_account_name}}
- Installed Production Assets: {{current_installed_base}}
- Critical Operational Friction: {{production_bottlenecks}}
- Target Efficiency/Cost-Down Goal: {{joint_cost_down_target}}
- Executive Stakeholder Landscape: {{stakeholder_matrix}}
- Proposed Multi-Site Growth Scope: {{proposed_expansion_scope}}
Task
Draft an exhaustive executive-level presentation script and verbal choreography for a 45-minute Joint Business Review (JBR), enabling the account team to transition from transactional equipment vendor to strategic multi-plant manufacturing partner while securing endorsement for {{proposed_expansion_scope}}.
Method
- Analyze {{stakeholder_matrix}} to establish distinct speaker cues, objections, and value anchors for engineering, procurement, and operations leaders.
- Script an opening executive narrative framing macro industrial supply chain pressures against {{oem_account_name}}'s specific throughput targets.
- Draft a retrospective review of performance metrics across {{current_installed_base}}, acknowledging historical service records and resolving {{production_bottlenecks}}.
- Articulate the commercial framework linking {{joint_cost_down_target}} directly to the phased deployment outlined in {{proposed_expansion_scope}}.
- Write conversational transition bridges that steer conversation from past vendor performance to the 3-year co-innovation roadmap.
- Structure a multi-voice dialogue blueprint incorporating spoken talking points for Account Executive, Lead Solutions Architect, and Executive Sponsor.
- Detail handling responses for three predictable executive objections around capital allocation, operational downtime during changeovers, and vendor lock-in.
- Formulate a definitive spoken closing call-to-action that locks in a signed memorandum of understanding (MoU) or pilot validation timeline.
Constraints
- The script MUST follow a realistic spoken cadence with parenthetical stage directions, tone markers, and pause indicators.
- You MUST address every technical variable within {{production_bottlenecks}} using manufacturing-accurate terminology (e.g., OEE, cycle time, MTBF, scrap rates).
- MUST NOT use generic corporate filler or vague value propositions without tying them to {{joint_cost_down_target}}.
- Keep speaker interventions balanced across the 45-minute timeframe without monologue blocks exceeding 180 words.
Output format
Provide the complete script organized into:
- Meeting Agenda & Speaker Cue Matrix (table format: Minute, Speaker, Slide Topic, Core Objective)
- Act I: Executive Alignment & Macro Operational Reality (Opening script with tone cues)
- Act II: Baseline Health & Bottleneck De-Risking (Spoken narrative referencing {{current_installed_base}})
- Act III: The Commercial Horizon & Co-Engineering Model (Pitching {{proposed_expansion_scope}})
- Act IV: Live Objection Handling Protocols (Procurement, Plant Operations, and Quality assurance dialogues)
- Act V: Close & Next Steps Formalization (Verbal close script)
Self-review
- Does the script explicitly articulate how {{joint_cost_down_target}} is achieved?
- Are all technical references aligned with standard industrial discrete/process manufacturing practices?
- Are stage directions and speaker handoffs explicit throughout the script?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.