The 10% Rule: How Much Should You Really Invest in Customer Success? With the CRO of Notion and VP of CS at GitHub

If you ask ten SaaS executives how much to spend on Customer Success, you will usually get eleven answers, two spreadsheets, and one panicked sigh from finance. That is exactly why the so-called 10% rule keeps showing up in serious post-sales conversations. It gives leaders a clean benchmark: invest roughly 10% of revenue in the full post-sales engine, then earn the right to move above or below it with evidence, not vibes.

That benchmark becomes especially interesting when you look at the perspectives associated with Erica Anderson, CRO of Notion, and Abbas Haider Ali, VP of Customer Success at GitHub. These are not leaders debating theory from a beanbag chair next to a kombucha tap. They have operated inside companies where customer growth, onboarding, adoption, retention, expansion, and product feedback loops all have real financial consequences. And their shared message is refreshingly practical: Customer Success should be treated neither as a cost center you starve nor a luxury spa you overfund. It should be run like a disciplined growth system.

Why the customer success budget question matters more than ever

In subscription and usage-based businesses, revenue does not end when the contract is signed. That is when the real work begins. If customers do not adopt the product, reach value quickly, renew, and expand, your shiny new ARR can leak out faster than office cold brew on a Monday morning.

That is why customer retention, net revenue retention, gross revenue retention, expansion rate, customer health, onboarding speed, and product adoption are not side metrics. They are operating metrics that tell you whether growth is durable. Many of the strongest SaaS and enterprise software companies now treat Customer Success as a lever for endurance, not just friendliness. Nice emails are lovely. Renewals are lovelier.

Notion and GitHub are useful case studies because both companies serve sophisticated users with very different needs. Notion has to help customers get to the “aha” moment fast in a product that is powerful, flexible, and capable of overwhelming people with a blank page if the experience is not guided well. GitHub operates at massive scale across enterprise and developer audiences, where operational rigor, transparency, and measurable value matter enormously. In other words, these are not businesses where Customer Success can survive on good intentions and a smiley-face survey.

What the 10% rule actually means

The smartest interpretation of the 10% rule is simple: use 10% of revenue as the envelope for all post-sales investment. Not just CSM salaries. Not just support. Not just onboarding. The whole machine. That includes some combination of support, implementation, onboarding, success management, technical account management, renewals, digital success, customer education, CS operations, and sometimes pieces of professional services.

This matters because companies often make one of two mistakes. The first is undercounting the real cost of post-sales and pretending they are efficient when they are just hiding expenses across departments. The second is stuffing everything into a vague “customer experience” bucket and calling the spend strategic because nobody wants to be the executive who sounds anti-customer. Both approaches create bad math and worse decisions.

The 10% rule is not magic. It is a discipline. It forces leaders to ask tougher questions: Are we funding activities that truly improve adoption, retention, and expansion? Which work should be automated? Which work should be premium and monetized? Which customers need high-touch coverage, and which customers need a brilliant digital journey instead of twelve meetings and a fruit basket?

Why Notion’s 3.9% target gets attention

One of the most striking talking points around this discussion is that Notion has aimed for a much leaner customer experience spend, around 3.9% of ARR. That does not mean Customer Success is unimportant there. Quite the opposite. It means the company is trying to deliver meaningful outcomes with a highly efficient model. In practical terms, that usually implies strong product-led behavior, sharper segmentation, better onboarding design, cleaner digital workflows, and a constant push to avoid throwing human labor at problems software should solve.

That is the key nuance many leaders miss. Spending less on Customer Success is not inherently impressive. Spending less while preserving or improving customer outcomes is impressive. Otherwise, you are not efficient. You are just underdressed for the weather.

Why GitHub’s operating rigor matters just as much as the budget

GitHub’s side of the conversation highlights a second truth: the budget is only half the story. The other half is operational design. If your Customer Success team cannot define leading indicators, track risk early, and connect its work to retention and expansion, the spend number becomes a guessing game. You are basically budgeting by horoscope.

