Agency delivery team capacity plan template
A client pod priced with contractors, fractional specialists, and subcontract spend.
No credit card. Edit every role, rate, date, and scenario.Why this template exists
A services delivery plan has to balance margin, capability, availability, and contract timing. The team is rarely made of full-time employees alone. Contractors may price monthly, specialists may be shared at 10 or 30 percent, and subcontractor spend may sit outside payroll while still determining whether the engagement works.
This template models engagement leadership, a delivery pod, shared functions, contractors, and vendor spend in one structure. Fractional allocation makes shared capacity visible. The contracted scope becomes the common base for extension and ramp-down scenarios, so a staffing decision can be evaluated without rebuilding the plan.
Decisions it helps you make
- Whether the engagement needs another full pod
- How contractor rates affect delivery margin
- Which specialists are shared and at what allocation
- When a ramp-down should remove capacity
- Whether subcontracting is cheaper than internal hiring
- Which staffing option fits the contracted envelope
What is already in the plan
A client pod priced with contractors, fractional specialists, and subcontract spend.
- Contractors priced from monthly rates, not salaries
- Shared specialists claimed at a fraction of a seat
- Extension and ramp-down as branches of the same pod
What the template costs
The plan opens already priced. At full ramp, when every dated seat has started, the contracted scope runs at an estimated $3,373,250 per year, with a first-year cost of $3,373,250 because seats are priced only for their active months.
| Team | Seats | Annual run rate |
|---|---|---|
| Engagement leadership | 2 | $485,000 |
| Pod A: platform build | 9 | $2,038,500 |
| Shared functions | 4 | $217,750 |
| Subcontract partner pod | Vendor | $570,000 |
| Cloud and licenses (client billed) | Vendor | $62,000 |
| Whole plan | 15 | $3,373,250 |
All figures are labeled benchmark estimates in USD, calculated from the Arrange benchmark rate card with fully loaded annual rates. The app reprices the same template in 7 currencies when you pick one, and every number can be replaced with your own rate. Method: how Arrange calculates workforce cost.
Every seat in the template
Each seat is a typed, costed object with a role, level, allocation, and effective window, so the composition below is exactly what the plan calculates from.
| Team | Role | Level | Seats | Details |
|---|---|---|---|---|
| Engagement leadership | Engagement Lead | Principal / Director (L6) | 1 | |
| Delivery Manager | Staff / Lead (L5) | 1 | ||
| Pod A: platform build | Tech Lead | Staff / Lead (L5) | 1 | |
| Senior Engineer | Senior (L4) | 2 | ||
| Engineer | Mid (L3) | 2 | ||
| Contract Engineer | Senior (L4) | 2 | contractor, monthly rate | |
| Product Designer | Senior (L4) | 1 | 0.5 FTE shared allocation | |
| QA Engineer | Mid (L3) | 1 | 0.5 FTE shared allocation | |
| Shared functions | Solution Architect | Principal / Director (L6) | 1 | 0.2 FTE shared allocation |
| Data Engineer | Senior (L4) | 1 | 0.3 FTE shared allocation | |
| Contracting and legal | Staff / Lead (L5) | 1 | 0.1 FTE shared allocation | |
| Billing and finance | Senior (L4) | 1 | 0.15 FTE shared allocation |
13 seats are marked filled, and 2 are contractors priced from monthly rates. Fractional allocations price the share of a person the team actually uses.
The scenarios included
The template opens on the contracted scope and includes the two staffing decisions every engagement eventually faces: growing the account and winding it down. Both branch from the same pod, so margin conversations compare real numbers.
| Scenario | Seats | Annual run rate | First-year cost | Change |
|---|---|---|---|---|
| Contracted scope | 15 | $3,373,250 | $3,373,250 | the base plan |
| Extension: second pod | 21 | $4,925,750 | $4,487,625 | +$1.6M run rate |
| Ramp down | 13 | $2,719,500 | $2,719,500 | -$653.8K run rate |
Contracted scope. The engagement as sold: leadership, one delivery pod, fractional shared functions, and subcontract spend.
Extension: second pod. Adds a second pod with its own dated start months. This is the branch for the expansion proposal.
Ramp down. Releases the two contract engineers and reduces the shared designer allocation. This is the branch for the wind-down conversation.
Use it in four steps
Replace the sample pod
Edit the engagement roles, levels, and structure. Contractor seats retain monthly-rate behavior while employee seats use annual loaded rates.
Set shared allocations
Assign the fraction of design, architecture, legal, finance, or data capacity the engagement actually consumes instead of pricing whole seats.
Model extension and ramp-down
Use the included scenarios to add capacity or remove the pod over time. Compare both options with the contracted scope and envelope.
Carry the decision into delivery
Share the approved plan, export it for the steering meeting, and retain the request and conditions behind every staffing change.
Frequently asked questions
Can Arrange model contractors and employees together?
Yes. Contractor positions use monthly rates while employee positions use annual loaded rates. Both appear in the same team and roll up to the same plan totals.
Can one specialist be allocated across multiple teams?
Yes. Positions can use fractional allocations, and combined-plan checks can identify named people allocated above 100 percent.
Can I include subcontractor and software costs?
Yes. Vendor objects sit beside positions and teams, so non-payroll spend remains part of the capacity and funding decision.
Open the agency delivery team.
The template becomes your plan. Nothing is locked, and every benchmark number can be replaced.
Start planning freeNo credit card. Your first plan stays free.