System-driven, not people-dependent — Amit Kumar

Amit Kumar's first finance job paid ₹9,750 a month at HT Media, doing ABC newspaper-circulation audits in the early 2000s. Two-plus decades later he runs the Finance Centre of Excellence at Avataar Ventures, supporting the portfolio's CFOs across India and ASEAN. Across the arc — Bosch, Oracle, GE Healthcare, Schweppes, Attune Technologies, his own fractional-CFO firm LOGIQORE — one operating thesis kept compounding. Companies should not be people-dependent. They should be system-driven.

The phrase sounds technical. In practice it’s a question of resilience. A system-driven company can lose a person without losing the process they ran. A people-dependent one can’t — every departure takes a process, a relationship, a piece of context out the door. Amit’s editorial position is that the CFO is the figure who decides where the routine paths get automated and where human judgment stays. The decision is rarely whether; it’s almost always where and when.

The three-eyes principle#

The clearest single application of system-driven thinking is the principle Amit picked up at GE: the three eyes. The person who does a transaction, the person who passes (reviews) it, and the person who approves it must all be different. Three roles, three sets of eyes. Manual systems try to enforce this with sign-off lists and named reviewers; the discipline breaks the moment someone is in a hurry. System-driven companies enforce the same separation automatically — the routing rules don’t allow the same role to do, pass, and approve.

It’s a control discipline, not a statement about trust. Even a perfectly honest person who processes all three steps creates risk — operational, not just fraud. Amit’s point is that the three-eyes principle is the kind of thing that gets harder to retrofit at scale. Build it into the systems before you need it; the alternative is rebuilding the systems while audit pressure is already on.

I firmly believe that a company should not be people-dependent — rather it should be system-driven.

The visibility trigger#

The mistake Amit names most often when CFOs ask him when should we automate is waiting for a revenue threshold. Revenue is a stage marker, not an operational one. A 50-person services company with simple invoicing may not need automated billing; a 50-person SaaS company with usage-based pricing and currency exposure probably does. The trigger isn’t size. It’s loss of visibility.

When the CFO can no longer give the management team a forward view because the underlying systems can’t produce it, automation is overdue. The defense to the CEO and the board is easier when the case is quantified. Amit’s worked example: $30,000 on SAP Business One can recover $20,000 in year-one cost-savings through system-driven contract negotiation, expense monitoring, and vendor-renewal tracking. Year two it compounds. The case to make isn’t about technology — it’s cost reduction with a visibility bonus. That’s the version that survives a budget review.

Automation is needed at every level. Don't go by the concept of what should be the framework for when to bring in automation — bring it in as early as possible.

Solutions, not vetoes#

The historical position of finance in most companies was the function business teams worked around. “You go to the CFO, he says no, and he doesn’t let you do the work” — Amit’s framing of the legacy stance. The modern CFO can’t operate that way and survive. The transition is from veto to solution.

Saying no is easy and unproductive. The modern CFO’s mandate is to offer a path forward inside the constraints — legal, compliant, financially viable — when the answer can’t be a direct yes. That’s what gets the CFO invited into decisions earlier, which is the only way to actually shape them. The CFO who only says no eventually gets briefed last. The CFO who offers solutions gets briefed first — and becomes what Amit calls the CEO’s eyes and ears: a forward-looking partner who flags where the business might go wrong before it does, rather than the backward-looking accountant who reports it after the fact.

Saying no is very easy. Giving a solution against that problem is what the modern CFO does and should do.

What to listen for#

The full episode runs longer on Amit’s stint at Attune Technologies — the HealthTech SaaS company he joined when there was no chair waiting for him, where he cleaned out a storage room himself with a broom on day one — and on Attune’s founder Arvind, whom he calls “the best person I’ve met in my life” and who died of pancreatic cancer young. The conversation also covers Amit’s view on working with investors (transparency and standardization, treating them as partners rather than auditors) and his IPL run-rate analogy for forecast modeling. His three-word descriptor is Straight Forward. Blunt. Helpful. Listen at /podcast/ep-005-amit-kumar; for the longer conversation across the catalogue, see /topics/modern-finance-function.