From assigning costs to explaining commitments

Mandate

Make product expenditure, subscription performance and transaction commitments intelligible to decision-makers.

Outcomes

• Corrected the proposed treatment of a ₹3.6 crore product programme
• Separated subscription retention from new-customer value in management reporting
• Added conditional payments and integration expenditure to acquisition scenarios

Decisions in context

The CFO role brings together financial reporting, planning and the explanation of investment choices. I lead twenty-seven colleagues through four managers and work with product and commercial leaders on the assumptions behind their proposals. My own expenditure authority concerns the finance function and the company's approved delegations; it is not a personal claim over every rupee of revenue. The recent cases required me to correct a development schedule, a retention headline and an acquisition paper, each of which had looked complete before its meaning was examined. I present such matters to directors without holding a board seat. I also expect my managers to explain what changed and why, so the organisation does not depend on the CFO noticing every ambiguity. My continuing task is to build that judgement into our ordinary financial work.

Reason for the move

Current appointment; developing finance leadership for a broader product portfolio.

Mandate

Connect management performance measures with underlying records and financial statements.

Outcomes

• Introduced separate reporting for subscription losses, expansion and new business
• Prepared documented reviews of significant expenditure judgements
• Improved the explanation of forecast changes in board papers

Decisions in context

As controller I became responsible for the consistency of an account assembled by several teams. A commercial measure, a product budget and a statutory reporting schedule might each be correct within their own definitions but still contradict one another when presented without explanation. I worked with eighteen colleagues to identify those differences before the board discussion. The growth of subscription products made this especially important because sales, billing and customer continuity did not move together. I learnt to ask which population and period a measure described, then reconcile it with the financial records rather than force every report to use the same number. The role also developed my ability to explain a correction directly. Promotion followed a wider capacity to support investment judgement, not simply an ability to close the accounts on time.

Reason for the move

Promoted to CFO as the company expanded its product and investment agenda.

Mandate

Build repeatable reporting and controls around product and project expenditure.

Outcomes

• Retained activity evidence behind significant product-cost classifications
• Clarified ownership of unresolved month-end judgements
• Distinguished committed customer work from prospective opportunities

Decisions in context

Managing nine colleagues meant turning my own questioning habits into work that others could perform reliably. I reviewed project and product schedules, assigned follow-up responsibility and made sure an unresolved judgement did not vanish merely because the reporting date had arrived. I worked with engineering colleagues to improve the evidence behind their cost records while recognising that they were not responsible for deciding accounting treatment. The appointment also taught me how easily a control can become burdensome if its purpose is unclear. I wanted the team to explain which decision a record supported and remove requests that added no useful evidence. Over time, I took on more planning work and helped prepare the financial material for directors. The controller role followed because I could connect those activities, not because every estimate had become certain.

Reason for the move

Advanced to controller with broader planning and board-reporting responsibility.

Mandate

Explain project effort and expenditure in terms finance and delivery could both verify.

Outcomes

• Reconciled delivery activity with project cost schedules
• Recorded the assumptions behind implementation estimates
• Flagged mixed product and customer work for review by responsible owners

Decisions in context

Software project finance required a different kind of evidence from the engineering-services work I had known. People could move between research, product correction and customer implementation without an obvious physical boundary. I prepared estimates and cost reports, then asked delivery colleagues to explain the activity behind unexpected movements. My authority was analytical; managers approved expenditure and qualified finance owners decided treatment. I learnt to keep the original estimate visible when a project changed, because replacing it with the latest forecast could erase the reason for the difference. I also became more comfortable asking for clarification when a familiar label concealed several kinds of work. That combination of careful records and useful questions prepared me to lead a team whose reports had to remain understandable to people outside finance.

Reason for the move

Promoted to manage the finance team and its reporting routines.

Mandate

Maintain accurate transaction records and identify missing project context.

Outcomes

• Matched supplier records with the relevant project evidence
• Prepared reconciliations for senior review
• Documented questions before assigning ambiguous expenses

Decisions in context

I began with practical accounting tasks: checking invoices, preparing entries and reconciling balances under supervision. The work taught me that an amount could be correct while its assignment to a project was not. I needed to understand enough of the operating activity to ask the right person for evidence, without claiming expertise in engineering itself. Senior colleagues reviewed the conclusions and helped me distinguish a missing document from a genuine judgement about the work. I also learnt to record the answer so another person could follow it later. The move to software finance grew from that interest in the relationship between activity and financial description. It was a change of industry and responsibility, not a claim that an accounts-assistant role had already given me authority over policy or investment decisions.

Reason for the move

Joined a software company to develop project-finance experience.