A deal's real profitability belongs on the deal

“Was that deal profitable” should be one question, with one answer, on the deal record.

In most firms it is a spreadsheet built two months after the project ends, by a finance lead reconstructing costs that never flowed through invoicing. The early estimate gets used as if it were the result. Sales reports attainment against numbers delivery does not recognize. Margin literacy lives in the head of the one person who reconciles them, and that person is always one resignation away from the firm not knowing what its book of business actually earns.

The two-numbers problem

A deal carries an estimate. A project carries actuals. Those are two different numbers stored in two different systems by two different teams with two different sets of incentives.

The estimate is the rep’s commitment at the moment the deal was sold. It is anchored to the proposal, the SOW, the assumed scope, the priced bill rate. It does not move after Closed Won, because the deal is closed.

The actuals are what the delivery team logs. Hours against the project. Overruns when the scope expanded. Subcontractor invoices the deal owner never saw. Discounts approved mid-project that nobody routed back to the deal record. Costs that came in higher than the estimated cost rate because the resource assigned was more senior than the estimate assumed.

The spreadsheet that reconciles them is rebuilt every quarter. It is built by someone whose actual job is closing the books, not chasing the deal owner for context. The reconciliation takes two months because two months is how long it takes to get answers to the questions the spreadsheet generates. By the time the spreadsheet is done, the next quarter’s reconciliation has started.

The compounding cost is the cultural one. The rep does not see the truth of the deal they sold. They see the estimate, they see their commission paid against the estimate, and they go close the next one. The next deal carries the same estimate-to-actuals gap. The firm runs on numbers nobody on the delivery side recognizes.

Why the estimate keeps getting used as if it were the result

Because the actuals live somewhere the deal owner cannot see.

The project tool has the time entries. The accounting system has the invoiced amount. The subcontractor folder has the SOW with the split. The deal record has the estimate from six months ago. The deal owner has the calendar of a salesperson, which is to say they do not have an afternoon to chase actuals across three systems.

The project lead has no incentive to reconcile. Their measure is on-time and on-spec delivery, not deal-level margin reporting. Reconciling the deal owner’s estimate against the project’s actuals is somebody else’s job, and somebody else has not figured out how to do it without a spreadsheet.

So the estimate is the number that gets reported, because the estimate is the number that is easy to find. The actuals are the number that is true. Those should be the same number, and in most firms they are different by enough to matter.

What changes when both live in the same place

The shape of “is this deal profitable” changes when the deal record carries billed, paid, outstanding (with aging), recognized vs deferred, cost, and margin, all sourced from the same engine that powers the project view.

The rep sees what the project lead sees. The rep sees their attainment against reality, not against the estimate. The deal owner sees the truth of the deal while the deal is still in delivery, not two months after close.

For shared-delivery work, where one project serves multiple deals, the math has to be honest about the split. A shared project’s cost has to be counted exactly once across the deals that share it, allocated in proportion to each deal’s contract value share. Deal-level margin and the portfolio total have to reconcile by construction, or one of them is wrong and the firm is back to running two sets of numbers.

The cultural shift is the part that matters most. Margin literacy stops being “what finance found out at the close.” It becomes “what the rep can see while the deal is still alive.” A deal owner who sees their margin slipping in week six does something different than a deal owner who finds out two months after delivery ended.

What PartnerView ships

The deal record carries the financial cockpit. Billed amount, paid amount, outstanding with aging, recognized vs deferred revenue, cost to date, margin to date. All on the deal. All sourced from the same engine the project view uses. The numbers on the deal and the numbers on the project agree by construction, because they are the same numbers rendered against the same source of truth.

For shared projects, cost is allocated across the deals that share the project in proportion to each deal’s contract value share. One shared engine handles the split. Deal-level margin sums to the portfolio total without a separate reconciliation. The fairness rule is encoded in code, not in a finance lead’s spreadsheet.

The portfolio view is the natural extension. The same numbers, ranked worst-first, sortable by variance against estimate. The fifth-worst project is visible the moment it becomes the fifth-worst project, not three quarters later when the reconciliation catches up.

Margin literacy belongs on the deal. The deal owner is the right person to see it. The right time to see it is now, not after the books close.