Customer Success Planning and Budgeting: How to Build Your CS Budget and Capacity Plan

Updated October 2026

A customer success budget covers everything the company spends to retain and grow its customers: CSM salaries and variable pay, CS leadership and operations, onboarding, tools, enablement and customer programs. A common range for SaaS companies is 5% to 15% of ARR. Low-touch, product-led models usually sit below that range, while enterprise companies with high-touch coverage often sit above it.

Where your number should land depends on your capacity plan: how many customers you serve, how much work each account needs, and how many people that work takes. In this guide I walk through the two ways CS leaders plan capacity and budget, top-down from financial ratios and bottom-up from the work itself, and how to combine them into a budget you can defend with your CFO.

If you want the models already built, the Customer Success Budget and Capacity Planning Template puts the top-down and bottom-up models side by side in one file.

What goes into a customer success budget

Before you plan a budget, agree with finance on what counts as CS spend. Teams that skip this step end up comparing their number against benchmarks that measure something else.

A complete customer success budget usually falls into three categories:

• People costs: base salary and variable pay (OTE) for every CSM, your leadership and management, and specialized roles like onboarding or implementation managers, CS Operations, and renewal managers if renewals sit in CS. Add benefits and payroll taxes to get fully loaded cost, plus any SPIFFs you plan to run on top of the comp plan.
• Tools and systems: your CS platform, data and analytics, and the digital CS tools you use to reach your low-touch customers.
• Programs and events: enablement and training, customer programs like advocacy and community, customer events, your CS kickoff and offsites, and the travel that goes with them, such as customer visits, executive business reviews and conferences.

Your finance team will likely track travel as its own T&E line, so tag those costs as you plan them.

Decide early whether support, professional services and renewals sit inside the CS budget. Each of those moves your percentage of ARR, so state your scope whenever you compare yourself to a benchmark.

Why customer success planning and budgeting matter

Customer success is a revenue function. It protects the renewal base, drives or sources expansion, and shapes how much of next year’s target the company can count on from existing customers. That makes the CS budget an investment decision that deserves the same rigor as the sales and marketing plan.

A solid plan lets you:

• Size the team to the number of customers and the revenue it has to protect
• Set realistic targets and KPIs for retention and expansion
• Justify investment in tools, specialized roles and enablement
• Show the return on what the company spends on CS

For the planning conversation itself, 2027 CS Planning: Six Moves to Make Before the Budget Is Set walks through what to settle before your budget is due.

Top-down vs bottom-up capacity planning

There are two ways to work out how many people your CS team needs and what it should cost. The top-down approach starts from a ratio, like dividing your ARR by a rule of thumb for ARR per CSM. It’s quick but ignores your engagement model. The bottom-up approach starts from the work: the hours each account takes and the hours each CSM has.

Finance usually thinks in top-down ratios, while your team’s workload is built bottom-up, so the strongest plans use both. I cover how to combine them after walking through each approach.

The top-down approach

The top-down approach sets headcount and budget from high-level financial metrics. The two most common are ARR per CSM and total CS cost as a percentage of ARR.

ARR per CSM

ARR per CSM divides the revenue your team manages by the number of CSMs. The number you’ll hear most often is about $2 million in ARR per CSM, Jason Lemkin’s rule of thumb at SaaStr for where most companies end up at scale.

It’s popular for good reasons:

• Simple to explain: finance and the executive team understand it immediately.
• Tied to revenue: headcount grows with ARR, which makes hiring easier to justify as the business grows.
• Easy to compare: it’s a common shorthand across SaaS companies.

Treat it as a reference point, because ARR per CSM moves with your deal size. In Gainsight and RevOps Squared’s 2023 Evolution of Customer Success report, 64% of companies with an ACV under $25K ran more than 50 customers per CSM, compared with under 10% of companies with an ACV over $250K. Two companies with $10 million in ARR can need very different teams. One sells $500,000 contracts to 20 enterprise customers while the other sells $5,000 plans to 2,000 small businesses.

I treat ARR per CSM as an output of the capacity plan rather than a benchmark to staff against. Build the plan bottom-up, then work out the ARR each CSM owns, for the whole team and for each segment. Leadership thinks in ARR per CSM, so show them the work behind yours.

