// Become AI-Native

Your internal AI system.

Four months, one system: the AI your company actually runs on, built into how you already work. Then three months of La Résidence, included, to run it in production. Not a chatbot parked on top of your data.

No seats left€75,000 · 4 months of build · 3 months of La Résidence included
// Why it exists

Everyone bought AI. Almost nobody is AI-native.

Most companies buying AI today are buying subscriptions and demos. The tools are real, but nobody wires them into the way the work actually happens, so the gain stops at the individual who happens to like the tool. One person prompts well; the company works exactly like before.

AI-native is something else. It is a system: agents that carry whole workflows end to end, the data they need to do it, one interface your team opens every morning, and the documentation to run it without me. You cannot subscribe to that. It has to be built into one company at a time, on its real workflows, and that is the only version I have seen actually hold.

// The proof

I am client zero.

ITzWorking runs on a system exactly like this. Client requests, task boards, deployments, the 2am bug: the machine behind my agency is an internal AI system I built for myself, and it is the reason one person can operate what normally takes a team. The self-healing house on the Résidence page is one visible fragment of it. The rest runs every day, quietly.

You will notice there are no screenshots and no internal numbers here. That is deliberate: what my system knows about my business and my clients is not for sale, and the same discretion will protect yours. I am not selling you a tour of mine. I am selling you yours: the same approach, your workflows, your name on everything.

// How it works

Seven months, written down.

Four months of build, then three months of operation. The scope is fixed at the end of month one, not before: fixing it earlier would be a guess dressed as a promise.

M1

The immersion

I move into your operations and watch how the work actually happens: where the hours go, what your team repeats, what only lives in someone's head. Together we pick the workflows the system will carry, the two or three that pay for everything else, and write them into a scope document. That document is also the exit: if it does not convince you, we stop there.

M2-3

The build

The system takes shape in your name: agents on the chosen workflows, the data they need, the interface your team opens every morning. No big reveal at the end: workflows go live one at a time, and your team is already working in the system while it is being built.

M4

The handover

The month that makes it run without me. Documentation written for your team, training done on the real system, and the scope document checked line by line: what was promised is what runs. Code, infrastructure, accounts: already yours, because they were from day one.

M5-7

La Résidence, included

The system moves into La Résidence for three months, on me: watched around the clock, bugs fixed before you notice them, small evolutions shipping as your team asks for them. The build proved it works. These three months prove it holds.

M8+

Then you choose. Keep the seat at the public price of La Résidence, and I stay the developer of your system. Or take it fully in-house: everything was in your name from day one, so leaving whole is the default, not a negotiation.

// The stack

What €75,000 actually buys.

One price, and no line can be removed. Here is the honest market cost of assembling the same thing yourself.

The immersion

A month inside your operations, mapping where the hours actually go, done by the person who will also build the system. The scope document is yours whatever happens next.

An AI strategy consultancy
€15,000-30,000, slides included, system not

The system

A custom internal platform in your name: agents that carry the chosen workflows end to end, the data they need, wired into the tools you already use. Software you own, not a subscription you rent.

A dev agency, same brief
€80,000-140,000

The interface

One place your team opens every morning: what the agents did, what is waiting on a human, what went live. A system nobody can see is a system nobody trusts.

Usually forgotten in the quote

The documentation and the training

Written for your team, not for developers: how it works, how to run it, what to do when something looks wrong. Training happens on the real system, on your real workflows.

A training vendor
€5,000-10,000

Three months of La Résidence

After the handover, the system lives under my flagship offer: watched around the clock, self-healing, evolving. The public price is on this site; the three months are in this price.

The public price, on this site
€24,000

Ownership, day one

Code, infrastructure, accounts, data: in your name from the first week, not transferred at the end as a favor. If we stopped tomorrow, everything already built is already yours.

The clause vendors never write
Assembled from the market

Split across a consultancy, an agency, and a training vendor, with the ownership and the three months of operation not for sale anywhere, and nobody answering for whether it still runs in month six.

€125,000-200,000

The internal AI system

One line. One name. Fixed before we start.

€75,000
// The honest part

What this is not.

Four months buy a system, not magic. The boundaries are part of the offer, in writing:

Not everything. The right things.

We will not automate your whole company in four months, and I will not pretend otherwise. We pick the two or three workflows carrying the most repetitive weight and do those completely. A system that owns three workflows beats a demo that gestures at thirty.

The month-one exit

The scope is fixed at the end of the immersion, and that moment is also a door: if the scope document does not convince you, we stop, you pay for the immersion month only, and the document leaves with you. Nobody is trapped in a four-month build on a weak premise.

It needs you in the room

The system is built on how your company actually works, and only your people know that. I need a point person, access to the tools where the work lives, and honest answers during month one. Everything after that is on me.

// The seats

One build at a time.

A build like this takes over my months, and the Résidence products I already answer for do not pause while it happens. So there is one build slot. Right now, it is taken.

The waiting list is exactly what it sounds like: no payment, no commitment, no ranking games. When the slot opens, this list is where I look first, and it is also how I measure whether this offer deserves a second slot.

// FAQ

The questions people actually ask.

Why €75,000?

Because of what it replaces. Assembling the same thing from the market costs €125,000-200,000 across a consultancy, an agency, and a training vendor, and the two lines that matter most, ownership from day one and three months of production operation, are not for sale anywhere. One price, one name answering for the whole, fixed before we start.

What do we own at the end?

Everything, and from the start: code, infrastructure, accounts, data, documentation. It is software in your name, not a license, so there is no subscription to cancel and nothing switches off if we part ways. The handover month exists precisely so your team can run it without me.

What happens after month seven?

You choose, and both answers are fine. Keep the seat at the public price of La Résidence, and I stay the developer of your system: watching it, fixing it, evolving it. Or run it in-house: the documentation and the training were built for exactly that, and everything is already in your name.

We do not know what we would automate. Can we still join?

Yes, and you are the reason month one exists. Choosing the right workflows is the hardest part of the whole build, and it is work we do together, inside your operations, before a single agent is built. You do not need a plan to join the list; you need repetitive work and the will to be rid of it.

Can we see the system you run for yourself?

No, and you should want that answer. What my system knows about my business and my clients stays private, and the same discretion will protect what your system knows about yours. The public fragment is on the Résidence page: the house that repairs itself. The rest I would rather prove on your workflows than demo on mine.

Why is the scope fixed? Our needs will change.

A fixed scope is what makes a four-month promise honest; a moving one is how builds eat a year. The system is built to be extended: new workflows are exactly what the Résidence months and everything after are for. Fixed scope is not a wall, it is the reason the first workflows actually ship.

Who does the work, you or the AI?

Both, openly: it is the whole point. My own agents carry a growing share of the build, inside rules I write, which is why one person can deliver this at this price. The reading of your business, the decisions, and the name on the result are mine. I would not sell you an AI-native company while working any other way.

What does joining the waiting list commit us to?

Nothing. No payment, no obligation, no small print. When the slot opens, the list is where I look first. If you want to move before that, book a CTO session: an hour of my time on your context, and the fastest way for both of us to know if this is a fit.

// One slot, one system

The list is the door.

I would rather tell you there are no seats than sell you a start date I cannot hold. Join the list: when the slot opens, you hear about it first.