How to Measure and Improve Project Profitability in 8 Steps

A project can bring in plenty of revenue and still be less profitable than expected. Labor takes longer than estimated, material costs increase, extra work goes unbilled, or small expenses accumulate until the margin you expected at the start looks very different at the end.

At its simplest, measuring project profitability means comparing the revenue a project generates with what it costs to complete. Project profit shows how many dollars you earned, while project profit margin shows how much of each revenue dollar remains as profit. Once you know these numbers, you can compare them with your original estimates and identify where you're gaining or losing margin.

The following steps show how to measure what drives it and improve the result.

Step 1: Determine the project's total revenue

Start with the revenue the project is expected to generate. For a straightforward fixed-price job, this may simply be the agreed contract amount. However, project revenue can change once work begins, so your original quote isn't always the number you should use when measuring profitability.

For example, suppose you agreed to complete a website redesign for $20,000. Halfway through the project, the client requests additional functionality that wasn't included in the original scope. You agree to a $2,000 change order, bringing the project's expected revenue to $22,000.

Depending on how you bill clients, project revenue may include:

• Fixed project fees: The agreed price for completing the defined scope of work.
• Hourly or time-based billing: Billable hours multiplied by the applicable client rate.
• Milestone payments: Amounts tied to specific stages or deliverables in the project.
• Approved change orders: Additional work formally added to the original scope and billed separately.
• Reimbursable expenses: Client expenses you can bill back under the contract.

Be careful not to automatically treat amounts invoiced or cash collected as project revenue. A deposit received before you've performed the work, for instance, may affect cash flow without representing revenue earned at that point. The appropriate accounting treatment depends on your accounting method and the terms of the arrangement.

For profitability management, I recommend maintaining an expected project revenue figure alongside the revenue already recognized or billed. This gives you a forward-looking view of where the project is heading instead of waiting until all the invoices have been issued.

Once you've established how much the project will generate, the next question is more difficult: How much does it really cost you to deliver it? That starts with identifying every cost you can directly trace to the project.

Step 2: Identify all direct project costs

Revenue tells you what a project brings in, but profitability depends just as much on what it takes to deliver the work. Start by identifying direct costs — costs you can reasonably trace to a specific project.

For our website redesign example, suppose the $22,000 project incurred the following direct costs:

At this point, the project appears to generate $10,000 before considering indirect costs. But that figure is only useful if you've captured the costs accurately.

Don't underestimate labor costs

Labor is often one of the biggest project expenses for service businesses, and it's also one of the easiest to underestimate.

Suppose an employee earning $30 per hour spends 100 hours on a project. Recording $3,000 as the project's labor cost is simple, but it may not reflect what those hours actually cost the business. Employer payroll taxes, benefits, insurance, and other employee-related costs can push the real cost higher.

A more useful measure is the employee's burdened labor rate:

Burdened labor rate = (Wages + employer payroll costs + benefits + other employment costs) ÷ productive work hours

If that employee's true cost works out to $40 per productive hour, those 100 hours cost the business $4,000 rather than $3,000. Using wages alone would overstate the project's profit by $1,000.

The same principle applies to the owner's time. A freelancer or business owner may not pay themselves an hourly wage for every hour worked, but treating their labor as free can make projects appear far more profitable than they really are.

Track costs to the project as they occur

Don't wait until the project is finished to reconstruct its costs from bank transactions and timesheets. Assign labor, contractor bills, materials, and other project-specific expenses to the appropriate project as they're recorded.

For businesses managing several projects simultaneously, consistent project or job coding is especially important. A contractor invoice recorded only as "Contract Labor," for example, tells you the expense category but not which project consumed that cost.

This distinction matters in bookkeeping. Your general ledger tells you what the business spent; project-level tracking helps tell you where the business made or lost money.

Step 3: Allocate indirect costs when appropriate

A project may look highly profitable when you subtract only labor, contractors, and other direct expenses. But those projects also rely on resources that aren't easily traced to a single job, such as office rent, accounting software, insurance, administrative staff, and utilities.

These are indirect costs, or overhead. Including an appropriate share of them can give you a more complete picture of whether a project contributes enough profit to support the business as a whole.

For example, our website redesign project has $22,000 in revenue and $12,000 in direct costs, leaving $10,000 before overhead. Suppose the business allocates another $3,000 of indirect costs to the project:

That distinction is useful because direct-cost profitability and fully loaded profitability answer different questions.

Direct-cost profitability tells you whether the revenue from a project exceeds the costs specifically required to deliver it. This can be useful when evaluating pricing, project execution, or whether additional work contributes positively toward covering overhead.

Fully loaded profitability goes further by assigning the project a reasonable share of business overhead. It provides a broader view of whether your projects are generating enough profit to support the entire operation.

