Service · Web development

Developing an AI strategy for your organisation.

You know AI is going to change your market — just not yet what, in which order and with which risks. We build an AI strategy that takes into account your data, your people, your regulations and your budget. And we don't walk away after the first presentation: we stay on to build it with you.

Readiness assessmentOpportunity mappingEU AI ActBuild vs buy

An AI strategy is not a list of tools — it is a choice about which problems you tackle first.

Most organisations that come to us have the same story. The board wants "something with AI". One department is already experimenting with ChatGPT, another team has quietly started a Copilot pilot, and the CIO is worried about data leaks. Everyone has an opinion, but nobody has the overview. The question you really want answered is: where can AI deliver measurable value in the coming period, without exposing you to legal or reputational risk?

A good AI strategy gives a well-founded answer to that. Not a slide deck full of buzzwords, but a concrete roadmap that takes your people, your infrastructure and your regulatory context as its starting point. We develop that strategy and, what sets us apart, we then help build the first pilots. Our advice isn't handed over to an implementation partner; we get our hands dirty in the system ourselves. That keeps us honest too: an adviser who never writes code finds it much easier to recommend something that won't work.

An AI strategy differs from a digital transformation programme. Digital transformation covers technology, processes and people broadly; an AI strategy zooms in specifically on where machine learning, language models and agents can add value, and which preconditions are missing in your organisation to make that possible. Many clients run both programmes in parallel or in sequence, particularly when their broader digital maturity is still limited.

Three tracks we run together.

Depending on where you stand, an AI strategy starts with sharper insight, a focused roadmap, or straight away with building the first pilot. We often work through them in this order, but not always.

Track 1 · fixed sprint budget

AI readiness assessment

We map out where your organisation stands today: data maturity, infrastructure, team skills, governance and culture. Not a questionnaire with scores from 1 to 5, but conversations with IT, business owners and management, combined with a short analysis of your actual data and systems. The result: an honest view of what is feasible and what needs to be solved first. Often, data quality, accessibility or organisational ownership prove more important than the choice of model.

Data auditSkills mappingInfrastructure scanGovernance baseline
Track 2 · fixed sprint budget

Opportunity mapping & roadmap

Which processes or products could benefit from AI, and which couldn't? We score opportunities on three axes: potential value (cost savings, revenue growth, customer experience), implementation complexity and risk. That overview gives us a phased roadmap: which pilots to start first for quick wins, which larger transformations to save for later, and which ideas to drop because they promise more risk than return. We also attach a rough first investment estimate so that management can turn the roadmap into budget discussions.

Use-case workshopsValue scoringRisk mappingRoadmap
Track 3 · fixed sprint budget

Pilot implementation

We help build the first concrete application from the roadmap. That could be an AI agent that takes over a specific process, an internal knowledge assistant for your staff, or an extension of existing software with AI functionality. It is not intended as a finished product, but as evidence that the strategy works in your reality. During this phase we sharpen the strategy based on what we learn, because in AI projects theory and practice diverge more often than in classic software implementations.

Proof of conceptLive pilotMeasurement frameworkKnowledge transfer

What you get at the end.

An AI strategy that sits on the board table, with enough detail beneath it to take the first steps the next morning. No 80-page report that nobody opens.

  • Readiness reportAn honest assessment of your data, infrastructure, team and governance, including what needs to be sorted out before AI can deliver real value.
  • Use case portfolio with scoringTen to twenty concrete AI applications scored on value, complexity and risk, so that the choice of which to tackle first isn't made on gut feeling.
  • Phased roadmapA concrete plan spanning several quarters, with dependencies, milestones and go/no-go decision points. Not a Gantt chart fantasy, but a workable plan.
  • Risk register and AI Act categorisationFor each use case, the EU AI Act risk classification (minimal / limited / high / unacceptable), plus GDPR implications and ethical pitfalls.
  • Build-versus-buy adviceFor each use case: build it yourself, buy it (Copilot, ChatGPT Enterprise, Claude Enterprise, Gemini), or take a hybrid approach. With reasoning behind it, not just "we recommend X".
  • Governance blueprintWho decides on new AI projects, which guardrails apply to data and models, how we measure success, and when we pull the plug.
  • Pilot implementation (optional)We help build the first use case from the roadmap, so the advice is tested straight away in your real world rather than gathering dust in a PowerPoint deck.

When an AI strategy is the right choice.

Four signals we often see in organisations that are ready for a strategy engagement. If you recognise one or more, we'd be happy to talk further.

Leadership

"Doing something with AI" is on the agenda

The board expects action, but there is no plan. You want to prevent AI from becoming a collection of scattered experiments without a shared direction. The C-suite is looking for justification for budget allocation.

Shadow AI

Everyone is already piloting, without coordination

Different departments are experimenting with ChatGPT, Copilot or industry-specific AI tools. Nobody has visibility over which data ends up where, which contracts have been signed, or what is actually being delivered.

Compliance

The EU AI Act is coming your way

You want to know in advance which planned AI applications fall into high-risk categories, what documentation you need to keep, and how to organise that in practice, before the regulation catches up with you.

Competition

Competitors make claims you need to be able to position against

Market players claim impressive AI results in pitches and webinars. You want to be able to separate marketing from reality, and decide which claims you can make yourself without damaging your credibility.

Not yet sure about a large project?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.

Explore OneDayBuild →

How a strategy engagement works.

1

Introduction

