Stop Discounting the Result Because You Had Help

I was on an onboarding call with a guy who had just joined Galadon Gold. Twenty years in pricing. Former American Express. Had worked inside some of the biggest companies in Europe - telecoms, payments, FMCG. Deep, legitimate, hard-to-replicate expertise.

Within the first ten minutes, he told me something that I've now heard from probably a hundred different consultants in some version or another. He said: "I want to use a case study where my team and I increased revenue by 10% at my current company - but I had help from data science. I couldn't have done that alone. So I don't think I can use it."

I want to sit with that for a second. Because this one belief - this one quietly held assumption about what "counts" as proof - is the single most expensive mistake a transitioning consultant makes. And it's completely invisible to the person making it.

The Prospect Doesn't Ask How You Staffed It

Here's what actually happens on a sales call. Your prospect is a CFO or a VP or a founder. They're sitting across from you, or on a Zoom, and they're running one calculation in their head: if I hire this person, will my company be better off than it is right now?

That's it. That is the entire mental model. They are not running a secondary calculation about whether you had data scientists supporting you, whether you had a full team behind the analysis, whether the market conditions happened to be favorable that year. They don't ask. It doesn't come up. It is not a variable in their decision.

What they're looking at is: a real company, in a real situation, hired someone who does something similar to what you do, and afterward that company had more money. That's a case study. That's proof. The attribution question - "how much of this was you specifically?" - is something you're asking yourself. Your prospect isn't asking it.

The guy I was coaching had a legitimate, documented, attributable 10% revenue lift at a company most people in his industry have heard of. In the context he was working in - B2B pricing consulting for mid-market and enterprise - that number translates directly to dollars. If you're a €10 million revenue telecom and someone walks in saying they've delivered 10% revenue growth at a comparable company, the math writes itself. The investment required to hire that consultant is a rounding error against the potential upside.

But he was about to throw all of that away because of a question no one was going to ask him.

The Bar for Proof Is Not "I Did It Alone"

I think this comes from years in corporate, where you're taught to be precise about attribution. You're in a performance review and you say "I drove this result" and your manager pushes back: "well, the whole team drove that result." So over time you get trained to hedge, to qualify, to distribute credit broadly.

That's good corporate politics. It is catastrophic consulting sales.

In consulting, you are the product. When someone hires you, they're buying your judgment, your methodology, your ability to see the problem clearly and point toward a solution. The question they're asking is not "did you personally write every line of code and make every decision in isolation?" The question is: "has your involvement in a situation like mine produced a good outcome before?"

If the answer to that question is yes - and for this guy, the answer is very clearly yes - then you have a case study. Full stop.

Think about how he described his work at his current company: he identified customer segments, analyzed willingness to pay across those segments, proposed adjustments to product and pricing, built a long-term forecast with a reporting structure so the company could track execution against the strategy. That is a complete, repeatable methodology. It has a beginning, a middle, and an outcome. The outcome is 10% revenue growth.

The fact that there was a data science team involved in the dynamic pricing component doesn't erase any of that. It means he knows how to work with data scientists. That's a feature, not a disqualifier. Any prospect big enough to afford a serious pricing engagement is also going to have internal technical resources. The ability to direct and leverage those resources is exactly what they're hiring for.

What a Case Study Actually Needs to Do

A case study has one job: it has to make the prospect believe that someone like them hired someone like you and got a result they would want. That's the full requirement list. There are no other items on it.

In a cold email context, my framework from The Cold Email Manifesto puts it this way: the offer gets their attention, the case study sets authority, and the call to action induces them to book a meeting. The case study's specific function is authority. It is answering the implicit question: why should I trust this person with my problem?

A 10% revenue lift at a recognizable company in a relevant industry sets authority. It does that job completely. What it does not need to do - what it was never meant to do - is serve as some kind of legal proof of sole causation. It's not a patent application. It's a trust signal.

This is why I pushed back immediately when he started hedging. We needed to work through the actual story: here's the company, here's the situation before, here's the methodology we applied, here's what changed afterward. When you tell that story, the data science dependency becomes a detail inside a larger narrative about strategic pricing leadership. It doesn't undermine the narrative. It fills it in.

The Warm Network Problem

There's another layer to this that's worth talking about, because it connects directly to the sales situation this guy was already in.

Before he joined, he had sent two LinkedIn messages to people he found through open job postings - companies that were actively hiring for pricing roles - and one of them had already responded and wanted to talk. That's a 50% response rate from a cold approach with zero optimization, zero sequences, zero tooling. That's an extraordinary signal.

And yet he was sitting on a warm network of 20 or 30 people in telecommunications and payments in Switzerland - a tiny market where he knew people at most of the relevant companies - and he hadn't touched any of them yet because he was waiting until he had his case study sorted out.

My advice: don't wait. The case study is already there. What he's actually waiting for is permission to believe it counts. And that's a different problem entirely.

When you're transitioning from employee to consultant, the fastest money you will ever make is inside your existing network. Not from cold email, not from LinkedIn outreach to strangers, not from ads. From people who already know you, who have already seen you work, who have already formed a view about whether you're competent. Those people do not need to be convinced of your expertise. They need an offer. They need a reason to engage you now rather than later. That's a much simpler sales problem than convincing a cold prospect from scratch.

