Profitability Principles Are Known. The Hard Part Is Running Them.

Most owners of IT services and professional services firms already know the principles that improve profitability.

Price work properly. Model deals before signing. Do not let discounting become the default sales tool. Record actual time as it happened. Protect scope. Use senior people where they create the most value. Keep bench visible. Resolve staffing conflicts deliberately. Review forward profit before the monthly close confirms the result.

None of that is new.

The problem is not that services firms lack profitability principles. The problem is that those principles are hard to run consistently as the firm grows.

They are easy to agree with in a leadership meeting. They are harder to maintain when sales wants to win a strategic deal, delivery wants to protect a client relationship, a project manager wants the status report to stay green, a senior architect steps in because it is faster, and finance only sees the financial consequence after the month has closed.

This is where many firms get stuck.

They do not need another slogan about profitable growth. They need an operating system that makes the principles practical in daily work.

Because profitability does not improve just because leaders know what good looks like. It improves when the firm embeds the right principles into how deals are sold, projects are delivered, people are staffed, and future profit is reviewed.

Principles Break Under Pressure

Most profit leakage does not happen because someone makes an obviously bad decision.

It happens because people make reasonable decisions locally.

Sales discounts a deal because the client is important. Delivery absorbs a scope change because the relationship matters. A senior person steps in because the team is under pressure. A consultant smooths time entry because the project is already over budget. A practice lead holds onto capacity because a major opportunity might close next month. A project manager reports the project as green because the milestone was met and the client is happy.

Each decision can be defended.

Together, they weaken the economics of the firm.

This is why principles fail. They are rarely violated dramatically. They erode quietly.

A firm may have a principle that all significant deals should be modelled before signature. But if the model lives in a spreadsheet outside the opportunity, sales will bypass it under time pressure. A firm may believe that all work should be sold at target contribution margin. But if target margin is not visible during deal shaping, it becomes an aspiration rather than a control. A firm may expect actual time to reflect reality. But if timecards are used mainly to explain budget overrun later, people will start managing the optics.

The issue is not intent. It is design.

If the principle sits outside the workflow, it depends on discipline, memory, and manual reconciliation. That works in a small firm where the founder can see most of the decisions. It breaks as the firm grows.

At 20 people, the owner may still know which client is over-serviced, which project is drifting, and which senior person is rescuing delivery. At 60 people, those signals are spread across sales, delivery, finance, people, and project management. They may exist, but they are no longer naturally connected.

The firm becomes larger than the founder's direct line of sight.

That is when principles need to become system behaviour.

The First Principle: One Source Of Truth

The first operating principle is simple:

Enter the operational fact once, where it belongs, and let the same fact drive the financial view.

Services firms often fail here.

The opportunity has one version of the deal. The pricing spreadsheet has another. Delivery builds a project plan from a third version. Finance later reconstructs margin from actuals. People leaders maintain resourcing assumptions somewhere else. Each view may be reasonable, but the firm no longer has one truth.

This creates friction and delay.

A deal is sold at one margin, delivered at another, and explained later through a reconciliation exercise. The project plan changes, but the financial outlook does not. A role is filled by a more expensive person, but the margin impact appears only after time is booked. A client asks for extra scope, delivery absorbs it, and finance sees the erosion after the close.

The cost is not only administrative. It is managerial.

When the firm has multiple versions of truth, leaders spend time debating the numbers instead of acting on them. The sales view, delivery view, and finance view all become defensible. The meeting becomes a reconciliation exercise rather than a decision forum.

One source of truth does not mean one person owns all data. It means the firm has one connected operating model.

Sales should own commercial assumptions. Delivery should own project reality. People leaders should own capacity and staffing decisions. Finance should own financial interpretation and control. But the facts should connect.

A role in a deal should not need to be re-created in a project spreadsheet. A person's cost should not be manually interpreted every time it appears in a plan. A project change should not wait for month-end to become financially visible.

The principle is operational:

The fact should be captured closest to where it happens, then used everywhere it matters.

That is how the firm reduces duplicate admin and improves decision speed at the same time.

The Second Principle: Shift Financial Insight Left

The second principle is to shift financial insight left.

In software delivery, "shift left" means moving testing, quality, or security earlier in the process so defects are found when they are cheaper to fix. Services firms need the same logic for financial insight.

Margin problems should not first appear in the monthly P&L.

By then, the deal has been signed, the client expectation has been set, the senior person has done the work, the scope has been absorbed, or the bench cost has already been carried.

The insight arrived too late.

Financial insight should appear when the operating decision is made.

When a deal is shaped, the firm should see role cost, commercial mode, phase structure, and target contribution margin. When the team changes, the project economics should change. When a scope extension appears, the forward view should move. When an open role stays unfilled, the delivery and financial risk should be visible. When pipeline with a defined deal model moves closer to conversion, leadership should see the potential future impact.

This does not mean turning every delivery person into a finance analyst.

It means the normal operating workflow should create financial signals automatically.

The person closest to the action should not need to maintain a separate finance model. They should do their work: model the deal, update the project, record actual hours, add the role, mark the scope change, review the capacity conflict. The financial consequence should follow.

