A quiet record is easy to misunderstand in a commercial discussion. No new instruction has arrived, no visible event has created a charge, and the arrangement can appear to require little attention. Yet the employer may change its finance team, a qualified adviser may need the basis of an earlier entry, or an authorised enquiry may require someone to reconstruct why the record looks as it does. The company selling administration cannot assume that the expectation of usefulness has paused merely because the transaction counter has stopped moving.
The absence of an event is not the absence of a service
At Tezmavi, I had allowed transaction-led pricing to carry too much of that expectation. It was easy to explain and familiar to customers. A visible piece of activity generated a visible charge. The difficulty was what happened between those events. Our service colleagues still needed to preserve an understandable record and respond within the agreed scope, but the commercial story depended on future activity paying for work already required. The contradiction became clearer as some arrangements matured and remained quiet for longer.
It would be convenient to say that operations understood this and sales did not. That would leave my own decision out of the account. I had accepted the familiar price structure because it made the offer easier to sell and compare. I had not required us to explain sufficiently how the continuing service would be funded under a quieter pattern of activity. When colleagues later raised the problem, they were not introducing a new expectation. They were describing a consequence of a proposition I had allowed the company to make.
In 2022 we spent ₹18 lakh examining the work around those arrangements. The study was not a search for an impressive number of invisible tasks to put on an invoice. I wanted to distinguish the service a customer had reason to expect from work we had created through our own inefficiency. Those are different commercial arguments. A company should not charge more simply because its internal arrangements are awkward. It should be able to explain the useful continuing work, the resources needed to perform it and the choices available if the customer wants a different scope.
Benefit administration also requires care about whose responsibility is being discussed. Tezmavi does not hold benefit funds, determine entitlements, value obligations or authorise payments. Our service concerns records and supporting administration for authorised owners. A fee for that work cannot become a suggestion that we have taken over the employer's or trustee's decisions. The commercial description should make the boundary easier to understand, especially when a long relationship has encouraged people to treat the administrator as the answer to every question.
A fee must describe work rather than hide a margin
We developed a base-service offer with activity described separately. Commercial colleagues worried that customers would interpret the base fee as payment for nothing happening. Their concern deserved a better answer than an instruction to sell harder. If we could not describe what remained useful during a quiet period, the price would sound like an unexplained surcharge. The operating and commercial teams therefore had to work on the proposition together, including what was excluded and which additional work required a separate agreement.
I did not want the discussion reduced to whether the customer understood our costs. Customers do not exist to maintain our preferred operating model. They can decide that a service is not worth its price, or that a different arrangement better suits their needs. Our task was to make the offer intelligible enough for that decision. We also had to be willing to accept a refusal. A supposedly transparent price is less meaningful if the supplier then treats every rejection as evidence that the buyer has failed to appreciate the business.
The distinction between cost and value mattered inside the company as well. We could identify a real expense without proving that every customer valued the associated service equally. Some arrangements required more frequent help; others had capable internal teams and a narrower need. That did not justify pretending the base work was absent. It did mean that the offer needed an explicit scope rather than a single claim that all quiet records created the same burden or deserved the same commercial treatment.
We took the revised structure to ten renewals. Six accepted and four declined. Those are the outcomes of that group, not a market study or proof of an optimal price. I resisted an account that led only with the six acceptances. The four refusals were part of the enterprise choice. We were changing the way the company expected to fund its continuing obligations, and that change reduced the set of customers prepared to buy on the terms offered. The board needed to see that consequence alongside the rationale.
A smaller renewal group is still a consequential choice
The ₹18 lakh study remained a programme cost. It was not a saving, and the six acceptances did not themselves establish additional profit. Revenue, cost to serve and the length of the relationship would all matter to a fuller financial assessment. Nor did the pricing change establish better benefit outcomes for employees. Those outcomes depended on decisions beyond our administration remit. The claim we could make was narrower: we had made the continuing service and its funding more explicit at those renewals and accepted the choices customers made.
For a CEO, the uncomfortable part is that a clearer business model can look smaller before it looks stronger. A familiar offer may attract customers partly because it leaves expensive expectations unspoken. Removing that ambiguity can expose a disagreement that was already present. It is tempting to postpone the conversation until volume makes it less noticeable, but that asks operations to carry the uncertainty in the meantime. It also teaches the customer that the unspoken part of the service is included without limit.
I would now raise the quiet-period question much earlier in a relationship. What continues when activity slows? Which changes in the customer's team require our support? What records must remain understandable, and to whom? What work sits with the employer, trustee or qualified professional rather than the administrator? Those questions can improve the contract discussion without prescribing a universal pricing formula. Different arrangements may justify different answers, but the company should know which answer it is selling.
The lesson is not that every service needs a base fee. It is that the unit on the invoice should not become the only unit through which management understands its responsibility. An enterprise can count transactions accurately while misunderstanding the promise that surrounds them. My job is to make that surrounding promise visible enough to price, resource and challenge. If a customer then chooses a different offer, we should learn from the decision without asking our colleagues to continue supplying an unspecified service in the hope that a later event will eventually pay for it.