Product management
AuraScore 89/100

Usage-Based Pricing Sensitivity and Margin Report

Model unit economics, gross margin impacts, and churn sensitivity across user cohorts for usage-based product pricing.

Apply this template when restructuring SaaS or API pricing models based on consumption tiers. It delivers a mathematically rigorous report detailing margin preservation, revenue elasticity, and cohort-specific risk exposures.

Template

Role: Product Lead specializing in monetization models, unit economics, and quantitative pricing analytics.

Context

  • Target offering: {{product_tier}}
  • Cost of goods sold structure: {{current_cogs_breakdown}}
  • Proposed consumption rate card: {{proposed_rate_card}}
  • Historical user consumption patterns: {{cohort_consumption_data}}
  • Target unit profitability: {{target_gross_margin}}
  • Churn exposure ceiling: {{churn_risk_threshold}}

Task

Generate a quantitative pricing sensitivity report that evaluates the financial viability of {{proposed_rate_card}} on {{product_tier}}, projecting gross margin changes and cohort migration risks.

Method

  1. Model baseline revenue and cost dynamics using {{cohort_consumption_data}} against {{current_cogs_breakdown}}.
  2. Simulate revenue capture across light, median, and heavy usage deciles under {{proposed_rate_card}}.
  3. Compute projected gross margins per cohort and benchmark results against {{target_gross_margin}}.
  4. Calculate price elasticity and identify user clusters exceeding the {{churn_risk_threshold}}.
  5. Run stress-test scenarios for extreme volumetric usage spikes and compute margin erosion floors.
  6. Formulate tiered mitigation mechanisms, such as volume discounts or minimum commitments, to protect margin stability.
  7. Deliver a phased migration roadmap that balances monetization upside with account retention.

Constraints

  • MUST provide explicit mathematical formulas for all margin and elasticity calculations.
  • MUST present a side-by-side financial comparison table across at least three consumption percentiles.
  • MUST NOT omit infrastructure variable costs detailed in {{current_cogs_breakdown}}.
  • Keep strategic narratives concise; prioritize tabular financial projections and sensitivity bounds.

Output format

  • Format: Markdown report
  • Structure: Financial Overview, Unit Economics Breakdown (table), Cohort Sensitivity Analysis, Margin Stress-Testing Results, Phased Implementation Plan
  • Length: 900 to 1,300 words

Self-review

  • Ensure all quantitative calculations reconcile with the stated {{target_gross_margin}}.
  • Verify that high-risk cohorts are explicitly bounded by {{churn_risk_threshold}}.
  • Check that every variable from context is actively utilized in the analysis.
AuraScore breakdown
89/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 engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification14/14 · Strong

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 efficiency7/10 · Adequate

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.

business-strategy
business-product
complex-reasoning-analysis-math
product management
pricing
unit economics