A resource-loading pricing scenario estimates a proposed team's delivery cost from role, allocation, duration, working hours, and governed cost rates, then compares that cost with the proposed fixed fee. The calculation makes staffing assumptions reviewable before sign-off. It does not prove the scope is deliverable or predict the final margin; delivery and finance still review the assumptions.
In plain words
Resource loading means saying how much of each person’s time the project needs, week by week. A pricing example uses that plan to calculate the cost of a team, compare it with the proposed fee and see the margin. It makes staffing assumptions visible before the price is agreed.
Who this helps: Presales consultants and delivery leads who plan teams and price proposals.
Questions this guide answers:
- What is resource loading in project pricing?
- How do you calculate team cost from allocation?
- How do you compare two staffing options?
What is resource loading, and which inputs does a price need?
Start with the people required to deliver the scope, not an arbitrary discount from the client's budget. A bottom-up scenario needs enough detail to show why the planned labor cost has the value it does.
- Role and level: for example, senior consultant, consultant, or analyst.
- Skill and location: where these affect the governed rate and working-hours policy.
- Allocation: the percentage of a normal working week assigned to the project.
- Duration: the number of periods for which that allocation is planned.
- Cost rate: the approved internal hourly cost used for the role.
- Deal budget: the proposed fixed fee used as the scenario's revenue basis.
- Included cost components: in this example, sales commission and labor overhead.
The example below applies two cost rules: sales commission as a percentage of the price, and labor overhead as a percentage of planned labor. Managed Margin lets finance configure rules like these once, so every pricing strategy uses the same basis.
Worked example: pricing one staffing option
A three-month fixed-price engagement has a proposed price of USD 120,000. The workspace uses a 40-hour week, 52 ÷ 12 weeks per monthly planning period (so three months is 13 weeks), 5% sales commission on the price and 15% overhead on labor.
Step 1: allocation to hours to labor
| Role | Allocation | Planned hours | Cost rate | Planned labor |
|---|---|---|---|---|
| Consultant | 50% for 3 months | 260 | USD 60 | USD 15,600 |
| Senior consultant | 25% for 3 months | 130 | USD 90 | USD 11,700 |
| Analyst | 100% for 3 months | 520 | USD 30 | USD 15,600 |
| Total | 910 | USD 42,900 |
A full-time person for three months is 40 × (52 ÷ 12) × 3 = 520 hours, so a 50% allocation is 260 and a 25% allocation is 130. A twelve-week engagement is a different duration (480 hours at 100%) and should be entered as weeks.
Step 2: apply the two cost rules
- Commission = 120,000 × 5% = USD 6,000.
- Overhead = 42,900 × 15% = USD 6,435.
Step 3: the scenario result
| Line | Amount |
|---|---|
| Price | USD 120,000 |
| Labor | − USD 42,900 |
| Commission | − USD 6,000 |
| Overhead | − USD 6,435 |
| Margin | USD 64,665 (53.89%) |
The result means the entered assumptions leave USD 64,665 after these three cost categories. It is not a forecast: subcontractors, travel, shared costs, scope changes and the real role mix can change it later.
How do you compare two staffing options?
Suppose Option B adds more senior-consultant time and reduces analyst allocation. The deal budget, commission rate, and overhead policy stay unchanged.
| Input or result | Option A | Option B | Review question |
|---|---|---|---|
| Consultant allocation | 50% | 50% | Is the core delivery capacity unchanged? |
| Senior allocation | 25% | 50% | Does the scope require more senior judgment? |
| Analyst allocation | 100% | 75% | Can less analyst capacity still deliver the work? |
| Planned labor | USD 42,900 | USD 50,700 | Is the higher-cost mix operationally justified? |
| Commission + overhead | USD 12,435 | USD 13,605 | Were the same cost policies applied? |
| Calculated margin | USD 64,665 / 53.89% | USD 55,695 / 46.41% | Which option balances delivery confidence and margin? |
Option A has the higher calculated margin, but that does not automatically make it the right option. If the project genuinely needs the added senior capacity, approving the lower-cost plan may simply hide delivery risk. Presales supplies the commercial context; delivery tests whether the staffing plan can execute the scope; finance checks the cost policy and result.
What happens after one option is chosen?
The selected scenario should become a controlled starting point, not a screenshot that is forgotten after sign-off. Preserve the approved price, chosen role mix, duration, allocation assumptions, calculation policy, and alternatives considered.
In Managed Margin, finalizing the strategy makes it the approved pricing baseline and keeps each line’s planning rate as a snapshot. After handover, delivery turns the plan into seats and names the people who fill them; if a substitute costs more than the planned role, the difference shows in the forecast rather than being absorbed quietly.
Once delivery begins, use the planned-versus-actual project margin review to compare recorded effort with this approved baseline, or track it in project margin tracking software.
What does a pricing example like this not prove?
- It does not predict final hours, final costs, completion date, or final margin.
- It does not test scope completeness, delivery quality, client dependency, or schedule feasibility.
- It does not recommend a price or a target margin.
- It does not use client billing rates, because this is a fixed-price example; time-and-materials revenue would come from billable hours at those rates.
- It does not include every cost category that may apply to a live project.
- It does not replace approval by people who understand the work and the firm's cost policy.
For the commercial product workflow, see project pricing and scenario planning. For the broader operating context, return to the professional-services project margin guide.
- Resource Loading Scenarios: Compare Team Options for a Bid
- Project Baseline Handoff: From Sales to Delivery
Real example: a presales consultant compares two team shapes
An illustrative story with invented figures, to show how the idea works in a real office.
Marta, a presales consultant, is asked to price a USD 90,000 job two ways for her manager. (Direct labor only: commission and overhead are left out to keep the example simple.) Option A: one senior at 50% and two juniors at 100% for 10 weeks. Option B: two seniors at 50% and one junior at 100%.
Senior cost is USD 90 an hour and junior USD 45; a week is 40 hours. In Option A the senior works 20 hours a week for 10 weeks (200 hours at USD 90, USD 18,000) and the two juniors work 800 hours at USD 45 (USD 36,000). Cost is USD 54,000, a 40% margin on the fee.
Option B has seniors for 400 hours (USD 36,000) and one junior for 400 hours (USD 18,000), also USD 54,000. The cost is the same, but Option A gives 1,000 hours of capacity against 800 hours in Option B, while Option B puts more senior experience on the work. Hours are not interchangeable capacity: compare the two only if both would deliver the same accepted output, and test that with the delivery lead before treating 1,000 and 800 hours as equal. Marta shows both to her manager, who asks delivery which team they could actually staff.
When do you use resource loading in pricing?
| Stage | Owner | Checkpoint |
|---|---|---|
| Collect inputs | Presales consultant | Roles, allocations, months, approved rates and cost rules are all stated |
| Load and cost | Presales consultant | Hours reconcile to allocations; the 52 ÷ 12 convention is applied the same way to every option |
| Compare options | Presales lead with delivery | Higher margin is not chosen if it hides delivery risk |
| Approve and hand over | Final approver, project manager | Chosen option, rates and alternatives are preserved as the baseline |
Resource loading pricing: frequently asked questions
How should two scenarios be compared?
At the same scope and fee, looking at cost, margin and delivery risk.
What should happen after one is selected?
It becomes the baseline for delivery, as in the sales-to-delivery handoff guide.
What is resource loading in project pricing?
Placing each role on the project timeline with an allocation (for example 50% for three months), converting that to hours, and multiplying by the approved cost rate to get planned labor cost. For a consultant at 50% over three months, that is 260 hours.
Continue the sequence: guides to read next
- Resource-Based Estimating: How to Estimate Project Cost: the estimate that feeds the scenarios
Sources and methodology
- Project Management Institute, Planned Resources and Cost. Used for the principle that planned resources and cost estimates should be built from explicit assumptions.
- UK Infrastructure and Projects Authority, Cost Estimating Guidance. Used for transparent assumptions and estimate review.
- The formula and handover boundaries were reviewed against the current Managed Margin application on 26 September 2026. Every monetary amount and role in the example is synthetic.