Project pricing for professional services converts a defined scope and proposed delivery team into a commercial price. A useful model estimates resource effort by role and period, applies documented cost assumptions, includes relevant non-labor costs, and tests the resulting margin. The selected option should remain traceable when delivery begins.
In plain words
Pricing a services project is different from pricing a product, because the main cost is people’s time. A good price starts from who is needed, at what level, for how many hours, and what those hours cost, then adds the margin you want. A target percentage alone cannot show you whether the plan is realistic.
Who this helps: Presales consultants, project managers and sales managers who build proposals.
Questions this guide answers:
- How do you price a professional services project?
- How do consulting firms set project prices?
- What goes into a services project price?
How is pricing a professional services project different?
In a product business, most of the cost is materials. In a services business, people are the largest controllable cost, so a price is only reliable when it can say who is needed, at what level, for how many hours and over which period.
Three words that are easy to confuse
- Cost is what the firm expects to spend: resources, hours and other inputs. In the example further down, USD 36,000 of labor.
- Price is the amount proposed to the client: USD 80,000 in the same example.
- Margin is what is left of the revenue after the costs the firm includes in its policy (commission and overhead as well as labor). Sales teams sometimes quote the margin on direct cost alone, before commission and overhead, and the result looks better than it is.
Two ways pricing goes wrong
- A price built only from a target percentage can hide an unrealistic team plan.
- A staffing plan built without a commercial calculation can be deliverable but uneconomic.
| Step | Calculation |
|---|---|
| 1 | Planned resource hours × approved cost rate = planned labor cost |
| 2 | Deal budget − included delivery costs = calculated scenario margin |
| 3 | Scenario margin ÷ deal budget × 100 = scenario margin % |
The UK Infrastructure and Projects Authority recommends that cost estimates document their methodology, assumptions, exclusions, evidence and uncertainty. Its guidance is written for public infrastructure rather than consulting proposals, but the control transfers: a decision maker should be able to see how an estimate was built and what could change it.
Which inputs should a project pricing model keep?
The smallest useful model is not necessarily the one with the fewest rows. It is the one that retains enough detail to explain a decision without creating false precision.
| Input | Question it answers | Control to document |
|---|---|---|
| Scope and deliverables | What work is included in the price? | Exclusions, acceptance boundary, and change process. |
| Role and skill mix | What kind of team is required? | Role definitions, skill tags, and delivery reviewer. |
| Location | Which cost and working assumptions apply? | Named location categories and approved rate source. |
| Allocation and duration | How much effort is planned and when? | Percentage or hours, period length, and standard hours basis. |
| Cost rate | What does the planned labor consume? | Rate owner, effective date, and included cost elements. |
| Commercial components | What else reduces the amount available for delivery and margin? | Commission, overhead, direct costs, and exclusions. |
| Deal budget | What revenue basis is being tested? | Currency, pricing model, scope version, and approval status. |
For a deeper calculation method, see resource-based project cost estimation. For rate governance, use the project rate-card guide.
Example: how do you price a proposed IT consulting team?
Assume a fixed-price engagement has an $80,000 proposed deal budget. The presales team models three roles using the firm's approved hourly cost inputs. This is an educational example, not a benchmark or customer result.
| Role | Planned hours | Cost rate | Planned labor cost |
|---|---|---|---|
| Senior consultant | 160 | $80 | $12,800 |
| Consultant | 320 | $50 | $16,000 |
| Analyst | 240 | $30 | $7,200 |
| Total | 720 | — | $36,000 |
If the firm's scenario policy applies 4% sales commission to the $80,000 deal budget and 10% overhead to labor cost, commission is $3,200 and overhead is $3,600. The calculated scenario margin is $37,200, or 46.5% of the deal budget.
$80,000 − $3,200 − $36,000 − $3,600 = $37,200
$37,200 ÷ $80,000 × 100 = 46.5%
That percentage does not prove the team can deliver the scope. Delivery still needs to validate the role mix, effort, and timing. It is also not a forecast of the final result; it is a transparent result from entered assumptions.
Why compare staffing scenarios before you price?
A single scenario invites a yes-or-no reaction. Multiple scenarios make the trade-offs visible. One option may use more senior time and cost more. Another may use a leverage-heavy team but require stronger review. The goal is not automatically to select the highest calculated margin. The goal is to select a plan that is commercially acceptable and operationally credible.
Review each option on the same basis
- Keep the scope and deal-budget definition consistent unless the purpose is to test a scope or price change.
- Use governed cost rates with clear effective dates.
- State commission, overhead, and other included costs rather than hiding them in a percentage.
- Ask delivery to challenge role mix, allocation, timing, and handoffs.
- Retain rejected options for context instead of overwriting the only workbook.
The resource-loading scenario guide includes a three-option comparison and decision checklist.
Give each review question an owner
Pricing works better when approval is shared but accountability is specific.
| Role | Reviews | Can override |
|---|---|---|
| Sales or presales | Client-facing scope, price, and commission assumption | Scope wording and the quoted price |
| Delivery | Role mix, effort, timing, and handoffs | Staffing plan and delivery approach |
| Finance | Rate basis, overhead treatment, currency, and calculation boundary | Cost policy and calculation assumptions |
| Final approver | Which option was selected and which exceptions were accepted | Whether the option proceeds to delivery |
This division prevents a common failure: a commercially attractive spreadsheet passes approval even though nobody has accepted responsibility for delivery feasibility. It also makes later review more useful. A rate exception is different from missing scope; a staffing substitution is different from a price concession. Recording the decision owner and reason lets the team respond to the actual cause rather than debate which version of the proposal was intended.
What should move from pricing into delivery?
The approved price alone is not a usable delivery baseline. The project manager needs the selected role plan, planned effort by period, cost-policy version, commercial assumptions, and scope boundary. Approved changes should be recorded as changes; they should not silently replace the original plan.
In Managed Margin, finalizing a pricing strategy makes it the approved pricing baseline, with each line’s planning rate kept as a snapshot. Handover then checks the client purchase order or agreement and the named project manager, and delivery accepts it and fills the seats with named people. Approved change requests add value and seats without touching the finalized strategy. See the project pricing to delivery handoff for the full checklist.
What should a pricing model not claim?
A scenario calculation is not predictive analytics. It cannot guarantee delivery performance, identify the best team automatically, or account for work that was never represented in the assumptions.
Managed Margin calculates each pricing strategy from resource profiles and planning rates, your cost rules and the revenue basis: the quoted price for fixed price, or billable hours at client billing rates for time and materials. It shows gross delivery margin, contribution margin, margin after all costs and markup. It does not import CRM, ERP, invoicing or accounting data.
Use the product to make assumptions visible and calculations consistent. Keep expert review, scope control, client negotiation, and delivery decisions with the responsible people.
- How a Discount Affects Project Margin: Formula and Example
- Profit vs Cash Flow on a Project: How Payment Terms Matter
- How to Price a Project to a Target Margin: Formula and Example
Real example: a presales consultant prices a small team
An illustrative story with invented figures, to show how the idea works in a real office.
Chen, a presales consultant, is pricing a 10-week project. He plans one lead at 20% (80 hours), two consultants at 100% (800 hours) and one tester at 50% (200 hours). Cost rates are USD 90, 55 and 45 an hour.
Cost is 80 x 90 = 7,200, plus 800 x 55 = 44,000, plus 200 x 45 = 9,000, for a total of USD 60,200. To keep the example simple he works on labor only: the firm wants a 30% margin on that cost, so the price is 60,200 / 0.7, about USD 86,000. (With commission and overhead as shares of the price, the divisor would also subtract those shares; see the target-margin guide.)
Chen can answer the client’s question “what are we paying for?” with a team and hours, not a percentage.
When do you price a project, and what comes before and after?
Pricing is a chain of stages with different owners. Each row below names the checkpoint to pass before moving on, and the guide that explains it.
| Stage | Owner | Checkpoint | Read next |
|---|---|---|---|
| Agree the rates | Finance | Cost and billing rates are separate, labelled and dated | Project rate card, cost rate vs billing rate |
| Estimate the cost | Presales consultant with a delivery lead | Every role has allocation, months and an approved rate | Resource-based estimating |
| Compare team options | Presales lead, delivery lead, finance | Same scope and cost rules for every option; feasibility confirmed | Resource loading scenarios, pricing example |
| Set the price | Presales lead and finance | Price meets the target margin after all included costs | Price to a target margin |
| Negotiate | Sales manager | Concessions are costed before they are offered | How discounts affect margin |
| Approve and hand over | Final approver, project manager | One baseline is accepted by delivery | Sales-to-delivery baseline |
| Deliver and review | Project manager and finance | Actuals and forecast are compared with the baseline | Fixed-fee margin |
Resource-based, value-based or market pricing: how do you choose?
Prices can be built in several ways.
| Approach | Use it when | Watch for |
|---|---|---|
| Resource-based (this guide) | People-driven work | Needs good estimates |
| Value-based | Outcome is measurable and valuable | Cost may not be covered |
| Market-rate pricing | Competitive bidding | Ignores your cost |
| Percentage markup | Quick checks | Hides role detail |
Use resource-based pricing as the cost floor, then consider value or market in setting the final price. Always keep the role plan.
Pricing a services project: frequently asked questions
Which inputs should a pricing model preserve?
Role, level, hours, period, rates, non-labor cost and the assumptions behind them.
What should pricing not claim?
It should not claim forecasts or outcomes the model cannot support; it shows the margin the plan implies.
How do you price a professional services project?
Estimate the people needed (role, hours, months), multiply by approved cost rates to get labor cost, add other costs that do not depend on the price, then divide by one minus your target margin and minus any charges that are a share of the price (price = cost ÷ (1 − share − margin)). Compare two or three team options before you decide, and hand the chosen plan to delivery as the baseline.
How do consulting firms set project prices?
Many firms start from a costed team plan and a target margin (resource-based pricing), then adjust for competition and the value to the client. The cost-based number is the floor; value and market conditions decide how far above it the price sits.
Continue the sequence: guides to read next
- Resource-Based Estimating: How to Estimate Project Cost: the estimate underneath the price
- Resource Loading Scenarios: Compare Team Options for a Bid: comparing staffing options
Sources and methodology
- UK Infrastructure and Projects Authority, Cost Estimating Guidance. Used for documented assumptions, exclusions, evidence, review, and sensitivity principles.
- Project Management Institute, PM101: Estimating. Used for the relationship among planned resources, duration, cost rates, and the project budget.
- UK Cabinet Office, Risk Allocation and Pricing Approaches. Used for fixed-price scope and supplier-risk principles.
- Product statements and formulas were reviewed against the current Managed Margin application on 26 September 2026. The worked example is original and educational.