The EA Tool Trap: Why Midsize Companies Don't Need Ardoq
There is a category of software that is excellent at solving a real problem — and completely wrong for most of the organisations that try to buy it. Enterprise EA tooling sits firmly in that category.
Ardoq, LeanIX, MEGA HOPEX, and their peers are serious platforms built for serious enterprise problems. They handle large, complex IT landscapes at the scale of global banks, automotive manufacturers, and public sector agencies with thousands of applications and hundreds of stakeholders. They invest heavily in metamodel flexibility, enterprise integrations, and governance workflows because their customers need all of that.
The problem is that a midmarket company with 200-5,000 employees and one IT leader reads the same analyst reports, sits through the same vendor demos, and ends up buying tools designed for a different world entirely.
What Enterprise EA Tools Require
Implementing an enterprise EA platform is not a procurement decision — it's a programme. The typical implementation for Ardoq or LeanIX at a genuine enterprise involves three to six months of metamodel design, another three to six months of data migration and integration work, a dedicated EA team to maintain the repository, ongoing training and governance, and a total cost of ownership that runs well into six figures annually before professional services.
This is not a criticism of the platforms. For the organisations they're designed to serve, that investment makes sense. When you have 800 applications, 40 business domains, and an enterprise architecture function with five practitioners, you need a purpose-built repository.
But when a CIO at a 600-person company buys Ardoq with the intention of getting a handle on their 80 applications and aligning IT to business strategy, something breaks. The tool is too flexible — it requires architectural decisions before you can do anything useful. The implementation complexity exceeds the internal capacity to deliver it. After six months and a significant consulting bill, the repository has partial data, no clear ownership, and declining confidence from the business.
This is the trap.
Why the Mismatch Persists
Part of the problem is how the market is structured. EA tooling vendors go to market through analysts, consultants, and procurement channels that naturally reach larger enterprises. The category doesn't have strong representation for the midmarket use case, so midmarket buyers default to the same vendors and reference points.
Another part is aspiration. EA tool selection often happens during a moment of ambition — a new IT leader, a digital transformation initiative, a merger. The desire is to do this properly, and "properly" gets conflated with "enterprise-grade tooling."
The honest reality is that most midmarket organisations need something fundamentally different: faster to implement, simpler to maintain, and optimised for the constraint that there is probably one person responsible for maintaining it.
What Midmarket EA Actually Needs
A midmarket EA practice — assuming one EA or IT leader with part-time attention to the discipline — needs a few specific capabilities. An application inventory with enough structure to classify and score. A capability model connected to strategic priorities. Enough visualisation to communicate to leadership. And something that can be maintained without a specialist team.
The right answer is not a stripped-down enterprise tool. It's a tool designed from the ground up for this context: opinionated enough to get you started without six months of metamodel decisions, simple enough to maintain without a dedicated team, and priced for the budget reality of a midmarket IT function.
These tools exist. The category is less visible than the enterprise platforms, but the alternatives are there for organisations willing to look past the analyst quadrants.
Making the Right Call
If you are in an organisation with fewer than 5,000 employees, one or two people responsible for EA, and an application landscape under 200 systems, the honest recommendation is to start small. You do not need Ardoq to answer the questions that matter: Which of our applications are strategically important? Where are we duplicating capabilities? What is technically unhealthy?
A focused tool — or in some cases, a well-structured spreadsheet with clear process — can answer those questions. The overhead of an enterprise EA platform will consume the time and energy you need to actually do the work.
Choosing the wrong tool is not just a wasted procurement decision. It's an opportunity cost. Every month spent on implementation is a month not spent understanding your landscape and making better decisions.
Start with what you need now. The platform can come later — if you ever actually need it.
Atlas is built for exactly this context: midmarket organisations that need real EA capability without the enterprise overhead.