Capacity Planning for Solo Delivery — Know When You Are Full Before You Overbook
Overbooking is the classic solo-founder failure because capacity feels abstract: each project individually fits, and the sum quietly does not. Capacity planning makes the abstract visible — hours per client, a board that shows the true load, and booking rules that say yes only when the hours exist.
The system takes one afternoon to build and prevents the specific quarter where you deliver everything late, badly, and resentfully.
The short answer
- Solo founders systematically underestimate recurring client load by 30-50% — measured hours fix the estimate.
- A visible capacity board prevents the incremental overbooking that no single "yes" reveals.
- Keeping 15-20% unbooked capacity absorbs the urgent work that otherwise breaks the whole schedule.
Who this playbook is for
Built for solo founders who keep saying yes to great projects and then drowning in the sum of them.
Step 1: Measure real hours per client with two weeks of tracking
Track actual time per client or project for two weeks — estimates are fiction, especially for retainers. The numbers usually shock: the "5-hour client" is nine. This measurement is the foundation; every rule below runs on these real hours, never on feelings.
Step 2: Build the weekly capacity board
One view: available hours per week (say 25 billable), minus recurring commitments, shows open capacity as a number. Active projects and retainers listed with their measured weekly hours. The board answers instantly: "Can I take this project starting in two weeks?" — a question answered by arithmetic instead of optimism.
Step 3: Set booking rules that survive pressure
Rules: book against the board, not against the calendar’s whitespace; keep 15-20% unbooked buffer; no new project starting until a current one closes if open capacity is under one week. New inquiries get start dates from the board — "I can start March 3" — which converts overbooking pressure into scheduling professionalism.
Step 4: Install the overload early-warning
Two triggers checked weekly: projected hours over available for any coming week, and any client’s actual hours running 25% over estimate for two weeks straight. Either trigger fires a response — scope conversation, deadline shift, or help — while it is still cheap. Overload is visible weeks before it is catastrophic, but only if you look.
Step 5: Raise prices when the board says you are full
The board doubles as a pricing signal: if you are consistently booked 3+ weeks out at 95%+ capacity, the market is telling you the price is wrong. Raise 20-30%, which filters demand back toward capacity. Full boards are not a throughput problem — they are a price signal wearing a calendar costume.
Your weekly operating rhythm
| Day | Action | Time |
|---|---|---|
| Setup | Two-week time tracking; build the board; set rules | afternoon |
| Friday | Update the board; check both overload triggers | 15 min |
| Per inquiry | Answer start dates from the board, not from hope | 5 min |
| Quarterly | Re-measure hours; adjust estimates and buffer | 1 hr |
KPIs that tell you it is working
| Metric | Healthy target | Why it matters |
|---|---|---|
| Booked capacity | 80-85% steady state | Fuller than that and the buffer is fictional |
| Estimate accuracy | Within 20% after a quarter | Improves automatically with measurement loops |
| Overload weeks per quarter | Zero tolerated without action | The early-warning system’s output |
| Weeks booked out | 2-3+ at high utilization | The raise-prices signal |
Common mistakes to avoid
- Planning capacity on billable ideals (40 hours) instead of reality (25-30 after sales, admin, life). The board must use sustainable hours or it lies beautifully.
- Letting "just this once" overbooking become the norm. Exceptions get logged with a make-up plan or the buffer evaporates within a quarter.
- Ignoring recurring clients when adding project work. Retainers quietly occupy real hours; the board counts them or new projects land on top of invisible commitments.
A tool stack that fits a one-person budget
| Tool | Where it fits |
|---|---|
| Toggl / Clockify | The two-week honest measurement |
| Notion / Airtable | The capacity board with per-client hours |
| Calendar | Booking against measured availability |
| Your Friday review | The trigger check that keeps it honest |
Keep going
Use these internal references while implementing this guide:
- One Person Company Hub
- How to Start a One Person Company
- Solopreneur Operating System
- The Solo Founder Time Audit
- The Decision Journal for Solo Founders
- The 45-Minute Weekly Ops Review
FAQ
Q: How many hours should a solo founder actually plan for?
Sustainable billable capacity is typically 25-30 hours weekly for service businesses — the rest goes to sales, admin, marketing and being a person. Plan delivery against 25 until measurement proves your real number, and re-verify quarterly because it drifts.
Q: What do I do when a great project arrives but the board is full?
Start-date it honestly: "I’m booked through March — I can start April 1, or refer you to someone excellent for sooner." Great projects wait for great operators more often than founders expect; fake availability is how great projects turn into late projects.
Q: How does this work with lumpy project work?
Lumpy load is why the buffer exists: projects convert to hours-per-week averages for the board, with peak weeks flagged. If two project peaks collide, the warning trigger fires weeks early — that is exactly the collision the system exists to prevent.
Q: Should I hire when I’m consistently full?
First raise prices and watch what falls out. If the board stays full at the higher price and the work you decline is work you would enjoy keeping — that is the hiring (or productization) signal. A full board at higher prices is a better business, not automatically a bigger team.
Get the weekly operating brief
Every Monday: 3 moves, 5 minutes. Actionable strategy for your one-person company — no fluff, no filler.