Approach
No model replaces judgement. But a good sequence prevents the most expensive mistakes.
Most AI initiatives do not fail on technology. They fail because the conversation turned to tools too early and to the business too late. That is why every engagement starts with listening — to the executive team, to the functions, and to the people who run the processes every day.
From that understanding a position emerges: where the effort is worth it, where it is not, and in what order to act. That position matters more than any technology decision, because every later decision rests on it.
And finally: an initiative only succeeds when people do their work better because of it. Everything before that is preparation.
miosu itself runs AI-first and remote. Analysis, research and preparation are AI-supported, which makes the work faster and leaner. I recommend nothing I have not tested in my own operation.
One more thing belongs to the approach: your team should end up able to do what I do. Building knowledge is not a by-product but a stated goal of every engagement. I actively share what I know — including what did not work.
The path
The steps build on each other, from the first question to a running solution. Skipped steps catch up with you later.
Before I hold an opinion, I want to understand your business: value creation, decision paths, bottlenecks, culture. That includes conversations across levels, because the view from the top and the view inside the process rarely match.
One to three weeks
A sober assessment of data, process maturity, capability, technology and risk. This is where it becomes clear which initiatives are realistic and which need a preliminary step that nobody enjoys hearing about but that saves time.
Two to four weeks
Prioritisation with the leadership team. Where to act first, why there, and what is deliberately not being done. Decisions made together hold when things get uncomfortable.
One to two weeks
This is where things get built. Depending on the initiative I implement the solution myself or lead a team drawn from your IT and my network — with a business owner, quality assurance, and an answer to what happens after the pilot. In the Microsoft environment I work with Microsoft 365 Copilot, Copilot Studio, Azure AI Foundry and Microsoft Fabric; where another platform fits better, I say so.
Eight to sixteen weeks per initiative
The step most often underestimated. Enablement along real tasks, internal champions, leaders who visibly work with the tools themselves, and measurement that shows more than usage statistics.
Three to six months, in waves
Working together
Advice only works when it fits into the daily life of your organisation. The engagement model is deliberately lean.
You work with me, not with a rotating team. Where specialist knowledge is needed, I bring in selected solopreneurs from Switzerland and Finland — named, transparent, and always with me accountable.
The work runs remotely, in short and well-prepared sessions. I am on site where presence makes the difference: workshops, leadership sessions and conversations that need trust.
Regular, short checkpoints instead of long reports. What cannot be explained in fifteen minutes is usually not yet thought through.
A few pages in the language of your business, written for decisions rather than for the archive.
Building knowledge on your side is not a by-product but a stated goal of the engagement. I work in the open: methods, templates, judgement criteria and mistakes all transfer to your team. We grow together, and your organisation continuing without me is the measure.
Clarity
This clarity is not a matter of attitude. It is what makes my recommendations worth anything.
Invitation
Sixty minutes going through your situation. You need no preparation and enter no obligation.
You leave with two or three concrete observations, whatever happens next.