04 — Case study
Reputation had been built on the founder’s eye, relationships and ability to hold complex briefs. That was the strength. At the next scale it became the constraint: every new project meant more of the same person.
A Mumbai firm in art curation, sourcing and installation, working with residential and commercial clients. The work is high-trust and high-touch. Clients buy judgment as much as they buy objects. For years, that judgment lived almost entirely in one person.
As volume and complexity rose, the founder was still in acquisition, creative calls, vendor coordination, project management and final approvals. The company could not add projects without adding founder hours. Capacity of the firm had become capacity of one calendar.
Hiring more people into an undocumented way of working would only have created more people waiting on the founder.
The company had reached the point where founder involvement was the growth limit. Scaling was not a demand problem. It was a design problem: which decisions actually require the founder’s expertise, and which are being pulled upward out of habit?
Until that split existed, “process” would be theatre. The founder would still be the bottleneck. In a trust business, clients will always want the principal at the table for some moments. The error is treating every moment as one of those. Creative direction and relationship risk are not the same as chasing a vendor, chasing a timeline, or approving a routine install.
We mapped the journey from first conversation through delivery. We separated decisions that needed founder craft from decisions the team could own with clear thresholds. Roles, repeatable workflows, project ownership and approval bands were the levers — not a speech about “empowerment.”
Recurring steps were standardised. Project visibility was improved so status did not live in one inbox. The team got mechanisms to decide without a hallway conversation. We also looked at where repeat and recurring work could sit, so growth was not only a hunt for net-new hero projects.
The founder was not removed from the business. They were reserved for the work only they could do. The rest of the journey — briefing the team, running the project, closing standard decisions under an agreed threshold — had an owner who was not the founder by default.
The firm moved toward a model the team could run, with fewer operational decisions requiring the founder in the room. New work no longer had to scale one-for-one with founder time.
Key outcome: Additional delivery capacity without a proportional increase in founder load.