When automation saves a company more than ₹3 crore in resources, the board does not ask which library you used. They ask: what counted as a resource, who agreed the baseline, and is the saving durable?
Here is a measurement model that holds up in leadership rooms.
Start with the current process cost
Before any script ships, price the status quo:
- Labour capacity — hours per cycle × volume × fully loaded cost (or opportunity cost of skilled time).
- Rework — percent of cases that bounce, plus the cost of each bounce.
- Delay cost — payment holds, late decisions, stockouts, or customer wait — only where you can tie delay to money or capacity.
- Leakage — duplicate spend, missed discounts, avoidable penalties, or uncontrolled access risk if finance owns a number.
Write assumptions in plain language. Invite challenge. A contested baseline is healthier than a silent one.
Separate one-time from recurring
Build and change-management costs are real. Recurring savings are what compound. Report both. Never mix a one-time cleanup windfall into the annual run-rate without saying so.
Track adoption as a gate
If 40% of volume still runs on chat and spreadsheets, your theoretical saving is fiction. Pair rupee estimates with adoption % and open exceptions. That is how you protect a ₹3 Cr+ story from becoming a slide that dies in QBR.
Phrase savings as resources conserved
“Headcount cut” is a political landmine. “Capacity returned to higher-value work,” “rework avoided,” and “leakage closed” are clearer and more honest. Leadership can still convert capacity to rupees; you do not need to oversell job loss.
Review the number on a rhythm
Quarterly, refresh volume, rate, and adoption. If the process changed, update the model. Durable crore outcomes come from governance — not from a one-time calculator in a kickoff deck.