You're spending $800,000 a year on support and customer success for your $10M ARR company.
Customer education — the thing that reduces that $800,000 — costs about $5,000 to start.
That's 0.05% of revenue. Less than 1% of what you're already spending on the problem it solves.
But you don't have budget for it.
Let's examine that.
The Spending You Don't Question
SaaS Capital's 2024 benchmarks put customer support and success spending at 8% of ARR for private B2B SaaS companies. For a $10M ARR company, that's $800,000 per year.
Here's what that $800,000 buys:
Support agents answering the same "how do I...?" questions. Every day. From every new customer. The same answers, typed from scratch or pasted from an internal doc that may or may not be current.
TSIA's research shows 60-70% of those tickets are knowledge-gap questions — things that could be answered by a well-written article the customer could find themselves.
At $25-35 per ticket (SaaS Capital 2024), that's $360,000-$588,000 per year you're spending on questions that have known answers. Not complex edge cases. Not bugs. Known answers that nobody wrote down in a place customers could find them.
Nobody questions that $800,000. It's just what support costs.
The Spending That Gets Questioned
Now someone proposes a customer education program. The immediate questions:
"What's the budget?"
"What's the headcount?"
"What's the ROI?"
"Can we justify this to the board?"
The Forrester Total Economic Impact study on Intellum (2024, based on interviews with 122 organizations) found the investment required: 0.051% of revenue in Year 1, scaling to 0.145% by Year 3.
For a $10M ARR company:
Year 1: $5,100
Year 2: $10,200
Year 3: $14,500
The same study found 372% ROI over three years and a 7-month payback period.
So the math is: spend $5,100 to start reducing $360,000-$588,000 in preventable support costs. A 70:1 ratio between the problem and the investment.
But the $800,000 doesn't need a business case. The $5,100 does.
Why the Asymmetry Exists
Support spending is invisible because it grows incrementally. You hired one support person. Then two. Then three. Each hire felt justified because ticket volume was up. Nobody ever summed the trajectory and asked: "Are we solving the problem or staffing it?"
Education spending is visible because it's new. New line items require justification. Existing line items just require continuation.
This is the budget illusion: the assumption that current spending is optimized and new spending is risky. In reality, current spending is often the riskiest position — you're paying a recurring cost for a problem that compounds while the solution sits unfunded.
What 96% Already Know
Forrester and Intellum surveyed 300 organizations with customer education programs in 2024. The results:
96% report positive ROI.
38.3% increase in product adoption.
35% increase in customer lifetime value.
28.9% increase in win rates.
15.5% decrease in support costs.
These aren't projections. They're measured results from 300 real programs.
But here's the number that matters most for the budget conversation: only 4% of companies have formalized customer education programs (Intellum 2024). Which means 96% either haven't started or are doing it ad hoc — unfunded, unstaffed, unmeasured.
The companies that DID formalize? 78% of high-success organizations have formalized programs, versus 35% of low-success organizations (Forrester/Intellum 2024).
Formalization — the thing that requires budget — is the variable that separates success from failure.
The Real Budget Question
The budget objection assumes a binary: allocate budget or don't.
But you're already spending the budget. You're just spending it on the wrong thing.
Every knowledge-gap ticket that costs $25-35 to answer manually could cost $0.50-$2.37 as a self-service interaction (SaaS Capital, Fullview 2025). That's a 10-70x cost difference for the same outcome: a customer who gets their question answered.
The question isn't "do we have budget for customer education?"
The question is "can we afford to keep spending $25-35 per answer when the same answer costs $0.50-$2.37 delivered once and served to everyone?"
The Phased Approach Nobody Tries
The budget illusion also assumes you need to fund a full program upfront. You don't.
Phase 0 (Week 1, $0): Export your top 10 support tickets by frequency. Write one help article for the #1 question. Publish it. Link it in your auto-reply for that ticket category. Measure the deflection after 30 days. (This was the 30-day pilot from our last post.)
Phase 1 (Month 2-3, $0-$500): Write articles for tickets #2-#10. You now have a mini knowledge base covering 60-80% of your ticket volume (Pareto principle). Measure total deflection. Calculate savings.
Phase 2 (Month 4-6, $2,000-$5,000): Use measured results from Phase 1 to build the business case. You now have real data, not projections. Present: "We reduced tickets by X%, saving $Y per month. Investing $Z in a proper platform will let us scale this to the full customer base."
By Phase 2, you're not asking for budget. You're presenting measured returns and asking to invest in scaling what's already working.
This is exactly how Forrester documented the 7-month payback: phased deployment, measured results at each stage, reinvestment from proven savings.
The Comparison Nobody Makes
Customer education at 0.05% of revenue is:
Less than your annual coffee budget.
Less than one month of a single support agent's salary.
Less than the annual cost of your project management tool.
Less than what you lose to a single churned mid-market customer.
For reference, the average employee training spend is 2.9% of revenue (ATD 2024). Customer education — which directly reduces churn, deflects tickets, accelerates onboarding, and increases expansion revenue — costs 0.05%.
You spend 58x more training your own employees than teaching your customers how to succeed with your product. The employees already know how to use it. The customers don't.
The 5.7x Risk of Doing Nothing
Skilljar's 2025 report (100+ customer education teams) found that teams unable to demonstrate their program's impact are 5.7x more likely to face budget cuts.
But here's the twist: the teams that have no program at all face something worse than budget cuts. They face invisible losses that nobody attributes to the missing program:
Churn that's chalked up to "competitive pressure" (when the real cause was onboarding failure).
Support costs that are chalked up to "growth" (when the real cause is knowledge gaps).
Expansion revenue that never materializes (because customers use 6% of features and think that's all there is).
These costs don't show up in a line item. They show up in your churn rate, your NPS score, your support headcount, and your NRR. They're real. They're recurring. And they compound.
For a $10M ARR company with 12% median churn (ChurnFree 2026), 5-25x replacement cost (Bain), and $25-35/ticket support costs (SaaS Capital), the annual cost of not having customer education is conservatively $500,000-$1,000,000.
The investment to start: $5,100.
That's not a budget question. That's a math question.
Three Questions for Your Next Budget Conversation
1. What percentage of our support tickets are knowledge-gap questions that a well-written article could answer? (Industry benchmark: 60-70%, TSIA.)
2. What are we spending annually on support for our current customer base? How much of that is answering the same questions repeatedly?
3. If we could reduce support tickets by 20% through customer education (conservative vs. the 38% measured by Screendesk/Kloeckner Metals in 30 days), what would that save annually?
If the answers to those three questions don't justify a $5,000 investment, customer education isn't your problem. But if you're like the 96% of organizations that report positive ROI — and the 96% that haven't formalized a program yet — the budget isn't missing. It's misallocated.
---
We're building Omumu for the teams that see the math but don't have the infrastructure. One platform where education, onboarding, and business outcomes live in one system — so you can start with a $0 pilot and scale with measured results.
If you're running customer education at a B2B SaaS company (or thinking about starting), join the waitlist accessibility.link.new-tab — we're building this with early customers, not in isolation.