The Signal

The Lead

The number is the wrong fight

Something lands on your desk that you are expected to sign. A vendor's change request. A statement of work. A fixed bid. A quote on a piece of work you committed to before the scope was fully drawn. There is a number on it, the number is larger than you wanted, and somebody with more authority than you wants it approved before it becomes a problem. You have about an hour.

Here is what almost everyone does with that hour. They fight the number. Is it reasonable. Can it come down. They trim it, they sign, and they feel like they did the job.

The number was never the thing to interrogate.

Underneath almost every contested commitment is a boundary nobody settled. On a change request, it is the question of whether the work is genuinely new or whether it was ambiguous in the original agreement, because if it was ambiguous, a real share of the cost is the other side's risk, not yours. On a fixed bid, it is which assumptions the price quietly depends on. On a vendor contract, it is who owns the gap when reality differs from the spec. The figure is downstream of that boundary every time. Negotiate the number before you settle the boundary and you are bargaining over the wrong quantity, and worse, you are writing the precedent that the next three commitments will be measured against.

The skill that separates the person who protects a budget from the person who processes paperwork is not negotiation. It is the discipline to ask, before anything else, what the boundary actually is and who carries the risk on the wrong side of it. That is not a personality trait. It is a repeatable read, and it is the same read whether the commitment is a six-figure integration change or a two-page scope addition.

This is the part of the work I keep coming back to in this newsletter. The hard, valuable thing is almost never the tool. It is the encoded judgment underneath the tool. The boundary question is a decision-logic question, and decision logic is exactly what the AI era makes both more valuable and easier to capture. A model is very good at running a disciplined read consistently, every time, without the fatigue and the deadline pressure that make a tired professional reach for the easy number at four on a Friday.

So I built the read into a tool. You paste the commitment on your desk and you get a structured view back: whether the number is honest and what pushes it in each direction, where the scope boundary actually sits, where your leverage is, the live risks, and the questions to close before you sign. It is reasoning support, not a verdict. It does not tell you what to do. It makes sure the hour you have goes to the right question.

The idea is universal. The first version is not. I built it first for PMO leaders and program directors, because the Friday change request is the sharpest, most repeated version of this problem and it is a room I know well. The engine underneath is general. More doors will follow for the other people who sign off on scope and price for a living. But a tool earns trust by being unmistakably built for one reader, so I started with one.

If you run a PMO or a program, there is a free worked sample on the page that runs a real ERP change request end to end, so you can see the read before you decide anything. If you sign off on scope and price in some other room, tell me which room. It is probably the next door.

Or read this issue on LinkedIn.