That is why disciplined operators obsess over frameworks, KPI definitions, journey maps, and clear accountability. A company can spend 7%, 10%, or 12% of revenue on post-sales, but if it has no reliable view into adoption milestones, time-to-value, product usage, executive engagement, onboarding velocity, renewal risk, and expansion triggers, it is not really managing Customer Success. It is just funding it.

So, should you really invest 10%?

For most B2B SaaS and recurring-revenue companies, 10% is a solid benchmark, not a law of nature. Think of it as the default answer before your business earns a customized answer.

You may need to invest more than 10% if:

• Your product is complex and requires heavy implementation or migration support.
• You are serving large enterprise accounts with compliance, security, and change-management needs.
• You are in an intense land-and-expand motion where post-sales work directly lifts expansion and net revenue retention.
• You are navigating a temporary transition, such as platform consolidation, packaging changes, or a new enterprise motion.

You may be able to invest less than 10% if:

• Your product is genuinely intuitive and time-to-value is fast.
• You have strong self-serve onboarding, in-product guidance, and automated lifecycle plays.
• Your segmentation model is sharp, so high-touch coverage is reserved for accounts that truly justify it.
• Your support and education systems do real work instead of existing as decorative corporate houseplants.

The real answer, then, is not “always 10%.” It is: Start with 10%, then prove your way down or justify your way up.

How to allocate the customer success budget intelligently

Once you accept the envelope, the next question is allocation. A healthy Customer Success investment usually spans four layers.

1. Reactive support at the minimum effective dose

Support is essential, but it should not swallow the whole budget. You want a support operation that is fast, reliable, and trusted without becoming an expensive substitute for product clarity or poor onboarding. If customers keep opening tickets because the product is confusing, that is not support demand. That is product and enablement debt wearing a fake mustache.

2. Onboarding and time-to-value

This is where many companies either win early or quietly lose. The faster customers reach meaningful value, the stronger your retention foundation becomes. Notion’s emphasis on helping customers get to the “aha” moment faster is a perfect example of budget going where it changes outcomes, not where it simply looks busy.

3. Ongoing adoption and outcomes

Mature CS teams do not just check in and ask whether everything is “going okay.” They drive usage, champion workflows, surface risk, coordinate stakeholders, and help customers achieve outcomes they can explain to their own executives. This is where Customer Success stops being hospitality and becomes business infrastructure.

4. Expansion, monetization, and leverage

The best teams know how to support growth without destroying trust. That means aligning expansion motions to customer value, not springing upsells like a pop quiz. It also means considering monetized professional services or premium support so the business can protect the core budget while still serving customers with advanced needs.

The metrics that should decide whether your spend is working

If you only track renewals, you are reading the scoreboard after the game is over. Strong Customer Success leaders use both lagging and leading indicators.

Lagging indicators

• Gross Revenue Retention (GRR)
• Net Revenue Retention (NRR)
• Logo retention
• Churn rate
• Expansion revenue

Leading indicators

• Time-to-value
• Onboarding completion rate
• Feature adoption
• Usage by persona or team
• Executive sponsor engagement
• Training participation
• Health score movement
• Support volume tied to known friction points

If your budget goes up while these indicators stall, the solution is not always more people. Sometimes the answer is better segmentation, cleaner playbooks, stronger CS operations, more automation, and a tighter relationship between product, support, and success teams.

Lessons from Notion and GitHub that most teams can apply

First, customer success should be designed around the customer journey, not around org chart tradition. A startup does not need a bloated post-sales department with six specialized titles before it has repeatable adoption. Early on, founder-led or generalist-led success may be exactly right. Later, as scale and complexity increase, specialization becomes more useful.

Second, efficiency is not the enemy of customer care. Notion’s lean spend target suggests that a company can be deeply customer-oriented without defaulting to a labor-heavy model. Smart digital experiences, thoughtful onboarding, and product design can eliminate enormous amounts of unnecessary service cost.

Third, rigor beats folklore. GitHub’s operational style reinforces the idea that Customer Success should have a measurable system behind it. Teams need clear metrics, documented definitions, monthly review habits, and a strong point of view on what leading indicators predict durable revenue.

Fourth, post-sales should help shape the product. Customer Success is closest to the moments where expectations collide with reality. That makes it a gold mine for product insight. If CS only renews accounts and never influences roadmap, messaging, onboarding design, or packaging decisions, the company is leaving value on the table.