Choose a reasonable allocation method

There's no single allocation method that makes sense for every business. The goal is to use a cost driver that reasonably reflects how projects consume shared resources.

A service business with labor-intensive projects, for example, might allocate overhead based on direct labor hours. A consulting firm might use direct labor cost, while another business may allocate certain expenses based on project revenue.

Suppose your business expects $120,000 in annual overhead and approximately 6,000 direct project labor hours for the year:

Overhead rate = $120,000 ÷ 6,000 hours = $20 per direct labor hour

A project requiring 150 direct labor hours would therefore receive $3,000 of allocated overhead.

The method doesn't have to be overly complicated, particularly for a small business. What matters is applying a reasonable method consistently so that profitability comparisons between projects remain meaningful.

Don't allocate costs blindly

Not every overhead expense needs to be forced into every project analysis. If you're deciding whether to accept an additional project while your rent, insurance, and administrative salaries will remain unchanged, looking at the project's contribution after direct costs may be useful.

However, if you're evaluating whether your pricing model can sustain the business over the long term, ignoring overhead can give you an overly optimistic picture.

This is why I prefer looking at both views instead of treating one calculation as the only measure of project profitability. A project can have a healthy margin before overhead but become much less attractive once you consider the resources required to run the business.

Step 4: Calculate project profit and profit margin

Once you've captured project revenue and costs, you can calculate profitability in both dollars and percentage terms. I recommend looking at both because they answer different questions about project performance.

Start with project profit:

Project profit = Project revenue − Total project costs

Using our website redesign example:

$22,000 − $15,000 = $7,000 project profit

The project generated $7,000 after the $12,000 in direct costs and $3,000 in allocated overhead identified in the previous steps.

Next, calculate the project profit margin:

Project profit margin = (Project profit ÷ Project revenue) × 100

For our example:

($7,000 ÷ $22,000) × 100 = 31.8%

This means that approximately 31.8 cents of every dollar of project revenue remains as project profit after the costs included in our calculation.

Look at profit dollars and margin together

Project profit tells you how many dollars you made, while profit margin tells you how efficiently the project turned revenue into profit. Looking at only one can lead to the wrong conclusion.

Consider two projects:

Project A produces more profit dollars, but Project B earns twice as much profit for every dollar of revenue. Neither metric alone tells you which project is better.

If your business has plenty of capacity, the additional $7,500 from Project A may still make it worthwhile. If staff time is limited, however, you may prefer projects similar to Project B because they generate a higher return from the revenue earned. Labor hours and other resource requirements would help you make that decision.

Don't rely on a universal "good" project margin

There's no single project profit margin that every small business should target. A healthy margin for a consulting firm won't necessarily make sense for a contractor, marketing agency, manufacturer, or freelancer because their labor requirements, overhead, pricing models, and business risks differ.

Instead, establish a target margin based on your own costs and pricing requirements, then compare projects against that target. Historical results can also be valuable: if similar projects typically earn a 35% margin and a new one earns 20%, the difference deserves investigation.

This is where measuring profitability becomes more useful than simply calculating it.

Our example produced a $7,000 profit and a 31.8% margin, but those numbers still don't tell us whether the project performed as expected. To answer that, we need to compare what actually happened with what we estimated before the work began.

Step 5: Compare estimated vs. actual profitability

Knowing that a project earned a profit isn't enough. You also need to know whether it earned the profit you expected.

This is where I find estimated-versus-actual comparisons particularly useful. A project can finish with a positive margin and still have performed poorly if costs substantially exceeded the original budget. Without that comparison, you may see a profitable project and miss the problems underneath it.

Let's return to our website redesign project:

At first glance, the additional $2,000 of revenue looks positive. But the project also incurred $3,500 more in direct costs than originally estimated. As a result, profit came in $1,500 below plan, and the margin dropped from 42.5% to 31.8%.

That's much more useful than simply knowing the project made $7,000.

Investigate the variance, not just the final margin

Once you identify a significant difference, trace it back to the underlying revenue, hours, or costs.

For example, the $3,500 direct-cost overrun might consist of:

• $2,000 in additional employee labor: The design and development work required more hours than estimated.
• $1,000 in additional contractor costs: Part of the change order required specialized work.
• $500 in additional software and other expenses: Extra tools and assets were needed to complete the revised scope.

This analysis changes the questions you ask. Instead of simply wondering why the margin fell, you can determine whether you underestimated the original work, allowed scope to expand, priced the change order too low, or managed the project inefficiently.

Separate revenue variance from cost variance

An increase in revenue doesn't necessarily improve profitability. Additional work is beneficial only when the revenue it generates adequately covers the additional resources required to deliver it.

