A year ago I managed projects. Now I manage a P&L. Here is what changed.

As a project manager, my question was "did we deliver this well?" On time, in scope, to quality, with a happy client. It is a good question and I still ask it. But as the owner of a P&L, the question underneath every decision became "did we build something healthy?" A project can be delivered beautifully and still lose money. A client can be delighted and still be the account that is quietly draining the practice.

That shift sounds abstract until the first month-end. Then it is very concrete: a list of engagements, each with revenue, cost, margin and a forecast for next month, and a CEO who wants to know why two of them are red.

I used to look at burn-down charts and ticket counts. Now there are five numbers I can state from memory for the practice and for each account.

The single biggest margin leak I found was not bad estimation. It was work nobody approved. A small favour in one sprint, a "quick" fix in another, an extra environment that was never priced. On one account a scope-reconciliation exercise surfaced more than 230 hours of unapproved work before it reached an invoice.

Now every change is written down the week it is discovered, with a price and a decision: bill it, absorb it on purpose, or map it to a future phase. Absorbing work is sometimes the right call for a relationship. It just has to be a choice, recorded and visible, not something that happened.

A new engineer is a fixed cost from their first day and billable only after onboarding. As a project manager I asked for people when a sprint was overloaded. As a P&L owner I look at the pipeline, the bench and the three-month forecast before I open a role. Sometimes the right answer is to hire ahead of demand. Often it is to move someone between accounts, or to say no to work that would need a hire we cannot keep busy.

When you own the number, you have to talk about money with clients: rates, change requests, disputed invoices, what a retainer does and does not cover. I expected those conversations to damage relationships. The opposite happened. Clients who see a clear scope-reconciliation workbook every month trust the invoice more, and the arguments move from "why is this so expensive?" to "which of these do we want to prioritise?"

I stopped being the best technical problem-solver in every escalation. My engineering background still matters, because I can read the logs and challenge an estimate, but the practice does not scale if every hard problem waits for me. I stopped treating a green status report as good news without checking the margin behind it. And I stopped saying yes early. The most valuable thing a P&L owner can do is decline work that will lose money or burn out the team, before anyone has committed to it.

If you are a project manager thinking about this move, start now: build a shadow P&L for your own programme. Estimate the cost, track the hours, compare with what was invoiced. You will learn more in three months of doing that than in any course.