Outcome-led growth
Stop Managing The Work. Start Reading The Result.
Most founders spend their week inside the work — chasing updates, sitting in reviews, asking why an order slipped. The work is not the problem. Nobody is reading what it produced.
See if this fits your company41
orders last month
Down from 62. Spend up 18% over the same period. That is the whole reason to look.
9.4 days
average follow-up delay
How long a quotation sat before anyone followed up. Not price. Not the market.
Your sales manager
owns that action
One name, one action, one week. Not “improve the sales process”.
Result, action, person. Every week, in that order.
Where this usually starts
You Already Know Something Is Off. You Just Can’t Point At It.
Nobody comes to me saying “my conversion rate is the problem.” They say something closer to this.
The spend keeps going up. The orders don’t.
More is going out every month and the number at the end has not moved with it. Nobody can say which part of the spend is the part that stopped working.
I ask why we lost the order. I get a different answer every time.
Price, timing, the competitor, the customer. Five losses, five explanations, and no way to tell which one is actually true.
It’s not in the review. The review sounds fine.
Everyone reports progress and the month still lands short. The review is measuring effort, and effort was never the thing in question.
The job
Read It From The Top Down.
Every week, the same three questions, in the same order. It is not a dashboard and it is not a report you file. It is a reading.
01
What did the number actually do?
Not what the team felt about the month. Orders, spend, quotations, conversion — what moved, in which direction, by how much.
02
Which action produced it?
A number never moves on its own. Something was done, or not done, and there is a record of it in the ads, the CRM, or the follow-up log.
03
Who owns that action?
One name, not a department. A person who can change what they do next week, and who will be asked about it the week after.
The four places we read
Where demand comes from
What is being spent, on which channel, and what it produced in enquiries — not impressions.
What happens to a lead
How fast it is answered, how often it is chased, and where in the CRM it stops moving.
How the pitch lands
What is being said, which objections come back, and whether the conversation ends on price.
Who is following through
What was committed in the review, and what was actually done by the following week.
Read in that order, the answer is usually specific and usually uncomfortable. That is the point of reading it rather than discussing it.
How it runs
It Runs On A Rhythm, Not On My Availability.
Same five days, every week, whether or not anything dramatic happened. The rhythm is what makes it work — one good audit changes nothing by itself.
Monday
The report lands
Your numbers read and written up. What moved, and against what it is being compared.
Tuesday
We tag what broke
The specific action behind the movement, found in the data rather than asked about in a meeting.
Wednesday
You get it in writing
One prescription: the action, the person who owns it, and what should be different by next Monday.
Thursday
Your manager walks it through
Thirty minutes, with the person who owns the action. Not with you — that is the whole design.
Friday
Nothing
Deliberately empty. The week needs a day where the work gets done rather than reviewed.
Six months of this beats one audit, every time.
In my own words
Ninety Seconds, No Slides.
If you would rather hear it than read it — this is me explaining why reading a business backwards changes what you do about it, and why I stopped running the other way.
What this is not
I Am Not Going To Run Your Business For You.
What I am accountable for
- Reading your data every week and diagnosing it accurately
- Naming the specific action that is costing you, not a category
- Naming who owns it and what has to change
- Checking the following week whether it actually changed
- Telling you plainly when the answer is uncomfortable
What you are accountable for
- Your team doing the thing that was prescribed
- Your manager being on the Thursday call, every Thursday
- Honest reporting of what got done and what did not
- Letting your manager own it while you step back
- Acting on an answer you did not want to hear
What The Consultant Takes Over The Doing, Your Team Stops Owning The Result. Six Months Later Nobody Can Say What Actually Worked.
Honestly
What You Have Tried, And Where It Stops.
I am not going to pretend the alternatives are useless. They are not. They just stop at a particular place, and it is usually the same place.
A digital agency
They can tell you what happened up to the enquiry. What happens after it — the follow-up, the quotation, the close — is invisible to them.
They cannot see what happens after the lead becomes your problem.
A consultant
Good diagnosis, a document, and a set of recommendations. Then the engagement ends and nobody comes back to check.
Nobody checks in week six whether any of it is still happening.
Hiring a senior person
Often the right move eventually. But they report on their own work, and there is no independent read of whether it is working.
You cannot mark your own homework and call it verification.
Doing it yourself
You can absolutely read your own numbers. The question is whether that is the best use of the twenty hours a month it takes.
It pulls you back into the thing you were trying to get out of.
Notice what none of them do: come back in week six, look at the number, and ask whether the prescribed thing actually happened.
And It Does Not Work For Everybody.
You are the sales team.
If you run sales and marketing yourself with nobody between you and the customer, there is nobody for the Thursday call. This needs a manager.
You want to be on every call.
Understandable, but it defeats the model. The point is that your manager runs it and you read the outcome.
You want somebody to do the work.
This is diagnosis and accountability, not execution. If you need hands, you need a different arrangement.
You are looking for a quick answer.
One diagnosis is easy and I will give you one free in the first conversation. What compounds is doing it every week for six months.
Honest expectations
What Actually Changes, And When.
I am not going to put a percentage on this page — anyone who does is guessing. Here is the honest sequence instead.
Month 1
You can finally see it
Mostly plumbing: data connected, the baseline set, and the first few readings. Nothing dramatic changes yet, and it should not.
Months 2–3
The arguing stops
Reviews move from opinion to number. People stop debating whether something happened, because the reading says whether it did.
Months 4–6
The numbers start moving
Not from one big fix. From twenty small corrections that each held, compounding across a quarter.
The real test
You stop attending
The week you realise you have not been on the call for a month and the number still moved. That is the outcome, not the report.
Who is behind this
Twenty-odd years inside manufacturing, trading, IT and services companies, mostly founder-run, mostly across Tamil Nadu, Kerala and Bengaluru.
I used to do this the other way round — get inside the business, run the thing myself, and hand it back working. It does work. It also stops working about a month after I leave, because nothing was ever read independently.
So this is built the opposite way. I do not touch the work. I read what it produced, name the action and the person, and come back the following week to check. It is a smaller job and a far more durable one.
Plain answers
The Questions People Actually Ask.
Two minutes
Does This Fit Your Company?
Five questions — the same ones I would ask on a first call. Answer honestly; a no here saves us both a wasted conversation.