§ Client manifesto
An AI system your company owns. Not one more tool.
22 sections12 min read
§ 01
You probably do not have an artificial intelligence problem.
You have a legibility problem.
Your teams know an enormous amount. Your tools hold years of data. Your processes work, most of the time. And yet nobody in your company can open one screen and see, in a single view, where the time goes, where the money goes, and what could be done differently.
That is why most artificial intelligence projects fail. Not because the technology does not work. Because it gets installed on an organization nobody ever made legible.
We start from the opposite end.
§ 02
We do not sell licenses.
We do not sell one more tool to add to the fifteen your teams already do not use.
We do not sell an impressive demo that stops working the day real data lands in it.
We do not sell an engagement that leaves you dependent on us.
And we do not sell artificial intelligence. No chief executive wakes up in the morning thinking they are short of agents. They think their sales people spend too much time preparing meetings, that support costs too much, that reporting takes three days, or that their teams are hunting for information instead of producing.
Those are the problems we take on.
§ 03
A system you own.
Built on your data, connected to your tools, deployed on your own accesses, with your code in your hands.
The day our collaboration ends, the system keeps running and your teams know how to evolve it. That is the standard we accept being judged on.
§ 04
Before we build anything, we set out to understand.
We interview your people, function by function. Not a questionnaire sent by email. Real interviews, with the people who do the work.
What we hand back is not a report nobody will open twice. It is a living view of your own company.
§ 05
We translate that understanding into a maturity score out of 100.
Your company is not simply good or bad at artificial intelligence. We assess twelve dimensions separately.
One company can have excellent developers and internal knowledge that is completely fragmented. Another can hold enormous amounts of data and no strategy at all. A third can have bought fifteen tools nobody uses.
The score tells you which one you are, and exactly which dimension has to be acted on first.
§ 06
Then we compare two realities: where you stand today, and where you could stand.
For every function that matters.
The space between the two is your set of opportunities. Each one is scored on its impact, its effort, its cost, its time to value, its dependencies and its risk level.
We are not looking for the most impressive one. We are looking for the one that will prove fastest that the transformation really does create value.
§ 07
We also build the risk map. Before, not after.
A professional system is not a system that works on demo day. It is a system that keeps working when something goes wrong.
§ 08
Only from there do we build a real roadmap.
The first thirty days go to quick wins. The next sixty go to the structural building blocks. At ninety days, the systems start connecting to each other. At twelve months, your organisation no longer works the same way.
Every initiative carries an objective, an owner, a cost, an expected impact, indicators, its dependencies, an architecture, a risk level, a deadline.
And above all a precise definition of what this means: this project succeeded.
§ 09
A roadmap that never moves is a dead document within six weeks.
Ours runs in a loop, and that is the heart of the method.
Each turn makes the next one sharper, because it rests on real data instead of assumptions. An initiative that does not deliver what it promised is stopped, not defended.
Every month, you see what shipped, what it produced, and what moves to the front of the queue.
§ 10
Your company knows an enormous amount, and that knowledge is scattered.
We build the Company Brain: one shared context layer for the whole organisation.
The goal is not to dump your documents into a vector database and hope it works. You need to know which knowledge exists, who can reach it, how it gets updated, which source is authoritative, and how permissions are handled.
That foundation is what makes everything else possible. Without it, your agents are guessing.
§ 11
Take one of your salespeople.
Before an important meeting, he spends thirty minutes researching the company, checking LinkedIn, rereading past exchanges, going through the CRM and preparing his questions.
A system pulls all of that together and hands him his briefing.
But we do not stop there. After the meeting, another system analyses the transcript, extracts the decisions, identifies the objections, updates the CRM, creates the actions, drafts the follow-up and enriches the customer knowledge.
That is no longer an agent. That is a complete workflow, end to end.
The same logic applies to support, operations, finance, recruiting, marketing, research, reporting and steering.
§ 12
This is where the difference is decided between a prototype and a system your company can actually rely on.
A model never exists on its own. Around it there is an environment, and that environment is what we build.
The model can be excellent: if its environment is badly designed, its behavior will stay fragile. That is exactly why so many impressive pilots never make it to production.
We build the harness first. It is less spectacular. It is what holds.
§ 13
For complex missions, a single agent is not enough.
We organize several specialized intelligences, the way you would organize a team.
Each one has its role, its scope, its tools, its rules, its permissions and its success criteria. And some outputs must pass through human validation before anything moves forward.
You do not get an assistant. You get an organization that works while yours sleeps.
§ 14
Sometimes the right answer is not an agent. It is software.
An internal tool that does not exist on the market. A dashboard your executives open every morning. A client portal. A business application that replaces three spreadsheets and two meetings.
We know how to build it, end to end.
And if that software has value beyond your walls, it can become a product you sell. Some of our clients discover their next revenue line inside a tool they had built for themselves.
§ 15
This is the part most vendors avoid, because it cuts into their own revenue.
We train your teams to work with these systems, and to build them.
The program is tailored to each function. A finance director and a technology director do not need the same foundation, and each leaves with their own.
§ 16
From the very start we identify the person who will carry this transformation internally once we are gone.
They take part in the projects. They understand the architectures and the roadmap. They learn the frameworks and the rules. They receive the playbooks. They are in the room when decisions are made.
Step by step, they become your AI Lead, your Head of AI, or your future in-house Chief AI Officer.
We do not leave software behind us. We leave an organizational capability.
§ 17
You know artificial intelligence is going to transform your sector. You do not necessarily want to hire a full-time executive for a role that did not exist three years ago, at twelve or twenty-five thousand euros a month, with three to six months of recruitment and no guarantee.
We take the role.
And we prepare your company to bring the role in-house when it is ready. It is a role in which we aim to make ourselves unnecessary.
§ 18
What is not measured is not managed.
Every system we put into production arrives with its indicators, its real running cost, its audit trail and its dashboard.
Your executives do not take our word for it. They open the screen.
§ 19
This is not a service engagement. It is an asset booked into your company.
§ 20
A monthly engagement, with no imposed term. You move up or down a tier when your need changes.
Compare that with the real cost of the alternative: a full-time Chief AI Officer, three to six months of recruiting, and one single person where a system is what is needed.
§ 21
No slides. No steering committee that decides to create a steering committee.
By the end of the first month, you have a working system that produces value every day. Not a proof of concept.
§ 22
You can spend the next twelve months watching your sector change, testing tools, launching pilots that never reach production, and starting the same cycle over again.
Or you can make your company legible, choose the three places where artificial intelligence genuinely creates value in your business, and put them into production.
The question is no longer what artificial intelligence can do.
The question is what you are going to build with it.
Let us talk.
§ Working together
Three monthly tiers, and a day rate for when you need a senior operator with no commitment.
5 000
€ / month
Continuous diagnosis, AI Maturity Score out of 100, the living roadmap, Company Brain foundation, the first agentic workflows in production, monthly executive review.
10 000
€ / month
Everything in Foundation, plus the full Company AI OS architecture, done-for-you build delivered by waves, the harness, team training, governance.
15 000
€ / month
Everything in Transformation, plus the ongoing fractional Chief AI Officer seat, internal apps and SaaS builds, the multi-agent agentic organisation, the Internal Champion programme, observability and ROI measurement.
750
€ / day
A senior AI operator for a day, no monthly commitment: a one-off audit, an architecture review, a technical unblock, board preparation, vendor evaluation.