Selected work · 2010 — 2013

RBL BankPricing & Operations.

I built pricing, reporting, and risk frameworks while the bank was growing quickly and modernizing how work moved through the institution.

Operating foundationBuilt

Pricing, reporting, and risk frameworks from the ground up.

Why this work matters

RBL Bank was still known as The Ratnakar Bank during my tenure. Its FY2012 annual report shows deposits and gross advances more than doubling year over year. The following report describes a bank centralizing back-office operations, implementing workflow tracking, upgrading its core banking system, and strengthening risk and operating controls.

This was not steady-state operations. The bank was trying to grow quickly while creating the systems and controls needed to grow safely.

What was hard

Growth puts pressure on every informal decision. Pricing that works in a small book becomes inconsistent. Reporting that depends on one person’s spreadsheet becomes too slow. Risk decisions that live in people’s heads become difficult to explain and govern.

Consumer and commercial products also have different economics and risk profiles. The operating system had to make those differences explicit without creating a new decision process for every product.

What I owned

As Head of Pricing and Operations, I connected product economics, reporting, and risk review. The work sat between business ambition and the controls that make growth durable.

I was responsible for turning one-off analysis into repeatable frameworks that leaders and operating teams could use across consumer and commercial products.

What I built

I built pricing, reporting, and risk frameworks from the ground up so teams could make the same decision from the same assumptions. The work created reusable models, clearer review points, and a shared language for evaluating products.

Those frameworks became operating standards across the institution. Long before I led software organizations, I was learning the core platform lesson: scale comes from making an important decision repeatable without hiding the judgment inside it.

What I learned

A platform does not have to begin as software. It begins as a repeatable decision: clear inputs, explicit rules, visible ownership, and feedback when the decision is wrong.

That lesson traveled with me into healthcare analytics, cloud contract systems, builder platforms, and engineering-organization design. The technology changed. The leadership problem did not.

Current chapter

Bringing platform and organization design together at Walmart scale.

Read the Walmart case study