Project margin management is the process of defining a project's price, delivery-cost assumptions, and planned margin before sign-off, then comparing that baseline with actual effort and supported costs during delivery. For professional-services firms, it connects presales, finance, and project management around one question: is the work being delivered on the economic assumptions that were approved?
In plain words
Project margin is what is left of a project’s fee after its costs, shown as a percentage of the fee. Project margin management means working out the margin you want when you price a job, keeping a plan to compare against, and checking the real margin while the work is happening, so a problem is found while it can still be fixed. It is not the firm’s profit; it is a view of one project.
Who this helps: Project managers, finance analysts, delivery leads and firm owners who want to know whether the work they sell actually earns what was planned.
Questions this guide answers:
- What is project margin management?
- What is a good project margin for a services firm?
- How do you control and track project margin?
- Where should a small professional-services firm start?
Start with a small project: the words you will use
A client pays a services firm USD 10,000 to redesign its website. The firm uses a designer for 40 hours, a developer for 60 hours (both cost the firm USD 50 an hour) and buys a USD 1,000 software license.
| Term | Plain meaning | In this project |
|---|---|---|
| Revenue (the fee) | What the client pays | USD 10,000 |
| Cost | What delivering it costs the firm | 40 h × 50 + 60 h × 50 + 1,000 = USD 6,000 |
| Margin | Revenue minus cost | USD 4,000 |
| Margin % | Margin ÷ revenue × 100 | 40% |
Project margin management means three habits: work out the margin you want before you quote (pricing), write down the plan you quoted on (the baseline), and compare it with what really happens while the work is going on (tracking).
Why the third habit matters
Suppose the developer needs 100 hours instead of 60. That is 40 extra hours at USD 50, or USD 2,000 more cost. Cost becomes USD 8,000, margin USD 2,000, and margin % drops from 40% to 20%. If you see it in week two you can act (raise a change request, adjust the plan). If you see it at the end, you can only record it.
Margin vocabulary used in these guides
These words are used the same way in every guide about project margin. Read this table once and the rest of the guides will be easier.
| Word | Plain meaning | Example (a USD 80,000 fee) |
|---|---|---|
| Revenue or fee | What the client pays for the work | USD 80,000 |
| Delivery cost | People, partners and direct costs needed to deliver | USD 48,000 |
| Gross delivery margin | Fee minus delivery cost | USD 32,000 (40%) |
| Contribution | Gross margin minus costs that rise with the deal, such as sales commission | USD 28,800 after USD 3,200 commission (36%) |
| Managed margin | Contribution minus the overhead share the model assigns to the project: the margin after all costs the model manages | USD 20,800 after USD 8,000 overhead (26%) |
| Net margin | The whole firm's profit after every cost, financing and tax; not a project measure | Not calculated per project |
| Word | Plain meaning |
|---|---|
| Cost budget | The amount the firm approves to spend delivering the project |
| Fee or deal budget | The amount the client pays; the revenue side. Pages say “fee” for this to avoid confusion |
| Baseline | The approved plan kept for comparison and not overwritten |
| Actual to date | What the recorded hours, costs and recognized revenue show so far |
| Forecast | Actuals plus the remaining plan; a calculation, not a prediction |
| Utilization | Hours spent on selected work divided by the hours available |
| Role | What they do in these guides |
|---|---|
| Presales consultant and presales lead | Estimate and price the work; the lead reviews |
| Project manager | Runs one project day to day, records actuals, runs the review |
| Delivery lead | Senior person for a team or practice; checks that plans can be delivered |
| Delivery head | Accountable across projects; decides how to respond to variances |
| Finance | Owns the cost policy, rates and the arithmetic |
| PMO lead | Sets reporting rhythm and consistency across projects |
What does project margin management measure?
At its simplest, project margin is the difference between the revenue basis assigned to a project and the delivery costs included by the firm. The percentage expresses that difference relative to the same revenue basis.
Project margin = project revenue basis − included project delivery costs
Project margin % = project margin ÷ project revenue basis × 100
The formula is simple; the policy behind it is not. A useful margin review must state whether delivery cost includes pay-rate labor, employment on-costs, subcontractors, infrastructure, sales commission, project overhead, or a share of central costs. Two firms can use the same formula and produce different percentages because they include different costs.
For example, a project with a documented USD 100,000 revenue basis and USD 65,000 of included delivery costs has a margin of USD 35,000, or 35%. The calculation guide works through a fuller version of this same arithmetic with commission, labor overhead, and infrastructure broken out line by line.
This guide describes an internal project-control view, not statutory revenue recognition, tax, or financial-statement policy. Finance should define the approved revenue and cost basis used by the firm.
Why should margin management begin before sign-off?
A delivery team cannot compare actual performance with a useful baseline if the proposal only preserves a final price. The baseline also needs the assumptions behind that price: the roles, level of effort, duration, cost rates, non-labor costs, and scope boundary.
This is especially important for fixed-price work. The approved client fee does not automatically rise when delivery takes more hours. A Project Management Institute case study describes fixed-price work as having a bidding cycle and a delivery cycle, and emphasizes clear scope, a defined baseline, progress assessment, and captured costs. The lesson is not that every services firm needs formal earned-value management; it is that the delivery review needs a traceable plan.
Four questions before a proposal is approved
- Which roles and skills are needed to deliver the scope?
- How much of each role is needed, and for how long?
- Which governed cost assumptions apply to those roles?
- Does the proposed fee leave an acceptable margin after the costs included by the firm?
These four questions assume the proposed fee holds through signature. If it is negotiated down before the contract is signed, the margin math changes before delivery even starts — see how discounts affect project margin for what a late-stage discount actually costs against a fixed delivery-cost plan.
The worked resource-loading pricing example shows how these inputs can be calculated without pretending the result is a forecast.
What is the proposal-to-delivery margin workflow?
A practical workflow has five connected stages. Each stage should preserve the assumptions needed by the next team rather than asking that team to rebuild them.
| Stage | Decision | Evidence to retain |
|---|---|---|
| 1. Cost policy | Which rates and cost components are controlled? | Role, skill, location, pay-cost basis, billing rate where relevant, commission, overhead, and effective dates. |
| 2. Pricing scenario | Which team can deliver the scope at the proposed fee? | Roles, allocations, duration, deal budget, calculation assumptions, and scenario result. |
| 3. Approval and handoff | Which option becomes the delivery baseline? | Approved budget, chosen resource assumptions, scope boundary, and reviewer decision. |
| 4. Delivery actuals | What effort and supported cost have been recorded? | Actual hours by resource and period, progress context, cost changes, and reasons for material variance. |
| 5. Review and action | What changed, why, and who owns the response? | Hours variance, cost variance, budget consumption, margin difference, scope decision, and follow-up owner. |
What should a project-margin review compare?
A weekly or milestone review should use the same units and period on both sides of every comparison. It should also separate a current observation from a prediction. A fully-booked team is not the same signal as a healthy margin—see why utilization and project profitability can move in opposite directions.
| Review question | Useful comparison | Common mistake |
|---|---|---|
| Is effort following the plan? | Planned and actual hours by resource and period. | Looking only at total hours, which can hide an expensive role mix. |
| Is cost following progress? | Supported cost recorded, budget consumption, and delivery progress. | Treating budget consumed as the same thing as work completed. |
| Did the margin basis change? | Approved price and included planned costs versus the current calculation on the same basis. | Comparing percentages built from different revenue or cost definitions. |
| Where did variance originate? | Resource-hours variance, rate or team-mix change, scope change, and non-labor cost. | Calling every difference "scope creep" without tracing the driver. |
| What should happen next? | Named decision, owner, and review date. | Assuming a dashboard automatically fixes the delivery problem. |
The planned-versus-actual project margin review turns this into a repeatable meeting checklist and worked example.
Can a spreadsheet manage project margin?
Yes—when the workbook has controlled inputs, visible formulas, named ownership, version discipline, and an agreed review process. Governance gets harder as teams, rate sensitivity, and scenario count grow; see the governance failure conditions and when to replace it with dedicated software for the full breakdown, and the project-margin spreadsheet template structure for which inputs, formulas, and controls a workbook needs.
Dedicated software can reduce version handling and preserve a structured baseline, but it does not remove the need for cost policy, scope decisions, or accurate actuals. Software supports the process; policy still matters. If you are comparing options, these are the calculation, baseline, access, and data-boundary questions to ask a vendor.
What Managed Margin currently does
Managed Margin follows the proposal-to-delivery workflow described above:
- Resource profiles and planning rates, with cost and margin rules.
- Pricing strategies per service order, fixed price or time and materials, compared side by side.
- Finalizing one strategy as the approved pricing baseline.
- Handover by purchase order, signed agreement or approved exception.
- Seats, named allocations, weekly timesheets, expenses and change requests.
- Baseline, actual-to-date and forecast margin, with each margin layer on a stated basis.
- Margin rollups by project and business unit.
See the complete Managed Margin workflow, project margin management software, or the margin measures the product reports.
What Managed Margin does not currently do
It does not import timesheets, CRM, ERP, invoicing or accounting data (people and pay can be synced from BambooHR), and it does not calculate operating or net margin or track cash. The forecast at completion is a calculation from recorded data, not a prediction.
Where should a professional-services firm start?
- Agree on one project-margin definition and document which costs it includes.
- Select one fixed-price project with a clear approved fee and resource plan.
- Record the original roles, hours, rates, duration, and non-labor assumptions.
- Assign one owner for periodic actual-hours and cost updates.
- Review resource variance, budget consumption, margin difference, and scope decisions together.
- Keep the baseline intact; record approved changes rather than silently overwriting the original plan.
For the product workflow, explore project pricing and scenario planning and planned-versus-actual margin tracking.
- Profit vs Cash Flow on a Project: How Payment Terms Matter
- How to Price a Project to a Target Margin: Formula and Example
- Project Margin Variance: Formula, Example and Causes
- Project Estimation: Process, Methods and What to Consider
At the office: Carla runs the month-end margin check
An illustrative story with invented figures, to show how the idea works in a real office.
At month end Carla, a finance analyst, compares each project with its plan. For one project, called Orion the fee is USD 90,000 and the plan was a 30% margin, so planned cost was USD 63,000. The project has just closed with a final cost of USD 70,000 against the USD 90,000 fee, so the actual margin is (90,000 − 70,000) ÷ 90,000 = 22.2%. (Part-way through a project she would not use cost to date this way, because the fee is not yet fully earned; she would compare recognized revenue and cost for the same date, or a forecast of the final cost.)
She does not stop at the percentage. Orion used 140 more analyst hours than planned. At USD 50 an hour that is USD 7,000, which explains the whole gap. She sends the delivery lead one line: “Extra analyst hours on Orion cost us eight points of margin. Is the extra work in scope?”
Because she compared like with like, using the same cost rules and the same project boundary for plan and actual, the conversation is about a cause, not a number. The 140 extra hours explain 7,000 ÷ 90,000 = 7.78 percentage points of the 7.78-point gap (30% planned against 22.2% actual).
Who does what at each stage of project margin management?
| Stage | Owner | Checkpoint before moving on |
|---|---|---|
| Agree the cost policy | Finance | One written list of which costs count in “margin”, and the rates, with dates |
| Price the work | Presales consultant and lead | Margin is calculated from roles, hours and rates, not just from a target percentage |
| Approve and hand over | Final approver and project manager | One baseline is accepted; delivery can explain it without the pricing spreadsheet |
| Deliver and record | Project manager | Hours and costs are recorded weekly, by role |
| Review and act | Project manager, finance, delivery head | Each variance has an owner, a response and a date |
What is a good project margin for a services firm?
There is no single percentage that is good for every project, and a number quoted without its definition is meaningless. A good margin is one that meets your firm's policy after the costs your firm chooses to include, with enough room for the risks of this particular job.
Step 1: agree what the margin includes
The same project has different margins depending on which costs you subtract.
| What is subtracted from the USD 100,000 fee | Cost | Margin |
|---|---|---|
| Delivery labor only | USD 55,000 | 45% |
| Labor plus commission (USD 5,000) and non-labor costs (USD 5,000) | USD 65,000 | 35% |
| All of the above plus a share of overhead (USD 5,000) | USD 70,000 | 30% |
A firm that says “we make 45%” and a firm that says “we make 30%” may be doing exactly the same business. Compare only margins built on the same list.
Step 2: ask what could go wrong on this job
- A fixed-price job with an unresolved dependency deserves a higher planned margin than a repeat job the team has done ten times.
- Scarce specialists, tight deadlines and slow payment terms all justify more room.
Scenario: Nora's approval meeting
- Nora, a finance lead, sees a USD 100,000 proposal with USD 70,000 of all included costs: 30%.
- Delivery says an unresolved dependency could add USD 10,000. The same fee would then leave 20% (100,000 − 80,000).
- The firm's policy minimum is 25%. So the question is not “is 30% attractive?” but “do we accept a chance of 20%?”
- The approver asks for a discovery step to remove the dependency first, and the margin is approved for the revised plan.
Use target-margin pricing to test the fee under your actual cost rules.
Frequently asked questions
How does this relate to Managed Margin?
The product follows the same cycle from pricing strategy to delivery tracking; this guide explains the logic independent of the tool.
What is a good project margin?
It depends on the firm's policy and on which costs are included, so a percentage on its own tells you little. A good margin is one that meets your policy after all the costs you include, and still does so in a realistic difficult case. For example, a USD 100,000 fee with USD 70,000 of included cost is 30%, but 20% if a USD 10,000 risk happens.
Is project margin control the same as project margin management?
They overlap. Project margin management is the whole cycle: decide the margin before you quote, keep the plan you priced on, and review it during delivery. Project margin control is the checks during delivery, project margin analysis explains the difference between plan and actual, and project margin assurance is an independent check that the figures and cost rules can be trusted.
Continue the sequence: guides to read next
- Planned vs Actual Project Margin: the control step
- What Is Managed Margin? Meaning, Formula and Software: the margin definition used throughout
Sources and methodology
- Project Management Institute, Managing fixed-price projects using earned value management. Used for the bidding/delivery cycle, baseline, progress, and actual-cost principles. Managed Margin does not claim to implement formal EVM forecasting.
- UK Infrastructure and Projects Authority, Cost Estimating Guidance. Used as an authoritative reference for transparent estimates and stated assumptions.
- Product statements were reviewed against the current Managed Margin application on 26 September 2026. Examples in this article are educational and do not represent a customer result.