// La Résidence

Your tech side, owned.

I take over the technical side of your product: run, watched, fixed before you notice, evolving every month. A short client list, capped on purpose. A twelve-month engagement, billed monthly. This is the offer; everything else on this site is a way in.

1 seat left
Start the auditPrefer to talk first? Book a CTO session
// Why it exists

The week your expert disappears.

You know the story because you lived a version of it. The CTO leaves for an offer he could not refuse. The agency delivers, invoices, and moves on. The freelancer answers slower every month, then not at all. The product still runs, but nobody owns it: problems surface the day they happen, every invoice is a small mystery, and with AI, everyone you interview seems like an expert, until the day it matters.

La Résidence exists so that story ends here. Your product moves in: watched, backed up, fixed, improved a little every month, with one person accountable by name and everything visible to you.

// How it works

The first three months, written down.

Two ways to move in: a product that already exists, or a product that does not exist yet. Different first months, the same house by month three.

Your product exists

The rescue

M0

The audit

Before anything is signed, I read your code: all of it. You get the verdict and the plan, and the last chapter of the PDF is already month one. €2,000, credited against your first month.

M1

Moving in

The rescue starts with the audit's fix list. Your product moves into its own space, in your name: test and production environments, nightly backups, a restore rehearsed for real. From this month on, every error is caught the second it fires.

M2

The rhythm

Dependencies brought current and kept there. Deploys become non-events: validated on test, live in under a minute, zero downtime. The first evolutions ship, and your first Friday digest arrives.

M3

Cruise

The backlog moves every month, most bugs die before you hear about them, and the monthly statement says exactly what the month was for. Every month after looks like this one.

Nothing exists yet

The first build

M0

The scope

We write version one down in the Forge before any code exists: what ships, in what order, and the smallest version that can face a real user.

M1

Foundations

A real URL in week one. Production infrastructure from day one: backups, monitoring, telemetry. Your product is born watched, not retrofitted years later.

M2

The build

Features land on the test environment every week and go live as you validate them. You follow every step in the Forge, and every sprint ends with a guided video tour.

M3

The launch

Version one opens to real users carrying what most products wait years for: watched around the clock, fixed overnight, one name accountable.

M4+

Month four, and every month after: the same house. Watched, evolving, one person answering for it, and the door always open.

// The stack

What €3,975 actually buys.

You see every line. The guarantee covers all of it and no line can be removed: that is what makes it a roof instead of a menu. The work is the one dial. Here is the honest market price of assembling it yourself.

La Résidence

Your product in its own dedicated space, in your name from day one: test and production, nightly backups with rehearsed restores, updates, watched around the clock.

Managed hosting + DevOps retainer
€800-1,500 / month

Incident response

One person accountable end to end. An incident is taken within two business hours and owned until the fix is live and its cause written down; miss that once, and the month's guarantee is free. At night, the machine watches.

A support contract with a guaranteed response time
€2,000+ / month

Evolution

The product improves every month, from 5,000 credits of work: small changes live within days, bigger ideas come back as a written proposal, priced before work starts.

A dev agency retainer
€4,000-6,000 / month

A CTO at your table

Architecture, trade-offs, build or buy, the next hire: technical questions get one owner, and the answer comes back with the trade-off spelled out.

A fractional CTO
€3,000-5,000 / month

The Forge

One page where you see everything: what is live, what I am working on, what is waiting on your decision. You never have to ask where things stand.

Not for sale anywhere

Reporting

A short digest every Friday, a guided video tour at the end of every sprint, and a written monthly statement, itemized line by line.

An account manager who proves it
€1,000-2,000 / month

Living documentation

How the system works, how to run it, what to do when things break, who owns what: written down and kept in step with the code as it changes. Yours from day one, which is what makes an exit calm instead of chaotic.

Elsewhere: a one-off PDF, stale on delivery

Self-healing

When a bug fires at 2am, an AI agent picks it up, diagnoses it, and ships the fix, checked against the rules of your codebase. Most bugs die before you wake up.

Not for sale anywhere

The warranty

If something I shipped breaks, fixing it is free, for as long as I operate your product. Agencies bill you for their own bugs; mine are on me.

Not in any agency contract

The handover

The documented, priced exit: code, infrastructure, accounts, everything transferred, with an architecture walkthrough and 30 days of questions. You can leave whole; that is why you stay.

The clause no agency writes
Assembled from the market

Spread across five vendors, with the five lines that matter most not for sale, and still nobody answering for the whole.

€11,000-16,000 / month

La Résidence

The guarantee, €1,200, plus at least 5,000 credits of work a month. One name. Twelve months, billed monthly.

from €3,975 / month

The same engagement, written for the buyer comparing providers: Fractional CTO Services. For a product that only needs keeping in production: Software Maintenance and Support Services.

