How to Calculate True Labor Cost for Your Projects

Why Base Salary Is the Wrong Number

Most project cost estimates that go wrong do so because they were built on an incomplete cost model. A manager looks at an employee's salary — say, $80,000 per year — does a quick conversion to an hourly rate ($38.46/hour), multiplies by estimated project hours, and arrives at a project cost figure. That figure will almost always be wrong by 25–40%, and always in the same direction: too low.

The $80,000 salary is only the most visible slice of what that employee actually costs the organisation. Every hour of their work also carries a proportional share of payroll taxes, benefits, equipment, software licences, management time, and overhead. When you leave those out of your cost model, you're pricing projects — and measuring profitability — against a fiction.

This matters for several distinct business decisions: setting client billing rates (if you under-cost your labour, you under-bill your clients and destroy margin), evaluating project profitability retrospectively (so you can learn whether your estimates were realistic), deciding whether to hire employees or contractors, and calculating whether a project is worth pursuing at all.

The True Labor Cost Formula

True labor cost has five components. All five need to be present for an accurate number:

For practical purposes: for every dollar of base salary, the true cost to the organisation is $1.37 to $1.65. The exact figure varies by country (employer payroll taxes vary significantly), benefit generosity, and how you account for overhead. The midpoint of $1.5x is a reasonable default for initial planning, but you should calculate your own organisation's figure explicitly.

Burden Rate Explained

The "burden rate" is simply the ratio of total employment cost to base salary. If an employee earns $80,000 per year and their total annual cost to the organisation is $116,000, the burden rate is 1.45x (or 145%). The loaded hourly rate — the number you should use for project costing — is the base hourly rate multiplied by the burden rate.

How to calculate your burden rate:

1. Start with annual base salary for a representative employee or role.
2. Add employer payroll taxes. In the US this is approximately 7.65% for FICA plus state unemployment insurance. In Australia it includes Superannuation at 11.5% plus payroll tax where applicable.
3. Add the annualised cost of benefits. For employer-sponsored health insurance in the US, this is typically $8,000–$14,000 per employee. Other benefits (retirement matching, leave entitlements, parental leave provision) add additional cost.
4. Add equipment and software costs. Amortise the cost of the laptop over 3 years, add annual software licence costs, add any home office or internet stipend.
5. Allocate overhead. A common approach is to divide total non-direct-labour overhead (management salaries, HR, office costs, tools) by headcount and add the per-person share.
6. Divide the total by base salary to get the burden rate.

"A useful sanity check: if your burden rate is below 1.25x, you're almost certainly missing something. No legitimate employment arrangement has a fully-loaded cost that's less than 25% above base salary."

Contractor vs. Employee Cost Comparison

One of the most common project costing decisions is whether to staff work with employees or contractors. The financial comparison is less straightforward than it appears, and the common assumption that contractors are always more expensive is often wrong — especially for short-duration or specialised work.

The contractor cost model

Contractors typically bill at a rate that reflects their own burden — they pay both sides of payroll taxes (around 15% in the US), carry their own insurance, fund their own benefits, and have no guaranteed work continuity. As a result, a contractor billing $65/hour may have an effective annual earnings equivalent of around $90,000 — comparable to an employee earning $85,000 with benefits.

The key variables that determine which is cheaper for a given piece of work:

• Duration — for short-term work (under 6 months), contractors are almost always cheaper because you avoid the fixed overhead of onboarding, benefits administration, and the employment relationship.
• Utilisation — an employee who is 60% utilised on billable work still costs 100% of their salary. A contractor can be engaged only when needed, eliminating idle cost.
• Specialisation — senior specialists (security architects, ML engineers, niche compliance experts) command a significant contractor premium, but sourcing them as employees may be impossible or carry a large recruiting cost.
• Management overhead — contractors are expected to be self-directing within the scope of their engagement. Employees require more ongoing management investment, which has a real cost even though it doesn't appear on the contractor's invoice.

Allocating Overhead to Projects

Overhead allocation is where project costing gets genuinely complicated — and where most organisations take shortcuts that produce misleading profitability data. The problem: overhead (management salaries, office space, HR, accounting, software infrastructure) is real and must be recovered from somewhere, but it doesn't attach neatly to individual projects.

There are three common approaches, each with trade-offs:

1. Flat overhead rate per hour

Divide total annual overhead by total annual productive hours across the team. Add this dollar figure per hour to every project's cost calculation. Simple to administer, but treats all projects equally regardless of how much management attention they actually consume.

2. Overhead as percentage of direct labour

More common in professional services: overhead is expressed as a percentage of direct labour cost and applied consistently. If your overhead rate is 35%, every $1,000 of billed labour carries $350 of overhead. This scales naturally with project size but can produce counterintuitive results when some projects are unusually management-heavy.

