They Paid for a Plan. They Got a Deck. Here's What Came Next.
The deck was 47 pages. It had 11 strategic recommendations organized into a roadmap with a color-coded priority matrix. The consulting engagement cost $45,000 and ran three months. Eight months later, the deck was on the shelf. Not because the recommendations were wrong. Because the company had no way to move it.
---
title: “They Paid for a Plan. They Got a Deck. Here’s What Came Next.”
slug: case-study-post-consultant
category: Case Study
targetKeyword: case study strategy consultant delivered deck no implementation
status: published
isFeatured: true
publishedAt: 2026-05-29T00:00:00Z
excerpt: “The deck was 47 pages. It had 11 strategic recommendations organized into a roadmap with a color-coded priority matrix. The consulting engagement cost $45,000 and ran three months. Eight months later, the deck was on the shelf. Not because the recommendations were wrong. Because the company had no way to move it.”
---
The deck was 47 pages. It had 11 strategic recommendations, organized into a roadmap with three phases and a color-coded priority matrix. The consulting engagement cost $45,000 and ran three months. The final presentation went well. The founder took notes.
Eight months later, the deck was on the shelf. Not because the recommendations were wrong. They were actually reasonable. Nothing on that deck had moved because the company had no way to move it.
The Situation
The firm was a 12-person professional services company at $4.2M in revenue. Founder-led, which meant the founder was still inside most operational decisions, still the primary relationship holder for key clients, and still the person the team defaulted to when anything went sideways.
The founder had hired the first consulting firm because growth had stalled. Revenue was up slightly year over year, but margins were compressing, client retention was softer than it should have been, and the founder was working more hours than they had when the company was half the size. The consulting engagement was supposed to unlock the next phase of growth.
Instead it produced a document.
By the time the founder reached out for a second engagement, skepticism was high. The reaction was direct: “I have a shelf full of advice. I don’t need more advice. I need someone to actually build something.” That framing was right, and it shaped everything that followed.
The Diagnosis
Three weeks into the engagement, before any solutions were proposed, the diagnosis was complete. There were three specific gaps, and none of them were in the consulting deck.
The first gap was execution architecture. The company had no shared system for how strategic priorities moved from agreement to completion. When something was decided in a leadership conversation, there was no consistent structure for who owned it, what progress looked like, or when it would be reviewed. Good ideas went nowhere because there was no mechanism to move them. The prior consulting deck had produced 11 recommendations and assumed an execution architecture existed. It didn’t.
The second gap was client experience infrastructure. Onboarding was handled differently by every team member, depending on who was assigned to the account. Delivery milestones existed informally, but weren’t tracked or communicated consistently. Follow-up at renewal time was ad hoc. The result was that client experience varied significantly depending on who was running the relationship, and retention reflected that inconsistency. The consulting deck had recommended “improving client experience” as a strategic priority. It did not identify that the infrastructure required to execute that priority was missing.
The third gap was leadership rhythm. There was no regular structured review of how the business was performing. The founder had a sense of things based on their own visibility, but there was no shared moment where the leadership team looked at what was working, what wasn’t, and what needed to change. Decisions accumulated until they became urgent. Problems surfaced late. The company ran reactively because there was no forward-looking rhythm.
These three gaps explained why the consulting deck hadn’t moved. Not because the recommendations were bad. Because the company lacked the infrastructure to implement anything, regardless of how good the recommendations were.
What We Built in 90 Days
The first 90 days were entirely focused on building. Not planning, not strategizing. Building the infrastructure that makes strategic movement possible.
The execution architecture came first. A 90-day sprint structure was established with the leadership team. Three priorities per quarter, each one owned by a specific person with a clear definition of done. A bi-weekly 30-minute check-in where each owner gave a one-sentence status and flagged anything stuck. The goal was not to solve problems in the meeting. The goal was to surface them before they stalled the quarter. Within six weeks, priorities were moving that had been stalled for over a year.
The client experience infrastructure was built in parallel. A structured onboarding sequence with defined steps, responsible parties, and client-facing milestones was documented and implemented. Delivery milestones were standardized across accounts. A retention check-in process was created: a structured conversation at 90 days post-engagement and again at 6 months, with a standard set of questions and a clear owner for following up. These weren’t complicated. They were documented and consistent, which is what the previous informal approach was not.
The leadership rhythm was the third piece. A weekly 30-minute ops review with the three senior team members. Agenda was fixed: prior week’s flags, this week’s priorities, anything that needs founder visibility. Monthly strategic check-in at 90 minutes: what moved in the past 30 days, what didn’t, what the next 30 days need to prioritize. Both meetings ran lean. The goal was not comprehensive status reporting. The goal was early warning and aligned direction.
A quarterly retrospective was added at month three. Ninety minutes. Three questions: what moved, what stalled, and what would we do differently? The answers fed directly into the next quarter’s priorities. The retrospective also surfaced patterns. Some categories of work moved consistently. Others reliably stalled for the same structural reasons. Naming those patterns made it possible to design around them rather than repeating them.
The Outcome at Eight Months
Revenue was up 31% without adding headcount. That outcome deserves unpacking because it wasn’t achieved by discovering a new market or executing a clever pricing move. It was achieved by building the infrastructure that let the existing team perform consistently.
Client retention improved from 67% to 89%. The structured onboarding and delivery milestones eliminated the variability that had been costing renewals. Clients now had a consistent experience regardless of which team member was leading their account. The retention check-in process surfaced problems early enough to resolve them, rather than discovering at renewal that a client had been quietly unhappy for months.
The founder reclaimed 12 hours per week that had previously been spent on operational decisions. That’s not a trivial number. It’s 12 hours per week of strategic capacity that had been sitting inside operational friction. The founder was able to focus on three new client relationships in that reclaimed time, which contributed directly to the revenue growth.
The weekly ops review was running without the founder in the room by month five. That is the specific outcome that matters most for long-term health. When the leadership team can run the operational rhythm without founder involvement, the founder has stopped being a single point of failure. The company can handle the week the founder is traveling, or sick, or focused elsewhere.
What Made the Difference
The consulting deck that preceded this engagement had a reasonable strategy. The recommendation to improve client experience was correct. The recommendation to clarify the firm’s positioning was correct. The recommendations weren’t the problem.
The difference was that someone stayed for 90 days and built the infrastructure the strategy required. The consulting deck told the company where to go. This engagement built the operating system that made going there possible. Those are different products.
It was also an engagement designed around accountability to outcomes, not deliverables. The measurement was not “strategy delivered” or “workshops completed.” It was whether retention improved, whether the founder’s capacity changed, whether the business was moving strategically. That framing kept the engagement focused on what actually mattered rather than on producing a polished artifact.
The prior consulting firm produced a polished artifact. This engagement produced a changed company. Both required competent people. The difference was what they were accountable to.
What This Looks Like Going Forward
The compounding effect of operational infrastructure is the part that surprises founders most.
When a new client is won, the onboarding sequence is ready. The delivery milestones are set. The retention check-in is scheduled. The experience is consistent from day one. The team doesn’t need to reinvent the process for each new account. The founder doesn’t need to oversee the onboarding to make sure it goes well. It goes well because the system runs it.
When a new team member is hired, the same thing happens. They step into a functioning operating model. The decision rights are documented. The accountability rhythm exists. The quarterly priorities are set. They learn the system by operating in it, rather than learning the informal patterns by trial and error. They contribute faster and more effectively because the infrastructure supports them.
The 47-page deck is still on the shelf. The company has simply outgrown the need for it.