Total CS cost as a percentage of ARR

This ratio compares the full cost of your CS function to your ARR. It includes salaries, variable pay, tools, training and operations costs. General ranges across SaaS look like this:

• 5% to 15% of ARR: the common range for SaaS companies running a mix of high-touch and scaled coverage.
• Below 5% of ARR: typical for highly automated, low-touch or self-serve models with less complex products.
• Above 15% of ARR: typical for enterprise companies with complex products and high-touch engagement.

The ratio gives you a full view of what CS costs relative to revenue, helps you balance spend across headcount, tools and enablement, and shows whether the function is cost-effective. It’s harder to calculate, though. You need clean data on every cost line. The ratio also doesn’t connect back to the productivity of individual CSMs. Pushed too far, a focus on the cost ratio leads to underinvestment, which shows up later in churn and missed expansion. I break down how spend changes with company stage in How Much Should You Actually Spend on Customer Success?

Customer success team-to-customer ratio benchmarks

You’ll also see benchmarks for how many accounts a CSM should manage. CS has never standardized this ratio, because it depends on your product, your customers, what you’ve promised them and what else sits on your CSMs’ plates. Use these ranges from practice as a guide only:

• High touch: 5 to 20 accounts per CSM
• Mid touch: 30 to 60 accounts per CSM
• Low touch: 100 or more accounts per CSM, often with a pooled team

Your own number comes from the bottom-up approach.

The bottom-up approach to capacity planning

Bottom-up capacity modeling compares the work your customers need with the time your team has. Demand is the hours your accounts need in a year. Supply is the hours your CSMs have for customer work. The gap tells you whether your team can deliver your engagement model and when to add people.

If this sounds familiar, it’s the same logic the World Health Organization uses to staff health facilities. Its Workload Indicators of Staffing Need method works out the workload first and the people second. Applied to a CS team, it comes down to four steps.

Step 1: Estimate hours per account

For one typical account, estimate a year of work. Count three kinds:

• Recurring work: check-ins, value reviews, success plan updates and renewal prep.
• Onboarding: a one-time block of hours for every new account.
• Reactive work: escalations, ad hoc questions and internal coordination with Sales, Product and Support.

Here’s what a year can look like for one high-touch account:

Activity	Times a year	Hours each	Hours a year
Monthly check-in	12	1	12
Quarterly value review, prep included	4	4	16
Success plan update	2	3	6
Executive sponsor touchpoint	4	1	4
Renewal prep	1	6	6
Escalations and ad hoc requests	12	2	24
Internal coordination with Sales, Product and Support	12	2	24
Total			92

A new account also needs a one-time onboarding block, around 40 hours in this example. If you run more than one engagement model, repeat this for each segment. A low-touch account served by a pooled team might take under 10 hours a year.

Product complexity changes the hours. A same-day setup takes far less CSM time than a multi-week implementation with many stakeholders. Customers who need hand-holding after go-live also keep coming back.

Step 2: Work out the hours a CSM actually has

Start with the year: 52 weeks of 40 hours is 2,080 hours. Take out holidays, vacation and sick days. Then take out internal work like team meetings, 1:1s, training, admin and internal projects. What’s left is the time your CSM has for customer work.

Don’t plan to fill all of it. Queueing research going back to J.F.C. Kingman in 1961 shows wait times climb steeply as people get close to fully booked, so a team planned at 100% has no room for renewal season, escalations or the work nobody predicted. Plan to fill a share of those hours, such as 85%, and keep the rest as a buffer.

Step 3: Turn hours into headcount and cost

Divide the planned customer hours per CSM by the hours one account takes. That gives you accounts per CSM. Divide your number of accounts by it to get the CSMs you need, then sense-check the result against the ranges above.

Then add the roles that don’t carry a book: managers, CS Operations, onboarding and renewal specialists. Multiply by fully loaded cost (base, variable pay, benefits and taxes) and add tools, enablement and customer programs. That total is your budget.

Step 4: Plan for next year

