Print on demand ~20% → ~40%
conversion to a final sale
Helping customers configure a print order out of a billion product combinations.
Transformation
Decide what agentic AI should change in your company, and see the change through.
I work with CEOs and function leaders on what to transform, in what order and against which number. Vstorm engineers each system and hands it to your team, so you own what we built.
The two models
Know which model you are changing.
Most stalled initiatives I see skipped the diagnosis. The team knew it wanted agents and had not decided which problem the agents should solve.
The business model is what your company is: what it sells, to whom, and why customers pay. The operating model is how your company runs: processes, people, data and decision rights. It now has one more layer, the agents, with its own rules about what they decide alone, what they escalate and who answers for them.
The second question is why you are moving. Defense means something threatens your position, and the clock is loud. Expansion means you see room to grow, and there is no clock, so you have to set one.
Operating model / Defense
Keep up.
Competitors run the same work cheaper or faster. The goal is to close the gap.
Operating model / Expansion
Grow without matching headcount.
Revenue rises only as fast as you hire. The goal is to break that link.
Business model / Defense
Reinvent before you are disrupted.
A new competitor, often built on agents from day one, offers most of what you sell at a fraction of the price.
Business model / Expansion
Offer something new.
Agents let you sell a service you could not staff before, or reach a market you could not serve.
Each quadrant needs a different sponsor, budget and timeline. Business model work usually starts with the founder or CEO and stays experimental for longer. Operating model work usually starts with a function leader and can reuse patterns that already work elsewhere.
The two circles
Find out which circle you are in.
A precise, coherent strategy can still fail when it was written for a game the team did not understand. With agentic AI, that is the failure I see most often.
The outer circle
Learning the game.
Before any plan, you learn how agentic AI works in enough detail, how a transformation actually runs, and which of your strengths can become an advantage. Every action is a probe, and breadth matters more than commitment.
You are here if your picture of agents comes mostly from vendor demos, or if nobody can yet name the workflow that would move your main number.
The inner circle
Playing the game.
This is classical strategy: the mission of the transformation, what to change and how, the KPIs and the plan. It works only after the outer circle has given you an accurate map.
You are here if you know which process goes first, what number it has to move, and who sponsors it.
The outer circle never fully closes. Each new transformation reopens it, and companies that stop learning get caught out by the next change.
How I help. In the outer circle I run working sessions with your leadership team. In the inner circle we write the strategy together and choose the first workflow.
How a transformation runs
Three stages, one team.
We call the method TriStorm. I lead the strategy, Vstorm's engineers build, and no stage starts before the previous one is signed off.
- Stage 01
Strategize.
We map the process as it runs today, place it on the grid above, and redesign it around what agents can do. We agree the success threshold before anything is built.
- Stage 02
Engineer.
Vstorm builds a proof of value, then a first working version, then the full system in production. I stay accountable for the outcome.
- Stage 03
Transform.
Your team takes over the system and learns to run and extend it. The next workflow builds on this one.
Who owns what
- I own the diagnosis, the strategy, the change inside your organization, and whether we hit the agreed number.
- Vstorm owns the architecture, the engineering, the system in production and the training of your team.
- You own the code, the IP and the decision logic, by contract.
Why me
Why leaders work with me.
01
One person accountable.
I run each engagement myself, from the first workshop to the hand-over.
02
Strategy and build in one team.
When one firm writes the strategy and another builds it, the reasons behind the plan rarely survive the handover. Here the people who agree the goals with you also build the system.
03
You can read how I think.
The essays on this site come from live work. Read two before you book.
Where I am biased
Vstorm builds custom systems that the client owns. If one well-defined workflow inside one system is the whole problem, an off-the-shelf tool will be cheaper and faster, and I will tell you so on the first call.
Proof
Results from transformations I led.
Print on demand 
Engineering software 2 hrs → 3 min
to build a validated workflow
Turning an engineer's request into a working automation.
Clinical triage 98%
accuracy, on par with a five-nurse expert panel at 94.4%
Matching a caller's symptoms to the right triage guideline, tested on a 50-scenario benchmark.
Questions
What leaders ask before the first call.
Q1 How long until we see first results?
The strategy stage takes two to four weeks. It ends with the first workflow chosen and the number it has to move agreed, and the build timeline follows from that workflow.
Q2 What does it cost to start?
The strategy stage has a fixed scope and a fixed fee, agreed after the first call.
Q3 Who does the work?
I lead the strategy and the change. Vstorm's 25+ AI engineers build the systems. You work with both directly.
Q4 Does this mean cutting jobs?
It always changes what people do. Whether headcount changes is your decision. Decide which outcome you are building toward before you promise anything to your team or your board.
Q5 Should we build or buy?
Buy when a product already fits your process. Build when the workflow is specific to you or central to how you compete, and you want to own the result.
Q6 What if our data is not ready?
Then preparing it is the first piece of work. In our deployments, getting data to the agents is more often the hard part than the model.
Start here
Start with where you stand.
Thirty minutes with me, no deck. We will place you on the grid and work out which circle you are in.