Magic Number by Segment
Magic Number by Segment decomposes the company-wide Magic Number — (Net New ARR × 4) / Prior Quarter S&M Spend — into separate calculations for each customer segment (SMB / Mid-Market / Enterprise) or GTM channel (Self-Serve / Inside Sales / Field). The blended Magic Number tells you whether the company is efficient overall; segment-level Magic Number tells you WHERE the efficiency lives. A blended Magic Number of 0.9 (acceptable) can hide enterprise efficiency of 1.5 (excellent) and SMB efficiency of 0.4 (broken). The investment implication is direct: pour S&M into segments with Magic Number > 1.0 (where every dollar in produces more than a dollar of ARR), starve segments with Magic Number < 0.5, and triage the middle.
The Trap
The trap is over-investing in the segment where revenue growth is loudest, not where Magic Number is highest. SMB growth feels exciting (lots of new logos!) but if SMB Magic Number is 0.4, you're burning $1 of S&M to generate $0.40 of ARR — and amplifying it accelerates losses. Conversely, enterprise growth feels slow (one logo at a time) but if enterprise Magic Number is 1.5, every additional dollar there is highly accretive. The second trap is allocating S&M cost to segments incorrectly: if you load all marketing cost onto SMB and only direct sales onto enterprise, you'll inflate enterprise Magic Number artificially.
What to Do
Build a segment-level Magic Number table updated quarterly. For each segment: (1) Net New ARR (new + expansion − contraction − churn), (2) Allocated S&M from prior quarter (allocate marketing programmatically, sales by team), (3) Magic Number = (Net New ARR × 4) / Prior Quarter S&M. Set a re-allocation rule: any segment with Magic Number > 1.2 for two consecutive quarters gets a 25% S&M increase next quarter; any segment below 0.5 for two consecutive quarters gets a 30% S&M cut. Hold yourself to the rule — segments don't 'turn around' without specific intervention, and S&M starvation is often the right call.
Formula
In Practice
Salesforce's annual analyst-day breakdowns historically showed segment-level efficiency: Enterprise (Salesforce CRM Enterprise, $250K+ deals) ran with Magic Number of ~1.2-1.5 for years, while SMB (Essentials, sub-$5K deals) often ran near 0.6-0.8. The strategic response was clear: Salesforce kept investing aggressively in enterprise direct sales while making SMB increasingly self-serve through trials and online onboarding. Compare to Snap's IPO disclosures around DAU monetization — early 2018 cohort analysis showed older user cohorts monetizing at $X per user with new cohorts monetizing at materially less, but Snap continued to invest heavily in user acquisition through Q3 2018, eventually cratering the stock 75% before they triaged segments and rebuilt unit economics by segment.
Pro Tips
- 01
KnowMBA POV: blended Magic Number on the board deck is fine; segment-level Magic Number is what you use to allocate next quarter's hiring plan. If the CFO can't tell you Magic Number for the top 3 customer segments separately, the segment view is fictional.
- 02
When allocating S&M cost to segments, use TOUCH attribution (which sales team and which marketing programs touched the deal) not just deal-size attribution. A 'mid-market' deal closed with enterprise rep involvement should bear some enterprise S&M cost.
- 03
If a segment's Magic Number degrades for two consecutive quarters, the answer is rarely 'try harder.' It's usually 'channel saturation' or 'pricing weakness' — fix the underlying cause or shift S&M to a healthier segment.
Myth vs Reality
Myth
“Magic Number is most useful as a single company-wide number”
Reality
Company-wide Magic Number is a summary metric for boards. Segment-level Magic Number is the actual decision tool. Operating a multi-segment business off the blended number is like steering a car while only looking at the average speed of all four wheels — useful for diagnostics, useless for control.
Myth
“Segments with low Magic Number should be cut entirely”
Reality
Sometimes, but not always. A segment with low Magic Number AND high NDR is an investment thesis (high acquisition cost amortized over long lifetime). A segment with low Magic Number AND low NDR is a clear cut. Always pair Magic Number with retention before deciding.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Challenge coming soon for this concept.
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Magic Number by Segment
Quarterly snapshot; 2+ quarters of trend matters more than single pointPour Capital In
> 1.5
Healthy Investment
1.0 - 1.5
Maintain / Optimize
0.5 - 1.0
Triage
0.3 - 0.5
Stop Investing
< 0.3
Source: Bessemer Cloud Index, OpenView SaaS Benchmarks, Tomasz Tunguz analysis
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Salesforce
2010-2020 segment efficiency
Salesforce's analyst-day disclosures historically broke out efficiency by customer segment. Enterprise (Sales Cloud Enterprise, Service Cloud Enterprise — $250K+ contracts) consistently showed Magic Number of ~1.2-1.5. SMB (Essentials, sub-$5K) often ran at 0.6-0.8. The strategic response was disciplined: Salesforce kept aggressively investing in enterprise field sales (4,000+ AEs at peak) while making SMB increasingly self-serve and inside-sales-driven. By 2020, Enterprise generated 70%+ of revenue with structurally better unit economics. The segment-level discipline drove decade-long stock outperformance.
Enterprise Magic Number
~1.2-1.5
SMB Magic Number
~0.6-0.8
Strategic Response
Field sales for Enterprise, self-serve for SMB
Revenue (2020)
$17B+
Segment-level Magic Number drives capital allocation. Salesforce poured resources into the segment where every dollar of S&M generated $1.20-$1.50 of ARR, and starved the segment where it didn't.
Hypothetical: Series B SaaS over-investing in SMB
2022
Hypothetical: A composite case based on multiple Series B SaaS companies in 2022. ARR $20M, blended Magic Number 0.8 (looked OK). Segment breakdown: Enterprise 1.4, Mid-Market 0.9, SMB 0.3. The company allocated 60% of S&M to SMB because 'SMB volume drives the funnel.' Over 4 quarters, SMB consumed $12M of S&M to generate $3.6M of net new ARR — destroying ~$8M of value. Enterprise was starved at $4M S&M and could have absorbed double that. Series C process revealed the segment problem; valuation came in 40% below founder expectations.
Blended Magic Number
0.8 (looked fine)
SMB Magic Number
0.3 (broken)
Enterprise Magic Number
1.4 (under-resourced)
Series C Outcome
40% below expected valuation
Blended Magic Number hides segment-level capital misallocation. The 'looks OK' blended number is the most expensive deception in SaaS finance.
Decision scenario
The Segment Reallocation Decision
You're CFO of a $35M ARR B2B SaaS company. Segment Magic Numbers (last 2 quarters average): Enterprise 1.5, Mid-Market 0.9, SMB 0.35. Total S&M is $20M/year. Allocation: Enterprise $5M (25%), Mid-Market $7M (35%), SMB $8M (40%). The board wants 50% revenue growth next year; CEO wants to add 8 more SMB reps to drive volume.
ARR
$35M
Total S&M
$20M
Enterprise Magic
1.5
Mid-Market Magic
0.9
SMB Magic
0.35
Growth Target
50%
Decision 1
If you add 8 SMB reps ($300K loaded each = $2.4M additional S&M), at 0.35 Magic Number that generates only ~$840K of additional ARR. Meanwhile Enterprise is under-resourced at $5M (could likely absorb $9-10M with same Magic Number based on quota coverage analysis).
Add 8 SMB reps as the CEO requested — top-of-funnel volume mattersReveal
Reallocate: cut SMB S&M from $8M to $4M (move to self-serve only), shift $4M to Enterprise (now $9M), keep Mid-Market flat. Add Enterprise reps and AE coverage instead of SMB.✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Magic Number by Segment into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Magic Number by Segment into a live operating decision.
Use Magic Number by Segment as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.