Workforce Analytics Band Restructuring Impact Report
Model revenue and retention impacts of restructuring employee headcount pricing tiers.
Run this template when updating tiered employee-count pricing for HR operations and people analytics enterprise software. It provides sales and revenue leaders with clear trade-off analyses between expansion revenue and churn risk.
Role: Director of Revenue Operations specializing in HR technology and enterprise workforce analytics packaging.
Context
- Account headcount bracket: {{client_headcount_range}}
- Existing employee unit price: {{legacy_rate_per_employee}}
- Proposed tier structure: {{proposed_band_structure}}
- Data sync cadence: {{data_refresh_frequency}}
- Account churn exposure: {{churn_risk_level}}
- Annual target revenue: {{annual_contract_value_goal}}
Task
Author a comprehensive pricing transition report evaluating the migration of accounts in {{client_headcount_range}} to the {{proposed_band_structure}}, balancing {{annual_contract_value_goal}} against {{churn_risk_level}}.
Method
- Analyze historical revenue generated at the {{legacy_rate_per_employee}} rate.
- Map the account's position within {{proposed_band_structure}} to calculate immediate contract value variance.
- Incorporate infrastructure cost adjustments associated with {{data_refresh_frequency}}.
- Quantify potential annual renewal contraction based on {{churn_risk_level}}.
- Design an opt-in incentive strategy for accounts agreeing to multi-year commitments.
- Formulate two concession options that protect base platform pricing.
- Prepare an account-facing justification deck outline connecting pricing to analytical insights.
Constraints
- Pricing models MUST hit or exceed {{annual_contract_value_goal}} without unbundling core analytics.
- You MUST NOT recommend grandfathering {{legacy_rate_per_employee}} beyond a 12-month bridge period.
- Infrastructure cost adjustments MUST reflect {{data_refresh_frequency}} compute overhead.
- Recommendations MUST explicitly address mitigation for {{churn_risk_level}}.
Output format
- Restructuring Impact Overview (1 paragraph, max 100 words)
- Band Migration Financial Model (Summary table: Metric, Pre-Migration, Post-Migration, Variance)
- Grandfathering and Transition Terms (3 clear contractual guidelines)
- Retention Safeguards by Risk Level (2 actionable mitigation tactics)
- Implementation Timeline (4 chronological milestone steps)
Self-review
- Is the 12-month sunset rule for {{legacy_rate_per_employee}} strictly enforced?
- Does the financial model directly address the {{annual_contract_value_goal}}?
- Are all 5 required output sections present and formatted cleanly?
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.