Everyone Is Busy. Where Is the Profit Going?

Professional Services · Management & Profitability

In companies that sell the time of expensive people, “busy” does not mean “profitable” — and losses rarely look like losses.

In professional services, weak sales and weak margins often start with the same issue: how the firm uses its capacity.

In professional services firms, profit is not always lost through major decisions. More often, it disappears through hours, staffing mix, absorbed scope and projects that look healthy until you measure them properly.

For years, I have worked with companies that sell the time of expensive people: consulting, software development, systems integration and technical services.

Healthy, growing companies with capable founders, valuable people, satisfied clients and a great deal of hard work behind them.

Companies that have done many things well: built relationships, attracted good people, won clients, delivered difficult projects and grown entrepreneurially.

But at a certain stage, two questions tend to appear side by side.

Why is there not more profit left if everyone is busy? And why are we not selling more if we are good at what we do and clients are satisfied?

They may seem different. One is about margin, the other about sales.

In professional services, they are often the same question seen from two different angles.

Because the same capacity that should be delivering profitably is also expected to sell, develop clients, build methodology and grow people.

If key people are trapped in delivery, there is no time left for sales and development.

If projects consume more than estimated, there is no energy left for business development.

If every delivery is handcrafted, no reusable methodology is being built.

If you absorb additional scope to protect the relationship, the client may be happy — but the firm loses margin and energy.

But this is not only a time problem.

In many technical firms, sales remains tied to delivery. It depends on founders, partners or a few senior people who know the client, understand the technical problem and somehow also need to find time to sell.

That works for a while, especially when the company is small and relationships are close.

At a certain point, however, business development needs its own discipline: a consistently managed pipeline, clear ownership, realistic stages and a forecast linked to capacity.

Otherwise, sales happen between projects — when there is a window in the calendar or when the gap begins to show.

And then the company enters a familiar cycle: when there is a lot to deliver, it does not sell enough; when delivery slows down, it starts selling too late.

This creates a common paradox: the company is busy, but not profitable enough; it has satisfied clients, but does not sell enough; it has good people, but depends increasingly on a few of them.

From the outside, it looks like a sales or profitability issue.

From the inside, it is usually deeper: the company has grown faster than the system through which it is managed.

Many firms grew precisely because they were flexible, close to the client and able to solve problems without too much structure.

But what works at 15–25 people begins to creak at 50, 70 or 100.

When a business is struggling, it is forced to look for causes.

When it is doing well but performing below its potential, losses can hide for years behind the assumption that “this is just normal”.

Where the Real Economics Hide

Accounting tells you what happened financially.

But in a services firm, the real economics start earlier: in estimation, staffing, delegation, timesheets, scope and the client relationship.

And they almost never appear as a loss with a name.

At an aggregated profit level, the company may look fine.

At project level, things become blurred: some projects pull the company up, while others only appear healthy because they generate high revenue but consume valuable capacity and leave little behind.

You do not see real utilisation. You see busy people. You do not always see project margin. You see total profit. And that is the trap: busy does not mean billable, and billable does not necessarily mean profitable.

There is something else that almost nobody tracks closely enough: not only how many hours were used, but whose hours.

A project can look excellent in revenue terms and disastrous economically if it was delivered with the wrong mix of people.

On paper, it was delivered.

In reality, the company consumed exactly the capacity it should have been multiplying.

This is hard to see without a fully loaded cost rate.

An expensive person does not cost only their salary. They cost salary, taxes, benefits, management, bench, training and overhead.

It is also hard to see without an effective bill rate — not the list price, but what remains after discounts and write-offs — and without basic discipline around project margin.

An estimated margin is not the same as a measured one.

The concepts are not sophisticated.

They are simply uncomfortable.

The Profit Engine Is Different from What You Think

When key people are too tied up in delivery, the firm can stay busy without building enough capacity to grow.

A traditional business, retail, manufacturing or distribution, makes profit by moving volume: selling more units while scaling relatively independently of a particular person.

A services firm does not work that way.

Your “unit” of sale is an hour of an expensive person’s time.

