Is AI the right tool for the job?
AI is an extreme solution and should be proportionate to the business value of the problem it is solving. Leaders should resist the urge to crack a nut with a sledgehammer; if a rules-based automation, a process redesign or a better-built dashboard will do the job just as effectively, that is usually a better answer than AI implementation. Environmental concerns and data quality and availability should also be weighed at this stage, before any commitment is made.
Indeed, sustainability concerns belong at the scoping stage rather than as an afterthought. Quantifying an AI footprint is difficult, even with your own GPUs, and AI is established to be environmentally damaging – this is especially true for agentic AI systems. It is important to consider sustainability ambitions, goals and compliance early, because there may be equally effective (or nearly as effective) solutions that are less environmentally taxing. Non-AI solutions can often get you most of the way there without the same sustainability (or even monetary) cost.
What type of AI is best suited to this work?
If AI is the right tool, the next question is what type. The benefits and challenges vary significantly across chat interfaces, retrieval-augmented generation, agentic systems and multi-agent architectures.
Task-level AI is often a waste of potential; one use case's leveraging of AI can frequently enable another, and thinking in terms of capability ecosystems rather than isolated tasks tends to yield better returns. In this way, one implementation (or coordinated implementation) can help address multiple business problems, or a single business problem with multiple contributing factors across different areas of the business.
“The organisations getting real value from AI aren't thinking task by task – they're thinking in capability ecosystems. One well-designed implementation can address several business problems at once, but only if you're willing to step back from the immediate use case and look at the wider operating model.” – Laurent Inard, Partner, Head of Research & Development, Forvis Mazars in France |
Established LLMs (versus proprietary models) are the most common design choice; they will usually be more robust and efficient and will be kept up to date with the right capabilities. They do, however, come with risks and requirements that must be considered, including heightened third party risk management (TPRM) considerations. Borrowed models do not reduce the maturity required for governance and oversight; if anything, they increase it.
What are the right success metrics for this use case?
One of the biggest hurdles for organisations in moving from “capability talk” to “performance talk” is defining the wrong success metrics for implementation. Every use case’s KPIs should be tied back to the strategic problem being solved and demonstrate real business value in their articulation. Quantifiable value like reduced turnaround time, improved exception rates and shortened value generation cycles will always be better than productivity, milestone or vague “efficiency” metrics.
Is this use case operating effectively without AI?
Even if a use case isn’t performing against the relevant success metrics, in most instances, it should be operational without AI. If the process is poorly defined or ineffectual as is, adding AI will only exacerbate those failings, not solve them.
Corporate tax: a use case primed for AI value
Organisations are seeing clear short-term cash tax savings thanks to AI-enhanced processes and analysis, delivering clear ROI on the relevant AI implementations. This is because corporate tax is often ideally suited to AI implementation thanks to its strong operational and governance foundations:
- Tax teams have well established and standardised operating processes
- Data is often well structured and governed thanks to compliance requirements
- Tax functions often involve manual processes and heavy data analysis
The key to successful AI implementation is, as always, the quality and standardisation of data and processes. Decentralised corporate tax can get value from AI too, but centralised operations and data mean a clearer path to AI value.
AI implementations have been particularly successful for data-heavy and repetitive use cases such as:
- Compliance & reporting
- E-invoicing and filing
- Purchase & acquisition data analysis (and post-merger integration)
Governance and data readiness: building the foundations for scale
Maturity alignment also matters: ambitions should be aligned to the organisation's current readiness across data integration, architecture and workforce skills, not to where leadership wishes the organisation were. If ambitions and maturity don’t align in reality, that signals the need for deep transformation prior to implementation.
Establishing a workflow contract
To move from ambition to action, a "workflow contract" should be established for each use case. This contract sets out five key elements:
| Workflow boundary – identifying exactly where the process starts and ends |
| Outcome metric – defining the specific, measurable change expected |
| Decision boundary – explicitly stating what the AI can do autonomously, versus what requires human review |
| Data boundary – specifying which data the system is permitted to use, and what is prohibited |
| Project owner – assigning a specific leader who is accountable for adoption and results |
Data readiness underpins all of this. Leaders must align their ambitions with the reality of their maturity along a practical maturity continuum, or their AI implementations are likely to fail. At best, premature or misaligned implementations will generate little to no value, even if “successfully” implemented.
Security and compliance by design
Security and compliance sit alongside governance and require similar discipline. The state of AI regulation in 2026 is more developed than it was even a year ago, with overlapping regional frameworks now placing concrete obligations on organisations deploying some kinds of AI.
Compliance is a core consideration of AI implementations, but like other forms of governance, it should be applied in a right-size manner. It should be an extension of business strategy and risk management. The same applies to cybersecurity: measures should be risk-based and proportionate to the data, processes, people and systems involved.
Both compliance and security should be embedded into the AI lifecycle from the beginning, during scoping and design, rather than as a final review gate. Repeatable governance approaches help here. Organisations should establish repeatable answers to common foundational questions for new use cases, including a standard data classification approach, standardised logging and retention patterns for audit expectations and, crucially, a clear "kill button" or fallback procedure for when quality drops or models behave inappropriately.
A clear exit strategy is essential. Organisations should ask themselves, how will they know when AI quality has dropped? What is the process for disabling the AI and ensuring continuity of the underlying process? Who has ownership and decision-making authority for this? These are questions that need answers before deployment, not after an incident.
Change management: turning AI adoption into transformation
Generating buy-in at the pilot stage
Successfully moving from pilot to scale, especially where user adoption is required, relies on demonstrable, highly visible impacts. Results that show up in finance dashboards or weekly operations reviews help earn the permission required for broader transformation.
Education is crucial throughout this transition. Employees must understand the benefits, boundaries and expectations around AI. The cybersecurity overlap deserves particular attention; employees should be well educated on the cybersecurity concerns around AI and data privacy, especially where AI chatbots and external tools are involved.
Users and use case owners should also understand the ESG implications of their work. This understanding will help keep usage focused on critical and valuable processes and will encourage them to use lower-impact solutions first where these are available.
Finally, the workforce should understand how new use cases are evaluated and governed, and this process should be highly visible. With repeatable governance in place, workers and leaders can bring forward new use cases for efficient and effective evaluation focused on improving business outcomes rather than chasing shiny objects.
Leadership sets the tone
Organisation leadership must set a strong example, both for AI enthusiasm and for day-to-day usage. The expectation is set from the top, and leadership defines the tone for how people across the organisation view the AI imperative. A leadership team that uses AI tools, talks openly about its capabilities and limitations and rewards thoughtful experimentation will see a very different adoption curve from one that ignores or rebukes AI in their own roles, delegating its use downward.
So, how can leaders in different areas of the business enable real, tangible business value generation through AI?
Define where value should be createdThe main risk isn’t doing too little – it’s doing too much without delivering impact.
|
Ensure value is measured and realisedTreating AI like a traditional IT investment is a mistake. Value is progressive, linked to adoption, and uneven across use cases.
|
Make value scalable and sustainableChasing the latest AI trend without strong foundations will increase fragility rather than value.
|
Pivoting from AI hype to AI value
For organisations who have either delayed AI implementation or seen little value return from their use cases, how can they pivot quickly, establishing the right foundation without losing ground? The good news is that, while true transformation takes time, there are ways to pivot current AI endeavours effectively:
| Take stock – build an inventory of existing AI use cases and prioritise them based on the potential to solve real business problems |
| Assign new success metrics – use those business problems to define new success metrics for existing use cases, effectively moving from “capability talk” to “performance talk” |
| Create exit plans – exit strategies are the easiest part of governance to retrofit, so define them for all use cases, and initiate them for use cases no longer performing in light of their new success metrics |
| Lay foundations alongside existing use cases – hastily implemented use cases should not necessarily dictate governance strategies, but their successes and failures can help inform strategic efforts |
| Build a pipeline – reprioritise AI use cases, both new and existing, into a pipeline – both bottom-up and top-down – based on what will solve real business problems within the organisation. Ensure this pipeline has clear evaluation criteria (assessing things like effort, impact, risk, data availability, technical infrastructure and skills) that can be applied to any new use cases. |
“Ignore the headlines. Look at your organisation and build a central strategy based on delivering real value instead of serving whoever is yelling the loudest. This will enable you to build the business case for new use cases and establish the right foundation for your organisation’s goals, leading to tangible value generation, as well as more resilience and confidence as AI continues to evolve.” |
Documents
This website uses cookies.
Some of these cookies are necessary, while others help us analyse our traffic, serve advertising and deliver customised experiences for you.
For more information on the cookies we use, please refer to our Privacy Policy.
This website cannot function properly without these cookies.
Analytical cookies help us enhance our website by collecting information on its usage.
We use marketing cookies to increase the relevancy of our advertising campaigns.











