What's the difference between capacity planning and quota planning, and why does the cheat sheet treat them as separate steps?

Capacity planning answers "how much can our team realistically sell given headcount, ramp, and attrition?" — quota planning then converts that modeled capacity into rep-level numbers with ramp curves, seasonality, and attainability targets. Conflating the two is how you end up with top-down quotas that look fine on a slide but have no grounding in what your actual team can produce. The cheat sheet separates them because the math has to flow in order: capacity first, quotas second, or you're just guessing.

What data do I actually need before I can build the capacity model in this cheat sheet?

At minimum, you need active headcount by role with start dates, historical ARR per AE and win rates by segment (pull from the last 4–6 quarters of CRM opportunity data), and current pipeline by segment versus your 3–4× coverage target. Without clean ramp curves and segment-level win rates, your capacity math will be off — medians by segment beat company-wide averages here. If your CRM data is messy, fix the firmographic fields first; the territory design step depends on clean industry, size, and region data.

Do I need a dedicated comp tool or CPQ system to apply the comp planning section, or can I run this in a spreadsheet?

You can absolutely build the comp plan design, payout curves, and cost scenarios in a spreadsheet — the cheat sheet's comp workflow is structured around a workbook output, not a specific platform. Where a system like a CPQ or comp tool earns its keep is in automating crediting rules, territory transfers, and proration at scale so you're not manually tracking exceptions. If you're under ~50 reps, a well-structured spreadsheet with a clear policy one-pager will cover most of what's here.

How do I know if my quota design is actually calibrated correctly and not just set to a number that feels right?

The cheat sheet gives you a concrete test: 70–80% of fully ramped reps should hit quota in a well-designed plan. If you're seeing attainment rates below 60% or above 90%, something is off — either the quotas are disconnected from modeled capacity or your territory potential is uneven. Run the P10/P50/P90 attainment curve the cheat sheet describes and compare it monthly against actuals; drift from that distribution is your early warning signal.

Which parts of this revenue planning process should stay human-led versus where can I lean on automation or AI?

The judgment calls — territory boundary decisions, quota calibration trade-offs, comp modifier design, and scenario interpretation — need human sign-off from CRO, CFO, and Sales VPs, as the RACI in the cheat sheet makes clear. Automation earns its place in the mechanical work: pulling CRM opportunity data, calculating pipeline-per-rep math, uploading quota values, and enforcing territory logic in your CRM or CPQ. The risk is automating the inputs before the assumptions are validated; run the manager focus groups and stakeholder reviews first, then let systems enforce the decisions.

How often should I revisit territories and quotas once the plan is live, and what should trigger an off-cycle review?

The cheat sheet recommends a bi-annual territory refresh with a lightweight change log, and weekly recalculation of capacity assumptions during the planning cycle before freezing at go-live. Off-cycle reviews are warranted when attrition spikes above the ~20% buffer you've modeled, a rep transfers mid-period, or pipeline coverage drops below the 3–4× threshold in a segment. The key is having a published change policy so mid-year adjustments follow a documented process — manager to RevOps to Finance — rather than becoming one-off escalations.