Interactive Tool · Chapter 22

CS Capacity Planner: Forecast Customer Success Capacity From Designed Effort

Find out when the customer work you have designed will exceed the capacity of the team available to perform it. The planner builds demand from designed effort (preparation, execution, and follow-through) and compares it with realistic team availability month by month for 12 months. The model behind it: How Many Customers Should a CSM Manage? and Chapter 22.

How the planner works: inputs, outputs, and assumptions

Inputs

  • Forecast growth: new high-touch and low-touch customers by month.
  • Current customers: existing customers by contract start month, so each follows its own lifecycle.
  • Designed effort: hours per customer by lifecycle month, for year one and for year two and beyond, by touch model.
  • Team capacity: current staff, future hires with start dates, and new-hire ramp (default 25%, 50%, 75%).
  • Availability: workable hours by month, target availability (default 65%), and the share of direct time held for reactive work (default 30%).

Outputs

  • Monthly demand against available capacity for 12 months.
  • Utilization by month, the first month over capacity, and peak utilization.
  • Additional headcount needed and when to start hiring to cover ramp.
  • Scenarios: base plan, conservative hiring, growth upside, and service redesign.
  • Context figures such as team cost and supported revenue.

Assumptions to challenge

  • 65% availability is a planning starting point, not a benchmark. Validate it against how your team spends its time.
  • Default effort values are starting assumptions. Replace them with your own plays and estimates.
  • It is a planning model, not a precision forecast. Its value is making the work and the assumptions visible.
  • When demand exceeds capacity, hiring is one option. Redesigning, automating, shifting, or explicitly reducing service moments are others.
Loading…