Why professional services companies lose margin — and how to fix it

And yet, margins start to come under pressure.

Not all at once. Not dramatically. But consistently enough that leadership starts asking the same question:

Where are we losing money?

In professional services, margin erosion rarely comes from one single issue. It usually happens through many small gaps that are difficult to see early enough: inaccurate estimates, weak scope control, delayed time entry, unbilled work, senior resources doing lower-value tasks, project overruns, subcontractor costs, write-offs, and reporting that comes too late.

Growth brings complexity. Control does not always follow.

Growth brings complexity. Control does not always follow.

In the early stages, things are usually under control. You know your projects. You understand your costs. If something goes wrong, you see it quickly and can react.

But as the organization grows, that clarity becomes harder to maintain.

What we typically see is that data starts spreading across multiple systems:

• project management tools,
• time tracking solutions,
• spreadsheets,
• finance systems,
• CRM,
• HR and resource planning tools,
• subcontractor cost records,
• billing and invoicing processes.

Each of them may be useful on its own. But together, they create fragmentation. At some point, no one has a complete and reliable picture anymore.

For CFOs, this often shows up as delays in understanding project profitability. For COOs and delivery leaders, it appears as uncertainty around utilization, capacity, project overruns, and delivery risk. For CIOs, it becomes clear that the system landscape is no longer sustainable.

From our experience, this is where margin erosion begins — not because of one big issue, but because of many small ones that are no longer visible in time.

Where margins actually leak

Professional services companies do not usually lose margin only at the billing stage. Margin is often lost much earlier, during estimation, staffing, delivery, scope management, and project governance.

Typical margin leakage areas include:

1. Estimation leakage

The project is sold with assumptions that do not reflect actual delivery effort.

For example, sales estimates 300 hours for implementation, but delivery realistically needs 420 hours. The project starts with margin risk already built in.

2. Scope leakage

Additional work is delivered without a change request.

For example, a client asks for additional workshops, extra reporting, additional configuration, or more testing support. The team delivers it to maintain customer satisfaction, but no commercial change is approved.

Revenue stays fixed. Cost increases. Margin drops.

3. Time leakage

Time is entered late, incompletely, or against the wrong project or task.

This means project managers and finance teams do not see the true cost of delivery until it is too late.

4. Resourcing leakage

Senior people perform work that was planned for junior or mid-level consultants.

The project may still be delivered successfully, but at a higher internal cost than planned.

5. Utilization leakage

People are busy, but not necessarily billable.

Internal meetings, presales support, rework, admin work, and unplanned support activities consume capacity but do not generate revenue.

6. Billing leakage

Work is performed but not billed on time, or not billed at all.

This may happen because time is not approved, milestones are unclear, project managers delay billing confirmation, or commercial terms are not connected to delivery progress.

7. Subcontractor leakage

External costs are not controlled against the project budget.

Subcontractors may be necessary, but if their effort is not planned and monitored properly, project gross margin can deteriorate quickly.

8. Governance leakage

Risks are visible only at month-end.

By the time finance reports that margin is below target, the project may already be almost complete. At that point, there is limited opportunity to correct the outcome.

Spreadsheets work — until they do not

Almost every professional services company goes through a phase where spreadsheets play a central role. And to be fair, they work well in the beginning. They are flexible, easy to use, and quick to adapt.

But there is usually a point where they stop working.

It often looks like this:

• different project managers use different forecast templates,
• actual effort is not connected to the original estimate,
• resource plans are maintained separately from project budgets,
• finance receives project updates too late,
• billing depends on manual confirmation,
• project profitability is reviewed only after month-end,
• management reports require manual consolidation,
• different teams work with different versions of the same data,
• there is growing uncertainty in the numbers.

At that point, the issue is no longer only efficiency. It becomes a question of trust:

Can we actually trust our data when making decisions?

For CFOs, COOs, CIOs, and delivery leaders, that is a critical moment.

Financial control is not just about reporting

Another thing we often see is that financial control is interpreted too narrowly.

It is not just about closing the books or producing reports. In professional services, real financial control means understanding what is happening in the business early enough to act.

