Churn saves
AuraScore 81/100

Industrial IoT OEM Account Salvage Brief

Synthesize telemetry reliability issues and plant KPIs into an executive-level account salvage brief for manufacturing IoT contracts.

Use this template when a key manufacturing facility threatens non-renewal of connected equipment or predictive maintenance telemetry contracts. It establishes root cause triage, financial exposure calculations, and operational turnaround milestones.

Template

Role: Senior Director of Industrial IoT Customer Success with 15+ years salvaging mission-critical manufacturing accounts.

Context

  • Manufacturing Account: {{plant_operator}}
  • Asset Coverage: {{installed_equipment_fleet}}
  • Outstanding Technical Issues: {{unresolved_telemetry_tickets}}
  • Commercial Exposure: {{contract_arr_at_risk}}
  • Critical Failure Point: {{churn_risk_root_cause}}
  • Key Stakeholder Demands: {{executive_stakeholder_stance}}

Task

Generate a definitive, high-stakes Industrial Account Intervention Brief that outlines the technical, operational, and commercial turnaround strategy to prevent contract termination and secure long-term renewal with {{plant_operator}}.

Method

  1. Deconstruct {{churn_risk_root_cause}} against the operating environment of {{installed_equipment_fleet}}, identifying specific telemetry, gateway, or edge computing vulnerabilities.
  2. Quantify the operational downtime or false-positive alarms tied to {{unresolved_telemetry_tickets}} in terms of lost plant capacity (OEE impact).
  3. Synthesize the posture described in {{executive_stakeholder_stance}} to isolate non-negotiable operational requirements from commercial leverage points.
  4. Design a 30-60-90 day Technical Remediation Stream focusing on sensor calibration, firmware stabilization, and data stream validation.
  5. Construct an OEM Engineering Service Level Agreement (SLA) addendum targeting mean time to detect (MTTD) and mean time to resolve (MTTR).
  6. Formulate a commercial retention structure protecting {{contract_arr_at_risk}}, incorporating temporary performance-linked milestone credits rather than permanent price discounts.
  7. Establish governance cadences bridging the on-site plant reliability team, the plant manager, and executive leadership.

Constraints

  • MUST express all operational impacts in standard industrial metrics (Overall Equipment Effectiveness, MTBF, unplanned downtime hours).
  • MUST NOT offer unapproved baseline software license discounts; all concessions must tie to technical milestones.
  • Brief MUST remain concise, professional, and actionable for senior industrial leadership.
  • Language MUST balance technical telemetry precision with commercial pragmatism.

Output format

Provide a structured brief under the following exact section headers:

  1. Executive Summary & Revenue at Risk (Max 120 words)
  2. Root Cause & Shopfloor Impact Analysis (Numbered breakdown)
  3. 30-60-90 Day Technical & Operational Recovery Plan (Tabular or milestone list)
  4. Retention Commercials & SLA Addendum Terms (Bullet points)
  5. Executive Engagement Protocol & Immediate Next Steps (Chronological list)

Self-review

  • Confirm that {{contract_arr_at_risk}} and {{plant_operator}} are explicitly addressed in the commercial terms.
  • Verify that every item in {{unresolved_telemetry_tickets}} has a corresponding operational remediation step.
  • Ensure no generic SaaS terminology is used where heavy industrial and OT terms apply.
AuraScore breakdown
81/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 engineering12/12 · Strong

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.

support-success
support-churn
manufacturing-industrial
churn saves
industrial iot
manufacturing