BUSINESS CASE GUIDE
What slow agent ramp actually costs a distribution network, and how IIFL built the internal case for its pilot.
THE GUIDE
Most business cases for a new training system stall because the pitch leans on the vendor's numbers, not the company's own. Here is how one BFSI operator, IIFL Finance, built a case that got signed off internally, with the honest version of what it actually proves.
A new field executive who takes three extra months to reach full productivity is three months of calls, collections or sales that do not happen at the standard the branch needs. Multiply that across a few thousand hires a year and the gap is large enough to justify a system, the question is what evidence makes that case real internally rather than theoretical.
Completion is not readiness. A field executive who finished a module is not the same as one who can handle a real customer objection in the branch's own language. The case has to be built on a readiness signal, not an attendance signal, or it will not survive contact with a skeptical CFO.
IIFL ran its pilot inside WhatsApp, so there was no new app for field executives to install and no IT project to approve first. The business case was built on what the pilot branches actually did, not on a projection, and it was framed to leadership as an early, correlational read rather than a proven causal result:
14,000
field executives live on the system
8
Indian languages covered at launch
+4pp
lead conversion, engaged vs. non-engaged branches
Source: IIFL Finance's own internal analysis. Correlational, not causal, and still early — 100,000+ AI-coached practice actions a month fed it, with roughly 2 in 3 role plays retried until mastered.
We don't, fully, and we say that upfront. IIFL frames the +4pp gap as a correlational read from its own internal analysis, not a controlled study. It is directional evidence worth piloting against, not a guarantee.
Pricing is prepaid and scoped to the pilot first, a few branches and one SOP, so the first number you see is a small one, not a company-wide commitment.
Delivery through WhatsApp, Teams or Slack means there is no separate app license sitting unused; if a pilot does not show daily practice happening, that is the signal to stop before scaling, not after.
L&D owns the content and curation, and branch or regional managers get a readiness view so coaching time goes to the people who need it, rather than sitting with one central team.
This is not a case built on a vendor benchmark. It is one operator's own early numbers, from a pilot that cost little to run and little to stop. That is a weaker-sounding pitch than a case study with a guaranteed ROI, and it is also the more honest one to walk into a CFO conversation with.
NEXT STEP
20 minutes, mapped to your rollout, not a generic demo.