Post-Consultant

They Paid for a Plan. They Got a Deck. Here's What Came Next.

12-person team, $4.2M ARR

+31% in 8 months

Revenue growth

67% to 89%

Client retention

12 hrs/week

Founder hours reclaimed

0

Headcount added

The Situation

The founder had invested $45,000 in a strategy engagement. The consulting firm delivered a 47-page deck with 11 strategic recommendations. Eight months later, none of the recommendations had been implemented.

What We Found

Three gaps: no execution architecture, no client experience infrastructure, and no leadership rhythm. The plan assumed capabilities the business didn't have.

The Approach

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.

What Was Built

  • --Execution architecture: 90-day sprints with clear ownership
  • --Client experience infrastructure: onboarding, delivery, and retention systems
  • --Leadership rhythm: weekly ops review, monthly strategic check-in
  • --Learning loop: quarterly retrospective tied to strategy

The Results

  • ++31% revenue in 8 months without adding headcount
  • +Client retention improved from 67% to 89%
  • +Founder reclaimed 12 hours per week previously spent on operational decisions
  • +Team now runs weekly ops without founder in the room

Six Months Later

The founder stopped being the single point of failure. The business can now onboard a new client and run delivery without the founder touching either. That's the compounding effect of operational infrastructure.

Related Frameworks