Our project's revenue increased by $2,000, for example, while direct costs increased by $3,500. That doesn't automatically mean the entire $1,500 shortfall resulted from the change order—the project could also have experienced overruns on its original scope. That's why revenue and cost changes should be investigated separately rather than assuming one caused the other.

This is also why tracking change orders separately, as discussed earlier, becomes valuable. You can compare the incremental revenue from additional work with its incremental cost and determine whether that work improved or diluted the project's margin.

Review profitability before the project is finished

Estimated-versus-actual analysis is most useful when you still have time to do something about the result.

For a project that's 50% complete, compare the hours and costs incurred so far with the amount you expected to consume at that stage. If you've already used 75% of the labor budget, waiting until completion to calculate profitability only confirms a problem you could have addressed earlier.

You may be able to reassign work, control additional revisions, discuss a change order with the client, or adjust the remaining project plan before the overrun becomes larger.

Step 6: Find what's reducing project profitability

When a project misses its target margin, cutting costs across the board isn't necessarily the right response. First determine where the margin was lost and why. Otherwise, you may reduce spending in an area that wasn't causing the problem while leaving the real issue untouched.

I find it useful to separate profitability problems into two broad categories: pricing problems and execution problems. If projects generally stay within their estimated hours and costs but still produce weak margins, your pricing may be too low. If the original estimate shows a healthy margin but the actual margin consistently falls short, the problem is more likely related to estimating, scope, or project execution.

Look for patterns across projects

One bad project doesn't necessarily mean your pricing model is wrong. Several similar projects showing the same variance are much more informative.

Suppose three recent projects were estimated at approximately a 40% margin, but each finished around 25% to 30%. If actual labor hours exceeded estimates every time, your estimating assumptions may need to change. If hours were close to budget but margins were still weak, look instead at pricing, contractor rates, material costs, or costs that weren't included when the jobs were quoted.

This is where historical project data becomes particularly valuable. Completed projects give you real information about how long work takes and what it costs—information you can use instead of relying solely on assumptions when preparing the next estimate.

Pay close attention to scope creep

Scope creep can be especially damaging on fixed-price projects because revenue stays fixed while the work required continues to grow.

Imagine a $10,000 project originally estimated to require 200 labor hours. The client then requests several small revisions that add another 30 hours. If those requests aren't treated as additional scope, you've increased project labor by 15% without increasing the contract price.

Individual requests may seem too small to matter. Collectively, they can materially reduce the project's margin.

That's why the profitability review should look beyond accounting transactions. Compare the original scope with what was actually delivered, review change requests, and investigate why actual labor hours differed from the estimate.

Don't confuse a busy team with a profitable project

High utilization doesn't automatically mean the work is profitable. A team can spend hundreds of hours on a project and stay fully occupied while the business earns a poor margin because those hours were underpriced or exceeded the estimate.

Likewise, keeping employees busy with low-margin work can prevent you from accepting higher-margin projects. That introduces an opportunity cost that won't necessarily appear as an expense in your accounting records but still matters when deciding what types of projects to pursue.

Step 7: Improve project profitability

Once you know what's reducing your margin, address the specific cause rather than simply cutting costs. Some of the most effective ways to improve project profitability include:

• Improve project estimates: Use actual hours and costs from completed projects to make future estimates more realistic. If similar projects consistently require 100 hours instead of the 80 you've been budgeting, update your assumptions.
• Control scope creep: Define what's included in the project and establish a process for approving and pricing additional work. On fixed-price projects, every unbilled extra hour reduces your margin.
• Track time even on fixed-price projects: Time tracking shows whether the amount you're charging adequately covers the labor required. It can also reveal excessive meetings, revisions, project management, or rework.
• Review your pricing: If projects stay within budget but still produce weak margins, your price may be too low. Work backward from your estimated costs and target margin when setting prices.
• Use the right resources: Match the skill and cost of employees or contractors to the work being performed. Using senior staff for routine tasks can unnecessarily increase project costs.
• Bill additional work: Make sure approved change orders and out-of-scope services reach the final invoice. Additional work doesn't improve profitability if you never bill for it.
• Reduce rework and delays: Look for recurring mistakes, unclear instructions, approval bottlenecks, and duplicated work that add hours without adding value for the client.
• Prioritize profitable work: Compare results across projects to identify which services, clients, and project types provide the best return on your available resources.

Step 8: Monitor profitability throughout the project

Project profitability shouldn't be something you calculate only after sending the final invoice. By then, you can explain what went wrong, but you have little opportunity to correct it.

Instead, treat profitability as a project management metric and review it while the work is underway. The goal is to compare what you've earned and spent so far with what you expected at the same stage of the project.

A simple process is to monitor profitability at three points:

Set a profitability baseline before work starts