What the future of customer success investment probably looks like

The headline may be the 10% rule, but the broader trend is toward smarter, more instrumented, more AI-assisted Customer Success. That does not mean the function disappears. It means repetitive work should decline while strategic work becomes more valuable.

In practical terms, AI and automation can help teams classify feedback, identify risk earlier, route accounts more intelligently, personalize guidance, and scale multilingual or digital support. That could compress the budget envelope for some businesses over time. But the companies that win will not be the ones that blindly cut headcount and call it innovation. They will be the ones that use technology to preserve quality while increasing leverage.

So yes, some organizations may move below 10% in the future. But the bar will stay the same: Can you still create adoption, retention, expansion, and advocacy at that lower cost? If yes, congratulations. If not, you did not invent the future. You just made churn cheaper to produce.

Conclusion: the right answer is disciplined investment, not emotional spending

The 10% rule works because it forces clarity. It reminds executives that Customer Success is not free, but it also cannot be funded like a mystery box labeled “customer love.” The best operators treat post-sales investment as a measurable growth system tied to time-to-value, retention, expansion, and product intelligence.

Notion’s lean target shows what efficient design can look like. GitHub’s operating rigor shows what scalable discipline looks like. Put those together, and the real lesson becomes clear: invest enough to make customers successful, but structure that investment so every dollar earns the right to stay.

If you need one sentence to bring into your next planning meeting, make it this: Start with 10% of revenue for post-sales, then let customer outcomes decide whether you should spend 7%, 10%, or 12%. Not opinion. Not panic. Not whatever the loudest person in the meeting just said after their second espresso.

Operator Notes: Real-World Experiences Teams Keep Running Into

One of the most common experiences companies have with Customer Success investment is realizing they were asking the wrong question all along. They start by asking, “How many CSMs should we hire?” when the better question is, “Where exactly do customers get stuck between purchase and renewal?” That sounds subtle, but it changes everything. Teams that begin with headcount usually end up staffing around symptoms. Teams that begin with friction points build systems that scale.

A second pattern shows up during onboarding. Leaders often believe the product is simple because internal teams use it every day. Then new customers arrive, hit three configuration decisions, invite five stakeholders, and suddenly “intuitive” turns into “Where do I click?” This is where Customer Success proves its value quickly. A great onboarding motion does not just teach features. It creates confidence, aligns use cases, and gets customers to their first visible win. That first win is often what determines whether the account becomes sticky or starts wobbling.

Another experience many post-sales teams learn the hard way is that customers do not buy software just to use software. They buy it to remove friction in their business. That means health scores built only on login frequency can mislead you. An account may log in every day and still be deeply at risk if the wrong team is active, if executive sponsorship disappears, or if adoption is shallow. The strongest teams eventually move from vanity signals to more meaningful ones: activation depth, workflow usage, cross-functional rollout, and signs that the product is embedded in a customer’s operating rhythm.

There is also the budgeting reality nobody loves at first: when Customer Success is not measured rigorously, it becomes vulnerable. In good times, it gets praised as strategic. In tougher quarters, it gets challenged as overhead. That is why experienced operators become almost obsessive about documenting leading indicators, operational definitions, and proof of impact. They know a budget survives when it can explain itself.

Teams also discover that not every customer deserves the same motion. This is usually a breakthrough moment. Once segmentation improves, the business stops overserving low-complexity accounts and underserving strategic ones. Digital-first journeys can carry a surprising amount of weight when they are thoughtfully designed. Meanwhile, high-touch coverage becomes more valuable when it is focused on customers with real expansion, renewal, or risk complexity.

Finally, operators learn that the best Customer Success teams are not merely protecting renewals. They are improving the business itself. They feed product teams better insight. They reveal packaging problems. They expose adoption blockers. They influence roadmap priorities. And they create the kind of customer evidence that sales, marketing, and leadership can all use. That is when Customer Success stops looking like a service layer and starts acting like a strategic engine. At that point, the 10% rule is no longer just a budgeting benchmark. It becomes a test of whether the company truly understands how recurring revenue is built and kept.

SEO Metadata