A conversation in which we understand where your question comes from, who is around the table, and which decision you want to be able to make on the basis of the strategy. No sales pitch. We will also tell you honestly if you are not yet ready for a strategy engagement.

2

Readiness and opportunity mapping

Interviews with IT, business owners and leadership. A brief data audit of a sample of your systems. Workshops to bring use cases to the surface. At the end of this phase: a shared picture of what is feasible and which opportunities look most promising.

3

Roadmap and governance

We build the roadmap with dependencies, risk classification and build-versus-buy decisions for each use case. At the same time we develop the governance structure: who decides, which guardrails apply, which yardstick we use. A closing session with leadership to secure commitment.

4

Pilot and ongoing support

We build the first pilot from the roadmap, or guide your own team through it, whichever suits you. Afterwards we remain available for the next hurdle: new use cases, AI Act documentation, or a revision of the strategy should the landscape shift again.

Why organisations work with us.

Four things we do differently from the average strategy consultancy, and which we make explicit so you know exactly what you are buying.

Advice and build

We also build alongside you

Our background is software engineering, not PowerPoint. A strategy we deliver is workable because we understand the implementation, and because we often build the first pilot ourselves. That keeps our advice honest and grounded.

Vendor-neutral

No preference between Claude, GPT, Gemini or open-source

We have no partner contract that pushes us towards a single AI vendor. For each use case, we make the choice on the merits: reasoning quality, data residency, cost model, or a multi-vendor setup to avoid lock-in.

Realistic

We also say where AI adds nothing

Not every process is improved by AI. Sometimes a good search function is more effective than a chatbot. Sometimes workflow automation without a language model is faster, cheaper and easier to explain. We state this explicitly in the roadmap.

Dutch context

Focused on Dutch regulation and language

The EU AI Act in practice, GDPR implications of American AI vendors, sector regulators (DNB, NZa, AP), and model performance in Dutch. This is built into our engagements as standard, not as an appendix but as a design parameter.

Frequently asked questions.

What decision-makers ask us before an AI strategy engagement begins.

When is an AI strategy worthwhile for our organisation?
An AI strategy is worthwhile once you move beyond isolated experiments. Three signals: leadership wants to make informed decisions about the AI budget, several departments are already piloting without coordination, or you fall under regulation (the EU AI Act, sector regulators) that requires documentation of AI systems. If you are still exploring entirely, you are better off starting with a short readiness scan or a focused workshop than with a full strategy engagement.
How long does an AI strategy engagement take?
A readiness scan often runs over a few sprints. A full strategy, including opportunity mapping, roadmap and governance blueprint, takes several sprints. We work iteratively, so you do not only see something at the end; each phase delivers tangible output you can act on along the way. The timeline depends mainly on how quickly your people are available for interviews and workshops.
Are you consultants or builders?
Both. Our background lies in software development; we have been building AI agents, web applications and integrations for years. As a result, we write strategies that are workable because we know the implementation. The difference from traditional consultancy: after the strategy, we can build the first pilot ourselves, or work closely with your own team. For large-scale enterprise implementations, see our page on enterprise AI implementation; for a specific agent, look at building an AI agent.
How do you handle the EU AI Act and GDPR?
In every strategy we classify use cases according to the risk categories of the EU AI Act (minimal, limited, high, unacceptable). For high-risk systems we map the documentation obligations: technical file, conformity assessment, post-market monitoring. We assess GDPR implications per use case, particularly around automated decision-making, profiling, and data transfers to AI vendors outside the EU. For deeper compliance questions we work with lawyers or refer you to our page on AI Act compliance software.
Which AI vendors do you recommend: Claude, GPT, Gemini, or open-source?
We are vendor-neutral. We have built working solutions on Claude, GPT models, Gemini, and open-source models such as Llama and Mistral. The choice depends on the use case: how critical reasoning quality is, what the data residency requirements are, how much volume will flow through it, and whether a vendor-independent architecture matters. In the strategy we make these choices explicitly per use case, rather than locking in one party in advance.
What if a pilot from the roadmap fails?
Some of your pilots will fail. That's to be expected, and we design for it. Every pilot gets clear success criteria and a go/no-go decision point upfront. If a pilot fails, we document why (technology, data, adoption or business case) and decide whether it's worth trying again or whether the use case should be dropped. A failed pilot only becomes a problem if nothing is learned from it, so the governance structure spells out exactly how that learning happens. Pilots that teach you nothing cost more than pilots that fail.
What does it cost?
The price of a strategy engagement depends on its scope (a single department or the whole organisation), the depth of the readiness assessment, and whether you also want pilot implementation included. There's no fixed price list and no indicative tier pricing, as that would mislead you more than inform you. In an initial conversation we'll outline which option suits you and roughly what that means in terms of investment. We're not more expensive than the large consultancy firms, and unlike them, we also help you build afterwards.
Do you also train our team?
Knowledge transfer is standard in all our engagements. Your people need to be able to carry the strategy forward without you depending on us permanently. For broader AI training for your employees (prompt engineering, responsible use, sector-specific applications), please see our page AI training for businesses. A strategy and well-trained people are two sides of the same coin.

Talk to us about your AI strategy.

A free, no-obligation half-hour introductory call. We listen to where your organisation stands and where the pressure is coming from, and give you direction you can act on straight away, even if we turn out not to be the right partner for the next step. An AI strategy often ties in with broader decisions; we're happy to discuss how it fits with your digital transformation programme.

Edit content