When outbound stops working, most teams rewrite the emails. I diagnose the pipeline first: the offer, then delivery, then everything after. Sometimes the fix has nothing to do with the copy, and I will tell you if it doesn't.
On the call: you show me your numbers, I tell you which stage I would check first and why. Thirty minutes. If I don't think I can help, I will say so on the call.
New subject lines, shorter emails, a different ask. Replies moved a little, or not at all.
More contacts, more inboxes, more sends per day. The numbers got bigger. The reply rate got worse.
New data source, tighter filters, better titles. Probably partly right. It did not explain the drop.
All three assume the problem is where you can see it. It usually isn't.
Think of it like a delivery truck. Before blaming the driver, you check what is being delivered, then the truck itself, then the route. Same here. Each stage gets checked, fixed if it needs fixing, and only then do we move to the next one.
A rewrite cannot fix a delivery problem. That one sentence is most of the method.
Run end to end by me: list building, research, writing, sending, every reply. Each email researched and written for one person. No merge-field templates.
My own sending domain failed silently. Every dashboard said delivered. A placement test showed the emails were going to spam at the two providers that mattered. I found it, fixed it, and now placement gets tested before every batch I send, for anyone. That lesson is baked into how I work, and it cost me two weeks so it doesn't have to cost you a quarter.
So when something breaks, I can open it and find out why. That is most of the job.
Reads a company's site, pulls out what is actually true about them, and drafts outreach grounded in it. It is not allowed to invent customers or results. That rule is in the code.
A short page written for one person, built from their own public information. Used in place of a pitch deck.
Placement testing, domain health checks, and reporting that splits every number properly instead of averaging it into one useless rate.
You might not need me for the whole pipeline. The diagnostic tells you which part, and sometimes the answer is that your copy is fine and something else is broken.
A written answer to which stage is failing and what to fix first. Yours to keep. Act on it with me or without me.
I run the pipeline. Research, writing, sending, replies, and a weekly report that tells you what the numbers mean, not just what they are.
Bigger scopes and team handovers are possible. Those get scoped on a call, not priced on a page.
You show me your numbers: sends, opens, replies, meetings. I tell you which stage I would check first and why. Thirty minutes. If I don't think I can help, I say so on the call instead of finding a way to charge you.
No. Anyone who guarantees a number before seeing your offer, your list and your sending setup is guessing. I will tell you what I think is realistic once I have seen yours.
A written document: which stage is failing, the numbers behind that conclusion, and a ranked list of fixes. Plus a call to go through it. You can act on it without me, and that is a fine outcome.
Then you saved yourself a rewrite. It happens. The point of diagnosing first is that you only fix what is actually broken.
For research and speed, yes. The judgment about who to write to and what to say is mine, and everything factual traces to something I actually read. Nothing goes out unread.
Lahore, Pakistan. I work European and US hours and have run outreach across nine time zones.
I went to medical school at King Edward, then into startups. Diagnosis before treatment is the whole habit, and it is the step most outbound teams skip.
I read every reply. I build my own tooling. I would rather send forty researched emails than four hundred templated ones, because I have measured both.
I currently run outbound for a Swiss AI company.
Thirty minutes. You bring your numbers, I tell you which stage I would check first. If I can't help, I'll say so on the call.