Today’s book tells you what you need now. Next year’s plan has to account for:

• New customers: from your targets, the Sales plan, or your last 12 months, turned into accounts.
• Churn: the accounts you expect to lose.
• Attrition: CSMs who leave, and the time until their book is covered again.
• Ramp: new CSMs count as fully productive only once they’ve ramped.

Open each role at least as far ahead as your time to hire plus ramp time, so the capacity is there in the quarter you need it.

A worked example

Here’s a simplified example with illustrative numbers for a high-touch team. Each CSM has 2,080 hours a year. Taking out 25 days off and 7.5 hours a week of internal work leaves about 1,530 hours for customer work. Planning to fill 85% of those gives about 1,300 planned customer hours per CSM.

Input	Value
Accounts	120
Hours per account per year	92
Total hours the accounts need	11,040
Planned customer hours per CSM	1,300
Accounts per CSM	14
CSMs needed	8.5

This team needs eight to nine CSMs before managers and specialist roles. If those 120 accounts bring in $12 million in ARR, each CSM owns about $1.4 million. A top-down $2 million rule would have given this team six CSMs, each carrying about 20 accounts that need 92 hours a year. That difference is the conversation to have with finance. The hours are what back up your side of it.

If you run mid-touch or low-touch segments too, build the same model for each one and add them up.

Strengths and trade-offs of the bottom-up approach

The bottom-up approach ties headcount to the real work in each segment, so resources go where customers need them. It protects your team from overload, evens out workload across CSMs and gives you a clear link between activities and the KPIs you coach.

It has costs too. Activity data takes time to gather and varies from account to account, so your estimates involve judgment. The model needs updating every time the Sales plan or your engagement model changes. Pushed too far, activity tracking can turn into micromanagement, so use it to plan capacity rather than to police how CSMs spend each hour.

Combine both approaches into one plan

The plans that get approved usually combine both approaches. Build your capacity plan bottom-up, cost it, and then check it against the top-down ratios finance will use:

1. Build headcount and cost bottom-up from the hours your accounts need.
2. Calculate the total CS cost as a percentage of ARR and the ARR each CSM owns in your plan.
3. Compare those against your top-down number and the ranges for companies at your stage.
4. If bottom-up needs fewer CSMs than top-down, check that you counted all the work, or confirm your digital journey really carries more of it.
5. If bottom-up needs more CSMs, look for capacity you can free up before you ask for headcount.

There are three places to find that capacity:

• Revisit segmentation: give high touch only to the accounts that need it most, and move the rest to a lighter engagement model.
• Move routine work into digital CS: let automated check-ins, onboarding content, webinars and office hours carry the work that doesn’t need a person.
• Hand off work that doesn’t need a CSM: send it to the team that owns it, such as billing questions to Finance or technical setup to Implementation.

Build the model first and let your headcount number come out of it. The result is a budget built on what your customers need that finance can also read in its own language. For the conversation with your CFO, The CS Budget Playbook covers four plays for making the case for headcount and investment.

Customer success budget template

The Customer Success Budget and Capacity Planning Template puts both approaches in one file. It covers:

• Inputs: your revenue plan (starting ARR, NRR, GRR and ending ARR), people costs, tools and systems, and programs and events
• Top-down: headcount and budget from ARR per CSM and from total CS cost as a percentage of ARR
• Bottom-up: hours per account, the hours a CSM has for customer work after a planning buffer, and the CSMs you need by segment
• Compare: both methods side by side, with the gap between them

Download the Customer Success Budget and Capacity Planning Template

Customer success planning goes beyond the budget

The budget is one output of your customer success plan. A complete plan also covers what CS should and should not own next year, the targets CS commits to, the segmentation and engagement model sized for next year’s scale, the team and org design to deliver it, how CS works with Sales, Product and the rest of the business, and the key initiatives for the year.

If any of those are unsettled, your budget will be too. Settle scope and targets first, then size the team and cost it.

Planning and budgeting customer success comes down to knowing the work your customers need, sizing the team to do it and translating that into numbers finance trusts. Start bottom-up, check against the top-down ratios, and revisit the plan every year as your customers and motion change.