How to Calculate and Lower CAC Using Statsig

Written by: Aaron Rovner, Founder, Saas Hero | Last updated: August 31, 2026

Key Takeaways

• Statsig lowers CAC by improving conversion rates through A/B testing and feature flags. Teams acquire more customers without raising spend.
• The platform provides funnel analysis, experiment results, and CRM integrations. These features track and measure the inputs that drive CAC calculations.
• Three core mechanisms, conversion rate gains, reduced wasted spend on ineffective changes, and a cost-effective experimentation platform, directly reduce the CAC numerator and boost the denominator.
• A practical workflow of defining CAC inputs, setting up funnels, running experiments, measuring impact, and recalculating CAC shows how teams can achieve a 23% reduction (from $1,000 to $769) in real-world examples.
• See how SaaSHero connects experimentation to revenue and lowers your CAC.

Why CAC Matters for B2B SaaS

Customer acquisition cost (CAC) uses a simple formula: CAC = Total Sales and Marketing Costs ÷ Number of New Customers Acquired. A company spending $1M in a quarter to acquire 20,000 new customers has a CAC of $50. The denominator must count only new paying customers acquired in that period, not leads, MQLs, or free users, per Sprints & Sneakers’ CAC guide.

CAC is a critical unit-economics metric for B2B SaaS for several reasons:

• The evidence states that an LTV:CAC ratio of 3:1 is generally considered healthy for SaaS.
• The evidence states that a CAC payback period under 12 months is considered strong.
• Median CAC varies dramatically by GTM motion: $702 for self-serve PLG, $3,840 for mid-market sales-led, and $11,400 for enterprise sales-led, per Digital Applied’s 2026 data.

CAC is a ratio, not a fixed number. Teams can lower it by reducing the numerator, which is spend, or increasing the denominator, which is customers acquired. Statsig’s experimentation infrastructure focuses on the denominator, which is why the next section explores how Statsig’s analytics layer supports CAC tracking.

How Statsig Supports CAC Calculation: The Analytics Layer

Statsig does not directly calculate CAC. It provides the analytics and experimentation infrastructure to track the inputs and measure the impact of changes on CAC.

Statsig’s features map to CAC inputs in the following ways:

• Funnel analysis tracks conversion events such as sign-ups, activations, and paid conversions. It identifies drop-off points. Statsig’s product and web analytics capture events, funnels, and retention views in the same project as flags and experiments, per Experimentation Club’s platform review.
• Experiment results quantify the impact of changes on conversion rates. These changes feed directly into CAC calculations.
• Integrations with Segment, Rudderstack, Hightouch, and mParticle connect Statsig with CRM data and ad platforms, per Statsig’s documentation.

The table below summarizes how each core Statsig feature tracks a specific CAC input and the mechanism it uses.

How Statsig Lowers CAC: Three Mechanisms

1. Conversion Rate Gains from Experiments

Statsig’s feature gates and A/B testing improve activation and conversion rates, which directly reduces CAC. The experimentation layer supports server-side and client-side A/B testing tied to flags. It includes CUPED variance reduction and sequential testing, per Spotify Confidence’s platform comparison.

A B2B SaaS company runs an A/B test on its onboarding flow using Statsig. Variant B simplifies the setup wizard from five steps to three. The experiment shows a 20% lift in activation rate, from 10% to 12%. This lift increases the number of customers acquired from the same ad spend. CAC falls without any budget change.

2. Cutting Wasted Spend on Losing Ideas

Statsig’s feature flags allow teams to validate changes before full rollout and avoid investment in ineffective features or campaigns. When a feature underperforms, a team can turn it off with one click, per Statsig’s Microsoft Marketplace listing.

A team plans a new pricing page. Instead of shipping it to 100% of traffic, they use Statsig to test it on 10% first. If the test shows no improvement or a decline in conversion, they roll it back. The team avoids wasting engineering time and ad spend on a change that fails to perform.

3. Lower Tooling Costs with a Single Platform

Statsig is a cost-effective alternative to legacy analytics and experimentation tools. Its free Developer tier includes 2M events per month, unlimited flag checks, and 50,000 session replays, per ABTesting.cc’s verified pricing data. The Pro tier is a flat $150 per month and does not use usage-based pricing on flags.

A team replacing LaunchDarkly, Mixpanel, and Contentsquare with Statsig saves approximately $2,589 per month at 10M events, per CheckThat.ai’s pricing analysis. That software savings directly reduces the “Total Sales and Marketing Costs” numerator in the CAC formula.

Learn how SaaSHero can help you cut tool costs while improving experimentation.

Step-by-Step Workflow: Using Statsig to Calculate and Lower CAC

Step 1: Define CAC Inputs

Start by identifying all sales and marketing costs such as ad spend, salaries, tools, and agency fees, and define what counts as a “new customer” such as first paid subscription. A fully-loaded CAC model includes media spend, sales wages tied to new logo acquisition, marketing salaries, and software costs. This is according to Sprints & Sneakers’ CAC guide. Once you have these inputs, match the time period between numerator and denominator. If measuring quarterly CAC, count only customers acquired in that quarter.

Step 2: Set Up Statsig Funnels

Create funnels for key conversion paths such as sign-up → activation → paid conversion. Statsig’s funnel analysis captures events and retention views in the same project as flags and experiments, per Experimentation Club. When setting up these funnels, avoid tracking only top-of-funnel signups. The activation-to-paid conversion step is where CAC reduction actually happens.

