Call notes from a first conversation. Anonymised, shared with consent.
A founder called me last month about funnels. The business is growing across several cities, demand is holding, and he wanted systems in place before the next push. The ask sounded routine: fix the funnels, automate parts of the outreach.
Four minutes in, it stopped being about funnels.
On these calls I'm not really listening to the ask. I'm listening to how things get described, where the sentence slows down, and what hasn't been named yet. Four things surfaced almost immediately, and none of them were in the brief.
One: nobody owns an outcome
There were layers of managers, but those managers were also executing. The execution roles were running everything from first touch to close. On paper that looks like hustle. In practice it means you cannot answer the simplest question in the business: who is accountable for what?
When everyone is in everything, accountability dissolves into effort. Effort is visible. Accountability is not, and only one of them can be managed.
Two: the system has no early warning
There's a CRM. Reports go out. But the founder said something in passing that mattered more than anything else on the call: they usually find out something is broken well after it broke.
That one line tells you there's no reporting rhythm, no leading indicator anyone watches, and no agreed point at which something gets escalated. Decisions land after the damage, not before it.
Three: attribution is a guess
Leads arrive from several channels. Nobody could say, with confidence, which of those channels converts. Spend continues anyway, and optimisation runs on instinct dressed up as data.
Four: the margin absorbs the mess
The actual risk sits here. The business runs on a seasonal cycle with a narrow window to hit its numbers. When the window closes short, the fallback is discounting.
Which means every inefficiency in the system eventually gets paid for out of margin. In the accounts it looks like a pricing decision, not an operations one.
Why none of this was in the brief
The stated requirement never moved. Fix the funnel, improve the automation.
This happens more than you'd expect. Founders describe problems in the language of tools, because tools are the part of the business you can point at. CRM, outreach, automation. The problem usually sits one layer under that, where ownership is fuzzy, reporting isn't trusted, and risk was never mapped.
There's a quieter reason too. Naming this properly means redefining roles, tightening accountability, and sometimes discovering that the current team can't carry the next stage. That's a harder conversation than buying software, and some founders aren't ready to have it on a first call.
So the work doesn't start with execution. It starts with agreeing on what the problem actually is, in language the founder can repeat to their team without it landing as an accusation.
The goal was never a working funnel. It's a system that holds when the season gets tight.
Most of what I do sits there: seeing the business clearly, sometimes earlier than it can see itself, then getting that clarity into the system in a form the team will actually adopt.
What I proposed
I sent a two-option proposal a few days later. Rather than a funnel fix, it was built around the four problems above, named in the document so nobody could quietly drop one: the visibility gap, attribution blindness, top-heavy friction, and the seasonal risk.
The first option was a two-month foundation project timed to land before the season, at a fixed fee of ₹4,50,000. Four deliverables: a funnel and tech audit to find the leakage points and set a standard attribution framework, a sales hierarchy design giving the new management layers actual KRAs, a blueprint to replace manual prospecting with automated outreach, and a single-view weekly reporting index so nobody has to assemble a spreadsheet to find out what broke.
The second option ran six months at ₹1,85,000 a month and added oversight during the season itself, because a system nobody enforces in the busy period is a document, not a system.
The piece I cared most about was the contingency. The business had no plan for missing its seasonal target beyond cutting price, which is how inefficiency gets paid for out of margin. So the proposal put a dated trigger in: a mid-July review that either confirms the target is reachable or activates a pre-designed bulk strategy. Same decision either way. The difference is making it six weeks early, deliberately, instead of in the last week of the season under pressure.
They would probably have discounted either way. The proposal was about deciding it on a date rather than in a panic.