It is perishable, constrained by capacity and impossible to produce for stock.

An unsold hour today does not carry over into tomorrow. It disappears at six o’clock, like an empty seat on a plane that has already taken off.

Capacity is perishable.

Rate × utilisation × leverage − cost

This is why profitability in a services firm rests on three multipliers and one cost.

It is not a formula to calculate literally. It is the structure of the engine.

You grow profit by increasing rates, improving utilisation or improving leverage — using the right delivery mix around senior talent.

You reduce profit through cost rate.

That is it.

And here is the trap: growth usually means more expensive people, which means cost rises before revenue does.

The factor that breaks most often is leverage.

And it has a name: underdelegation.

Senior people do too much.

Managers do not take enough on.

Junior people are kept away from real work because “there is no time to train them now”.

Founders intervene because “this is an important client”.

Everything is understandable. Sometimes even necessary.

But when it becomes the operating model, expensive people end up doing work that should be done by less expensive people.

You scale cost without scaling margin.

A company that is “growing” can quietly become less profitable.

Growth without the right leverage is not growth. It is dilution.

The cost is double.

You deliver at high cost and low margin. And younger people do not grow because nobody gives them enough space to do so.

You pay once in profitability and again in the development of your people.

Underdelegation does not appear in a financial report under its own name.

It appears as lower profitability, burnout, lack of capacity, slow growth and dependence on a few people.

That is why the important question is not only, “How much did we bill?” It is: “What capacity did we consume in order to bill it?”

Utilisation Looks Simple Until You Try to Define It

Utilisation looks like a simple number. It only becomes useful when the company decides clearly what it measures: available time, billable time, write-offs, bench, presales and internal work.

If the engine runs on utilisation, you might think anyone could tell you the number immediately.

Ask two people and you may get two different answers, without either realising that they are measuring different things.

Available time: all hours, or net of holidays, training and administration?

Billable time: invoiced hours only, or also hours later lost through write-offs?

Where do you place productive but non-billable work, presales, methodology and accelerators?

Is bench included in delivery cost or OPEX?

Does the person who informally helps three teams appear anywhere?

Is management time separated or mixed into delivery?

These questions may sound technical.

They are not.

They reveal how you see the business.

If utilisation is not clearly defined, every manager has their own version of it.

If it is not linked to cost rate, bill rate and staffing mix, it only tells you that people were busy — not whether the company generated healthy profit.

Whether bench belongs in delivery cost or overhead does not have one “correct” answer.

But it needs to be a conscious choice, applied consistently.

Most companies have never made that choice explicitly.

That is why their project margin figures cannot be trusted.

Without explicit definitions for the numerator and denominator, utilisation is not a number. It is an opinion with decimals.

And everything depends on the timesheet at ground level.

If it is poor, everything above it is simply a well-formatted opinion.

That is why a timesheet is not merely time tracking.

Many people dislike it, sometimes for good reason.

But without it, you cannot see the difference between plan and reality: what staffing mix you estimated, what mix you actually used, where time went, what you billed, what you absorbed and what you learned.

What Project Numbers Do Not Tell You

A good project is not judged by revenue and margin alone. What it builds matters too: people, methodology, the client relationship and capacity for the next stage.

Many firms judge a project through two numbers: revenue and margin.

But a good project is more than that.

And what the numbers miss tends to move in two directions.

First, inward.

Projects do different things in the life of a company.

Some create revenue.

Some build reputation, important accounts, stronger people or reusable methodology.

Others simply keep the team busy and consume critical capacity without leaving anything behind.

A mature company sees the difference.

Because people are its core asset — but an asset that needs to be developed through projects that stretch them, roles that challenge them and senior people who delegate.

Otherwise, the company consumes the very talent it claims to be developing.

The Client Buys Peace of Mind, Not Only Technical Quality

Then there is the client side.

Technical firms often believe that if delivery is technically good, the service is good.

Not always.

Many clients cannot fully assess technical quality.

But they can assess the experience very clearly.

Did you communicate?

Were you available?

