Reasoning & math
AuraScore 85/100

Paid Acquisition Payback Velocity Model

Model channel-specific customer acquisition costs and payback periods to establish scaling thresholds.

Deploy this framework before scaling growth budgets across paid marketing channels. It evaluates cash conversion cycles and unit economics to prevent premature scaling.

Template

Role: Growth Marketing Econometrician specializing in performance marketing unit economics and customer acquisition math.

Context

  • Focus Channel: {{primary_channel}}
  • Monthly Capital Allocation: {{monthly_ad_spend}}
  • Baseline Deal Value: {{average_contract_value}}
  • Conversion Benchmark: {{funnel_conversion_rate}}
  • Customer Lifetime Span: {{retention_period_months}}
  • Pipeline Duration: {{sales_cycle_days}}

Task

Construct a CAC Payback and Capital Efficiency Framework that establishes clear scaling triggers, payback timelines, and budget risk boundaries for {{primary_channel}}.

Method

  1. Establish the maximum allowable Customer Acquisition Cost (CAC) using {{average_contract_value}} and {{retention_period_months}}.
  2. Compute the current blended and paid CAC using {{monthly_ad_spend}} and {{funnel_conversion_rate}}.
  3. Model the cash-flow trough by integrating {{sales_cycle_days}} into working capital burn calculations.
  4. Calculate the Months-to-Payback metric across three customer retention curves.
  5. Determine the Marginal Efficiency Threshold (the CAC inflection point where scaling decays ROI).
  6. Formulate a sensitivity grid mapping conversion fluctuations to payback velocity.
  7. Establish discrete scaling triggers based on capital recovery timelines.

Constraints

  • MUST show explicit arithmetic derivations for CAC, LTV:CAC, and payback velocity.
  • MUST NOT assume instant cash realization; pipeline lag from {{sales_cycle_days}} must be accounted for.
  • Keep formulas transparent and avoid unverified attribution assumptions.
  • Recommendations must be segmented into safe, neutral, and high-risk capital deployment zones.

Output format

  1. Unit Economics & CAC Ledger (derived acquisition cost, payback months, and margin)
  2. Payback Velocity Matrix (3 scenarios: conversion drop, baseline, conversion gain)
  3. Channel Scaling Protocol (3-phase allocation rules based on payback benchmarks)
  4. Risk Guardrails & Abort Triggers (maximum 4 bullet points)

Self-review

  • Did I accurately factor the time value of money and pipeline delays into payback calculations?
  • Does every scaling trigger correspond to a mathematically viable CAC boundary?
  • Are all calculations derived strictly from the supplied budget and conversion variables?
AuraScore breakdown
85/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 efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

research-analysis
research-reasoning-math
business-strategy-marketing-sales
cac
growth-marketing
unit-economics