Before beginning a project, document the assumptions behind your expected profit. At minimum, establish the expected revenue, labor hours, labor cost, other direct costs, applicable overhead, and target margin.

This gives you something meaningful to compare against later.

A budget of "$15,000 in total project costs," for example, is less useful than knowing that $8,000 is expected for labor, $3,000 for contractors, $1,000 for other direct costs, and $3,000 for overhead. If the project begins running over budget, the additional detail helps you identify where the problem originates.

Monitor how much of the budget you've consumed

Don't judge progress based only on how much you've spent. Compare the percentage of the project completed with the percentage of the budget already consumed.

Suppose a project is roughly 50% complete but has already used 75% of its estimated labor hours. The project may still appear profitable today because much of the revenue remains, but the current pace suggests the final margin could be substantially lower than planned.

That warning is far more valuable before the remaining 25% of the labor budget disappears.

Forecast profitability at completion

Current profitability can also be misleading for an unfinished project. What matters is where the project is likely to finish.

A simple forecast is:

Projected total cost = Costs incurred to date + Estimated cost to complete

Then:

Projected profit = Expected project revenue − Projected total cost

Projected profit margin = Projected profit ÷ Expected project revenue × 100

For example, assume our $22,000 website project has incurred $10,000 in costs so far. If you estimate that another $5,000 will be needed to finish the work:

Projected total cost = $10,000 + $5,000 = $15,000

Projected profit = $22,000 − $15,000 = $7,000

Projected profit margin = $7,000 ÷ $22,000 = 31.8%

If your target was 40%, you now know the project is likely to miss that target before it's finished.

More importantly, you can investigate why and determine whether anything can still be changed.

Establish a review frequency that matches the project

How often you should review profitability depends on the size and duration of the work. A two-week project probably doesn't need a formal monthly review, while checking a yearlong engagement only at completion would be far too late.

For many small businesses, a weekly or milestone-based review is practical for active projects. Longer projects may also benefit from a more detailed monthly profitability review tied to the accounting close.

The frequency matters less than consistency. Review often enough that an unfavorable variance can still be corrected.

Key project profitability metrics to track

You don't need a long list of KPIs to understand whether your projects are profitable. Focus on metrics that help answer three practical questions: Are we making enough money? Are we staying within budget? And if not, where is the variance coming from?

Best software for tracking project profitability

Accounting and project-tracking software can reduce the amount of manual work involved in calculating project profitability. My top options are:

In QuickBooks Online Advanced, I wouldn't rely on only one tracking dimension. Use Projects to measure individual job profitability, classes to analyze departments or service lines, and locations to compare branches or business locations.

Common project profitability mistakes

Even when the profitability formula is correct, the result is only as reliable as the revenue, costs, and assumptions behind it. A project can appear profitable on paper while important costs are missing or additional work has quietly consumed the expected margin.

Here are some of the most common mistakes to watch for:

• Treating revenue as an indication of profitability: A $100,000 project isn't necessarily better than a $30,000 project. What matters is how much remains after the resources required to deliver the work are considered.
• Ignoring the owner's time: Freelancers and owner-operated businesses sometimes treat their own labor as free because there isn't an employee paycheck attached to it. This can make time-intensive projects appear more profitable than they really are.
• Using wages as the full labor cost: Employee wages may represent only part of what labor costs the business. Employer payroll taxes, benefits, and other employment costs may need to be considered when determining a burdened labor rate.
• Leaving overhead out of every analysis: Direct-cost profitability is useful, but relying on it exclusively can hide whether projects generate enough margin to support administrative salaries, software, insurance, rent, and other shared business costs.
• Failing to track time on fixed-price work: Fixed pricing changes how you bill the customer, not the importance of knowing how many hours the project consumed. Without time data, it's difficult to determine whether the price was adequate or improve future estimates.
• Allowing scope changes without tracking their financial effect: A change order can increase revenue and still hurt profitability if the additional price doesn't adequately cover the additional labor and other costs.
• Waiting until project completion: Review profitability while work is still underway so you have time to correct overruns.

How to use project profitability results to make better business decisions

Once you have reliable profitability data, use it to guide future pricing, project selection, and resource planning.

• Compare project types: Identify which services consistently produce stronger margins and which tend to run over budget.
• Evaluate client profitability: Look beyond revenue to determine which clients require excessive revisions, meetings, or unbilled work.
• Improve future estimates: Use actual labor hours and costs from completed projects instead of relying only on previous estimates.
• Prioritize limited capacity: When staff time is constrained, consider both total project profit and the profit generated relative to the resources required.
• Set target margins before quoting: Estimate project costs first, then determine the price needed to achieve your target margin.
• Investigate low-margin work: Decide whether the problem comes from pricing, scope, staffing, estimating, or execution before making changes.

Frequently asked questions (FAQs)