Step 3: Run Experiments

Use Statsig’s A/B testing and feature gates to test changes that could improve conversion rates. Focus on high-leverage areas such as onboarding flow, pricing page copy, and activation emails. Statsig’s power analysis calculator estimates experiment duration based on actual user behavior patterns, per Statsig’s engineering blog.

Step 4: Measure Impact

Use Statsig’s experiment results to quantify the change in conversion rate. Statsig’s Pulse feature automatically analyzes results across hundreds of metrics and surfaces unexpected impacts. These can include downstream effects on retention or revenue when testing an onboarding flow, per Contentsquare’s A/B testing guide.

Step 5: Recalculate CAC

Apply the new conversion rate to the CAC formula to show the reduction. The worked example below makes the math concrete.

Worked Example: Reducing CAC from $1,000 to $769

Before the experiment:

• Monthly sales and marketing spend: $100,000
• Monthly sign-ups: 1,000
• Activation rate (sign-up → paid): 10%
• New customers: 100
• CAC: $100,000 ÷ 100 = $1,000

The experiment: A B2B SaaS company runs an onboarding experiment using Statsig. The team tests a simplified setup wizard with three steps instead of five against the original.

Results:

• Activation rate improves from 10% to 12%, which is a 20% relative lift
• New customers from the same 1,000 sign-ups: 120
• New CAC: $100,000 ÷ 120 = $769

The CAC reduction came entirely from the denominator, which means more customers from the same spend. The team did not cut budget. Companies with structured A/B testing programs see conversion rates improve by 30% or more annually, per Charle Agency’s A/B testing guide.

Talk with SaaSHero about tying experiments to pipeline and closed revenue, not just activation counts.

Projecting CAC Gains with Aggregated Impact

Statsig’s aggregated impact feature projects the cumulative effect of multiple experiments on key metrics like CAC. After running three experiments such as onboarding simplification, a pricing page headline test, and activation email optimization, Statsig’s aggregated impact can show a projected 15% reduction in CAC. This projection allows growth teams to communicate expected ROI to a CFO or board before all experiments are fully rolled out. It also strengthens the business case for continued investment in the experimentation program.

Frequently Asked Questions

How long does it take to see CAC improvements with Statsig?

Meaningful lifts in activation and conversion can appear within weeks or a few months of focused work. Larger system changes take longer. B2B SaaS sales cycles mean the full CAC impact may take 60 to 90 days to materialize, especially when measuring paid conversion rather than trial starts. The key is to start with one high-leverage experiment such as onboarding simplification and build from there rather than waiting for a comprehensive program to launch simultaneously.

What team roles should be involved in a Statsig CAC optimization program?

A cross-functional team works best. A growth marketer or product manager should define the CAC inputs and own the metric. An engineer implements Statsig SDKs and feature flags. A data analyst or RevOps lead connects Statsig data to CRM revenue outcomes and distinguishes a form fill from a sales-qualified opportunity. SaaSHero’s model pairs an internal marketing owner who sets goals and approves creative with a specialist execution team covering paid media, landing pages, and attribution across the full acquisition chain.

How do I adapt this process for a smaller versus larger B2B SaaS organization?

Smaller teams, typically under $10M ARR, should start with one high-leverage experiment such as onboarding simplification and use Statsig’s free Developer tier, which includes the features described above. Larger organizations should run multiple concurrent experiments and use Statsig’s aggregated impact feature to prioritize by projected CAC reduction. The core five-step workflow, define inputs, set up funnels, run experiments, measure impact, and recalculate CAC, remains the same regardless of scale. What changes is the number of experiments running in parallel and the sophistication of the CRM integration feeding results back into the ad platforms.

What are the typical risks when using Statsig for CAC reduction?

The biggest risk is running experiments without sufficient sample size, which produces unreliable results. Statsig’s power analysis calculator helps mitigate this by estimating experiment duration from actual traffic patterns. A second risk is optimizing for the wrong metric. A pricing-page test that lifts trial starts but lowers paid conversion is a common self-inflicted wound in self-serve SaaS, as noted in guidance on SaaS A/B testing best practices. A third risk is identity inconsistency. Statsig’s experiment assignments depend on stable user identity keys, and inconsistent identifiers across sessions or devices cause bucket drift and incorrect experiment attribution.

How often should I revisit my CAC optimization process?

CAC should be monitored weekly by channel and campaign, with monthly reviews of the full funnel. Experimentation should be continuous. A 2% improvement repeated across 50 tests compounds to a 165% overall gain, which makes cadence as important as individual test quality. The practical cadence for most B2B SaaS teams is weekly performance updates, bi-weekly strategy reviews to decide what changes, and a quarterly budget analysis to reallocate spend based on what the data shows.

Conclusion: Turn Experimentation into CAC Reduction

Statsig provides the infrastructure to measure the inputs and systematically improve the conversion rates that determine CAC. By running A/B tests on activation and onboarding flows, a B2B SaaS team can reduce CAC by 20% or more without cutting ad spend, as demonstrated by the worked example earlier and other case studies.

The critical step most teams miss is connecting experimentation results to CRM-level revenue outcomes rather than stopping at form-fill counts. An activation lift in Statsig only reduces CAC if the downstream measurement, from sign-up through to sales-qualified opportunity and closed revenue, is in place to confirm it. That connection between the experimentation layer and the CRM record is where the real work happens.

See how SaaSHero builds CAC-focused experimentation programs that rely on CRM revenue data and make your CAC number defensible to your board.