"We think you should stop paying us."
The room went quiet. Not the thoughtful, "let’s-digest-this" quiet you get in a productive strategy session. This was the heavy, uncomfortable silence of a boardroom that had just heard something that defied the laws of traditional consulting physics.
I was sitting across from the CIO and the Transformation Director of a global financial services firm. We were three months into a programme rescue engagement for a £200M enterprise transformation that had been in a tailspin for nearly a year before we arrived.
When we walked in, the programme was a classic "Watermelon": bright green on the outside (dashboards), deep red on the inside (actual delivery). Morale was in the basement. The "Junior Tax" from their previous "Big Four" partner was costing them millions in rework.
In 90 days, we had stabilised the governance, re-baselined the roadmap, and filled the "Empty Chairs" with practitioners who actually knew how to ship code, not just build slide decks. The delivery velocity had tripled. The "red" was finally turning "green": for real this time.
And that’s when I told them they didn't need us anymore.
The £200M Red-to-Green Sprint
To understand why I told a high-paying client to fire us, you have to understand the mess we inherited.
Large-scale transformations fail for many reasons, but in my 20 years of experience, it usually boils down to a lack of delivery governance. This client had plenty of reporting, but zero governance. They had 40-page status reports that didn't actually tell the CIO if the platform would launch on time.
We don't do "slide-deck consulting." We use an execution-first mindset. Our first move was a Delivery Diagnostic to find where the oxygen was being cut off. We found that the previous partner was charging a premium for "Senior Partners" who were nowhere to be found, leaving the actual work to juniors who were learning on the client's dime. This is what I call the Junior Tax, and it's a silent killer of enterprise ROI.
Our 90-day stabilization plan was simple but brutal:
- Kill the Watermelon Status: We moved to objective, data-driven milestones. No more "subjective green."
- Execute the Roadmap: We stopped the "planning to plan" phase and started delivering high-impact features every two weeks.
- Internal Capability Transfer: We didn't just do the work; we coached their internal PMO on how to maintain the pace.
By the end of those three months, the ship was righted. The "Death Spiral" had been averted.
The Uncomfortable Conversation: From Partner to "Hostage Taker"
Most consulting firms operate on a "land and expand" model. Once they get their foot in the door, they find more problems to solve, more seats to fill, and more billable hours to stack. They make themselves indispensable by creating a "black box" of knowledge that the client can't access without them.
That’s not a partnership. That’s a hostage situation.
I looked at the CIO and said, "The governance is stable. The roadmap is clear. Your internal team is now capable of running this. If we stay for the next six months of 'business as usual' execution, you’ll be paying a premium for senior leadership that you no longer strictly need for this specific phase. We’ve done what you hired us for. We should ramp down."
The CIO’s reaction wasn't what I expected. He didn't say "thank you." He looked worried. "But what if something breaks? What if the velocity drops? I can't afford a relapse."
This is the fear many leaders have: the fear of the "Empty Chair." They would rather pay for the insurance of a high-cost consultant being in the room than risk the perceived instability of going it alone.
But as a practitioner-led firm, our success is measured by business outcomes, not by the length of our invoice. If I'm not willing to tell a client when to stop paying me, I'm not a partner: I'm just another vendor.
The 4-Week Handover (And the ROI of Integrity)
We didn't just walk out the door. We handed them a transition plan and a 4-week ramp-down. We documented every process, handed over the governance frameworks, and ensured their team felt confident "driving the car" themselves.
We left money on the table. A lot of it. Six months of high-margin billable hours, to be exact.
But here is what happened next:
8 months later, that same CIO called me. They had a new, much larger initiative: a $200M platform modernization across three global regions. It was high-risk, high-complexity, and high-visibility.
He didn't put it out to tender. He didn't call the "Big Four" he’d used for years. He called us.
"Kunal," he said, "I know if I bring you in, you'll tell me the truth. I know you'll fix it, and I know you won't stay a day longer than necessary. That’s the kind of partner I need for this."
Our "lost" revenue from the first engagement became the highest ROI marketing we ever did.
Why "Execution-First" Means Knowing When to Leave
At Dark Consultancy, we believe that the best way to grow a business is to solve problems so effectively that you become obsolete for that specific problem.
When we engage in a Programme Rescue, our goal is always to:
- Stabilize: Stop the bleeding.
- Execute: Deliver the value.
- Enable: Hand over the keys.
In an industry where "over-servicing" is the norm, being the firm that says "you're good now" is a massive differentiator. It builds a level of trust that no marketing campaign or slide deck can ever replicate. It moves the relationship from "transactional" to "foundational."
If you are a CIO or a Transformation Head, ask yourself: Is your current partner focused on your independence or your dependency? Are they telling you what you need to hear, or what keeps the meter running?
Execution-first transformation isn't just about speed; it's about integrity. It’s about being accountable for outcomes, not just hours.
Key Takeaways for Leaders:
- Watch out for "Watermelon Status": If your reports are green but your gut says red, you need a Delivery Diagnostic.
- Beware the "Junior Tax": Ensure you are paying for practitioners, not just "smart people" who are learning on your dime.
- Demand a Handover Plan: From day one, your partner should be showing you how they will eventually leave.
If you’re currently overseeing a programme where delivery failure is not an option: or if you suspect you’re paying for a "hostage situation" rather than a partnership: let’s talk. We’ll tell you if you need us. And more importantly, we’ll tell you when you don’t.
FAQ: Programme Rescue & Delivery Governance
1. What is a Delivery Diagnostic?
A Delivery Diagnostic is a high-impact, short-duration assessment (usually 14 days) designed to identify the root causes of programme stall, governance gaps, and hidden risks. It provides a clear Execution Roadmap to get delivery back on track.
2. How do you avoid "Watermelon Status" in large transformations?
We implement objective delivery governance. This means moving away from subjective RAG (Red-Amber-Green) reporting and towards data-driven milestones, automated reporting, and clear "definition of done" criteria for every phase of the project.
3. What is the "Junior Tax" in consulting?
The Junior Tax occurs when a consultancy bills for senior-level expertise but staffs the project with junior resources who lack the experience to navigate complex enterprise environments. This often leads to rework, delays, and poor strategic decisions.
4. Why is "execution-first" better than traditional consulting?
Traditional consulting often focuses on strategy and theory, leaving the difficult "how" of delivery to the client. Execution-first consulting starts with the delivery outcome in mind, focusing on practical modernization, technical enablement, and measurable results.
5. How do you handle capability transfer during a ramp-down?
We use a "shadow and support" model. During the final phases of an engagement, the client's internal team takes the lead on delivery while we move into a coaching and governance-oversight role, ensuring a seamless transition without a drop in velocity.
About the Author
Kunal Patel : CEO & Founder, Dark Consultancy
Kunal Patel founded Dark Consultancy after two decades leading technology and transformation programmes across the public sector, financial services, defence, and energy industries. He has directly managed programme recovery engagements for government agencies, development finance institutions, and regulated enterprises across the US, Middle East, South Asia, and Southeast Asia ; ranging from $5M platform migrations to $200M+ enterprise transformation portfolios. Kunal is a recognised practitioner in delivery governance for regulated environments and holds PMP and PRINCE2 Practitioner certifications. He leads every new client engagement personally and remains accountable throughout the programme lifecycle. Connect with Kunal on LinkedIn