The first hour: setting up Fable 5 as one seat for a wellness business.

The instinct, when a business decides to ‘do AI’, is to go shopping: a tool for the inbox, a tool for the notes, a tool for the socials, a login for every leak in the boat. Six months later there are eight subscriptions, no one owns any of them, and the gap between demand and care is exactly where it started. A wellness business does not need ten tools. It needs one seat, set up like a role — and the setup takes about an hour, not a quarter.

So here is that hour, mapped to the roles a clinic or studio keeps dropping. Not a feature tour for its own sake — the specific setup moves that let one seat carry the operator work nobody wants to pay for, with a human still holding the pen where it matters.

move zero: set the sign-off gate first (five minutes)

Before the seat is useful enough to tempt anyone, decide the rule and write it into every workspace: nothing the tool drafts reaches a client, a lab, or a booking system without a named human signing off. In a client-facing business this gate is not bureaucracy — it is the difference between AI that protects your reputation and AI that quietly damages it in your own voice, at scale, while no one is looking. Set it before you build anything that could get past it.

move one: write the operations handbook (fifteen minutes)

Teach the seat your business. Write one page: your services, your pricing rules, your booking policies, your tone of voice, and what a good client reply looks like. Paste it in as the standing brief. This is the induction you never have time to give a new front-desk hire — except you write it once and every workflow inherits it. The businesses getting value are not the ones with clever prompts; they are the ones who wrote the handbook first and let everything run from it.

move two: wire one read-only connector (ten minutes)

Connectors turn a smart drafter into an operator by letting the seat work from live information — the shared inbox, the calendar, the intake forms — instead of a snapshot someone pasted in. In your first hour, wire exactly one, and make it read-only. A connector that can read the inbox and draft a reply is enormous leverage and low risk. A connector that can send on its own is a different decision entirely, and in a client-facing business one to make slowly, if at all. Let the seat read and draft; let a person send.

move three: build a room per workflow (fifteen minutes)

A project is a persistent workspace with its own standing instructions and files. For a business, build a room per workflow rather than per client: an ‘enquiries’ room that holds your services and voice, an ‘intake’ room that knows your form and what a good summary looks like, a ‘rebooking’ room that knows your cadence. Set up your leakiest one during the hour — usually enquiries. Each room is inducted once and then runs consistently, no matter who on the team opens it.

The highest-leverage use is to let the room interview the operation once it holds your flow: where are clients falling through the gaps, what do you collect at intake that you never use, which follow-up never happens? It is not deciding anything. It is reading your business as a system and showing you the leaks you are too close to see.

move four: schedule the drudge (five minutes)

Finish with one recurring job on the workflow that leaks most: a Monday draft of the week’s rebooking notes, or a weekly list of enquiries that went cold. Most of the gap between demand and care is simply things not happening on time. The seat remembers; a person decides. Turn it on for one drudge task, keep the sign-off human, and measure the hours it hands back to the people who should be delivering care.

“The worker you could never afford now sits at a desk that costs almost nothing, wired into the tools you already run — set up in an hour. The manager who signs off on its work is still, and always, a human you.”

the trust rule for a client-facing business

Two commitments keep the setup clean as you grow. First, a human owns every client-facing output — the seat drafts, a person sends. Second, hold client data with the same care you hold it everywhere else; a seat that reads your whole operation is only safe inside the boundaries you already keep for records and consent. Handle those two and the seat stops being a risk and becomes what it should be: the role that lets you say yes to the next ten clients without dropping the care you built the business on.

what to do this week

Block one hour. Set the gate, write the handbook, wire one read-only connector, build the room for your leakiest workflow, and schedule one drudge task — in that order. Run it for two weeks and count the hours returned. Do not connect everything on day one; the point of one seat is that you can actually see what it is doing.