Choose your lens
Use hours, tickets, deliverables, response windows, or any other unit you can describe consistently. The label remains yours.
Service planning · tool
Make room
before you promise.
Plan recurring service capacity with your own unit, cycle, reservations, one-off commitments, and anonymous retainers. Browser-only tool with visible assumptions.
Browser-onlyMicro-unit mathNo customer data
Local scenario · no saved state
Put every commitment in one cycle view.
Name the unit yourself. Add capacity, operational reserves, one-off work, and anonymous retainers; the result keeps a safe buffer visible per period.
Your period view will appear here.
Enter a unit, aligned start date, capacities, and a non-zero new retainer scenario, then calculate.
Planning output uses only your inputs; it is not a capacity, delivery, contract, or revenue guarantee.
A visible method
The assumptions stay in the room.
Protect the cycle
Reserved and one-off units sit beside retainer included usage. Buffers are rounded per retainer before they are added together.
Test one more
The post-add scenario shows the load of one new retainer and floors the safe same-spec count by the tightest positive period.
Read this before using the number
A planning lens, not a promise.
Planning output uses only your inputs; it is not a capacity, delivery, contract, or revenue guarantee. Do not enter customer names, contract text, rates, or addresses.
Source notes
Cycle context, not platform rules.
- Upwork recurring weekly paymentsConfirms a recurring support workflow context; this planner does not copy platform hours, rates, or rules.
- Stripe subscription lifecycleProvides general cycle vocabulary; this preview does not connect billing or model prorations.
- Stripe usage-based billing overviewSupports a user-entered usage lens; no platform thresholds, prices, or default units are included.
FAQ
The scope stays explicit.
What is a retainer capacity scenario?
It is a period-by-period planning view built from your own custom unit, available capacity, reservations, one-off commitments, and anonymous included usage.
Does the planner assume hours, tickets, or a market standard?
No. You name the unit and enter every capacity, usage, and buffer assumption. The page does not interpret that label as an industry definition.
Can I share or save the values?
No. This tool deliberately keeps values in the current browser session. It has no share link, URL state, saved inputs, or account. Calculation inputs stay in this browser. If you allow analytics, Google receives usage events without input values. Only your analytics preference is saved.
Is the result a delivery promise?
No. Planning output uses only your inputs; it is not a capacity, delivery, contract, or revenue guarantee.