Realized Hourly Rate: Where Your Margin Is Really Made

The proposal states an hourly rate of €150. At the end of the project, the post-calculation shows a realized hourly rate of €118. This gap of €32 per hour is not an exception but the norm in IT consulting, management consulting and engineering firms with mixed billing models.

In short, this is how the gap between nominal and realized hourly rate affects things at project level:

• Fixed-price projects swallow more hours than calculated, but revenue stays fixed.
• Discounts, goodwill hours and unplanned change work are not recorded separately.
• Non-billable set-up time, travel time and internal coordination dilute the rate further.
• On paper, management sees healthy utilization, while the real margin per project falls.
• Without project-level analysis, the gap remains invisible until the annual accounts.

For finance leads and management, this is a tangible steering problem: the hourly rate on the price list describes wishful thinking. The realized hourly rate describes what is actually earned.

What the realized hourly rate actually measures

The nominal hourly rate is the price per hour agreed in the framework contract or proposal. It is the starting point for calculations and proposals, but says nothing about the actual profitability of a project or consultant.

The realized hourly rate, by contrast, works back to what was actually earned per hour worked after deducting discounts, non-billable hours and extra work on fixed-price projects. In simplified form, the formula at project level is:

Realized hourly rate = project revenue actually earned / hours actually spent

With time-and-material contracts, the realized rate should ideally be close to the nominal rate, since every hour can be invoiced. With fixed-price projects or retainer models, the gap usually arises from three effects:

1. ‍Unplanned extra work. A fixed-price project is calculated at 200 hours, but 260 hours actually go into it. Revenue stays the same, and the realized rate falls by around 23 percent.‍
2. Undocumented discounts. Goodwill hours, free rework and "we'll just quickly do that too" shift the numbers without ever becoming visible as costs.‍
3. Mixing billable and non-billable time. Internal coordination, onboarding new team members and proposal work count towards utilization but not towards invoicing. If this is not recorded separately, it distorts both metrics.

An analysis by TimeLog on financial KPIs for consulting firms confirms this link: the average hourly rate says little about actual profitability, because a considerable share of working time is not recorded at all, so the rate does not reflect real costs. Only the realized hourly rate shows the real profitability of a project hour.

It is also worth looking at the billability rate, since together the two metrics give a more complete picture of project profitability than either does on its own.

What the metric means for margin, utilization and forecast

The realized hourly rate is not an isolated financial metric. It has an effect in four directions at once, which is exactly why it deserves a closer look.

On margin, the metric has a direct impact. Every difference between the nominal and realized rate is margin that was calculated but not realized. Multiplied across several projects and a financial year, this quickly adds up to an amount that decides the profitability of an entire business unit.

On utilization, the realized rate acts as a corrective. A utilization rate of 85 percent looks healthy at first glance. If the realized rate is at the same time 20 percent below the nominal value, high utilization mainly means that many hours were delivered without a corresponding return.

On resource planning, the metric has an effect as soon as it is analysed per employee or skill group. If certain roles or project types systematically show a lower realized rate, this provides important arguments for staffing decisions and for calculating future proposals.

On the forecast, the realized rate acts as a correction factor. If you base revenue forecasts on nominal rates, you systematically overestimate expected income. A reliable forecast instead works with historical, realized values per project type and client.

For management, this results in a simple rule:

If the realized hourly rate is not analysed regularly, every plan, every proposal and every capacity decision is based on a more optimistic figure than reality.

Where the calculation fails in practice

The formula for the realized hourly rate fits on one line. The real challenge lies in the data this formula needs – and this is exactly where the typical pain points of the different roles lie.

COO and finance lead: figures that arrive too late

For COOs and finance leads, the realized hourly rate is one of the most important early-warning metrics in the project business. The problem: in many organisations, time tracking, invoicing and project calculation sit in separate systems. By the time someone has merged the Excel sheets from three sources, the project is often already finished.

The typical question from this group is: how do I get a clean link between projects and invoices without consolidating data by hand every month? The answer lies in a consistent data basis that automatically links hours, costs and invoicing per project and per employee, instead of merging them manually at month-end.

Project leads: steering without an early-warning system

Project leads carry operational responsibility for the realized rate, usually without having the right tools for it. If extra work only becomes visible in the weekly report, it is often too late to take corrective action. The plan-vs-actual comparison between calculated and actually booked hours must be available daily, not in hindsight at the end of the project.

Without this early-warning system, the following happens: a project lead only realises during post-calculation that a supposedly profitable fixed-price project ended up with a realized rate well below the salary cost threshold. By then, the project has already been invoiced and the loss is locked in.

Management: margin that falls despite growth

At decision-maker level, the problem often only shows up as a symptom: revenue grows, but margin does not. This discrepancy can almost always be traced back to an excessive gap between nominal and realized hourly rate, spread across many projects and consultants.

The article on billable hours describes this pattern well: the more projects run in parallel, the more billable hours disappear into the operational noise, without it being noticeable at any single point.

{{blog-cta}}

Working without and with a system

Without systematic recording, getting to the realized figure remains laborious: export timesheets from various tools, add project costs from accounting, enter discounts by hand, rebuild the formula in Excel for each project. For a single project, that is doable. For twenty parallel engagements, it becomes a full-time job that usually does not exist.

