Shahid DezqemtiLeadership review 2026

The journal · Conditional growth

Do not let a conditional acquisition become the base case

A growth percentage can conceal a change in business perimeter and several kinds of assumption. I separate those components so directors can discuss the future that remains if a transaction does not close.

There is an appeal in giving a strategy one headline growth number. It is easy to repeat, looks decisive and appears to offer a common destination. The difficulty begins when the number combines events with very different conditions. An acquisition that has not closed, a pricing assumption and growth in existing activity may all contribute to the total. If the presentation does not preserve those differences, the audience can agree with the headline while each person has a different understanding of what it means.

A Qevzenti planning model in 2023 projected premium of ₹1,500 crore from a ₹1,200 crore base. Its ₹300 crore increase represented twenty-five percent. Inside that increase were ₹180 crore associated with a proposed acquisition, ₹90 crore from pricing and mix assumptions and ₹30 crore of organic expansion. The transaction remained unclosed. The calculation was not the problem. The problem was allowing its combined result to stand in for a clear account of the existing business's planning trajectory.

One percentage can contain several different choices

The acquisition contribution depended on a change in perimeter. It could not be treated as though it had already become part of the business simply because it was included in an annual plan. The pricing and mix component raised different questions about assumptions and the composition of business. The organic expansion component described another mechanism again. A director might support one part, challenge another and want a separate decision on the third. A single percentage makes that discrimination harder unless its components remain prominent.

I do not regard a detailed appendix as an adequate answer to a misleading main proposition. Supporting material is valuable, but it should deepen an account rather than reverse the meaning a reader would reasonably take from the opening page. If the most repeated number depends substantially on an uncompleted transaction, that condition belongs beside the number. The point is not to burden every sentence with every assumption. It is to retain the condition that materially changes the choice.

Our acquisition sponsor preferred a combined ambition, arguing that a single destination would encourage coordinated action. I understood the managerial purpose. Yet coordination built on different interpretations of the same number can fail when teams discover that they were planning different businesses. One team may assume acquired capabilities, another may budget for the existing operation, and a third may interpret the percentage as a requirement to increase volume. Clarity about the mechanism supports coordination more effectively than agreement on an ambiguous total.

I asked finance and business owners to reconstruct the planning account. A ₹42 lakh review supported the work. Excluding the conditional acquisition contribution left a ₹1,320 crore base planning case, an increase of ₹120 crore or ten percent over the ₹1,200 crore base. The conditional combined case remained ₹1,500 crore. Those were alternative planning descriptions with different conditions. They were not two reports of achieved performance, and neither established an accounting revenue figure.

A base case is a planning proposition, not a promise

Removing the acquisition did not make the remaining scenario certain. The ₹90 crore pricing and mix component still depended on assumptions owned and assessed by the relevant specialists. The ₹30 crore organic component also required examination. Calling a case base should identify its role in planning, not confer a stronger evidential status than the underlying work supports. I would be concerned if the correction replaced one overconfident headline with another that simply sounded more conservative.

My responsibilities as CSO do not include setting insurance prices, approving underwriting appetite or certifying actuarial calculations. I can ask whether the assumptions in a strategy paper are clearly attributed, whether their consequences are understood and whether different cases use them consistently. I should also make space for qualified owners to disagree. The quality of a strategy recommendation depends partly on how well it preserves those professional boundaries when an attractive commercial conclusion is under pressure.

There is a communication challenge here. Too many scenarios can make the paper harder to use, and a team can hide a weak recommendation behind a catalogue of possibilities. I still owe the CEO and board a view about which case should guide the next decision and why. The discipline is to distinguish that recommendation from a claim that other outcomes are impossible. A manageable set of materially different cases is more useful than either one unexplained number or an exhaustive menu without judgement.

The scenarios should also use a consistent starting point. If the base period changes between slides, the apparent growth rate can change without any change in the future being proposed. Similarly, a later revision to transaction assumptions should be visible in the case it affects. I want the reader to be able to follow a change through the argument. A strategy paper is not improved when an old headline survives after the conditions that supported it have been replaced.

Show what the condition changes

The most valuable part of separating the acquisition case was not the new ten-percent number. It was the conversation about what the organisation would do if the transaction did not proceed. Which activities remained justified? Which capability assumptions had to be reconsidered? Which preparations could continue without creating commitments that belonged only to the acquired business? Those questions turned a forecast distinction into an actual strategic choice rather than a cosmetic improvement to the presentation.

A conditional case can still be important. Preparing for a possible acquisition may be sensible, and failing to consider it could leave the business poorly equipped if it closes. The distinction is between preparing for a possibility and quietly treating that possibility as an accomplished fact. Preparation should have a scope, a cost and a point at which the organisation decides whether to proceed further. The model should help make that boundary visible rather than allowing expenditure to inherit authority from a projected total.

The figures in this account are fictional. Their purpose is to show the reasoning, not to suggest an investment recommendation or a particular insurer's actual performance. My practical test is whether a director can remove the major condition and still understand the remaining plan. If that requires reconstructing the entire paper, the main account is probably doing too much concealment. A leadership forecast should make the organisation's dependence on a future decision easier to see, even when doing so makes the headline less exciting.