About
No handovers. One problem at a time.
- Practice
- Business solutions, end to end
- Based
- Chandigarh, India
- Capacity
- A limited number of engagements at a time
- Confidentiality
- Default, NDA on request
You work with the person who does the work, from diagnosis to delivery.
I started it because most businesses I met were not short on effort or ideas. They were stuck behind one structural problem: a leak in retention, a message nobody understood, a process that broke the moment it scaled. And it was invisible from where they were standing.
The way I work is analytical before it is creative. I trace how a business actually moves. Where attention enters, where money is made, where people quietly leave. Then I say what is broken, in plain words, and fix that one thing properly instead of touching six.
The part that makes this practice different is what happens after the diagnosis. Writing is my first skill and always has been, so if the answer is that the words are wrong, I write them. I have also built complete websites end to end, this one included, so if the answer is that the site is wrong, I build it. Most consultants stop at the document. I would rather hand you the finished thing.
Engagements are taken on in limited numbers on purpose, so each one is read properly and answered directly rather than queued behind a pipeline.
Advice and execution, from the same person.
The brief never has to be written twice, because the person who wrote the diagnosis is the one doing the work.
The business, not the symptom
Offer, funnel, delivery, retention and message, traced end to end until the actual blockage has a name.
Copy, posts, scripts, research
Sales pages and ads, thought leadership in your voice, video scripts, and long-form work that needed real research behind it.
The website that carries it
Positioning through to a live site, written and built to order. This one is the sample.
How I think about it
Structure before tactics
More ads on top of a broken funnel just buys the problem more traffic.
One thing, properly
A list of twelve improvements is usually a way of avoiding the hard one. I would rather name it.
Plain language
If a diagnosis needs jargon to sound impressive, it probably is not one.
Finish the fix
Naming the problem is half the job. I would rather write the page or build the site than describe what somebody else should do.