The NBFC Operations Execution Gap

The NBFC operations execution gap: A common but misunderstood problem

In most NBFCs, when performance varies across branches, the first diagnosis is straightforward:

• Is the SOP defined?

• Is the policy documented?

• Has communication been done?

And in most cases, the answer is yes.

Yet outcomes still differ.

This gap between what is defined and what actually happens in the field is what we call:

The NBFC operations execution gap

SARTHI NBFC Operations Framework | Playbooks help !

Why strong SOPs are not enough in NBFC operations

Most NBFCs today have invested heavily in process design:

• Detailed SOPs

• Credit and operations policies

• Defined approval hierarchies

• Structured review mechanisms

From a design standpoint, the system looks complete.

However, NBFC SOP vs execution reality tells a different story:

• Collections outcomes vary across branches

• Sourcing quality is inconsistent

• Early warning signals are not uniformly captured

• Identical processes lead to different results

This is not a design failure.

It is a failure of execution consistency.

Where NBFC field execution breaks: The deployment layer

Between SOP and outcome lies a critical layer:

Deployment (field execution)

NBFC field execution is not just about rollout.It is about:

• Whether teams interpret the SOP correctly

• Whether execution is consistent across branches

• Whether processes are repeatable across people

When deployment weakens, the NBFC operations execution gap widens.

Three ways the execution gap shows up in NBFCs

1. SOP interpretation varies across branches

Same SOP → different execution

• One branch follows it strictly

• Another adapts it

• A third shortcuts it

Over time, this creates branch-level variation in NBFC operations.

2. Execution consistency drops below required levels

NBFC field execution typically operates in a grey zone:

• Not fully compliant

• Not completely broken

At 60–70% adherence:

• Outcomes become inconsistent

• Risk signals get delayed

• Productivity becomes unstable

3. Execution depends on individuals, not systems

In many NBFCs:

• Strong managers drive outcomes

• Weak managers struggle

• Transfers disrupt performance

This indicates:

Execution is not system-driven. It is person-driven.

Impact of the NBFC operations execution gap on ROA

When execution varies:

• Credit cost increases (missed early signals)

• Productivity drops (rework, duplication)

• Opex rises (more supervision, more control)

• Growth becomes uneven

Two branches with the same:

• Product

• Geography

• AUM

…can still deliver very different outcomes.

That difference is the NBFC operations execution gap translating into ROA drag.

Why most NBFCs misdiagnose the problem

Typical responses to inconsistent outcomes include:

• Adding more reviews

• Increasing control checks

• Introducing additional trackers

• Expanding supervision layers

These actions assume:

The problem is lack of control.

But in many cases:

The real issue is weak SOP implementation and inconsistent field execution.

So instead of fixing execution, organisations add layers over it.

The missing layer: Playbooks in NBFC operations

Most NBFCs stop at:

SOP → Communication → Monitoring

What is missing is:

Execution playbooks

What is a playbook in NBFC operations?

An SOP defines what should be done

A playbook defines:

How it actually gets done on the ground—every day

A strong NBFC operations playbook includes:

1. Field-level execution sequence

• Step-by-step flow of activities

• Non-negotiable steps

2. Decision clarity

• What the LO or BM can decide

• What must be escalated

• What qualifies as a red flag

3. Operating rhythm

• Daily routines

• Weekly review cadence

• Timing of critical actions

4. Known failure points

• Where SOP implementation typically breaks

• Early indicators of deviation

• Immediate corrective actions

5. Output definition

• What “done correctly” looks like

• How quality is verified

Why playbooks reduce the NBFC operations

execution gap

Without playbooks:

• Each branch interprets SOPs differently

• Execution evolves locally

• Variation increases

With playbooks:

• Execution becomes standardised

• SOP implementation improves

• Branch-level variation reduces

• Outcomes stabilise

SARTHI perspective: Closing the execution gap

SARTHI evaluates NBFC operations on three linked layers:

1. Approach (Design)

• Are SOPs and policies correctly defined?

2. Deployment (Execution)

• Are they consistently followed across branches?

3. Playbook (Standardisation)

• Is execution clearly defined and repeatable?

  
  

The key insight:

Strong design without strong deployment—and without playbooks—creates variability, not performance.

A simple way to identify your execution gap

Instead of asking:

“Do we have SOPs?”

Ask:

• Do branches execute processes the same way?

• Can a new manager deliver similar outcomes quickly?

• Do we know where execution typically breaks?

If not—

You are facing an NBFC operations execution gap.

Closing thought

In NBFC operations, success is often attributed to strategy and product.

But in reality:

Outcomes are driven by execution consistency.

And consistency does not come from SOPs alone.

It comes from deployment discipline and playbooks.

SARTHI is a structured operations framework for NBFCs and MFIs that improves growth, risk, and efficiency outcomes by strengthening field execution through 300+ defined practices.

To know more, visit sarthiworks.com