Unit Economics Payback Sensitivity Specification
Evaluate CAC payback and margin thresholds across customer tiers to define a mathematical unit economics specification.
Use this template when planning pricing restructuring, sales incentive changes, or customer segment expansion. It models payback timelines and margin sensitivities into an actionable commercial specification.
Role: Senior B2B SaaS Commercial Strategist specializing in unit economics modeling and pricing architectures.
Context
- Product: {{saas_product_name}}
- Target Customer Segment: {{target_customer_tier}}
- Average Contract Value: {{average_contract_value}}
- Fully Loaded CAC: {{estimated_cac}}
- Target Gross Margin: {{gross_margin_percentage}}
- Net Revenue Retention Rate: {{expected_net_revenue_retention}}
Task
Synthesize the provided revenue metrics for {{saas_product_name}} into a definitive unit economics sensitivity specification that identifies CAC payback thresholds, cash recovery milestones, and scenario-based margin vulnerabilities.
Method
- Calculate the raw monthly recurring revenue (MRR) equivalent from {{average_contract_value}}.
- Apply {{gross_margin_percentage}} to establish the baseline gross profit contribution per account per month.
- Compute the unadjusted CAC payback period in months using {{estimated_cac}} and monthly gross profit.
- Incorporate {{expected_net_revenue_retention}} to derive an expansion-adjusted payback timeline.
- Model three distinct sensitivity scenarios: standard retention, a 15% churn spike, and a 20% CAC escalation.
- Determine the critical threshold where CAC payback exceeds acceptable working capital limits for {{target_customer_tier}}.
- Formulate specific guardrails for allowable sales discount percentages that protect target gross payback windows.
Constraints
- MUST calculate exact month-to-payback figures showing step-by-step arithmetic.
- MUST NOT make qualitative assumptions about conversion velocity without mathematical justification.
- MUST present all monetary comparisons in normalized monthly terms.
- All scenario projections must reference the baseline values provided in the context.
Output format
Return a clean markdown document with four titled sections:
- Baseline Metric Formulas & Computed Constants
- Payback Matrix (Tabular sensitivity analysis across 3 scenarios)
- Margin Vulnerability Thresholds (Bullet list with numerical limits)
- Operational Guardrails Specification (Concise policy table) Keep the total specification under 650 words.
Self-review
- Did I calculate exact payback months for all three sensitivity scenarios?
- Are all inputs from the context explicitly integrated into the baseline formulas?
- Does the document conform strictly to the four requested output sections?
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.