Resource-based project cost estimation calculates delivery cost from the people required to perform the work. Define each role, its cost rate, planned allocation, and duration; convert the plan into hours; then add the non-labor costs included by policy. The estimate should record its assumptions, exclusions, source dates, and reviewer.
In plain words
Resource-based estimating works out the cost of a project from the people who will do it: which roles, how many hours each, and what each hour costs. You add up role hours times cost rates, then add any other costs such as travel or software. It is the most common way services firms cost a project because people are the main cost.
Who this helps: Presales consultants and delivery leads who build cost estimates, and the finance and sales staff who turn those costs into a price.
Questions this guide answers:
- What is resource-based estimating?
- How do you build a resource-based cost model?
- How do you estimate project cost from roles and hours?
- What tools support resource estimation in project management?
What is resource-based estimating, and how does it work?
Project Management Institute guidance describes planned project cost as a result of the activity plan, resource assignments, duration, and resource cost rates. A bottom-up estimate aggregates lower-level estimates into a project total. For a services engagement, the lower-level units can be roles or named resources planned by week or month.
The practical sequence is straightforward:
- Define the deliverables and the work needed for each.
- Select the roles, skill levels, and locations required.
- Set each role's allocation for each planning period.
- Convert allocation percentages into planned hours using an explicit standard-hours assumption.
- Multiply planned hours by the approved cost rate.
- Add included direct costs and the firm's documented overhead treatment.
- Record exclusions, uncertainty, and the person who approved the estimate.
Allocation % × standard hours in period = planned resource hours
Planned resource hours × cost rate = planned labor cost
A cost rate needs a defined meaning. It might contain only an hourly pay input, or it might be a loaded rate that includes employment on-costs. The label alone does not settle the policy. Finance should document what is included, and all compared scenarios should use the same definition.
Resource-based estimating example: a three-month IT project
A consulting team estimates a three-month discovery and implementation project (about 13 weeks, because each month is counted as 52 ÷ 12 weeks). The worked numbers use a 40-hour working week. Converting a week-based year to months gives 40 × 52 ÷ 12 = about 173.33 hours for a person allocated 100% for a month.
Step 1: turn allocation into hours and cost
| Role | Monthly allocation | Months | Planned hours | Cost rate | Labor cost |
|---|---|---|---|---|---|
| Engagement lead | 25% | 3 | 130 | USD 95 | USD 12,350 |
| Consultant | 75% | 3 | 390 | USD 55 | USD 21,450 |
| Analyst | 50% | 2 | 173.33 | USD 32 | USD 5,546.67 |
| Total | 693.33 | USD 39,346.67 |
The lead and consultant work three months and the analyst two. Keep the unrounded hours in the calculation and round only what you display.
Step 2: add the other costs
| Line | Amount |
|---|---|
| Labor | USD 39,346.67 |
| Specialist contractor | USD 2,500.00 |
| Overhead at 12% of labor (the firm's policy) | USD 4,721.60 |
| Estimated delivery cost | USD 46,568.27 |
The total is useful because each part can be challenged. Delivery can question the allocations. Finance can verify the rates and the overhead basis. Presales can test the result against the proposed price. One unlabelled top-down number supports none of those conversations.
What should reviewers challenge before sign-off?
| Review area | Question | Evidence | Who answers |
|---|---|---|---|
| Scope coverage | Does every material deliverable have planned effort? | Scope-to-role mapping and exclusions | Presales lead |
| Role mix | Is the skill level realistic for the work? | Delivery review, not a margin percentage | Delivery lead |
| Timing | Are allocations placed in the months the work happens? | A week or month plan with start assumptions | Project manager |
| Rates | Are rates current and defined the same way? | Rate owner and effective date | Finance |
| Completeness | Are non-labor and shared costs treated consistently? | Cost policy and documented exclusions | Finance |
| Uncertainty | Which input would move the estimate most? | A sensitivity check | Presales consultant |
Scenario: the review meeting
The delivery lead reads the table and says the analyst cannot finish in two months: data preparation runs into the third month.
- Analyst extends from two months to three at 50%: 260 hours instead of 173.33.
- Analyst cost becomes 260 × 32 = USD 8,320, so labor rises from USD 39,346.67 to USD 42,120.
- Overhead at 12% becomes USD 5,054.40; with the USD 2,500 contractor the estimate moves from USD 46,568.27 to USD 49,674.40.
- Presales records the change as a correction (a missed piece of work), not as new scope, and re-tests the price.
Keep the reason visible. New client scope or an approved schedule change justifies a revised plan; a missed work package, an invalid allocation or a stale rate means the original estimate needs correcting. For a more structured way to size uncertainty than one guess per input, see three-point estimating with the PERT method.
What does a resource-based estimate not tell you?
A resource-based estimate does not prove the scope is correct, guarantee productivity, or predict the final project outcome. It also does not decide the client price. Value, competition, contract risk, and commercial strategy influence price separately from delivery cost.
Managed Margin turns an estimate like this into a strategy: stages with each role’s loading, or a weekly or monthly grid, hours from each location’s working week, costed at planning rates, with your cost rules and margin layers applied. It can then work the price out from a target Managed Margin; see how to price a project to a target margin. It does not look up market rates or predict delivery performance. See project pricing software.
Not sure resource-based estimating is the right method yet? See the project estimation methods guide. Continue with the broader project-pricing guide, compare resource-loading scenarios, or review the current Managed Margin pricing workflow.
Real example: a delivery lead costs a 12-week data clean-up
An illustrative story with invented figures, to show how the idea works in a real office.
Nina, a delivery lead, is asked to cost a three-month (12-week) data clean-up. She starts with roles, not a total. Using 8-hour days, a lead who spends one day a week for 12 weeks works 96 hours: 96 hours at USD 90 an hour is USD 8,640. An analyst works full time: 480 hours at USD 50 is USD 24,000. A tester works 120 hours at USD 45, which is USD 5,400.
Labor adds up to USD 38,040. She adds USD 1,500 of expenses for a total cost of USD 39,540. The sales team can now turn that cost into a price, and anyone can see what happens if the analyst is needed for two more weeks.
Because the estimate lists roles and hours, a reviewer can challenge a specific line instead of arguing about a total.
When do you use resource-based estimating, and what comes before and after?
| Stage | Owner | Checkpoint |
|---|---|---|
| Scope outline | Presales lead | Deliverables and exclusions are written down |
| Build the estimate | Presales consultant with a delivery lead | Every deliverable has roles, allocation, months and an approved rate |
| Review | Delivery lead and finance | The reviewer's checklist above is answered, and the author is not the only reader |
| Price and approve | Presales lead, finance | The estimate version used for the price is recorded |
| Hand over | Project manager | The estimate becomes the plan that actuals are compared with |
Resource-based estimating: frequently asked questions
What does this estimate not tell you?
It does not forecast revenue or guarantee outcomes; it calculates cost from the inputs.
How does it connect to resource loading?
Loading places the role hours into time, as in the resource-loading guides.
What is resource-based estimating?
Estimating project cost from the people needed: define each role, its cost rate, its allocation and the months it is needed, convert that to hours, multiply by the rate, then add other costs. For example, 130 hours of an engagement lead at USD 95 is USD 12,350.
Continue the sequence: guides to read next
- What Is a Project Rate Card? How to Build One: where the rates come from
- How to Price an IT or Professional Services Project: how professional-services firms set project prices
Sources and methodology
- Project Management Institute, PM101: Estimating. Used for the relationship between resources, duration, cost rates, and project budget.
- Project Management Institute, Lexicon of Project Management Terms, Version 5.0. Used for the bottom-up estimating and baseline definitions.
- UK Infrastructure and Projects Authority, Cost Estimating Guidance. Used for transparency, assurance, documented exclusions, and sensitivity principles.
- The worked example is original. Product statements were reviewed against the current Managed Margin application on 26 September 2026.