I told him: let's get you clients from your network first. Get the money flowing, refine the case study through real engagements, then scale outbound from a position of strength. That's the sequence. The best lead strategy for someone at his stage isn't volume - it's surgical. A few conversations with the right people who already have context on his work can unlock deal sizes that would take months to generate through cold outreach.

The Pricing Structure That Actually Works for This Kind of Engagement

One thing I genuinely liked about how he was thinking through his offer was the instinct to build in recurring revenue alongside the project fee.

His thinking: charge a significant upfront fee for the core work - the customer segmentation, willingness-to-pay analysis, pricing adjustments, long-term forecast. Then charge a smaller monthly retainer for the reporting and deviation analysis: are you on track with the strategy we set? Why or why not? That's a clean productized structure. You do the heavy strategic lift once, then you stay in the picture as the company executes against it.

What I pushed him to layer on top of that: a win fee. If we can track revenue before the engagement and after, and tie the improvement to the pricing work, take a percentage of the new revenue. Even something like 10% of the documented lift.

This does a few things. First, it aligns your incentives with the client's outcome in a way that is extremely credible in a sales conversation. You're not just saying "trust me, this will work" - you're saying "I'm so confident this will work that I'm putting part of my compensation at risk on the outcome." Second, it changes the math for the client dramatically. The project fee becomes much easier to justify when a chunk of the total cost only gets paid if the result actually materializes.

And here's the compounding effect: once you have two or three of these engagements running with documented outcomes, your case study problem is permanently solved. You now have numbers that you generated yourself, in your own consulting practice, for clients you can reference. The attribution question disappears because it's your name on the engagement and your methodology that drove the result.

Cold Outreach: When to Go Wide, When to Stay Surgical

We also talked about tooling, because he'd been reading up on Lemlist and had some questions about whether to use it or move to something else.

My take: Lemlist is a solid tool, and the founder Guillaume Moubeche has done great work building it. But the architecture of the platform is optimized for a world where you're sending from one or a small number of accounts with heavy personalization on each email. That approach worked well a few years back.

What's changed is the inbox environment. There is a genuine war going on for attention in email. The way to break through now is inbox rotation across multiple sending domains - you're spreading volume across many accounts so no single account looks like it's blasting. Tools like Smartlead and Instantly are built for that model from the ground up. They handle multi-domain rotation natively, which is what you need if you're doing any serious volume.

But - and this is the important part - in his specific situation right now, volume is not the constraint. He's not trying to book 200 meetings. He's trying to get 5 to 10 clients for a high-ticket consulting engagement. For that, the warm network approach I described above is going to generate results much faster than cold email infrastructure.

Cold outreach becomes powerful for him once two things are true: he has a locked-in case study with a real number he can reference, and he's ready to scale beyond his current network into adjacent markets or geographies. At that point, you want infrastructure. You want multiple domains. You want sequences that run while you sleep. If you're building that list yourself, tools like ScraperCity's B2B database or an email finder make it much faster to build targeted prospect lists without spending weeks on manual research. But right now, cold email is a Phase 2 problem. Phase 1 is: close something from the network, get a documented win, stop hedging on the case study you already have.

The Real Cost of Disqualifying Your Own Wins

Let me bring this back to the core thing, because I don't want it to get lost in the tactical detail.

The consultant who keeps disqualifying their own track record keeps starting from zero. Every conversation, every sales call, every proposal - they're fighting for credibility from a cold start because they've decided that their 20 years of legitimate work doesn't count as proof. They'll say things like "I'm still building my case studies" when they have a decade of case studies sitting in their employment history, all of which they've convinced themselves don't apply.

The consultant who understands that assisted wins are still wins does something different. They walk into a sales conversation with a story. The story has a company, a challenge, a methodology, and a result. They tell the story with confidence because they believe it - not because they've puffed it up or exaggerated, but because they've stopped subtracting from it.

That confidence is detectable. Prospects feel it. It's the difference between a pitch that sounds like "I think I can help you" and one that sounds like "I've solved this before, here's what we did, here's what happened, let's talk about what it would look like for your company." One of those closes. The other one generates a lot of very polite emails saying they'll be in touch.

My guy on that call had everything he needed. The expertise, the network, the methodology, the case study. What he didn't have yet was the conviction that it was real enough to use. That's what the call was for. And if you're reading this recognizing yourself in any part of this - the hedging, the waiting, the "I need one more case study before I can really start" - I want you to sit down right now and write out the best result you've contributed to in the last five years. Not the result you produced alone in a vacuum with no support. The result that happened, that was real, that you were part of making happen.

That's your case study. Go use it.

If you want to get into the specifics - the offer structure, how to tell the story on a sales call, how to handle the objection when someone pushes back on attribution - that's exactly what we work through on the sales calls inside Galadon Gold. And if you want to get your outbound infrastructure sorted for when you're ready to go beyond your network, grab the top 5 cold email scripts as a starting point. They're free and they'll give you a foundation to work from.

But first: stop discounting what you've already built. It counts.