The Operations Brain

How it works

One conversation, then files. No dashboard to learn.

The files are the product. Everything below is how they get written, wired and kept honest. It is a fixed piece of work followed by a bounded month, and every step has something you can read.

The interview

Nineteen questions, one at a time, with a person. Not a form. The interviewer reads your website first and checks what they think they know rather than asking you to repeat it. Every guess is confirmed or corrected, and every decline is kept.

“How does work arrive? I count four doors: the phone, the website form, referrals by email, and people walking in. Which of those are real, and is there one I have missed?”

The Brief

Your answers as one typed document: the roles, what each does alone and never alone, the procedures, the workflows that cross them, the walls, the numbers you actually watch, and the systems by name. You read it back and say yes. Nothing you did not say gets in, and no target is invented.

“Two numbers recorded: did-not-attends under five percent, checked monthly, and claims ready within seven days, checked weekly. New-patient wait noted as not tracked, so I will not invent a target.”

The Brain

The Brief becomes twenty to forty plain files in a private Brain on your own PageMotor site, checked so every workflow step points at a procedure its role owns. JSON for what the AI queries, prose for what it reads. Any AI you connect reads it every session.

# brain: your-business (about thirty files) CLAUDE.md read first, every session owner.md you, and the walls org.json the graph: who owns what integrator.md operators/ front-desk/ operator.json charter.md procedures/ return-the-door.{json,md} book-appointment.{json,md} claims/ operator.json charter.md procedures/ prepare-claim.{json,md} workflows/ referral-to-first-appointment.{json,md} session-to-claim.{json,md}

Wired, by name

Your diary, inbox, forms, portals and accounts are named in the files, and the keys are kept elsewhere. No password ever lives in the Brain. What a role may touch is written next to what it may never touch.

Scheduled

Nothing runs by itself until something wakes it. We set the schedule and the inbound doors so the Integrator runs when work arrives: first thing, on a timer, or when an enquiry lands. That is the honest limit, and it is stated rather than hidden.

Thirty days of tuning

A person reads what the team did each week and adjusts the roles: a wall moved, a procedure sharpened, a number corrected. Then the owner’s manual: how to read the Brain, change a wall, add a role, and leave. After that, a bounded monthly call, never an open line.

Every write, snapshotted

The Brain is versioned underneath, so a change can be read back and undone. Access is per Brain. The files stay on your domain, and if you stop, they stay yours.

The walls come first

Before a role is written you name what must never happen without a yes. The team reads that list every session, and the list is yours to change.

Ask for the interview

Tell us which job you would hand over first. A person comes back within one working day with a time, and a number for your roles in writing before anything starts.

Ask for the interview

Honest limits: nothing runs by itself until the scheduler is set, no password ever lives in the files, access is per Brain, and every write is snapshotted underneath. Delivered on PageMotor, on your own domain, as files any AI can read.