Agent Team Cost and Capacity Planner
Model five bounded workflows against one founder’s weekly review budget. Change the workload, operating profile and cost assumptions, then inspect the review bottleneck before adding more work.
Set your planning assumptions
Your modeled week and month
| Measure | Value | Interpretation |
|---|---|---|
| Planned accepted work / week | ||
| Planned unfinished work / week | Incoming items minus the independent final-acceptance assumption. | |
| Owner time value / month | Noncash valuation of routine review, rescue and maintenance. | |
| Full modeled cost / month | Software plus owner time value; excludes other business costs. | |
| Software cost / planned accepted item | Not a realized unit cost when the review budget is exceeded. | |
| Full cost / planned accepted item | Includes the noncash owner time valuation. | |
| Conditional two-attempt software amount / month | If every incoming item receives two attempts at the stated unit costs. This is not an enforced bill cap. |
Selected profile
Role-level weekly workload
| Role | Incoming | Attempts | Variable CU | Routine h | Rescue h |
|---|
Fixed assumptions and interpretation
The planner models a fixed mix of five types of work. It does not mean five deployed agents, five subscriptions or five employees. Routine review is charged on every attempt. Exception rescue is an additional workload per affected incoming item.
| Role | Mix | CU / attempt | Routine min / attempt | Extra rescue min / exception |
|---|---|---|---|---|
| Research | 10% | 1.20 | 6 | 20 |
| Sales | 20% | 0.25 | 4 | 15 |
| Operations | 20% | 0.80 | 10 | 30 |
| Finance | 10% | 0.15 | 4 | 10 |
| Support | 40% | 0.10 | 3 | 12 |
| Profile | One extra attempt | Exceptions | Final acceptance | Routine-time multiplier |
|---|---|---|---|---|
| Lean | 10% | 5% | 95% | 0.75× |
| Planning | 25% | 10% | 90% | 1.00× |
| Surge | 50% | 25% | 75% | 1.50× |
- Each item receives one initial attempt and at most one extra attempt. Reruns and exceptions may overlap; do not add their shares to estimate unique affected items.
- Final acceptance is an independent scenario assumption, not a result inferred from retry success. Fractions represent planning averages across a workload.
- Maintenance stays at 2 owner hours/week, even when the incoming workload is zero.
- Capacity is an incoming-work limit under the same fixed mix, linear review effort and profile. It does not establish delivery deadlines, queue stability, accepted throughput or profitability.
- No allowance is made for work arrival bursts, parallel-task limits, outages, non-agent fulfillment, taxes, financing, sales activity outside these items or other business expenses.
- The conditional two-attempt software amount assumes unchanged unit costs and no usage beyond the modeled attempts. Actual spending needs separately enforced limits and monitoring.
Formulas and zero-workload behavior
For each role: n = N × role share; attempts = n × (1 + rerun share).
Weekly variable software = sum of attempts × CU per attempt. Routine review hours = sum of attempts × routine minutes × profile multiplier / 60. Rescue hours = sum of n × exception share × extra rescue minutes / 60.
Total owner hours = routine + rescue + 2. Planned accepted = N × final acceptance share. Planned unfinished = N − planned accepted.
Monthly software = fixed monthly cost + weekly variable software × 52/12. Monthly owner time value = total owner hours × 52/12 × chosen hourly value. Full modeled cost is their sum. Per-accepted-item figures divide monthly cost by planned accepted weekly items × 52/12.
Conditional two-attempt software amount = fixed monthly cost + sum of n × 2 × CU per attempt × 52/12.
Incoming capacity = floor(max(0, review budget − 2) / ((routine + rescue) / N)). With zero incoming items, fixed software and maintenance remain; per-accepted costs and incoming capacity are unavailable to avoid division by zero.