This is the difference between reporting and operating control.

Reporting explains what happened. Operating control shows what is forming while there is still time to act.

For an owner, the key question is:

Where does financial truth first appear in your firm: at the point of decision, or after finance rebuilds the story?

If the answer is after finance rebuilds the story, the firm is learning too late.

The Third Principle: Preserve Commercial Intent

The third principle is to preserve commercial intent.

Many services firms lose margin because the economics of the deal do not survive into delivery.

Before signature, the deal may have a clear case: target margin, role mix, phase structure, commercial mode, delivery assumption, timeline, and risk profile. Once the deal becomes a project, that context often weakens.

Delivery inherits the work, but not always the financial intent. The project plan is built again. People are assigned based on availability. Scope shifts. Senior people step in. The client asks for more. The status report remains green until the financial result says otherwise.

The deal case becomes a memory.

That is a problem because the deal case is where commercial discipline begins. If it disappears after signature, the firm cannot tell whether delivery is preserving or eroding the economics that justified the work in the first place.

Preserving commercial intent means the project is managed against the case it was won on.

If the deal assumed a mid-level consultant and a senior architect is substituted, margin should move. If a fixed price phase takes longer than planned, margin should move. If a scope change is unsigned, it should be visible as a commercial event. If the client asks for additional work, leadership should see whether it is recoverable scope, goodwill, or margin leakage.

This is especially important as firms move between T&M, fixed price, and fixed fee models.

Each commercial model carries different risk. T&M may protect the firm from some scope risk but is vulnerable to pricing pressure and utilisation dependency. Fixed price can improve margin if delivery is controlled, but exposes the firm to estimation and scope risk. Fixed fee can create repeatable revenue, but requires strong capacity and service boundary discipline.

Commercial intent is not just the price. It is the logic behind the price.

The firm needs to preserve that logic through delivery.

The Fourth Principle: Separate Future Realities

The fourth principle is to separate future realities.

Many firms talk about "the forecast" as if there is one future.

There is not.

A services firm usually has at least three different financial realities forming at the same time.

First, there is contracted work: what is already signed and committed.

Second, there are extensions and change requests: the scope that may expand existing work, recover margin, or create additional contribution if handled commercially.

Third, there is modelled pipeline: opportunities that may convert, but only with the economics currently assumed in the deal model.

Blending these into one forecast creates false comfort.

If contracted work is weak but pipeline is strong, the blended view may look acceptable. If extensions are likely but unsigned, the firm may overstate certainty. If pipeline exists but the deal model is thin or unrealistic, the forecast may create confidence that delivery later destroys.

Leaders need to see the layers separately.

Contracted work tells the firm what it already has. Extensions and change requests show what could improve or protect the current position. Modelled pipeline shows what future wins would do if they convert under the assumptions currently held.

This is not forecasting for its own sake. It is decision support.

If contracted margin is below target, leadership can ask whether extensions can recover it. If pipeline is strong but low-margin, sales can adjust deal shape before signature. If open roles create delivery risk, people leaders can act before the revenue becomes exposed. If a future scenario depends heavily on uncertain pipeline, the owner can see the risk rather than discovering it late.

Separating future realities helps leaders avoid managing the business through optimism.

It makes the difference between what is committed, what is possible, and what is still only potential.

Why Dashboards Are Not Enough

Many firms respond to these problems by adding dashboards.

Dashboards can help, but they do not solve the core issue.

A dashboard is only as useful as the operating discipline underneath it. If the deal model is disconnected, the dashboard will show delayed or incomplete margin. If actual hours are smoothed, the dashboard will show managed optics. If scope changes are not captured commercially, the dashboard will miss leakage. If pipeline has no financial model, the dashboard will show revenue hope rather than profit consequence.

The answer is not simply more visualisation.

The answer is embedding profitability principles into the workflow.

That means the principle is not something leaders remind people to follow. It is something the system makes easier to follow than ignore.

If every qualified deal requires a deal model, sales discipline improves. If target contribution margin is visible before commitment, discounting becomes explicit. If actual delivery changes move project economics, green status is harder to fake. If open roles and bench appear as financial exposure, staffing decisions become commercial decisions. If contracted work, extensions, and modelled pipeline are separate, leadership can act on the right version of the future.

This is what a profitability operating system should do.

It should not add another admin layer. It should reduce the need for disconnected admin by connecting the facts already being created in the business.

The Owner Question

Every growing services firm eventually reaches the same point.

Founder intuition is no longer enough. Spreadsheets multiply. The leadership team sees different versions of the truth. Sales, delivery, people, and finance are each making reasonable decisions locally, but the combined financial outcome is not clear until too late.

That is when the owner has to decide whether profitability will remain a management intention or become an operating system.

The principles are known.

The question is whether the firm can run them.

A useful test is this:

If you asked your team today how a deal moves from sales assumption to delivery reality to forward profit, would they describe one connected operating model, or a chain of spreadsheets, meetings, and reconciliations?

If the answer is the second, the firm does not have a profitability problem only.

It has an operating system problem.