Estimate how much defined-scope client work fits into your available freelance schedule. Instead of treating every working hour as sellable, the calculator removes recurring non-billable time and then compares the remaining capacity with the average hours required for one scoped engagement.
This is useful for deciding how many statements of work you can run concurrently, whether a pipeline can fit into the next week, and when new work should be scheduled rather than accepted immediately. The project count is an average derived from hours, so deadline clustering and client dependencies still need separate judgment.
1. Define the week
Enter the number of hours you actually plan to work during a representative week.
2. Account for non-billable obligations
Subtract administration, prospecting, internal planning, and other time that cannot be assigned to client scope delivery.
3. Estimate one scope
Enter the typical delivery hours for a single defined scope of work.
4. Check the capacity ratio
Use the billable-hour result as the main limit and the scopes-per-week figure as a rough workload translation.
This is a time-capacity model. It assumes the average scope-hour estimate and non-billable workload are representative of the week being planned.
The main result is the weekly client-delivery time remaining after non-billable work has been removed.
Results depend on the assumptions you enter; use realistic inputs and update them when workload, costs, or pricing conditions change.
Given:
Calculation:
Billable capacity = 36 − 9 = 27 hr/week
Average scopes per week = 27 ÷ 16 = 1.69
Billable share = 27 ÷ 36 × 100 = 75.0%
Result:
27.0 billable hours per week, equivalent to about 1.69 average scopes.
Because complete scopes may not divide neatly into a week, the project count is best used for pipeline pacing rather than as a literal weekly booking target.
It represents capacity as an average. A value of 1.5 means the available weekly hours equal one and a half typical scopes, not that a half project must be sold.
If the meetings are included in what the client pays for, include them in scope hours. If they are general sales or administrative meetings, put them in non-billable time.
Run separate scenarios for small, typical, and large scopes. A single average is most useful when project effort is reasonably consistent.
No. It measures total hours, not calendar sequencing. Several projects can fit by hours and still create an unrealistic deadline cluster.
Indirectly. Once you know realistic billable capacity, you can pair it with a required-rate estimate to see whether your available hours can support your income goal.