Call notes from a first conversation. Anonymised, shared with consent.
This call was with the founder of a fast-growing creative and marketing agency, and his background is unusually strong for the seat: finance and strategy training, investment banking, turnaround work, several ventures running in parallel. The core agency is around thirty-five people, revenue has grown consistently on word of mouth alone, and there was no formal sales engine until recently.
He understands numbers, systems and growth. His constraint isn't ambition or demand. It's bandwidth, and more precisely, delegation.
What he thought was wrong
He believed the business had outgrown his ability to run it personally. He wanted to focus on other ventures and hand the agency to someone with skin in the game, so the fix in his head was hiring a CEO on profit share or equity.
He'd already tried a Chief of Staff. Then a second Chief of Staff. Then equity for one of them. And he was still getting pulled back into firefighting, which is where the real problem announces itself.
What I asked
I didn't evaluate candidates or structures. I went at failure points. What decisions still come to you by default? When clients escalate, why do they bypass the team? Which decisions are you unwilling or unable to delegate? Is the Chief of Staff delegating or executing? What happens when priorities collide across clients?
Those questions move the conversation off roles and onto decision flow, which is the thing that actually determines whether a CEO hire survives.
What the answers revealed
The pattern held everywhere. The Chief of Staff was buried in execution rather than coordination. Tasks were delegated downward while prioritisation stayed centralised, so the founder remained the final arbiter every time something conflicted. The team was capable but not forceful under pressure, and client expectation management still routed back to him.
He had help. He did not have replacement judgment, and those are not the same purchase.
On the follow-up call he walked me through what he'd built: outbound sales plans, tool stacks, pricing models, hiring JDs, internal SOPs, client guidelines, proposal systems, a large portfolio, internal governance rituals. By most external standards the business looked well set up.
His frustration was sharper than before. He put it plainly: his challenge isn't strategy, it's execution. He didn't want another framework or another system. He wanted someone who could sit with a thirty-person team, enforce priorities, push work to completion and make judgment calls daily.
What I was actually watching
The content of what he showed me mattered less than the pattern behind it. How often he personally validated that a thing existed. How often execution still routed back through him. How tightly "I've built it" was bound to "it should now run." How central he remained despite the layers, the tools and the documentation.
This wasn't missing infrastructure. It was control and enforcement.
The real problem, refined
Not a Chief of Staff problem, not a hiring problem, and not a shortage of available CEOs. A CEO readiness mismatch.
The business still depended on the founder to decide what matters when everything is urgent, push back on clients, trade off revenue against team load and delivery quality, and absorb the emotional escalation when something goes wrong. Until those decision rights leave his head, no CEO can succeed in that seat. Not because the CEO is weak, but because the system routes authority upward and will keep doing it.
The reframes that mattered
Chief of Staff is not a default path to CEO; if the role is execution-heavy it builds the wrong muscle entirely. Two Chiefs of Staff don't add up to one CEO, they add coordination overhead without adding authority. Systems without enforcement create a false sense of readiness, because having things built is not the same as having them run.
Execution leadership is a temperament problem more than an intelligence one. Plenty of people design excellent systems and then avoid the confrontation required to enforce them. Delegation isn't task assignment; it's transferring judgment under pressure, which is a much scarier thing to hand over.
Founders routinely misdiagnose exhaustion as a strategy gap when the real issue is decision saturation. And the instinct to bring in a partner tends to surface precisely at the execution ceiling, when internal authority can't stretch any further.
How it ended
No dramatic resolution. The question changed, which is usually the point.
Not "I need to find a CEO immediately," but "my system still routes the hardest decisions back to me."
That realisation is worth more than the hire.
What I proposed
Worth saying plainly: he had offered me the CEO role on the call, and I had said no. My own direction was moving elsewhere, and taking a seat I would have left in a year would have cost him more than the vacancy. So I offered two other things instead. Introductions to people who might actually fit, and a proposal for the work that had to happen before any of them could succeed.
The proposal opened on a number rather than a philosophy: move profitability from 34 percent to 50 percent. Everything under it was in service of that, which kept the scope honest.
The margin work came first. A full analysis across every service vertical, looking specifically for the two failure modes agencies always have and rarely name: services priced below what they cost to deliver, and retainers being over-serviced out of habit. Then minimum pricing thresholds on high-effort deliverables, tiered pricing on the services with real business impact, and standardised delivery wherever the work repeated. Rebuilding the process for every client costs margin, and it rarely shows up as a line item.
Sales and go-to-market ran alongside: defined ideal customer profiles, an outbound engine on Sales Navigator with enrichment and cold email infrastructure across multiple warmed domains, cadences assigned to a new sales hire, and pipeline tracking in Sheets to start with rather than a CRM nobody would fill in yet. Plus weekly founder-led LinkedIn content, because in agency sales the founder's credibility is doing a lot of the lead generation already.
Two more pieces. Hiring support for the gaps in operations and sales. And three to five real case studies with before-and-after numbers, since the agency had wins and no artefacts proving them.
I also wrote down what I would not touch. Their task workflows and revenue monitoring already worked. Rebuilding those would have looked like effort and delivered nothing, and rebuilding something that already works is an easy way to spend a client's money badly.
Three months, ₹2,25,000 a month, ₹6,75,000 total, against a fixed 40 hours a month. I broke the hours down in the document itself: two on the weekly call including prep, three on async support, seven on execution, three on hiring and case studies. Fixed fees without a stated hour count tend to drift, and I would rather sort that out before starting than in month two.
What happened after
We spoke again months later, and this is the part I find more instructive than the proposal.
He had built a great deal of it himself. The outbound engine, the audience mapping, a two-hundred-page portfolio, a new website carrying the case studies, and customisable proposal templates. The strategy had landed. He simply hadn't needed anyone to stay and deliver it.
What he wanted by then was the opposite of what he had originally asked for. Not strategic input, which he now had plenty of, but execution capacity. And rather than a retainer he proposed joint projects, pulling in his other companies across branding, product, global sourcing and legal, on a revenue share.
So the original diagnosis held and the original engagement shape was wrong. He never needed a CEO, and he never quite needed a consultant either. He needed hands attached to judgment, and he needed them project by project rather than by the month.
I would rather have found that out than signed the retainer. It has made me slower to assume a monthly engagement is the right shape.