From billing support to revenue assurance
A career that moved from testing software to owning payment assurance, and what each step contributed to how I read a number today.
I started as a tester, logging defects in e-wallet, e-commerce and CRM applications. It taught me the one habit that has outlasted every tool I have used since: assume the system is telling you a partial truth until you have reproduced it yourself.
Provisioning and billing activation at Airtel came next. Validating tariff and VAS configurations, and supporting Switch-to-ARBOR reconciliation, is where the abstract idea of revenue became concrete — a configuration flag chosen in one system decides what a customer is charged in another, and traceability between them is the whole game.
Customer lifecycle management moved the question from correctness to behaviour. Segmentation and campaign analysis across IVR, USSD, SMS, WAP and VMS is fundamentally analytics work with money attached, and it built the instinct to ask what a metric will cause someone to do, not just whether it is accurate.
At Dish TV, those threads converged into revenue assurance: reconciliation across primary, secondary and tertiary flows, billing validation, financial controls, MIS and executive reporting — across roughly thirty thousand distributors and twenty-four circles. Post-merger, the same discipline applied to a payment-system migration reduced financial discrepancies by around sixty percent.
The through line is not the domain. It is that every role asked the same question in a different vocabulary: does the record match the reality, and can you prove it? Applied AI is simply the newest vocabulary for that question, and it is the first one that gives back time rather than consuming it.