That means being able to:

• see project profitability as it develops, not months later,
• compare planned margin with actual and forecast margin,
• connect project activities with financial outcomes,
• identify scope risk before it becomes a write-off,
• understand utilization and capacity by role, team, and practice,
• monitor unbilled work and WIP,
• control subcontractor and expense costs,
• forecast project margin at completion,
• identify risks before they impact results.

Without this, growth becomes harder to manage. Decisions are delayed. Planning becomes less reliable. Margins become less predictable.  

The KPIs that matter in professional services

Knowledgeable professional services leaders do not only need general financial reports. They need operational and financial KPIs that show where margin is being created or lost.

Important KPIs include:

• Project gross margin
  Revenue minus direct delivery cost, measured by project, customer, service line, and project manager.
• Planned vs. actual margin
  Shows whether projects are delivered according to the commercial assumptions used during sales.
• Estimate-at-completion margin
  Forecasts expected final margin based on actuals, remaining work, and known risks.
• Billable utilization
  Shows how much available capacity is converted into billable work.
• Realization rate
  Shows how much recorded billable work is actually invoiced and accepted by the customer.
• Write-off percentage
  Measures work performed but not billed or not recovered commercially.
• WIP aging
  Shows how long work remains uninvoiced.
• Unbilled revenue
  Highlights delivery already performed but not yet converted into invoices.
• Change request conversion rate
  Measures how much additional scope is formally approved and billed.
• Forecast accuracy
  Compares project forecasts with actual outcomes.
• Resource allocation vs. availability
  Shows overbooking, underutilization, and future capacity gaps.
• Margin by contract type
  Differentiates risk between fixed-price, time-and-material, managed service, and retainer work.

These KPIs help leadership move from reactive reporting to active margin control.

In a Dynamics 365 context, these KPIs are strongest when project, resource, time, billing, and finance data are connected instead of managed in separate tools. This is where Dynamics 365 Project Operations, Dynamics 365 Finance, Power BI, and integrated CRM processes can provide a stronger management foundation.

Margin risk differs by contract type

Not all professional services work carries the same margin risk. A stronger financial control model recognizes the differences between contract types.

Time-and-material projects

In time-and-material projects, margin risk often comes from:

• low utilization,
• discounted rates,
• write-offs,
• delayed time approval,
• poor billing discipline,
• senior resources working below their rate level.

The key control question is:

Are all billable hours captured, approved, and invoiced at the correct rate? 

Fixed-price projects

In fixed-price projects, margin risk usually comes from:

• weak estimation,
• uncontrolled scope,
• rework,
• unclear acceptance criteria,
• poor change request discipline,
• underestimated testing or deployment effort.

The key control question is:

Are we protecting the planned margin as delivery effort changes?

Managed services

In managed services, margin risk often comes from:

• ticket volume exceeding assumptions,
• SLA obligations requiring more effort than planned,
• poor automation,
• too much senior involvement,
• unclear service boundaries.

The key control question is:

Is the recurring service profitable at the actual effort level?

Retainers

In retainers, margin risk often comes from:

• over-servicing,
• unclear consumption tracking,
• unused but non-transferable capacity,
• work delivered outside the agreed scope.

The key control question is:

Are we managing consumption and profitability within the agreed commercial model?

The professional services margin control loop

Companies that protect margin well usually manage profitability through a connected control loop.

The process is simple to describe, but difficult to maintain if sales, delivery, resource planning, finance, and billing operate separately.

A strong margin control loop includes:

1. Estimate the work realistically
   Sales and delivery agree on effort, roles, assumptions, risks, and commercial model.
2. Staff the project according to the planned delivery model
   Resources are assigned based on role, seniority, availability, cost rate, and margin expectations.
3. Deliver within scope and budget
   Project teams manage work against agreed scope, budget, milestones, and acceptance criteria.
4. Capture time and expenses accurately
   Time, expenses, subcontractor costs, and project activities are recorded regularly and correctly.
5. Forecast margin at completion
   Project managers do not only review historical actuals. They forecast expected final cost, revenue, and margin.
