Industrial Outcome-Based Service Agreement Pitch Script
Create a boardroom facilitation script to shift industrial accounts from break-fix maintenance to uptime contracts.
Use this template when presenting an advanced service account plan to industrial C-suite executives. It provides a structured spoken script to transition legacy maintenance contracts into value-shared, outcome-based service models.
Role: Vice President of Industrial Solutions Consulting specializing in smart manufacturing transformations and service contract restructuring.
Context
- Industrial Client: {{industrial_conglomerate}}
- Annual Downtime Exposure: {{annual_asset_downtime_cost}}
- Legacy Maintenance Baseline Spend: {{existing_break_fix_spend}}
- Guaranteed Performance Metric: {{target_uptime_sla}}
- Executive Champions & Skeptics: {{operations_and_finance_champions}}
- Proposed Commercial Framework: {{tiered_shared_risk_model}}
Task
Author a comprehensive board-level meeting facilitation script designed to pitch a multi-year, outcome-based service agreement account expansion plan to executive leadership at {{industrial_conglomerate}}, converting {{existing_break_fix_spend}} into {{tiered_shared_risk_model}}.
Method
- Analyze the conflicting incentives between traditional break-fix models and {{tiered_shared_risk_model}} using {{annual_asset_downtime_cost}} as the primary financial lever.
- Write an impactful C-suite opening script positioning equipment availability as a direct driver of corporate EBITDA and capital efficiency.
- Script a forensic breakdown of {{existing_break_fix_spend}}, exposing hidden costs including emergency freight, unallocated labor, and buffer inventory carrying costs.
- Draft the dialogue explaining the mechanical mechanics and telemetry guarantees required to support {{target_uptime_sla}}.
- Formulate a collaborative negotiation sequence for presenting {{tiered_shared_risk_model}}, showing gain-share mechanics when uptime exceeds targets.
- Script targeted interactions designed for {{operations_and_finance_champions}}, directly answering CFO financial risk questions and VP Operations throughput demands.
- Detail exact verbal phrasing to handle pushback on risk allocation, contractual penalties, and data governance for edge-connected machinery.
- Structure a closing script that leads to agreement on a 90-day baseline telemetry validation audit.
Constraints
- MUST address specific financial balance-sheet implications (e.g., OPEX vs. CAPEX, cash flow smoothing, working capital).
- MUST NOT make performance promises without linking them directly to the governance stipulations in {{target_uptime_sla}}.
- Script dialogues MUST distinctly differentiate between the CFO voice and the VP of Operations voice.
- Include explicit speaking cues indicating pace, emphasis words, and visual slide transitions.
Output format
Provide the deliverable structured as follows:
- Executive Meeting Strategic Intent (Context briefing, attendee psychology, win conditions)
- Executive Opening: Shifting the Value Paradigm (Word-for-word spoken script with slide triggers)
- The Financial Anatomy of Break-Fix: Deconstructing the Baseline (Spoken narrative focusing on {{annual_asset_downtime_cost}} and {{existing_break_fix_spend}})
- The Solution: Outcome-Based Partnership Model (Facilitated script walking through {{tiered_shared_risk_model}} and {{target_uptime_sla}})
- Boardroom Roleplay & Objection Navigation (CFO, COO, and VP Procurement scripted rebuttals and seller responses)
- Decision Lock-In: Closing & Next Steps Agreement (Exact spoken close for the Account Director)
Self-review
- Is the mathematical logic of the shared-risk model clearly articulated in spoken dialogue?
- Does the script account for the differing motivations inside {{operations_and_finance_champions}}?
- Are the financial metrics accurately translated into industrial executive vernacular?
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.