Call notes from a first conversation. Anonymised, shared with consent.
This call was with the two co-founders of a growing services business. One runs sales and growth; the other runs delivery. Revenue was climbing, they'd landed a few names bigger than they expected this early, and the operation underneath was held together with freelancers and founder attention.
What they thought was wrong
They called it operational chaos. Miscommunication across the team, delivery stalling whenever a founder stepped away, deadlines slipping, quality moving around, clients losing confidence somewhere between production and handover. Team members hesitating to make a call without checking first.
Their proposed fix was the usual one: better tools, better systems, someone experienced in operations.
What I asked instead
I skipped the tooling entirely and went at consequences. Where exactly does work stall without a founder in the room? How often do deadlines slip, and how often does quality drop with them? Have you actually lost a client over this? What's the split between freelance and full-time? Who owns the client relationship the moment a deal closes, who decides when scope is complete, and how many iterations are allowed before someone says no?
Those questions moved the conversation off "confusion" and onto ownership, which is where it needed to be.
What the answers showed
Roughly 60 to 70 percent of delivery ran through freelancers. They were reliable for output and structurally incapable of ownership, which is not a criticism of any individual freelancer. No single person owned a project end to end. Scope boundaries existed on paper and were almost never enforced, so client delays got absorbed quietly by the team, and founders stepped in to rescue delivery often enough that it had become the process rather than the exception.
The loop was tidy and self-reinforcing. Freelancers had no authority, so full-timers had no enforcement power, so founders absorbed the pressure, so clients picked up on the instability.
The real problem
Not tools. Not skill. Ownership and accountability, which are cheaper to buy and much harder to install.
Freelancers deliver tasks, not outcomes. A team without a strong project owner drifts by default. And when nobody owns the project, the founders become the project managers whether or not anyone planned it that way. As long as delivery depends on a founder being present, scale stays fragile no matter how good the revenue chart looks.
What I told them
They needed one strong full-time project owner: someone who picks up the account the moment sales closes, owns scope and timeline and communication, and is willing to push the team and push back on the client. That role does the sales-to-delivery translation, which is non-negotiable, because someone has to understand what was actually sold and enforce it internally.
Iteration limits have to be explicit and enforced. Unlimited revisions quietly destroy morale, timelines and trust, in that order. Capacity planning has to be real rather than optimistic, because overcommitting a timeline guarantees frustration on both sides of the contract.
And remote teams amplify all of this. Weak ownership in an office produces confusion; weak ownership across a distributed team multiplies it.
How the call ended
No dramatic fix. What changed was the sentence they were using.
Not "we need better people." Instead: "we need clear owners who can enforce decisions."
That's the difference between a business that plateaus and one that scales.
What I proposed
The blueprint I sent afterwards put numbers to what the call had described. Between 70 and 80 percent of projects were running 30 to 40 days late, and they had already lost a large client over a delivery breakdown. Written down, those two facts made the ownership argument better than any framework would have.
The engagement was 60 hours a month, roughly 15 a week, across three phases.
Month one was stabilisation: hiring support for a full-time project manager including the job description and scoring rubric, migrating off Trello and DMs onto something with actual visibility, a tracker mapping every stuck workstream, and founders stepping out of daily task tracking.
Month two was the harder one. Coaching the new PM weekly, workflow templates for onboarding and reviews, delivery SOPs with padded timelines, async standups, and an audit comparing what the team scoped against what it actually delivered.
Month three moved to capacity planning across both the internal team and the freelancer bench, an explicit split of founder versus PM decision rights, and a client communication pack covering onboarding, ETA formats and escalation.
Success was measured on five things, all of which can be checked without asking anyone how they feel: percentage of projects delayed more than seven days, percentage requiring founder escalation, client churn, PM closure and communication ownership, and team NPS.
Pricing was ₹3,75,000 for three months, or ₹6,30,000 for six at ₹1,05,000 a month. I recommended the six. Three months is enough to install a system and not enough to find out whether it survives contact with a bad week.