Lots of pilots, little use
There are plenty of ideas, but AI isn't used systematically in day-to-day work. After the demo, it fizzles out.
By now, most companies have tried something with AI. A pilot, a trial, an enthusiastic colleague who got started with it. And then? Usually, not much happens. We make AI part of how people work every day—with buy-in, working agreements, training and follow-up that doesn’t stop after the first month.
30 minutes, no obligation. We first determine whether the issue lies in use cases, adoption, governance or process design. No additional AI project if that is not the solution.
| Team | Status | Use cases | Progress | Next step |
|---|---|---|---|---|
| Sales | In use | 8 | 92% | Scale |
| HR | In training | 6 | 65% | Complete training |
| Finance | In training | 7 | 60% | Documenting how we work |
| Service | Stuck | 5 | 25% | Build support |
| Operations | Yet to start | 4 | 10% | Choose use cases |
Five causes. They almost never occur alone.
There are plenty of ideas, but AI isn't used systematically in day-to-day work. After the demo, it fizzles out.
It’s unclear when and how AI may or must be used. As a result, it remains optional and everyone does it differently.
Employees don't know what it means for their work, or fear for their roles. No one says it out loud, but it slows everything down.
No one feels responsible for adoption. It slips to the bottom of the priority list.
Initiatives disappear without measurement, feedback, and adjustment. There’s no point when anyone asks: is this still working?
Not sure which model fits a use case? Use the AI Model Advisor to compare models by task, cost, speed and governance.
Five components. Together, they make the difference between a successful demo and a habit.
We start with the work that’s taking up time now, not with the technology.
Support doesn’t come from an email; it comes from showing people how it’s done.
Governance that works instead of getting in the way.
Practice with your own proposals, emails, and lists.
If you don’t measure it, you don’t know it.
Five steps. The first is the Fresh Perspective — the conversation starts with your own figures instead of assumptions.
Adoption usually stalls because for one party it is a goal and for the other it is a burden. That's why a different answer per role.
Adoption is only successful if it continues to work without anyone monitoring it. You establish seven things for that.
Clear steps, checklists, and quality criteria—so the work doesn’t depend on who happens to be doing it.
AI policies, guidelines and risk management documented and easy to find.
Approved prompts and formats available centrally, instead of in everyone's personal notes.
Reliable data and sources, ready for reuse.
Owner, sponsor, and users: everyone knows what’s expected of them.
Dashboards and reports for management and accountability.
Decisions, lessons learned and changes properly documented.
Five signs. If you don't measure them, you won't know it has fizzled out until someone asks.
Adoption rate
share of employees who use it weekly
Active teams
teams with at least one running application
Working agreements
processes with documented rules
Hour per week
time saved per person, measured rather than estimated
Satisfaction
of the people who work with it every day
Adoption is not separate from the rest. These eight pages cover the components you encounter along the way.
What applies now and what has been postponed, and which risk class you fall into. To the AI Act →
Register, ownership, approvals, and audit trail. To AI governance →
Where does your data go with ChatGPT, Claude or Copilot? To data sovereignty →
Benefits, costs, risks and three scenarios, all substantiated. To the business case →
Decisions, risk overview and governance. To business leaders →
Privacy, security, testing and working agreements. To implementation →
A pilot with a hypothesis, measurement, and a decision at the end. To proof of concept →
Eight tracks, from the basics to building, data and automation. To the workshops →
What works and what doesn’t when you put AI to work on your numbers. To AI in BI →
Documenting, designing checks, and writing code — and where the boundary lies. To data engineering →
Want to find out where the problem is for you first? Take the AI scan — five minutes, and you’ll have a figure per task. You can compare your result with other companies via the benchmark. Or measure with the Completion Index or whether what you started last year is still running.
Background in the blog: what the EU AI Act means for SMEs and seven tasks you can automate with Microsoft Copilot.
Start with the free online Fresh perspective: thirteen components, approximately six minutes. You immediately see where you stand with data and AI, and how you compare to your industry.
Ask your question about AI, the AI ActEuropean law that sets requirements for those who develop or use AI. Determines which risk category your application falls into and what you must document for it., connections or digitalization. The answer comes from the pages of this site, with references to where it is located.
Figures and context: AI use in SMEs, why AI projects fail and preserve knowledge when employees retire.
Adoption is about people. The foundation beneath it is about AI capability model: 86 capabilities across nine layers, with a nine-question scan that puts your result in your portal.
View the model →Also good to know: frequently asked questions · security and data · terms and conditions · partners · research and figures · templates · what's changing · where you start
AI tools are available, but employees do not yet use them effectively. Which task, guidance and quality checks will make a difference?
Start with a concrete business problem and a measurable outcome, not with an AI tool. Arrange data, ownership, risk and human control before you scale up.
We connect analysis, business intelligence, data and execution so you don't get stuck in advice or loose tooling.
A concrete analysis, priorities, decision criteria, an executable next step and visibility into what needs to be built, integrated or secured next.
Right for Dutch SMB organizations that want to solve a concrete process, knowledge, data or AI problem. Not for organizations looking only for a generic tool demo or unproven AI promise.
Price and scope depend on the chosen next step. View the current fixed packages and pricing logic at pricing for digitization.
We work step by step, make assumptions and ownership explicit, use only the minimum necessary data, and maintain human control over decisions and execution.
No. The preference is one clearly defined problem with a measurable outcome, then scale up.
The current pricing and package logic is on the pricing page; custom work is only chosen if the scope really requires it.
By defining the problem, owner, success metric and stop criteria in advance, and doing readback and verification after each step.
We map your current process, systems, exceptions and costs. Only then do we advise whether an off-the-shelf solution, a custom integration or another approach makes sense.
This page supports the following concrete solution.
Choose the next step that fits what you are viewing now.
Bedrijfsgeheugen gebruikt noodzakelijke cookies voor een goede werking van de site. Met jouw toestemming gebruiken we ook analytische cookies (Google Analytics) om te meten hoe de site wordt gebruikt en die te verbeteren. Je keuze wordt onthouden en je kunt 'm altijd wijzigen. Meer weten? Zie onze privacyverklaring.Met jouw toestemming meten we met Google Analytics hoe de site wordt gebruikt. Zonder toestemming meten we niets. Privacy