"Let’s just build it ourselves."
In the world of enterprise IT, those six words are the most expensive sentence ever uttered.
I’ve sat in boardrooms from London to Singapore, listening to brilliant engineers and ambitious CTOs explain why their specific problem: whether it’s a legacy migration, a data lake implementation, or an AI rollout: is so unique that it requires a ground-up, bespoke solution.
Here is the brutal truth: It isn't.
In twenty years of digital transformation consulting, I have seen hundreds of millions of dollars wasted because leaders fell in love with the process of building instead of the outcome of delivering.
Most enterprise problems have already been solved. The patterns exist. The frameworks are battle-tested. The "wheel" you’re trying to reinvent is already sitting in a warehouse, ready to roll. You just need to know which one to pick.
The "Not Invented Here" Trap
Why do we do this? Why does a CIO at a regulated bank think they need a custom-built delivery governance tool when proven delivery governance frameworks already exist?
It usually comes down to three things:
- Engineering Ego: Developers want to build. It’s what they are trained for. Building a bespoke system is "fun." Implementing a standard pattern is "boring."
- The Uniqueness Fallacy: Leaders believe their organization’s complexity is a badge of honor. "Our regulatory environment is different." "Our data is too messy for standard tools."
- The Sunk Cost Fallacy: You’ve already spent $5M on a custom "Innovation Lab," so you feel obligated to let them build something, even if a COTS (Commercial Off-The-Shelf) solution or a standard architectural pattern would do the job for 10% of the cost.
When you reinvent the wheel, you aren't just paying for the build. You are paying for the maintenance, the technical debt, the training, and: most importantly: the opportunity cost of not solving the problems that actually differentiate your business.
The 2024-2025 Reality: AI and the ROI Gap
Look at the current state of Generative AI.
According to recent data, average enterprise AI spend exceeded $1.9M in 2024, yet fewer than 30% of executives are satisfied with the ROI. Why? Because everyone is trying to build their own custom "GPT-killer" or complex internal LLM architecture from scratch.
Meanwhile, the "Reinventors": the companies that systematically outperform their peers: are using the Assembly Pattern. They aren't building models; they are composing modular accelerators. They use RAG (Retrieval-Augmented Generation) as a standard pattern (now used in over 51% of successful deployments) rather than trying to fine-tune massive models for every minor use case.
The difference in outcomes is staggering. Organizations that lean on standard architectures and proven processes see 2.5x higher revenue growth and are 3.3x more likely to scale AI successfully.
Patterns Over Projects
In my work at Dark Consultancy, we don't start with a blank whiteboard. We start with a Delivery Diagnostic.
We look for where the organization is trying to be "clever" where they should be "consistent."
1. Application Modernization
85% of applications can be modernized using a standard 2-3 step iterative approach (rehosting, replatforming, refactoring). Yet, I still see programme rescue consulting engagements where the client tried a full ground-up rewrite of a legacy system: only to have it stall three years in.
2. Cloud Infrastructure
You don't need a custom cloud orchestration layer. You need a landing zone that follows the provider’s Well-Architected Framework. If you are building "bespoke" cloud governance, you aren't being innovative: you’re creating a future outage.
3. Delivery Governance
Does your PMO have 15 different ways to report status? Are you dealing with Watermelon Status reports (green on the outside, red on the inside)? This is a solved problem. Delivery governance is about discipline, not custom software.
How to Tell the Difference: Custom vs. Commodity
If you want to stop the bleed, you have to ruthlessly categorize your IT initiatives:
- Commodity (Buy/Reuse): Payroll, CRM, Cloud Infrastructure, Basic Data Pipelines, Standard AI Chatbots. Use patterns. Do not build.
- Context (Configure): Industry-specific workflows, Regulatory reporting. Use accelerators. Customize only the last 10%.
- Core (Build): The 5% of your technology that actually makes your company different. The proprietary algorithm that prices your insurance, the unique logistics engine that beats the competition. This is where your engineers should be "reinventing."
The Execution-First Mindset
Most enterprise technology execution fails because leadership can't distinguish between innovation and unnecessary labor.
At Dark Consultancy, we are practitioners, not "slide-deck consultants." When we enter a programme rescue engagement, the first thing we do is identify the "wheels" being reinvented. We strip away the bespoke complexity and replace it with proven, low-risk execution roadmaps.
We’ve managed transformation portfolios ranging from $5M to $200M+. The common thread in the successful ones? They didn't try to be unique where they needed to be reliable.
Summary: The Path Forward
Innovation is essential. But building a bespoke version of a solved problem isn't innovation: it's waste.
If your transformation is stalled, or your AI ROI is non-existent, look at your architecture. Are you building a custom engine when you just need to buy the car? Are you rewriting a legacy platform when a standard replatforming pattern would work?
Stop the build. Start the delivery.
FAQ: Common Reinvention Questions
Q: But my industry is highly regulated (Defence/Finance). Can we really use "standard" patterns?
A: Especially in regulated environments, standard patterns are your best friend. Regulators prefer "proven and predictable" over "new and experimental." We’ve implemented these patterns in some of the most complex public sector and financial environments globally.
Q: Won't using standard patterns lead to vendor lock-in?
A: Building a custom, undocumented system creates "talent lock-in": where you are beholden to the three developers who know how it works. Standard patterns are portable and hireable.
Q: How do we start shifting the culture away from "building everything"?
A: Start with a Delivery Diagnostic. It provides an objective, third-party view of where your custom efforts are adding value and where they are just adding weight.
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
SEO Metadata:
- Focus Keyword: enterprise technology execution
- Secondary Keywords: programme rescue consulting, digital transformation consulting, delivery governance, IT platform modernization
- SEO Title: Stop Reinventing the Wheel in Enterprise IT | Dark Consultancy
- Meta Description: CIOs & CTOs often fall into the 'Not Invented Here' trap. Discover why proven patterns outperform custom builds in enterprise technology execution and AI ROI.
- Slug: stop-reinventing-the-wheel-enterprise-it-execution