F/AS/T Book a walkthrough
Case studies

The work, written up.

One engagement in production, told straight — and six sketches of what a phase delivers across the sectors we work in. Outcomes get printed when they’re measured and the client signs off, not before.

Where it runs today

In production

The client

A listed Indian lender

A national network — zones, regions, areas, branches, and field units below them — with thousands of people between the CEO and the customer. Name shared in conversation with their permission, not on the web.

The problem

Numbers nobody could stand on

Reporting assembled by hand every month. Definitions contested between functions — sourcing, processing, collections each counting differently. Below the regional level, performance was effectively invisible until someone asked for a special cut.

The build

All three letters in one contract

Phase 1: core metrics defined, documented and signed off — portfolio, onboarding and conversion funnels, loan processing, collections — and executive dashboards drillable from the national figure to the last field unit. Phase 2: role-based rollout across the organisation, people and hiring metrics, a review of field tooling. Phase 3: an AI layer over the governed metrics and live business planning.

Where it stands

Live and expanding

In production with leadership today, phased engagement underway. Engineers embedded, definitions holding, and the monthly argument about whose number is right — retired.

Want to be the named case study in your sector? Early engagements get disproportionate attention — that’s the honest trade.

What a phase delivers

Six engagements, sketched

NBFC · collections

The Monday review that stopped arguing

A consultant and a product manager embed with a lending team whose branches each report collections their own way. Definitions get settled in the room and wired into the review itself.

21 daysto settled definitions
14 brancheson one review
Hospital chain · operations

Adoption as the deliverable

A rollout across sites where earlier dashboards died unused. The team sits in the daily huddles and stays until the huddle runs on the system.

11 siteslive on the system
9 weeksto every huddle on it
QSR network · store ops

A store scorecard in one phase

Store-level sales, staffing and stock in one scorecard, built on the base in a single phase — drill-downs to the outlet, an exceptions workflow on top.

240 outletson one scorecard
90 dayskickoff to live
Logistics · field service

An exceptions agent on the rails

Telematics and job data piped onto the platform, and an agent that reads the same governed definitions to flag the routes that need a human.

5 systemspiped onto the platform
6 weeksto a live agent
Lender · board pack

The board pack reads from the layer

Monthly reporting moves from a hand-built deck to scorecards computed from one metric layer — so the pack means the same thing every month.

5 days → 5 hoursto produce the pack
120+ metricsone owner each
Retail network · hierarchy

National to store, one truth

The org chart lives in the platform: every figure drills from national to store with ranked lists at each level, every function on the same definitions.

1,100 storesdrillable from national
6 levelsnational to store

Be the next one written up

A walkthrough is a working session, not a sales call. Bring one metric your teams disagree on — we’ll show you what settling it looks like.