Did you warn them early when something was drifting?

Did you explain the risks?

Did you reduce anxiety?

The client buys peace of mind as well.

You can deliver flawlessly from a technical perspective and still leave the client feeling that things are going badly.

And you can have a difficult internal project with a calm client because they were kept informed and involved.

A company that measures only on-time, on-budget and margin confuses internal delivery with client experience.

On both axes, the obvious number does not tell you whether the project was actually good.

Between Heroics and a Repeatable System

Everything above is an expression of one thing: how mature the system is through which the company is managed.

One established model in the services industry, developed by SPI Research, describes five maturity levels.

Level 1 — Initiated / Heroic

The company runs on key people and improvisation.

Things get solved because certain individuals carry them on their shoulders.

What you tell yourself: “We are agile.”

---

Level 2 — Piloted / Functional

You have timesheets, targets and reporting, but they do not speak to one another.

Sales, delivery, finance and HR are looking at different versions of reality, in parallel spreadsheets.

Projects are reviewed late, once things have already happened.

What you tell yourself: “We have the data. It is just in several places.”

The pipeline exists, but it is closer to a list of opportunities than a management tool.

It is not sufficiently linked to capacity, staffing or realistic probability of closing.

This is where more firms find themselves than they would like to admit — especially because having data creates the appearance of maturity.

---

Level 3 — Deployed / Project Excellence

Projects have baselines and reforecasts.

Utilisation is defined and tracked by role.

Margin is visible at project level.

You no longer discover at the end that you lost money.

---

Level 4 — Institutionalised / Portfolio Excellence

Staffing is proactive.

The company makes portfolio decisions: what types of projects it wants, which clients are worth developing, what work should be declined and which capabilities need to be built.

The pipeline is linked to capacity and is no longer only the responsibility of sales.

---

Level 5 — Optimised / Collaborative

The company is managed almost like a predictive system.

The data is reliable, decisions are fast, forecasts are credible, and every project improves the way the company sells, staffs, delivers and develops people.

Most companies are not at only one level.

They may be mature financially and immature in staffing.

The uncomfortable part is that many firms measure maturity only against themselves, compared with last year.

“We are doing better than last year” may be true and still not mean the system is ready for the next stage.

And if the reaction is, “We have tried many things,” one more question is worth asking:

Have we tried everything that was visible from inside, or have we also had an external benchmark?

That is precisely why the conversation can be useful.

A Platform Does Not Fix Confusion. It Only Makes It More Visible.

Many firms reach the conclusion: “We need a better platform.”

Sometimes that is true.

But if you do not have clear definitions for utilisation, cost rate, bill rate, bench, project margin and planned versus actual staffing, any platform will simply reflect the existing confusion.

It may do it more beautifully, more quickly and with better dashboards.

But it will still be confusion.

Software becomes useful after you have decided what you need to see and how you want to manage the business.

Otherwise, you digitise instinct and call it a system.

Questions Worth Asking

• What is our current utilisation, and what is the target?

• What was the margin on the last three major projects?

• What is the fully loaded cost rate by role?

• What is the effective bill rate, not the list rate?

• How much bench do we have, and how do we treat it financially?

• How much time was spent on work that could have been delegated?

• When do we discover that a project is losing money: during the project or after it?

• Which projects develop people, and which merely consume them?

• Which clients generate margin, and which simply keep the team busy?

• Is the operating model written down, or is it only known by a few people?

If the answers are clear, you have a rare discipline.

If they are approximations, the company has probably reached a familiar point in its growth: instinct still works, but it is no longer enough as a management system.

Let’s Talk

Knowing what you cannot see is the first step.

Building the management tools that make these things visible — without killing the entrepreneurial energy of the company — is the harder part.

And usually the part that needs to be worked through in the specific context of each business.

The model that got the company this far deserves respect.

But at a certain point, it needs to be made explicit if it is to take the company further.

Eventually, the question is no longer:

“Do we have good people?”

It becomes:

“Do we have a system that turns good people into repeatable performance?”

The first step is not having all the answers.

It is seeing the right questions.