How do you measure CAC payback under outcome pricing in 2027?
Direct Answer
Traditional CAC payback = months to recover acquisition cost from gross margin, but outcome pricing (Intercom Fin at $0.99 per resolution, Aviso per-accuracy, Salesforce Agentforce per-action, OpenAI per-token) breaks the formula because revenue is variable, lagged, and consumption-shaped.
The 2027 fix is five reformulations: (1) replace ACV with T12M (trailing-12-month customer revenue annualized); (2) replace gross margin with outcome-derived contribution margin that nets the COGS of every billed outcome; (3) add a consumption-ramp curve to the payback model (Snowflake's filings imply an 18-24 month ramp to run-rate); (4) split CAC by motion — PLG-self-serve / inbound-AE / outbound-AE / enterprise; and (5) introduce a leading-indicator payback built from activation and expansion proxies until T12M data exists.
The new boardroom metric is AI-attributed CAC — the share of CAC sourced by autonomous agents (11x, Artisan, Clay) — and Bessemer's Cloud 100 still grades a healthy payback at 12-18 months at Series B, under 12 at scale.
1. Why Traditional CAC Payback Breaks Under Outcome Pricing
The classic formula — CAC ÷ (ACV × Gross Margin) in months — assumes three things that outcome pricing violates. First, ACV is fixed at signature: in outcome pricing, the contract caps usage or sets a per-event rate, but the actual revenue depends on customer demand. Second, gross margin is stable: in outcome pricing, each Fin resolution costs Intercom inference + escalation, so margin moves with the model and the mix.
Third, revenue starts on day one: in outcome models, revenue starts when the first event fires, which can be 30-90 days post-close and ramps for 6-24 months.
2. The Five Reformulations
2.1 Replace ACV With T12M
Use trailing-12-month revenue, annualized as the numerator. For a customer 8 months in, T12M = (sum of 8 months × 12 ÷ 8). Snowflake reports 125% NRR on this basis, and Datadog, MongoDB, and Stripe all publish T12M-equivalent metrics in their 10-Ks.
The advantage: T12M reflects actual consumption, not the contract ceiling, and removes the perverse incentive to oversize commits.
2.2 Replace Gross Margin With Outcome-Derived Contribution Margin
Strip out the direct COGS of each billed outcome — for Intercom Fin, that is LLM inference + human-fallback cost; for Salesforce Agentforce, the Flex Credit consumption + Hyperforce compute; for Aviso, the forecast-accuracy guarantee reserve. The result is a per-outcome contribution margin, typically 55-72% in 2026 for AI-agent SKUs, versus the 75-82% seat-based SaaS norm.
2.3 Add A Consumption Ramp Curve
Replace the constant-revenue assumption with an explicit ramp curve. Public disclosures and analyst models (Bessemer, Mostly Metrics, OpenView Consumption Sales Index) suggest:
- Months 0-3: 10-25% of run-rate (pilot, integration)
- Months 4-9: 40-70% of run-rate (production rollout)
- Months 10-18: 80-100% of run-rate (steady state)
- Months 19-24+: 100-130% (expansion to new use cases, the NRR lift)
Fold this curve directly into the payback calculation so finance stops over-counting Month-3 revenue.
2.4 Split CAC By Motion
A single blended CAC hides which acquisition motion is actually paying back. The 2027 standard is a four-motion split:
| Motion | Typical Payback | CAC Driver | Tooling |
|---|---|---|---|
| PLG self-serve | 3-9 months | Product + paid acquisition | Pendo, Heap, Amplitude, Stripe |
| Inbound AE | 9-15 months | Marketing + AE comp | HubSpot, Marketo, Clari, Gong |
| Outbound AE | 15-24 months | SDR + AE + tooling | Outreach, Salesloft, Clay, Common Room |
| Enterprise | 18-30 months | AE + SE + exec sponsorship | Salesforce, Clari, Gong, MEDDICC discipline |
Bessemer Cloud 100 companies report blended payback that masks PLG paying back in 6 months while enterprise drags at 26 — the split is the only way to allocate growth dollars rationally.
2.5 Leading-Indicator Payback
Before T12M exists, build a proxy payback from leading indicators: activation rate (first valuable outcome within 14 days), expansion velocity (second use case within 90 days), and outcome density (events per active user per week). Stripe, Twilio, and Snowflake all use a "committed consumption forecast" built from these proxies as their internal CAC-payback truth source.
3. The Math, Worked
Consider an Intercom-like AI agent vendor closing a $100K committed-spend outcome contract.
Two numbers fall out: the steady-state payback (the marketing-deck number) and the ramp-inclusive payback (the CFO number). Publish both. Hiding the ramp is how Series B companies surprise themselves at the Series C raise.
4. AI-Attributed CAC: The New Boardroom Metric
When 11x Alice, Artisan Ava, and Clay workflows source pipeline, the conventional CAC denominator quietly shifts. The 2027 instrumentation pattern:
- Stamp every opportunity with a source_agent_id in Salesforce.
- Roll those into a quarterly AI-attributed pipeline % (Bessemer Cloud 100 median crossed 22% in Q1 2027).
- Compute AI-attributed CAC = (agent platform spend + AI Agent Ops headcount + inference) ÷ (closed-won ARR sourced by agents).
- Benchmark against human-AE CAC. When AI-attributed CAC is 40-60% below human-AE CAC, OpenView and Tomasz Tunguz call it the "agent advantage line" and recommend rebalancing pipeline mix.
Clari, Gong, Salesloft, and Outreach all shipped AI-attribution columns in their 2026 releases, so the data is now native to the forecast stack — no Snowflake gymnastics required.
5. Tooling The Reformulated Payback
The analytics stack that makes outcome-pricing CAC payback computable in real time:
| Layer | Tools | Owner |
|---|---|---|
| Source of truth | Salesforce, HubSpot | Systems |
| Forecast and ramp curves | Clari, Aviso | Sales Ops |
| Consumption telemetry | Snowflake, Datadog | Analytics |
| Billing and reconciliation | Stripe Billing, Metronome, Orb | Finance + Deal Desk |
| Modeling layer | dbt, Hightouch, Looker, Mode | Analytics |
| AI attribution | Clari, Gong, Common Room | Sales Ops + AI Agent Ops |
The Stripe / Metronome / Orb layer is the load-bearing addition for 2027: outcome contracts produce per-event invoices that legacy ARR systems cannot reconcile, and Finance needs the metering data joined to Salesforce opportunities to compute T12M-based payback correctly.
6. Benchmarks To Hold Yourself To
- Bessemer Cloud 100: 12-18 months healthy CAC payback at Series B, <12 at scale.
- OpenView Consumption Sales Index: PLG payback <9 months, enterprise <24 months.
- Snowflake / Datadog / Stripe public filings: 125-135% NRR, <15 month payback on T12M basis.
- Pavilion 2026 Benchmark Survey: median outcome-pricing payback 17.4 months end-to-end (ramp-inclusive).
- Rule of 40 still applies — but the growth half must be computed on T12M consumption, not booked ACV, or the rule lies.
7. FAQ
7.1 Why is ACV the wrong numerator under outcome pricing?
ACV reflects the contract ceiling, not the realized consumption. Outcome contracts routinely under-consume the cap in year one and over-consume by year three. T12M annualized is the only honest numerator.
7.2 What is a healthy CAC payback in 2027?
12-18 months at Series B, under 12 at scale, per Bessemer Cloud 100. Outcome-pricing companies should publish two numbers: steady-state payback and ramp-inclusive payback.
7.3 How long does the consumption ramp take?
18-24 months to run-rate is the modal answer across Snowflake, Datadog, MongoDB, and Stripe public disclosures. Pilots produce 10-25% of run-rate revenue in months 0-3.
7.4 How do I compute AI-attributed CAC?
Stamp every opportunity with a source_agent_id in Salesforce, then divide (agent platform spend + AI Agent Ops headcount + inference cost) by agent-sourced closed-won ARR. Clari, Gong, Salesloft, and Outreach ship native AI-attribution columns as of 2026.
7.5 Should I report a single blended CAC payback to the board?
No. Report the four-motion split — PLG / inbound AE / outbound AE / enterprise — plus the AI-attributed cut. A blended number hides which motion is actually paying back and which is destroying cash.
7.6 What new tools do I need for outcome-pricing CAC math?
A metering and billing layer — Stripe Billing, Metronome, or Orb — joined to Salesforce opportunities, with Snowflake + dbt + Hightouch + Looker computing T12M and contribution margin downstream. Without metering, T12M and outcome-derived margin are uncomputable.
Bottom Line
Outcome pricing did not kill CAC payback — it killed the lazy version of CAC payback. Swap ACV for T12M, swap gross margin for outcome-contribution margin, model the 18-24 month ramp explicitly, split CAC by four motions, and add AI-attributed CAC as the metric the 2027 board actually cares about.
Companies that publish both steady-state and ramp-inclusive payback raise their next round on the front foot.
Sources
- Bessemer Venture Partners — Cloud 100 Benchmarks Report 2026
- OpenView Partners — 2026 Consumption Sales Index and SaaS Benchmarks
- Snowflake — Q4 FY2026 10-K and consumption-revenue commentary
- Datadog — FY2026 investor disclosures on customer ramp
- Stripe — 2026 outcome and usage-billing benchmarks
- Intercom — Fin AI Agent outcomes and per-resolution pricing
- Salesforce — Agentforce pricing models and FY2026 results
- Pavilion — 2026 Outcome Pricing Benchmark Survey
- Tomasz Tunguz — AI-Attributed CAC and the Agent Advantage Line (2026)
- Mostly Metrics — How Snowflake Forecasts Consumption-Based Revenue
- Gartner — 2026 Forecast: Outcome-Based Pricing in Enterprise SaaS