Cutting a Founder's Approvals From 40 to 11

A Rs.55 Cr manufacturer's founder was signing off 40 or more decisions a week. Eleven weeks of work on who decides what brought that down to 11. This is the real case, with the numbers the business recorded.

How do I cut the approvals that land on me?

A founder delegation framework works by moving authority instead of tasks. The founder writes down the decisions that reach the desk each week, names an owner for each one, and sets the money or risk limit inside which that owner can act without asking. Approvals fall because fewer decisions are allowed to travel upward in the first place.

For six years, every decision above Rs.1L in a Rs.55 Cr manufacturing business went to the founder: pricing, hiring, vendor payments, weekend escalations and the Monday reviews. The founder still ran the company the way it had been run at Rs.8 Cr. This post describes what happened when that pattern finally broke. It's a real engagement, and the numbers below are the ones the business recorded.

The BEFORE State

The company was a mid-market manufacturer with under a hundred people across more than one production site. It had Rs.55 Cr in annual revenue and was growing 28% year on year.

The founder's week looked like this:

  • Monday: 9 vendor payment approvals above Rs.1L
  • Tuesday: 4 L2 hiring approvals
  • Wednesday: 6 pricing exception requests from sales
  • Thursday: 8 supplier onboarding decisions
  • Friday: catching up on the decisions that had queued up

That came to forty-something approvals a week, and sixty in a busy week.

The company wasn't new, and the team wasn't weak. Each L2 manager had 8 to 14 years of experience, and two of them had run functions at larger organisations before they joined. The founder wasn't distrustful or controlling for the sake of it. What the founder lacked was a framework for scaling without founder approval, so every attempt to delegate had failed in the same way: a decision type was handed over, it got escalated back, the founder concluded the team wasn't ready and took it back.

This is the most common version of the founder's delegation trap. A founder who delegates the task without delegating the structure around it gets the decision back within weeks.

What Was Actually Happening

The founder's approvals had built up because of how decisions were structured, and adding capacity wouldn't have changed that. Mapping the business showed four gaps in that structure:

  1. There was no decision rights map. Nobody had written down, in one document, which decision types belonged to which role at which rupee band. The founder had one intuition about it and the team had another, and the two didn't match.
  2. There was no reversal budget. When an L2 manager got a decision wrong, the result was a conversation, a review and, in one case, a demotion. No band had been defined inside which L2 was allowed to be wrong without a penalty, so L2 stopped deciding.
  3. There were no escalation gates. Every decision either went to the founder or stayed stuck, because no L3 triage layer filtered decisions before they reached the founder's desk.
  4. There was no review after the decision. Every decision was approved upfront, which meant each one had to be explained, defended and justified in advance. That made approvals expensive and slow.

The Install

The work began with a Diagnostic Sprint and was followed by a partial install. It took eleven weeks in total, and most of the early weeks went into how decisions were structured.

  • Decision Rights Map. One document assigned every recurring decision type to a specific role at a specific rupee band. Vendor payments below Rs.3L sat with L3, payments between Rs.3L and Rs.15L with L2, and anything above Rs.15L with the founder.
  • Escalation Gates. Three tiers (L3, L2 and the founder) each had defined data inputs. An escalation reached the founder only if it crossed a rupee band, a strategic line or a reversibility threshold.
  • Reversal Budget. Each L2 decision-maker got a defined quarterly rupee band inside which they could be wrong without a penalty. This change had the biggest effect on behaviour, because once L2 knew the cost of a wrong decision was counted and capped, L2 started deciding again.
  • Post-Decision Log. Instead of approving upfront, the founder reviewed a weekly log of the decisions made at L2 and L3. That review turned into a coaching conversation instead of another approval step.

The AFTER State

Eleven weeks later, the numbers looked like this:

  • Founder approvals per week: from 40+ to 11
  • Average L2 decision time: from 9 days to under 48 hours
  • Founder hours freed per week: 14
  • Margin from the founder's redeployed time (supplier renegotiations): Rs.2.8 Cr a year

The founder stopped approving vendor payments below Rs.15L, stopped approving L2 hires and left the pricing exception loop for deals under Rs.15L. The founder's week now had four fixed blocks: supplier strategy on Monday morning, leadership coaching on Tuesday, customer strategy on Wednesday and a review of the decision structure on Friday.

The decisions didn't get worse. A ninety-day review found that 94% of L2 and L3 decisions matched what the founder would have decided. The other 6% were discussed in the weekly coaching conversation, and two of them turned out better than the founder's own call would have been.

The Principle

In founder-led businesses, a decision bottleneck comes from the structure, and changing people's behaviour alone won't clear it. Trust has nothing to travel through until someone writes down who decides what. The delegation trap breaks only when four things are in place at the same time:

  • a written decision rights map
  • defined escalation gates
  • a quantified reversal budget
  • a review loop after the decision

Any one of the four on its own will fail. Most delegation attempts fail because the founder installs one of them, usually the map, and skips the other three.

The Close

A team that keeps sending decisions upward is usually working inside a structure that gives it no permission to decide.

If You Recognise This

Most founders running Rs.10 Cr to Rs.100 Cr businesses have some version of this problem. The approvals look a little different and the rupee limits vary, but the mechanism is the same. If every decision above a rupee threshold still comes to you, and every attempt to delegate keeps coming back, the missing piece is a written map of who decides what.

Book a free 30-minute Fit Call at metmov.com for a structured diagnostic and an honest recommendation.

Pick a time that suits you.

Book a call