OneVector — Client Setup Capacity Model
The unit: 1 client setup = ~8.5 hrs in-house (one person-day)
Team capacity per week (assuming dedicated setup work, not sales/support):
| Setup staff | Hrs/wk available | Clients/wk | Clients/mo |
|---|---|---|---|
| 1 person, 5 days | 40 hrs | ~4.5 | ~18 |
| 1 person, 4 days (buffer) | 32 hrs | ~3.5 | ~14 |
| 2 people, 5 days | 80 hrs | ~9 | ~36 |
With the 15% overrun buffer (messy stack, slow access, revisions):
| Setup staff | Effective clients/wk | Clients/mo |
|---|---|---|
| 1 person | ~4 | ~16 |
| 2 people | ~8 | ~32 |
Rules of thumb:
- Never book setup hours at 100% — leave ~15% for overruns and rework
- Kickoff calls, review sessions, and launch walkthroughs eat client-side hours but don't count against setup capacity
- Priority (3-day) clients cost the same hours — they just consume calendar slots faster, so they can push your queue
The one number to remember: every client ≈ 8.5 hours ≈ 1 person-day. If you're selling more clients than capacity, either the queue backs up or you need a second set of hands on setup.
Want me to make this a downloadable doc or a sheet you can plug real numbers into?