With project time tracking that separates billable and non-billable hours from the start and links them directly to project budgets, the realized hourly rate emerges almost automatically as a running metric. Project leads see deviations as soon as they arise, not only after project close. Finance sees at client level which engagements are really profitable and which are coming under structural pressure.

Feeding back into the calculation of future proposals

An often underestimated effect of the realized hourly rate lies in calculating upcoming projects. If a particular project type, such as an IT rollout with a high share of change requests, repeatedly shows a realized rate well below the nominal value, that is a clear signal for Proposals. Either the nominal rate for this project type is adjusted, or the scope is defined more tightly to structurally limit extra work.

Without historical data on the realized rate, this feedback loop is missing entirely. Every new proposal is calculated on the original price list, without drawing on actual experience from past, comparable projects. The result: the same under-calculation repeats itself project after project, client after client, without anyone stepping in, because nobody sees the systematic deviation.

For engineering firms with HOAI projects (projects under the German fee scale for architects and engineers, Honorarordnung für Architekten und Ingenieure), this effect is particularly pronounced, since service phases run for months or years and the actual effort per phase can differ greatly from the original fee calculation. A structured analysis by service phase shows which phases regularly take more time than calculated and thus provides the basis for more realistic proposals.

Benchmarks as orientation, not as a target

How large can the gap between nominal and realized rate be before it becomes critical? There is no blanket answer, as it depends heavily on the business model. With pure T&M contracts, the difference should remain small, since almost every hour is billable. With fixed-price and retainer models that include a priced-in risk buffer, a moderate gap is factored in and unproblematic.

What matters is less the absolute value than its development over time. If the gap widens from quarter to quarter without any change in the business model or contract structure, this points to a structural problem in project control, not a temporary fluctuation.

Why Excel reaches its limits here

Excel can easily represent the formula for the realized hourly rate. What Excel cannot do is link three constantly changing variables on a daily basis: recorded hours, project budget and invoicing status. Each of these usually sits in a different system or is entered manually after the fact.

This is exactly the point at which buying software becomes relevant. The formula itself is trivial. Applying it every day becomes error-prone, time-consuming and expensive as the number of projects grows. Every hour lost between recording and analysis is an hour missing from the margin calculation.

ZEP brings Project Time Tracking, Resource Planning and project controlling onto a shared data basis. Hours are marked as billable or non-billable directly when they are booked and assigned to a project budget. This means the data for the realized hourly rate is available continuously at project, team and client level, not only in retrospective reporting.

For IT consultancies with work packages and change requests, this means every additional hour that was not originally calculated becomes visible immediately, before it disappears from the margin. For management consultancies with mixed models of T&M, retainer and fixed price, the consistent data basis provides the foundation for reliable client contribution margins. For engineering firms with HOAI projects, it becomes clear early on when service phases take more effort than calculated in the fee proposal, as the article on HOAI billing also describes.

Moving from Excel analysis to an integrated data basis is not a big-bang project. If you already book project hours in ZEP, you can add project controlling by moving to ZEP Control and Resource Planning as an add-on, without completely changing existing processes.

Analysis at team level, not just at project level

Alongside the project perspective, a second level of analysis is worthwhile: the realized hourly rate per employee or skill group. Two consultants with an identical nominal rate can achieve very different realized values, depending on how efficiently they deliver projects, how much coordination effort they generate and how consistently they record their time.

This view is delicate if it is used as a control instrument against individuals. It becomes effective when it is used to identify structural patterns: certain skill profiles or experience levels show lower realized rates more often, for example because they are deployed more frequently in complex change request situations. This insight then feeds into staffing decisions and the calculation of future projects, not into individual performance appraisals.

For management consultancies with a high share of bench time, there is a further dimension: consultants who are briefly without utilization between engagements distort the average realized rate at team level if bench time is not shown separately. A clean separation between project time, bench time and internal project work is therefore a prerequisite for meaningful analysis.

The link to proposal speed

Another often overlooked effect concerns the speed at which new proposals can be calculated. If historical data on the realized hourly rate per project type is systematically available, a new proposal can be backed by realistic assumptions within minutes. If this data is missing, sales and project management fall back on experience from memory, which varies greatly from person to person and is rarely documented.

This speed becomes a competitive advantage as soon as several proposals have to be prepared in parallel under time pressure. If you can calculate reliably faster, you win more tenders. At the same time, you calculate every single project with more realistic margin expectations from the start, because the figures come from your own project history rather than a static price list.

This closes the loop between operational time tracking, commercial control and strategic proposal work. The realized hourly rate is therefore not merely a backward-looking metric but an active steering instrument for every future calculation in the project business.

Conclusion: steer by the rate that really counts

In your next project closings, specifically check the difference between nominal and realized hourly rate per client. Set a tolerance threshold above which a project lead is automatically notified, for example a deviation of more than 10 percent. Separate billable and non-billable hours consistently at the time of booking, not only in hindsight.

If these three steps still fail today because of Excel or scattered tools, now is the right time to consolidate your data basis, before the next growth phase widens the gap further.