The most consequential weakness in a margin proposal may be the boundary of its revenue rather than the quality of its arithmetic. A worksheet can add correctly, calculate a percentage accurately and still imply more commercial certainty than the underlying agreement provides. In an engineering-service business, proposed variations often arise from real work and informed discussion. They are not necessarily fanciful. But plausibility is a different basis for committing resources from an authorised scope, and a financial presentation should preserve that difference where the decision is made.
I learned this through a proposal I supported as finance director in 2017. The combined case showed ₹10 crore possible revenue and ₹7.7 crore estimated cost, a 23% contribution margin. Within it, the authorised base was ₹8.2 crore with ₹7.2 crore cost. Proposed variations added ₹1.8 crore revenue and ₹50 lakh estimated cost. Without that proposed scope, contribution was ₹1 crore on ₹8.2 crore revenue, about 12.2%. The two calculations described different commercial cases. My presentation had allowed the more attractive one to become the headline without making its unresolved premise sufficiently visible.
The upside case deserves a place, not an assumed status
It would be easy to respond by excluding every uncertain opportunity from a management discussion. That would also be a mistake. Commercial teams need to explain what they are negotiating, why it might be valuable and what resources would be required if it proceeds. A board that sees only the most narrowly authorised work may miss an important choice. The problem is not the existence of an upside scenario. It is the loss of its status when the scenario becomes the number on which someone else is expected to rely.
The contract sponsor in our case believed the additional scope was likely. Operating colleagues wanted to secure resources early so that the workshop would not be unprepared. Those were legitimate considerations. They did not establish that the customer had agreed to the variation. I should have made the dependency explicit and shown what remained worthwhile on the base scope alone. Instead, the combined margin encouraged a reader to treat the improvement as though it were already part of the commercial commitment. The presentation borrowed certainty from the authorised work and extended it to a proposal.
A useful discussion asks what management is being asked to do now. It may be preparing a quotation, reserving a limited option, committing materials or authorising the full programme. Each decision has a different exposure if the variation does not arrive. The finance account should follow that exposure. A possible future contribution can be relevant to an option decision without supporting an irreversible commitment of the same scale. This is not a universal formula for conservatism. It is a requirement to connect the stated choice to the actual commercial position.
The base case must remain intelligible on its own
When we returned to the proposal, we showed the authorised base and the proposed variation separately. The roughly 12.2% contribution on the base was not a punishment applied to the commercial team. It was the economics of the work on which the company had an agreed basis to proceed. Management deferred the additional resource commitment while the commercial options were reviewed. That gave up speed and made the immediate account less attractive, but it allowed the decision to be discussed without an unresolved conversation silently carrying the margin.
The base case also needs a credible cost boundary. Removing proposed revenue while retaining every cost associated with it can be as misleading as assuming the revenue will arrive. In our example, the ₹50 lakh estimated variation cost was separated with the ₹1.8 crore proposed revenue. The authorised work retained its own ₹7.2 crore cost estimate. That does not mean every real contract will divide so neatly. Shared preparation, capacity commitments and cancellation terms may make the boundary harder to establish. When they do, the difficulty should be explained rather than concealed by a single reassuring percentage.
This management comparison was not an accounting conclusion about recognised revenue or a legal determination of the customer's obligations. Those questions need their own evidence and professional review. The distinction matters because a forecast meeting can otherwise become an accidental substitute for processes it was never designed to perform. Finance can help directors understand the decision while being clear about which questions remain with contract, accounting or technical specialists. A careful boundary strengthens the discussion; it does not make the financial contribution less useful.
There is a people dimension as well. When an assumption has already travelled through a senior presentation, correcting it can feel like challenging the competence of its sponsor. I found it more useful to identify my own responsibility first. I had supported the combined margin and should have described its dependency more clearly. That acknowledgement made it easier to discuss the proposal without requiring someone else to absorb all the discomfort. The aim was to improve the basis of the decision, not create a retrospective contest over who had been optimistic.
Keep the dependency visible after the meeting
Separating the cases once is not enough if the combined number returns in the next dashboard. The company needs a usable record of which scope was authorised, which changes were still proposed and what resource decision management actually made. This is a commercial account rather than a ceremonial disclaimer. If the variation is later agreed, the record can change on that basis. If it is not, the business should still be able to explain why it committed, reserved or deferred resources at the earlier point.
The record should also preserve the limits of the result. Our fictional case does not establish that the customer later accepted the variation or that the deferral delivered a measured saving. It establishes that management revisited the resource decision with the base and proposed work distinguished. That is a narrower outcome, but it is meaningful. A finance leader does not need to invent a successful commercial ending to explain why an earlier presentation was inadequate or how the decision process improved.
I now look for the premise on which the attractive part of a margin depends. The answer may still support proceeding. A company can deliberately accept uncertainty, especially when there is a defined option or a compelling strategic reason. What it should not do is accept the uncertainty unknowingly because a percentage has combined different states of agreement. The CFO's contribution is to make that choice discussable: here is the authorised work, here is the proposal, here is the resource exposure and here is what would need to change before the stronger case becomes the one we can rely on.