// The signature

The house that repairs itself.

La Résidence does something no agency contract does: when a bug happens, an AI agent picks it up, diagnoses it, and ships the fix. Most of the time, before you ever knew there was one.

02:14

An error fires in your app. Nobody is awake. It is caught anyway.

02:15

The agent picks it up, reads the error, and starts diagnosing.

02:47

The fix is written, checked against the rules of the codebase, and shipped.

Friday

You read about it in your weekly digest. That is how you find out.

Not every fix ships itself: the ones that need human judgment come to me, within two business hours, not to you. Either way, the error was caught the second it fired, and the digest tells you the story.

// No hostages

Twelve months, and the exit in writing.

The usual agency model keeps you by making leaving painful. I would rather keep you by being worth it, every month. So the exit is part of the offer, in writing:

A year, billed monthly

La Résidence is a twelve-month engagement, billed monthly: the guarantee, €1,200, plus your month of work, from 5,000 credits at the yearly rate. The first month is often the rescue: the audit's fix list, executed.

Defects are on me

If something I shipped breaks, fixing it is free, for as long as I run your product. Not a gesture: a warranty.

Leaving is a product, not a fight

Want to take it in-house one day? The handover is documented and priced: your code, your infrastructure, your accounts, everything transferred, with an architecture walkthrough and 30 days of questions. You leave with everything, because everything was already yours.

// The seats

Ownership does not scale.

Watching a product, knowing its code down to the last line, answering for it under a guarantee that costs me a month whenever I miss it: I can do that for a handful of products, not for forty. So the cap is written into the offer, and I would rather turn work away than carry more than I can answer for.

When the seats are full, the door becomes a waitlist: the audit still runs, the verdict is still yours, and the next free seat is offered in order.

// How to get a seat

Seats are capped, so the audit decides.

I only take responsibility for products I have read down to the last line. So every seat starts with the Expert Audit: you get the verdict and the plan, I get the answer to whether I can own your product with you. Working products with real users and real revenue come first; that is what the seats are for.

If the audit says yes and a seat is open, the last chapter of the PDF is already your first month's plan, and the audit is credited against that month. If it says no, you keep the verdict and the plan. No seat required.

// FAQ

The questions people actually ask.

Why from €3,975, when a freelancer costs €1,500 a month?

A freelancer sells you hours; €1,500 buys availability, not accountability. Nobody is watching the product at night, nothing carries a warranty, and the exit is never priced. La Résidence is the whole stack above with one name answering for all of it: €1,200 for the guarantee, the rest is your month of work. If hours are all your product needs, a freelancer is honestly the better buy.

What if nothing breaks for a month? Am I paying for silence?

A quiet month is the product working: watched around the clock, backed up nightly, dependencies patched, evolutions shipping. Quiet does not mean idle, and the monthly statement proves it line by line: what was caught, what was updated, what went live. You are never asked to take the month on faith.

What is included, and what costs extra?

Every month includes evolution credits, the currency of change: at least 5,000, more at the same rate when the month needs it. A small change costs a few hundred credits and ships within days; a bigger idea comes back as a written proposal, priced in credits, before any work starts. You always see the price before I start, and the statement shows where every credit went.

My product was built by someone else. Can it still move in?

Yes: that is the rescue path. The audit reads everything first and turns the verdict into a plan; we start with its fix list, and the worse the shape, the more of the early months it takes. Your product moves in as it is; it just does not stay that way.

Who does the work, you or the AI?

Both, and openly: it is what makes the offer possible at this price. The AI writes more of the code every year, inside rules I wrote for your codebase; the reading, the decisions, and the name on the result are mine. Accountability is the one thing I never delegate.

You are one person. What if you are the one who disappears?

Then you are inconvenienced, not trapped. Everything is in your name from day one: the code, the infrastructure, the accounts, the documentation kept current for handover. That is also why the exit is a product, a documented handover: the door works even if I am not there to hold it open.

How fast do you respond when something breaks?

Within two business hours, Monday to Friday, 9:00 to 18:00 Paris time: an incident is taken, owned until the fix is live, and its cause written down. Miss that once, and that month's guarantee is free. Errors reach the machine the second they fire, day and night, and most fixes ship before anyone could have reported them. When you write to me, you write to the person who knows your code line by line, not a support queue.

The seats are full. What does the waitlist actually mean?

The audit still runs: you get the verdict and the plan either way, and both are yours to execute with anyone. If the audit says yes, you hold a place in line and the next free seat is offered in order; the plan, meanwhile, does not expire.

// One seat, one decision

Worst case, you get the verdict.

Start with the audit: €2,000, the truth about what you own in 48 hours, and the plan I would run. Best case, your product gets an owner.

Start the auditPrefer to talk first? Book a CTO session