Contents · 5 min read
01 / 05 · The choice
What kind of help does the company need?
In short
The firm comparison starts too late. The CEO first needs to define the result the company is buying: technical delivery or leadership capability.
A global enterprise buying scale should start by naming the result. If it needs a platform built, it should hire a technical provider. If its leaders cannot yet see where AI changes the business, they must build that judgment themselves. That is a different mandate.
System builders can deliver the platform work the company has set out. GRAIL helps leaders decide where AI changes the business and how they should act.
The comparison turns on what must change at the end: the company’s systems or its leaders’ ability to set direction. The honest comparison on GRAIL vs the alternatives starts with that choice.
The CEO can separate the two mandates by defining the outcome.
02 / 05 · The job
Does it need delivery or leadership capability?
In short
A delivery mandate can be specified before work starts and judged against a known result. A capability mandate changes what leaders can see and decide, so they must gain the experience themselves.
Delivery
The company can describe the finished system before the provider starts. A technical team can complete the mandate, and the CEO can judge whether the agreed result works.
Capability
For the global enterprise, ask whether its leaders can say where AI changes the business. If they cannot, the work starts with their own decisions and work. They need to use AI in the work that matters before they can set direction from experience.
The company may need both. The distinction tells the CEO which mandate belongs with which partner.
03 / 05 · The build
Is the outcome already known?
In short
When the result is already specified, implementation is the mandate. GRAIL does not take pure automation work or technical builds without management involvement. The global enterprise should choose the provider responsible for making that result work.
The boundary is practical. A platform provider owns the integration and the performance of the system. GRAIL works with the management team above that layer. It does not build the link or compete with the provider.
Putting GRAIL inside that build would leave the company buying the wrong type of work.
A narrow tooling problem needs less: a specialist or vendor may be enough. That route is also set out on GRAIL vs the alternatives.
Once the build is clear, the next question is who will own the change.
04 / 05 · The owners
Will the CEO and leadership team take part?
In short
GRAIL fits only when the CEO and leadership team will build and own the capability from week one. For the global enterprise, that means real work by its leaders, not a mandate sent down to IT. If the team will not take part, GRAIL is the wrong partner.
A global enterprise may need a large firm for scale. That does not teach its leaders where AI changes their business.
Where GRAIL fits, the team leaves with fluency in its own work. It also leaves with a ranked roadmap and tools it already uses. The AI strategy workshop describes that first step.
In the management-team approach, leaders use AI in their own decisions. From that experience, they rank the opportunities worth acting on and start using working tools. That leaves one final hiring choice.
05 / 05 · The hire
Who should the CEO hire?
In short
The decisive test is whether delegation preserves the result. A technical team can own a known build. The CEO and leadership team must own the judgment about where AI changes the business. GRAIL fits only the second mandate. Scale and narrow tooling point elsewhere.
For the global enterprise, delegation preserves the result when a technical team can complete the mandate alone. When the result is leadership judgment built through experience, sending the work elsewhere defeats the purpose.
Use this in the next buying meeting:
Name the job
The CEO writes one sentence on the result needed. The sentence should call for either a known build or a leadership team able to decide what should change.
Test delegation
The CEO asks whether a technical team alone can complete the mandate. If it can, do not hire GRAIL.
Match the partner
Choose a technical provider for a known build. Choose a large firm when the company is buying scale. Use a specialist or vendor for a narrow tool.
Keep the leadership work close
The CEO brings the management team together when the business case is still unclear. Why GRAIL explains why the work starts there.
For the global enterprise, that route may mean choosing a different firm now. Hire GRAIL only when the result must live in the leadership team’s own judgment. For a result a technical team can deliver alone, hire the provider built to deliver it.
Match the mandate
The next task is to decide whether your mandate is a known technical build or a leadership question that the management team must own. If it is the second, See The Opportunity gives the team hands-on experience with AI in its own work, then turns that experience into a ranked roadmap. That makes the engagement a way to test and shape a leadership-owned mandate before choosing what should be built and who should build it.
Three to four weeks, three workshops with your management team: hands-on use of AI, custom AI agents for each leader, and a ranked roadmap of opportunities. Fixed fee, no access to your live systems.
Questions CEOs ask about this
When should a company not hire GRAIL for AI help?
A leadership capability partner is wrong when you need technical delivery. A global enterprise buying scale should choose a large firm or technical provider. A known build belongs with the provider responsible for making it work. The CEO must decide whether the needed result is a system or leadership judgment.
What if we already know exactly what must be built?
Hire a technical provider. The outcome is implementation, so the firm should be chosen for its ability to build that known thing.
What if our main need is a data platform or systems integration?
That is technical delivery work. GRAIL does not build integrations or compete with your platform provider, so keep that mandate with the provider that does.
What if the leadership team will not participate?
Do not hire GRAIL. Its model depends on the CEO and leadership team building and owning capability in their own work.
What if we want outsourced delivery rather than internal capability?
GRAIL will not fit that need. Its work leaves the leadership team with capability and tools it owns, rather than supplying a delivery team to run the work for it.
Which alternatives fit those situations better?
Choose a large firm when the company is buying global scale. Use a specialist or vendor for a narrow tool. Use a technical provider for a known platform or integration build.
Founder, GRAIL
Johan has spent fifteen years in management consulting and executive leadership, including as Chief Product Officer of a SaaS company. He founded GRAIL to help European leadership teams work out what AI changes at the core of their business. He is the author of The Execution Revolution and the host of the ThinkRoom podcast.
Related reading
Sources
- GRAIL vs the alternatives: when to use a large firm or specialist, and when a vendor or GRAIL fits. (accessed October 8, 2026)
- AI consulting for the Nordics: why leadership-team experience comes before a large IT program. (accessed October 8, 2026)
- The McKinsey alternative, built for the mid-market: the leadership capability and roadmap GRAIL builds, plus the working tools the team uses. (accessed October 8, 2026)
- AI strategy workshop for management teams: what the leadership team leaves with. (accessed October 8, 2026)
- Why GRAIL: GRAIL’s position as neither a platform vendor nor a large firm selling a report. (accessed October 8, 2026)
Next scheduled review: February 17, 2027