Time and effort
How long it takes and what it costs you
How soon do the first results show?
The first tangible result is usually measured in weeks rather than months, provided you start with a narrow, well chosen task. A recurring routine that affects many people is the best entry point, because the benefit shows up quickly.
Organisational change is slower. The 90 day programme runs for three months because that is how long it takes for usage to become part of daily work, rather than an enthusiastic start that fades.
How much time does adoption take from our team?
The training sessions take a fixed amount of time, but the real effort is the practice in between. Realistically that means a few hours a week per participant, plus one internal owner who holds the process together.
With less than that the knowledge does not stick, and much more than that is not worth committing to alongside daily work. If nobody can spare an hour a week, this is probably not the right project yet.
What is the difference between the workshop and the 90 day programme?
The workshop is one day and it is about shared understanding. By the end the leadership team sees the same picture and the first concrete steps are agreed.
The 90 day programme comes after that and is about actual adoption, in a weekly rhythm with measurable results. At many companies the workshop is what decides whether the larger programme makes sense. Both are described under services.
Cost
What it costs
How much does AI adoption cost?
The fee depends on scope, so there is no single list price. A one day executive workshop is a different order of magnitude from a three month adoption programme or a custom system build.
On the free consultation we clarify the goal and the scope, and you get a concrete proposal after that. If it turns out the company is not at that point yet, I will say so, because a badly timed project serves nobody.
How can we estimate the return in advance?
Return does not hinge on the price of the model. It hinges on how many repetitive working hours are freed up and what happens with that time. The estimate therefore always starts from your own processes.
The ROI calculator gives a first approximation, though an accurate picture requires going through the specific tasks.
Prerequisites
Whether you need prior knowledge
Do we need technical knowledge or a programming background?
Not for the leadership and end user programmes. They are built on using AI well within your own profession, not on becoming a developer.
The engineering and developer material naturally requires a technical foundation, but that forms a separate track.
What if the team resists?
This is the most common real obstacle, and it is almost never technological. People worry about becoming redundant, or about being monitored through the system.
That is why adoption starts at task level rather than job level, and why the leader has to say openly what will happen with the time that is freed up. Where that is missing, even the best tool gathers dust regardless of what was paid for it.
How do we know where our company stands?
An honest picture of who uses what today and where the repetitive burdens sit is enough to start. For a quick self assessment there is the AI readiness test.
In my experience several people at most companies already use some AI tool, it is just that nobody knows about it at a system level. The assessment usually surfaces this first.
Data and tools
Data security and tool selection
What happens to our company data?
This is one of the most important questions and the answer depends on the tool. With free and consumer services it can happen that submitted data is used for model development, so trade secrets do not belong there.
Enterprise plans typically exclude this, but that has to be verified at contract level rather than assumed. During adoption we always clarify what data may leave the organisation at all, and what has to stay inside.
Which AI tool should we adopt?
The tool is the smallest decision, yet it is where most companies start. First you clarify what task it is for, what data it works with, and who will use it. The tool follows from that, not the other way around.
Because I work as an independent consultant, the recommendation does not follow any software vendor's sales interest. Tools also change quickly, whereas the process and the capability remain.
What happens when the technology changes?
It will change, that much is certain. That is why we do not teach the operation of a single tool, but the thinking and the process that stay valid after the tool is replaced.
The long term partnership is precisely about making sure the capability you built does not erode when the market shifts.
Format
Who it is for and in what form
What size of company is this for?
The method works regardless of size, but the emphasis changes. At a smaller company the goal is fast, concrete benefit. At a larger organisation regulation, lines of responsibility and organisation wide capability come to the front.
Is it online or in person?
Both work. The executive workshop is usually stronger in person, because the discussion and the shared thinking are the point. For longer programmes the online format is often more practical, since it is easier to fit into calendars.
Everything can be delivered in English if the team is international.
Who delivers the training?
I do, as an independent AI consultant. I work on enterprise AI training and adoption programmes, and I do not represent any software vendor. More on the about page, and previous work under case studies.
Still have a question
Let us talk about specifics
Thirty minutes of free consultation about your situation. By the end you will know what the first step is, even if we do not end up working together.