The denominator belongs in the board paper

A service proposal often reaches a board with a price, a volume and a margin. Those three figures appear to describe a complete commercial proposition. In practice, the most consequential part may be a sentence elsewhere in the contract defining the unit that can be billed. An account can exist in an operating system without qualifying for a fee. A document can be received without being accepted as complete. If the financial model uses a broader population than the contract, the apparent margin is partly an interpretation that the customer has never agreed to purchase.

A volume is a definition before it is a number

I learnt this in document processing before I worked in services for financial institutions. Our teams counted work at different stages because they needed different measures. A supervisor wanted to know what had arrived. A client wanted to know what had been completed. The billing team needed the subset that met the agreed acceptance rule. None of those counts was necessarily wrong. The mistake was to use one as though it answered every question. A finance review that only checks multiplication can miss this problem because the arithmetic is perfectly correct for the wrong denominator.

At Mirelva, a proposed account-administration contract used 90,000 records at ₹120 a month. The draft billing terms supported 74,000 of those records. Dormant accounts and records still awaiting migration acceptance remained relevant to some operating work, but did not qualify for the monthly fee. The difference reduced annual revenue from the proposed ₹12.96 crore to ₹10.656 crore at the same rate. I did not need a more elaborate forecasting model to understand the issue. I needed the operating file and the contract definition to be read together before the company committed itself.

This kind of review can be uncomfortable because it arrives after a relationship has developed and a proposal has acquired supporters. Commercial colleagues may hear a question about volume as an attempt to reopen the whole negotiation. I try to make the question precise. Which records qualify, at which date, under which agreed rule? If the answer differs from the model, we need to calculate the consequence and choose how to respond. We may accept a lower contribution, change the price, narrow the service or decline the contract. What we cannot reasonably do is preserve the original margin by leaving the disagreement unexplained.

The cost does not always follow the count

A smaller billable population does not necessarily bring a proportionately smaller cost. The contract may still require supervision, reporting, a minimum staffing pattern and work on accounts that are not currently billable. A client may expect a response to an enquiry about a dormant record even when that record earns no monthly fee. I ask operations to identify which costs move with volume, which move only after a threshold and which remain over the period under review. A simple percentage reduction can create a second error while appearing to correct the first one.

In our proposal, recurring direct costs were planned at ₹11.4 crore. At the lower billable volume and original rate, the contract would fall ₹74.4 lakh short before central overheads. The eventual ₹132 monthly rate produced a planned recurring contribution of ₹32.16 lakh at that volume. A separate mobilisation fee covered transition work, but it did not make the recurring economics more attractive. I kept it outside the recurring contribution. This was a less impressive proposition than the original paper, and that mattered. The company needed to decide whether the smaller contribution justified the relationship and operating commitment it would undertake.

There is also a distinction between spare capacity and avoidable cost. An operating team may be able to absorb a contract within its present staffing for a time. That can support a particular decision, but it should not be turned into an assumption that the service is permanently inexpensive. The review needs to state how long the capacity is available, what other work it displaces and what happens when demand changes. Conversely, allocating a share of a fixed central cost does not prove that the cost would disappear if the contract were declined. The decision needs both the incremental economics and an honest view of the wider business.

I do not expect every bid to contain a perfect account of future exceptions. I expect the material assumptions to be identifiable and the uncertainty to be owned. If a particular type of rework could alter the economics, the proposal should describe how it has been estimated and how the parties will review a material change. This is more useful than adding a broad contingency without explaining what it covers. It also gives the operating manager a way to distinguish ordinary variation from a change that requires a commercial conversation. Without that distinction, an exception can become routine long before anyone adjusts the price.

Preserving the agreement after signature

The financial model should not become a historical document as soon as the contract is signed. The definitions that supported approval need to survive into billing and operating reviews. I want a manager to be able to trace the monthly invoice back to the agreed population and identify the reason for a material difference. That does not require a board to inspect account-level records. It requires a process in which the relevant teams can explain the movement and a director can see whether the approved proposition is still recognisable in the business being delivered.

A useful review separates several possible explanations. The population may have changed within the agreed terms. The service scope may have expanded. Acceptance may be delayed because our work is incomplete. A client may dispute our interpretation of the rule. Each calls for a different response, and none should automatically be described as a collection problem. I ask finance to preserve the explanation alongside the amount so that a recurring issue cannot disappear inside a monthly variance. The aim is to shorten the path from an observed difference to a decision about its cause.

The board's role is to examine whether management has made a coherent commitment, not to negotiate each billing clause. Directors should understand the unit that drives the economics, the costs that remain when volume changes and the process for resolving a material difference. They should also see the opportunity the company gives up when it chooses a particular price or service standard. A contract can be strategically useful at a modest contribution, but that is a decision to be made openly. It is not a reason to retain a larger figure that depends on a definition the customer does not share.

The lesson I carry from this work is that the denominator is part of the proposition, not a technical footnote. It determines what the client is paying for and what the company must continue to do without a corresponding fee. Putting that definition in the decision paper does not remove commercial judgement. It makes the judgement possible. I would rather discuss a smaller margin supported by agreed terms than celebrate a larger one that will be renegotiated, disputed or quietly absorbed by the operating team after the announcement has been made.