3. Activity-based overhead allocation

More accurate but more complex: allocate overhead based on the actual resources consumed by each project. A project that required significant executive time, custom legal work, or unusual infrastructure costs gets a higher overhead allocation than a routine project. This produces the most accurate margin picture but requires more tracking discipline.

For most teams under 50 people, the percentage-of-direct-labour approach is the right trade-off between accuracy and administrative burden. Make sure your overhead rate is reviewed and updated at least annually as your cost structure changes.

Project-Level Profitability: The Three Key Metrics

Once you have accurate labor cost data, three metrics form the foundation of project profitability analysis:

Billable hours ratio (utilisation rate)

The percentage of total available hours that are billed to clients or allocated to revenue-generating work. A developer working 8 hours per day but spending 2.5 hours in internal meetings, administration, and non-billable work has a utilisation rate of 68.75%. Target utilisation rates vary by role: delivery staff in well-run service businesses typically target 75–85%; support and management roles are expected at 50–65%.

Actual utilisation data from monitoring systems is typically 8–15 percentage points lower than self-reported timesheet data, simply because people don't accurately track internal time or round billable hours up. This gap has direct revenue implications — at $120/hour billing rate, a 10% utilisation improvement on a 5-person team generates approximately $120,000 in additional recoverable revenue per year.

Gross margin per project

Revenue minus total direct cost (true labor cost of hours worked on the project plus any direct expenses). This is the primary measure of whether a project was profitable. A project with $50,000 in revenue and $38,000 in direct cost has a gross margin of 24% — reasonable for many service businesses, but below the 35–40% required to cover overhead and generate net profit at typical overhead ratios.

Estimate accuracy

The ratio of estimated project hours to actual project hours, tracked over time across projects. If your estimates are consistently 20% under actual hours — which is typical for teams without good historical data — and you use estimates to set prices or commitments, you have a systematic margin problem that will compound over time. Tracking estimate accuracy requires accurate actual hours data, which is exactly what automated timesheets provide.

Worked Example: 5-Person Team Project Cost Analysis

A software development agency is pricing a 3-month project for a client. The team: 1 lead developer, 2 mid-level developers, 1 UX designer, 1 project manager. Here is the full cost analysis using the true labor cost framework.

Project hours and direct cost:

If this agency bills the client $145,000 for the project, the gross margin is ($145,000 − $111,380) ÷ $145,000 = 23.7%. Healthy for a fixed-price project, but dependent entirely on the hour estimates being accurate. If actual hours run 15% over estimate — which is common on fixed-price software projects — total cost rises to approximately $127,000, shrinking margin to 12.4%. A 20% overrun makes the project borderline break-even.

This is why accurate actual-hours data is not merely an administrative nicety. It's the difference between profitable projects and ones that erode the business, and the difference between estimate models that improve over time and ones that keep making the same errors.

How Automated Timesheets Improve Cost Accuracy

The Achilles heel of any project costing system is the accuracy of the hours data it's built on. Manual timesheet entry — the default in most organisations — has well-documented accuracy problems. Research consistently finds:

• 8–15% under-reporting of actual hours worked (people forget to log time or don't bother with short tasks)
• Systematic rounding to nearest half-hour or hour, smoothing out the real distribution of time across tasks
• Retroactive entry — entering a week's time on Friday afternoon produces estimates rather than records
• Bias toward billable work — internal meetings, administrative tasks, and non-billable activities are consistently under-recorded

Automated time tracking — where the system records actual application and project activity continuously — eliminates most of these problems. Hours captured automatically are within 2–5% of actual clock time, compared to 10–20% variance for manual entry. Project codes can be assigned based on application context or employee confirmation rather than retroactive recollection.

For a 5-person team billing at $120–150/hour average, closing a 10% time-capture gap translates to approximately $100,000–$120,000 per year in additional accurately tracked hours — some of which is genuinely billable, some of which surfaces true internal cost that was previously invisible in project margins.

Putting It Into Practice

The organisations that manage project profitability most effectively share a common infrastructure: they have accurate, automated hours data at the task and project level; they have an explicit, documented burden rate that is reviewed annually; and they track estimate accuracy over time to continuously improve their models.

None of this requires sophisticated financial software. A spreadsheet with the right inputs, fed by accurate timesheet data, is sufficient to run the analysis above for most teams. The constraint is almost always the quality of the hours data — which is why the first investment worth making is ensuring that the time capture layer is accurate before building any cost model on top of it.

Start there. Once you have reliable actual-hours data, everything else follows: better estimates, more accurate billing, clearer profitability by client and project type, and a foundation for pricing decisions that reflect what work actually costs rather than what you wish it cost.