6. Bill work quickly and correctly
   Milestone billing, time-and-material billing, expenses, retainers, and recurring services are invoiced according to agreed commercial terms.
7. Review profitability by project, customer, and service line
   Leadership reviews margin at project and portfolio level, not only in aggregate.
8. Correct early when margin risk appears
   Teams can issue change requests, adjust staffing, renegotiate scope, escalate risks, or reforecast projects before margin is lost.

When this loop is broken, margin erosion becomes difficult to detect. When it is connected, leaders can act while there is still time to influence the outcome.

For growing professional services companies, margin control is not only a finance discipline. It is a scalability discipline: the company can only grow profitably if project, resource, billing, and financial decisions are connected early enough to influence outcomes.

Where ERP and PSA actually make a difference

This is typically the point where companies start seriously considering ERP or PSA platforms.

Not because they are simply looking for new technology, but because they need more structure.

The platform matters, but it is not the starting point. The starting point is the operating model: how sales, delivery, operations, finance, and management agree to plan, execute, measure, and correct project profitability.

In successful professional services organizations, ERP and PSA platforms create value by connecting the full lifecycle:

• CRM opportunity,
• quote and commercial estimate,
• project budget,
• work breakdown structure,
• resource plan,
• role-based cost and sales rates,
• time and expense entry,
• subcontractor costs,
• project accounting,
• revenue recognition,
• milestone billing,
• WIP,
• invoicing,
• project forecasting,
• profitability reporting.

The value is not only that data is stored in one place. The value is that project, delivery, resource, and financial data are connected.

This allows leaders to answer questions such as:

• Did we sell the project at the right margin?
• Are we delivering according to the original estimate?
• Which projects are at risk?
• Which customers are profitable?
• Which service lines create the best margin?
• Where are we using too much senior capacity?
• What work has been delivered but not billed?
• Which projects need a change request?
• What is the forecast margin at completion?

These questions cannot be answered reliably if sales, project delivery, time tracking, resource planning, and finance all operate separately.

How integrated ERP and PSA platforms support margin control

For professional services companies, integrated ERP and PSA platforms support a more connected operating model across the full project lifecycle.

In a Microsoft Dynamics 365 environment, this operating model is typically supported through Dynamics 365 Sales, Dynamics 365 Project Operations, Dynamics 365 Finance, Power BI, and Power Platform.

The typical solution architecture may include:

• Dynamics 365 Sales for opportunity management, qualification, pipeline, and commercial handover.
• Dynamics 365 Project Operations for project estimation, project contracts, work breakdown structure, resource planning, time and expense, project execution, and project-level visibility.
• Dynamics 365 Finance for project accounting, billing, revenue recognition, cost control, intercompany processes, approvals, financial reporting, and finance operations across legal entities.
• Power BI for management dashboards, project profitability analysis, utilization reporting, margin forecasting, and portfolio-level insights.
• Power Platform for workflow extensions, approvals, lightweight applications, integrations, and process automation where standard processes need controlled flexibility.

The important point is that Dynamics 365 is not only an ERP replacement. In a professional services context, it can become the operational and financial backbone connecting sales, delivery, resourcing, billing, and finance.

For example:

Sales estimates are disconnected from delivery reality → addressed through opportunity, quote, project estimate, and project contract integration.

Project managers use separate forecast spreadsheets → addressed through project budgets, forecasts, actuals, and estimate-at-completion visibility.

Time entries arrive too late for margin control → addressed by connecting time and expense capture to project accounting.

Senior resources are used on work planned for junior roles → addressed through role-based resource planning, cost rates, and utilization reporting.

Fixed-price projects lose margin through uncontrolled scope → addressed through project baseline, change control process, project forecasts, and billing control.

Work is delivered but not billed on time → addressed through project contracts, milestones, invoicing, WIP, and billing integration.

Finance sees margin issues only at month-end → addressed through project-level actuals, forecasts, reporting, and Power BI dashboards.

Leadership lacks portfolio-level visibility → addressed through reporting by customer, project, project manager, service line, country, and contract type. 

This is where ERP and PSA become more than administrative systems. They become a control layer for professional services profitability.

Concrete example: fixed-price implementation project

