It was a Tuesday morning meeting, about three years into my engagement at Mission Cloud, when the VP of Sales said something that changed the entire project.
We were reviewing performance numbers. Three reps were outpacing the rest of the team by a wide margin, and everyone in the room knew it. The VP pulled up a pipeline report, pointed at the gap between the top performers and the middle of the pack, and said, “If we could get everyone selling like these three, we wouldn't need to hire anyone.”
He meant it as a throwaway observation. I heard it as a diagnosis.
Because by that point, I already knew the slide deck they had asked me to redesign wasn't going to move the needle. The deck was fine. It wasn't great, but it wasn't the reason most of the team was underperforming. The real issue was sitting right there in the data, visible to everyone in the room but framed as a personnel problem instead of a systems problem.
The best sellers had built their own frameworks. Their own ways of reading a deal, handling objections, navigating complex conversations. And none of it was written down. None of it was shared. None of it was accessible to the reps who needed it most.
“The gap wasn't talent. The gap was distribution.”
What Leadership Was Asking For
Mission Cloud had set an aggressive target: 47% year-over-year revenue growth. And the constraint was just as aggressive. No new hires. No expanded headcount. The team they had was the team that needed to deliver.
I had been working with Mission Cloud for years at that point, embedded across multiple projects. The presentation deck redesign was the latest ask. That was the scope. That was the deliverable. And if I had just done that, shipped a cleaner set of slides and moved on, everyone would have been satisfied. The project would have been “complete.”
But every week, as I sat in those meetings with sales and marketing leadership, I kept asking questions that had nothing to do with slides. Who's closing the most? Why? What do they do differently? Where does the process break down for the reps who aren't hitting quota?
The answers pointed in one direction every time. The company's best thinking about how to sell their product lived inside three people's heads. And there was no mechanism to get it out.
The Temptation to Stay in My Lane
Here's the part nobody tells you about consulting. There's a moment in almost every engagement where you see the real problem, and it's bigger than what you were hired to solve. You have a choice. You can stay in scope, deliver what was asked, and avoid the risk of overstepping. Or you can flag what you're seeing, make the case for a different approach, and accept that the client might not want to hear it.
I've taken the safe route before. This time, I didn't.
I brought the pattern I was seeing to the VPs. Not as a pitch. Not as an upsell. Just as an observation: your best performers have built systems that work, and the rest of the team can't access any of it. The deck isn't the bottleneck. The knowledge gap is.
They listened. And then they asked me what I'd do about it.
What We Actually Built
A Career Path That Didn't Exist
The first problem was structural. Mission Cloud's account executives had no promotion path that didn't involve becoming a manager. If you were a great seller who wanted to keep selling, you had nowhere to go. That's a retention risk with your best people and a missed opportunity for the rest.
I proposed a new “Lead” role. A promotion that recognized top performance, kept the best closers on the floor doing what they did best, and gave the rest of the team something concrete to aspire to. Not management. Mastery.
We identified three reps based on historical performance data and promoted them into the role. The process itself sent a signal to the entire department: advancement here is based on measurable results.
A Knowledge Transfer System
The Lead role came with two built-in responsibilities designed to benefit the whole team.
Weekly Office Hours
Each Lead held open sessions where any rep could walk in, bring a deal they were stuck on, and get real-time coaching. This was the mechanism that turned individual expertise into shared knowledge.
Quarterly Presentations
Every three months, each Lead presented to the full department. What was working. What they were learning. What patterns they were seeing. A self-sustaining rhythm of knowledge sharing.
The Deck (Finally)
For two months, I sat in on the office hours and the coaching sessions. I captured everything. The frameworks. The objection-handling techniques. The deal navigation strategies that the top performers had developed through years of trial and error.
In the third month, we took all of that material and built it into the slide deck that had been the original ask.
But it wasn't a standard presentation anymore. It was a modular system of over 100 slides, organized so that any rep could assemble a tailored deck for a specific prospect. Mission Cloud had a complex offering, and different buyers needed to see different combinations of capabilities. The modular structure meant reps could build a custom presentation in minutes instead of starting from scratch every time.
The deck became a container for the team's collective intelligence. Not a static set of slides but a living tool built from what actually worked.
What Changed
The sales department's overall efficiency increased by roughly 30%. Same team. Same headcount. Measurably more output.
The Leads had some of their strongest performance that year. The office hours and quarterly rhythm created a self-sustaining culture of improvement that didn't require management to push it. And the modular deck gave every rep on the team a tool that reflected the best thinking of their highest performers, available on demand.
Mission Cloud got the growth they were looking for. But it didn't come from a better slide deck. It came from building a system that made invisible knowledge visible.
What This Was Really About
I was hired to redesign a presentation. What I delivered was a knowledge transfer system, a career progression framework, and a modular sales enablement tool.
That's what happens when you stop treating the surface request as the whole problem. The ask is almost never the issue. The issue is the system underneath it. And the only way to find it is to keep asking questions after everyone else has stopped.
“The knowledge exists. It's just trapped.”