A one-person business does not have forty project hours each week. Sales, support, administration, learning, and recovery all draw from the same human system. Plans fail when calendar time is mistaken for delivery capacity.
The practical answer is to promise from a conservative capacity budget, then allocate that budget to outcomes—not fill every available hour with tasks.
Calculate a credible weekly budget
Start with the hours you are genuinely willing and able to work. Subtract:
- fixed meetings and personal constraints;
- recurring administration and customer support;
- sales and relationship work;
- maintenance and operational duties;
- a buffer for uncertainty and recovery.
What remains is project capacity. If thirty hours remain, do not schedule thirty. Reserve part of it for variance, especially when the work is new or externally dependent.
Use three capacity buckets
Committed
Work tied to customer promises, legal or financial dates, and already accepted responsibilities.
Growth
Experiments, product improvements, marketing, and sales work that may create future value.
Resilience
Maintenance, documentation, recovery, health, and the buffer that prevents one surprise from collapsing the week.
A useful week needs all three. The percentages will change with cash and obligations, but deleting resilience every week eventually makes committed work less reliable.
Convert capacity into outcome slots
Instead of scheduling twelve projects, define two or three meaningful weekly outcomes. Estimate each as a range, not a point. A new integration might require six to ten focused hours; a familiar report might need two to three.
Then test the plan:
- Does the high end fit the available budget?
- Is any outcome waiting on someone else?
- Which work can pause without breaking a promise?
- What will be dropped first if an urgent issue appears?
If there is no honest answer to the last question, the plan has no buffer.
Track variance without blaming yourself
At the end of the week, compare estimated and actual effort. Label the cause: unclear requirements, interruption, dependency, underestimated complexity, rework, or low energy. Use the pattern to improve future ranges.
Capacity planning is not a moral score. Its purpose is to make promises more trustworthy and protect attention for work that deserves it.
Warning signs of overcommitment
- every project is marked active;
- growth work happens only at night;
- support interrupts the same deep-work block every day;
- the plan assumes every dependency arrives on time;
- missed work is moved forward without removing anything;
- recovery time is treated as a reward rather than infrastructure.
When these appear, reduce simultaneous outcomes before optimizing your calendar.
A compact weekly capacity card
Available working hours:
Committed operations:
Uncertainty buffer:
Project capacity:
Committed outcome(s):
Growth outcome:
Resilience work:
First item to defer if conditions change:
Pair this with cash-flow-aware prioritization when short-term survival must influence allocation.
FAQ
How large should the buffer be?
Use recent variance. Stable, repeated work may need a small buffer; unfamiliar or dependency-heavy work needs more. If you have no data, start conservatively and adjust after several weeks.
Should meetings count as capacity?
Yes. Meetings consume time and often create preparation and follow-up work. Count the whole footprint, not only the minutes on the call.
What if every commitment is urgent?
Rank by consequence: legal or safety exposure, customer harm, cash timing, reversibility, and relationship impact. “Urgent” is a label; consequence reveals the real order.
Make the plan survivable
A good weekly plan still works when one reasonable surprise occurs. PlanovAI can combine commitments, project states, risks, and prior effort into a compact operating view, helping you choose a credible week without turning capacity tracking into another job.