Consider a fixed-price implementation project sold for EUR 250,000.

The commercial estimate assumes:

• 1 project manager,
• 2 senior consultants,
• 3 consultants,
• 1 solution architect part-time,
• total planned effort of 1,200 hours,
• planned gross margin of 35%.

During delivery, several things happen:

• the client requests additional workshops,
• testing takes longer than planned,
• senior consultants perform tasks planned for consultants,
• time entries are submitted late,
• project risks are discussed internally but not reflected in the forecast,
• no change request is issued for additional scope.

At month-end, finance reports that the project margin has dropped to 22%.

The issue is not discovered early enough because delivery activity, time, scope changes, and financial forecasting were not connected.

With a stronger ERP/PSA model, the organization could see much earlier that:

• actual hours are exceeding the plan,
• senior resources are consuming more budget than expected,
• remaining work is higher than forecast,
• unapproved scope has been delivered,
• estimated margin at completion is below target.

This gives the project manager, delivery director, and CFO time to act: issue a change request, adjust scope, change staffing, escalate commercially, or reforecast the project before the margin is lost.

In a Dynamics 365-based model, this kind of control is possible when the original estimate, project contract, work breakdown structure, resource plan, time entries, project actuals, billing milestones, and financial reporting are connected. The purpose is not only to report the final margin. The purpose is to detect margin risk while it is still possible to influence the outcome.

Concrete example: managed services contract

Consider a managed services contract with a monthly fee of EUR 20,000.

The original financial model assumes:

• 120 hours of support per month,
• mostly consultant-level work,
• limited senior escalation,
• standard SLA response times,
• target gross margin of 40%.

After six months, the customer is still paying EUR 20,000 per month, so revenue appears stable. But actual delivery shows:

• 180 hours per month are being consumed,
• senior specialists are involved more often than expected,
• ticket volume has increased,
• recurring issues are not automated,
• SLA pressure requires faster response,
• customer-specific knowledge limits resource flexibility.

The contract is still active and the customer is satisfied, but the margin is deteriorating.

Without detailed service profitability tracking, this may remain hidden. With proper ERP/PSA visibility, leadership can decide whether to renegotiate the scope, automate recurring work, adjust the service model, increase pricing, or change staffing.

In a Dynamics 365 environment, profitability of recurring work can be analyzed by contract, customer, service line, resource role, cost category, and actual effort. This allows leadership to separate commercially healthy managed services from contracts that consume more capacity than originally planned.

What good margin control looks like

A strong professional services operating model usually includes:

1. Commercial estimate connected to delivery plan

The estimate used in sales becomes the baseline for project delivery and financial control.

2. Role-based planning

Projects are planned by role, cost rate, sales rate, seniority, and availability.

3. Real-time time and expense tracking

Time is captured regularly, approved quickly, and connected to project budgets.

4. Forecast margin at completion

Project managers do not only report actuals. They forecast expected final cost and margin.

5. Structured change control

Additional work is identified, priced, approved, and billed through a clear process.

6. Integrated billing

Milestones, time, expenses, retainers, and service fees are connected to invoicing.

7. Portfolio-level visibility

Leadership can see margin by project, customer, project manager, service line, country, and contract type.

8. Governance routines

Project margin is reviewed regularly, not only after month-end close.

Dynamics 365 can support these routines when business processes are designed end-to-end rather than module by module. The implementation focus should not only be on system configuration, but also on defining how sales, delivery, operations, and finance work together around one version of project and financial truth.

Practical warning signs for professional services leaders

Professional services companies should review their operating model when they see these signs:

• project margin is understood only after the project is complete,
• project managers maintain financial forecasts in separate spreadsheets,
• sales estimates are not connected to delivery planning,
• time entries are late or incomplete,
• change requests are discussed but not formally approved,
• utilization looks high but profitability is declining,
• senior resources are constantly pulled into delivery escalations,
• WIP and unbilled revenue are increasing,
• fixed-price projects regularly finish below target margin,
• finance and delivery teams disagree on project status,
• reporting is too slow to support corrective action.

These are not just reporting issues. They are control issues.