01
You have explained it four times
Once to your assistant. Once to a developer. Once to ChatGPT. Once to yourself, late, in the notes app. Every version was slightly different, and every version was true.
L’Atelier · Business design, installed
Everything works. As long as you are the one holding it together.
L’Atelier is where House of Her designs how one important part of your business should actually work, then installs it with you in the room and hands it over so your team can run it without me.
- Written scope and hour cap
- Two counted iterations
- Clients in France and the United States
You already know what you want
You can describe the outcome. Getting it built is the part that keeps stalling.
Your team is capable. The platform is fine. And the thing you are asking for still has to work inside a business nobody has written down yet.
02
Someone built exactly what you asked for
It does what the brief said. It does not do what you meant. And the gap between those two things only became visible once it existed.
03
The automation runs on last year’s offer
It was built when the package was one thing. The package is now three, one of them custom, and the sequence keeps sending clients a welcome that no longer matches what they bought.
04
Your team asks the same question three ways
And you answer it three different ways, depending on the day and the client. Nobody wrote the rule, because the rule lives in your judgment.
05
You bought the platform in March
The subscription renews. The tab is still open. Nobody could decide what was supposed to move into it, so nothing did.
06
You are the integration layer
The pieces do connect. Through you. Every handoff between two people, two platforms or two decisions passes across your desk first, and that is why Friday afternoon is never what it was supposed to be.
What L’Atelier is
Business design, and then the build.
House of Her works out how one important part of a company should operate: the logic, the source of truth, the decision rules, the handoffs between people and platforms.
Then builds and installs it with you present, and trains your team to run it. The person who works out what should happen is the person who builds it.
The price is agreed in conversation, because the scope is. What is fixed is the shape: a written scope, a cap on hours, a stated rate for anything beyond it, two counted iterations, and hours you can see.
What you keep
Nine things your business owns at the end.
None of them depend on which software is current. That is the point of building it this way.
What the business knows
- An organised business context
- Everything the company knows, in one readable place instead of six.
- A source of truth
- One record that wins when two systems disagree, owned by one named person.
- The reasoning, in plain language
- Written so it outlives the platform it runs on today.
How decisions get made
- Decision rules, written down
- The calls you make by instinct, turned into rules your team can apply.
- Roles and responsibilities
- Who does what, who decides, and what happens when that person is away.
- Where a human decides
- Marked explicitly. Some judgment never leaves the room.
How the work moves
- Workflows and handoffs
- The route work takes between people and platforms, designed on purpose.
- The checks
- What catches a mistake before your client does.
- A system you have already used
- You use it during the build, on live work, while I can still adjust it.
How it runs
Five phases, in this order, every time.
The Studio covers the first two when what should be built is still unclear. L’Atelier carries all five.
The first sessions are not about software
A long series of questions about how the business actually decides things. Who the client is. What wins when two documents disagree. What your right hand means when she says a client is difficult.
What actually consumes the team, not what they believe does
The audit reads the real material: mail, calendar, the channels where the work really happens. It returns findings nobody had seen, and they are rarely about technology.
Roles first, tools second
What starts a job, what “done” looks like, where the output goes, who checks it, and what happens when it breaks. Written down before anything is built against it.
Installed with you in the room, on your own data
On your machines, on your live work. Nothing is handed over as a finished black box you have to reverse-engineer later.
The phase most installations never get
The system is checked against reality, and reality keeps producing surprises. One question about a schedule once uncovered three days a week that had been invisible.
A client
“I wanted him to tell you personally, because I want you to know how much you’re helping us.”
Installed
Three businesses, three different problems.
What was installed, and what the founder said afterwards.
A film production company
The audit surfaced that the CEO had been scheduled in two places at the same time, more than once. Every system was right on its own; the conflict only existed between them. Twelve AI roles were installed, nine still used every day.
480 ha year, per employee. Their COO checked the figure himself
before signing off
“Flavie rocked my world. The brilliance of this is how she caters it for you.”
Mari Bonnemaison · CEO, Emmy Award-winning producer, Bonnemaison, Inc.
A coach with a broken funnel
A quiz funnel rebuilt from broken to live: landing page, opt-in and archetype email automation. Plus a brand document so her AI writes in her voice rather than a robot’s. The quiz launched at a business expo.
43pages of brand document, so her AI writes in her voice
“Thank you for all your support.”
Coach · launched at a business expo
A founder passing everything through herself
A webinar that filled, an Instagram direct-message automation, and a GoHighLevel account rebuilt so the pieces finally spoke to each other. The follow-up now runs without her reading every message first.
110registrations on the webinar, with the follow-up running on its own
Who it is for
Built for a business that already works.
And has outgrown the way it was originally put together.
This is your engagement if
- You have real clients, real revenue, and an offer that already sells.
- You can name the outcome you want, and working out how it should function is the part you want handled.
- Important knowledge lives in one person’s head, and that person is usually you.
- You want your team to run this afterwards, and to understand it well enough to change it.
- You would rather be told half of what you asked for should not be built, than be sold all of it.
This is not your engagement if
- You have not launched. There has to be a business here to design around.
- You want someone to execute a finished specification without questioning it. That is a different hire, and a good one.
- What you actually want is to learn the software. L’Atelier works on your business instead.
Questions about L’Atelier
Before you write.
What does L’Atelier cost?
The price is agreed in conversation, because the scope is. What is fixed is the shape: a written scope, a cap on hours, a stated rate for anything beyond it, two counted iterations, and hours logged where you can see them. You will never get an open-ended bill.
Do you build it, or does my team?
It is installed on your live work with you and your team present, on your own systems, so the people who will run it have already run it once. Nothing is handed over as a finished black box you have to reverse-engineer later.
What happens when the software changes?
The reasoning is written down in plain language, separately from the tool it currently runs on. The logic, the source of truth, the decision rules and the handoffs stay valid when the platform underneath them is replaced.
Get in touch
Bring the part that keeps coming back to you.
You do not have to turn it into a tidy brief first. Turning it into something workable is the job. I read every message myself.