Size the lane before you price it.
The reference rate answers what a user costs. Capacity planning answers how many users, which work, and how fast — the questions that decide whether the rate is even the right conversation yet.
Four inputs shape how much capacity a lane needs.
None of these are visible from a user count alone. Reviewing them together avoids sizing a lane for the easy scenario and being surprised by the real one. The same inputs also feed a vCIO-style roadmap conversation, if a practice wants delivery to help assemble them.
- User range
- How many people fall inside the lane today, and how fast that number is expected to change.
- Request mix
- The balance between user-support, Microsoft 365, and managed-cadence work, since each carries a different effort profile.
- Existing debt
- Unresolved technical debt or inconsistent baseline conditions that create above-average exception volume at the start.
- Growth trajectory
- Whether the client group is expected to stay flat, grow steadily, or expand in a step — a new location or an acquisition.
A phased rollout keeps sizing honest.
Rather than sizing a lane for a guessed steady state, most client groups are easier to size by starting narrow and watching what actually happens.
Pilot scope: one client group, inside the written lane, for an agreed period.
Watched signals: request mix against what was expected, and exception frequency from the escalation matrix.
Expansion decision: made at the next scheduled review, using the readiness and review-cadence inputs — not assumed in advance.
This is a representative structure, not a projected volume, cost, or margin outcome.
Signals worth watching once a lane is running.
- Is delivery routinely near the edge of what the written lane covers?Frequent near-misses suggest the scope was drawn too tight.
- Are managed-cadence exceptions increasing faster than user count?That points at a baseline or tooling issue, not just growth.
- Would the client group benefit from Plus, or just from clearer scope in Essential?More coverage is not always the right fix for friction.
- Is the pressure from more users, or a wider request mix than originally scoped?The two call for different responses.
Ground the planning conversation in the actual reference rates.
Sizing decisions eventually meet a real number. These are the same CAD per-user reference bands used across the site.
A sized lane is easier to price.
Bring the sizing inputs above into the readiness review before a first commercial conversation.