AI Strategy & Roadmap
What should we prioritise, and what would it take to deliver it?
Decide where to invest in AI and what delivery requires.
Discuss your project
What it is
I help you compare AI opportunities against your business priorities. The result is a roadmap that makes costs, expected value and delivery requirements clear enough to decide what deserves investment.
- You have several ideas and need a reasoned investment decision.
- Process owners can explain the current work, its exceptions and the information involved.
Included work
- Ranked opportunities, with reasons to proceed, defer or stop
- A business case showing costs, expected value and how changes in the assumptions affect the decision
- A map of data and system dependencies, with gaps to resolve
- A delivery roadmap with accountable owners, decision points and success measures
A defined scope
AI assessment
A defined review of where AI may help your organisation and what would have to be true for it to work. We look at the current process before choosing a tool.
- An opportunity map linked to business priorities and current work
- A review of source quality, access, system constraints and human responsibilities
- A prioritised recommendation with assumptions, open questions and a proposed next decision
This is a scoped assessment of your actual situation. Implementation, specialist assurance and any wider audit require a separate agreement.
Discuss this scopeIllustrative possibilities
What this can look like at work
Examples of possible applications, not customer cases or measured results. We check sources, permissions and human review for your situation.
Preparing quotes
Sales and bid teams preparing quotes from approved commercial material.
- A draft uses approved earlier quotes, the current price list and the enquiry; access follows the sales role.
- The account owner checks scope, prices and commitments before sending. Missing commercial terms stay open.
- A pilot compares drafts with representative enquiries, including different languages and unusual requests.
Pre-sorting the inbox
Customer service and operations teams sharing an enquiry mailbox.
- Approved mailbox access lets the workflow propose categories, priority and a responsible department.
- Uncertain items go to a reviewer; deletion, forwarding and replies follow separately agreed permissions.
- The team tests routing on typical and ambiguous messages, including the languages it receives.
Write-up after the meeting
Account and project teams documenting decisions after customer meetings.
- Approved notes become a draft report with decisions, actions and unresolved questions kept separate.
- The meeting owner checks the original notes, assigns actions and approves the recipients before sharing.
- We agree source access, retention and the review needed for translated summaries.
Weekly list of repetitive work
Department heads comparing repeated work across a team.
- I map recurring tasks with the people doing them, using representative work instead of assumed time savings.
- We separate tasks that need judgement from tasks a system could prepare or move between tools.
- The process owner selects what to investigate; estimates remain assumptions until tested.
Recurring client questions
Support teams standardising answers across departments and languages.
- Approved email examples and maintained policies form a draft answer set; customer details are removed where needed.
- Content owners approve the facts, tone and language versions and mark questions that need personal review.
- We record the source owner and update process before using the answers in an assistant.
Knowledge from heads and folders
IT and knowledge owners deciding which departmental information a tool may use.
- I identify the documents, owners, versions and access groups that could feed a knowledge base.
- The plan names outdated, conflicting and missing information that must be resolved before building.
- We agree source citations, access checks and representative questions for acceptance.
Onboarding new people
HR and department managers creating a consistent onboarding route.
- The plan brings approved instructions, role-specific tasks and language requirements into one onboarding route.
- HR and managers decide what a tool may explain and which questions go to a colleague.
- Access, source updates and checks by new starters become requirements for a later build.
The quote process first
Commercial managers and IT choosing where to improve the quote process.
- I map enquiry intake, product and price data, review and the handoff to existing sales systems.
- The plan separates draft preparation from commercial approval and identifies supplier or access limits.
- The first build step has its own scope, costs and acceptance criteria.
Who is allowed to see what
IT, information owners and managers agreeing access across roles or locations.
- I document roles and permissions with the owners before the build, including sensitive source groups.
- You approve who may view, change or share each class of information; the system must enforce those rights.
- The acceptance plan includes checks that one role cannot retrieve another role's restricted information.
Which process first
Leadership comparing competing AI ideas from several departments.
- I compare candidate processes on actual need, source readiness, access, effort and consequences of failure.
- Together we choose a first process with a named owner and an outcome that can be inspected.
- The remaining ideas stay visible, with reasons to defer or stop rather than assumed benefits.
How we work
Stage 01
Understand the work
I examine the selected process with its owner and the people doing it. We use actual work examples and review the tools already available.
Stage 02
Check the requirements
With IT and the source owners, I map approved data, access, system limits, working languages and the decisions that must stay with a person.
Stage 03
Compare the options
I set out what to start, defer or leave alone, including a simpler process or an existing tool. Costs and expected value are tied to explicit assumptions.
Stage 04
Decide the next step
You receive the recommendation, open questions and a proposed delivery scope. Leadership chooses whether to proceed; the assessment does not authorise a build.
Delivery and ownership
We review the agreed work against the acceptance criteria with its responsible owner. I record what is ready, what remains open and who will maintain it. Approval to use or publish the result is a separate decision.
- Documentation, accounts, source material and ownership are agreed before work begins.
- Your IT team can review access, integrations, security requirements and operating arrangements.
- Guidance covers the intended users and languages, review responsibilities and exception handling.
What we agree first
What I need from you
Your business priorities, process owners, examples of current work and an overview of the data and systems involved. I identify missing information before relying on an estimate.
Implementation is a separate decision. Cost and value estimates depend on the assumptions documented in the business case.
I work directly with you from the Netherlands. Remote collaboration is available across Europe, Asia and the Americas. Travel, working languages and time zones are agreed per engagement.
Before we begin
Can the assessment recommend doing nothing?
Yes. If a simpler process change or an existing tool solves the problem, that belongs in the recommendation. Uncertain benefits remain assumptions to test.
Is an AI assessment the same as the online scan?
The online scan is an indicative starting point. An assessment examines your actual processes, sources and constraints with you. Its scope and required access are agreed first.
