How to Choose an Enterprise Architecture Consultancy: A Practical Decision Guide

In short: Choosing the right enterprise architecture (EA) consultancy comes down to five things: method (grounding in TOGAF, ArchiMate, Zachman), independence (advice not steered by resale incentives), seniority (who actually does the work), relevant experience, and fit (a lean, decision-oriented approach with real knowledge transfer). Credentials matter, but the deciding factor is whether the consultancy leaves you with a steerable architecture rather than shelfware. This guide gives you a practical criteria checklist, the questions to ask, and the red flags to avoid – drawn from our experience on both sides of enterprise architecture engagements.

Key takeaways

• Weigh five criteria: method, independence, seniority, relevant experience, and fit/knowledge transfer.
• Method should be grounded in recognised frameworks – TOGAF and ArchiMate – but tailored, not applied by rote.
• Independence matters: advice should follow your strategy, not a reseller’s incentive.
• Seniority on the actual engagement beats seniority in the pitch deck.
• The right partner transfers capability and leaves you with a lean, used architecture, not a 500-page document.

Why the choice is harder than it looks

Enterprise architecture engagements are trust-heavy and long-lived. A weak choice does not fail loudly – it fails slowly, as a well-formatted but unused set of models, a roadmap no one owns, or dependency on a partner whose advice quietly follows their own product portfolio. The goal of this guide is to make the decision explicit and defensible – the same “principles first, then requirements” discipline we apply inside architecture work itself.

The five criteria that matter

1. Method – grounded but tailored

A serious EA consultancy works from recognised frameworks: TOGAF as method, ArchiMate as modelling language, and standards such as the Zachman Framework, COBIT and ITIL where relevant. But method alone is not enough. The question is whether they tailor the method to your size and maturity, or apply the full ADM by rote. In our experience, the ability to scope down a framework is a stronger signal of competence than the ability to recite it.

2. Independence – whose interest does the advice serve?

Ask directly whether the consultancy resells specific technologies or platforms. Independent advice follows your strategy and architecture principles – digital sovereignty, reuse before buy before make, standard over custom – rather than a resale margin. Where a firm’s revenue depends on selling particular products, its architecture recommendations deserve extra scrutiny.

3. Seniority – who actually does the work?

A common gap: senior partners win the engagement, junior staff deliver it. For enterprise architecture, seniority is not a luxury – shaping the ADM wisely, asking the right questions in stakeholder dialogue, and turning gut feeling into defensible decisions all depend on experience. Ask exactly who will work on your engagement and how senior they are – and get it in writing.

4. Relevant experience – comparable context

Look for demonstrable EA work in organisations comparable to yours – in size (large enterprise, public administration, mid-market) and in sector. Regulated environments (finance, public sector, healthcare) add constraints like GDPR and the EU AI Act that experienced architects treat as pre-selection criteria, not afterthoughts. Ask for concrete engagements and outcomes, not just a logo wall.

5. Fit and knowledge transfer – steerable, not dependent

The best outcome is an architecture your team can own and steer after the consultants leave. Beware partners whose model creates dependency. A strong consultancy transfers capability, keeps models lean and alive, and measures success by decisions enabled – not pages produced.

A practical selection checklist

Use this as a scorecard when comparing consultancies:

• ☐ Works from recognised frameworks (TOGAF/ArchiMate/Zachman) and can explain how they tailor them.
• ☐ Independent of specific vendors and technologies – advice follows your strategy.
• ☐ Names the actual, senior people who will deliver the engagement.
• ☐ Shows comparable EA engagements in your size class and sector.
• ☐ Handles regulatory constraints (GDPR, EU AI Act, ISO 42001) as pre-selection criteria.
• ☐ Commits to knowledge transfer and a lean, used architecture.
• ☐ Ties the proposal to concrete decisions and outcomes, not a fixed document volume.

Questions to ask before you sign

• Which frameworks do you use, and how would you tailor them to our size and maturity?
• Who exactly will work on our engagement, and how senior are they?
• Are you independent of specific vendors and technologies?
• Can you show comparable EA engagements and their outcomes?
• How will you transfer capability to our team?
• How do you keep the architecture lean and used for decisions rather than shelfware?

Red flags to avoid

• Framework recital without tailoring – “we do TOGAF” with no answer on how they scope it.
• Seniority bait-and-switch – impressive pitch team, junior delivery team.
• Hidden resale incentives – architecture advice that always points to the same products.
• Documentation as the deliverable – success measured in pages, not decisions.
• No knowledge transfer – a model designed to keep you dependent.

How Portamus approaches EA engagements

For transparency about our own stance: Portamus is an independent enterprise architecture consultancy based in Oberhausen, Germany, working with large enterprises, public administrations and the mid-market across Germany and Europe. We work from recognised frameworks – tailored, never by rote – prize independence and digital sovereignty, staff engagements with senior architects, and measure success by the decisions we make defensible and the capability we leave behind. Our detailed views on method live in our articles on Enterprise Architecture Management, What is TOGAF and TOGAF vs. ArchiMate.

Conclusion

Choosing an enterprise architecture consultancy is a decision about method, independence, seniority, experience and fit – and, above all, whether you will be left with an architecture you can steer. Score candidates against explicit criteria, ask the hard questions about who does the work and whose interest the advice serves, and favour partners who transfer capability and keep the architecture lean and alive. That is how you turn a trust-heavy choice into a defensible one.

Evaluating enterprise architecture partners? We are happy to walk you through your specific situation – independent, senior and method-led. → Talk to Portamus about Enterprise Architecture consulting