Context
The client is an enterprise software vendor. I am engaged directly, under my own name, and the mandate covers two things at once: moving the company off SaaS into its own environment, and building AI capability that stays with the teams afterwards.
Business problem
SaaS is a recurring bill, and the systems in question did not need to run there. The second half of the problem was not cost at all. AI practice that lives in a deck leaves when the consultant does; what the teams needed was capability they hold themselves, in the systems they already work in.
My mandate
Move the company from SaaS to on-premises, and build AI skills across the teams together with best practices in their internal systems.
Decisions
- Move the systems into the company’s own environment. The migration off SaaS is the cost decision, and the result is stated in subscription cost alone — more than €190,000 — with nothing else folded into the figure.
- Build the capability inside the teams, not beside them. The AI skills went to the people doing the work, across more than one team, rather than to a central group the others would queue for.
- Put the practices where the work happens. The best practices went into the company’s own internal systems, so they sit in the place the teams already open every day.
Delivery
Two tracks run side by side: the migration off SaaS, and the enablement work inside the teams. The engagement began in July 2026 and is ongoing. No duration or team size is published.
Outcome
The migration is set to save more than €190,000 in SaaS costs alone. The teams are building AI skills of their own, with the practices written into the internal systems they work in every day. The engagement is ongoing.
Evidence
The €190,000 is a saving in the client’s own subscription spend, quoted by them. The engagement began in July 2026 and is still running, so the figure is labelled projected rather than measured: it is the saving the migration is set to deliver, not one already banked. The capability outcome carries no number and is stated as qualitative. No duration, team size or technology list is published for this engagement.