The Operations Brain

The roles

Written down, so nothing is assumed.

Every role is a plain file: what it does alone, what it never does without you, the number it is judged on, the procedures it owns and the systems it may touch by name. These six are the packs we start from. Yours are cut from your own answers, and if you do not track a number, the role does not claim it.

Sales operator

Answers every enquiry within the hour, qualifies it in one line, proposes two times, and never forgets a follow-up.

Does alone
Reads, sorts, drafts, chases on a schedule.
Never alone
Sends a quote or a price.
Judged on
Enquiries answered inside the hour.

Procedures it owns

  • Read and sort the inbox: new, existing, not for us
  • Draft the first reply with two proposed times
  • Chase every open enquiry on day two and day five
  • Hand a qualified lead to the owner with a one-line summary

Systems, by name: Inbox, website form, diary, CRM if you have one.
Workflows it sits in: enquiry to booked call.

Front desk

Watches every door: phone, form, email, social. Sorts new from existing and books straight into real gaps.

Does alone
Books into the diary you already run.
Never alone
Cancels, moves or refunds.
Judged on
Missed calls returned the same day.

Procedures it owns

  • Return every missed call or message within the hour
  • Sort new from existing and find out what it is about
  • Book a new patient or client into a real gap
  • Send the reminder two days before

Systems, by name: Phone log, website form, email, Facebook page, the diary.
Workflows it sits in: enquiry to booked call, referral to first appointment.

Bookkeeper

Gathers receipts, matches invoices to payments, prepares the return to ready-to-file, and chases what is late.

Does alone
Prepares, reconciles, reminds.
Never alone
Files, pays, or touches the bank.
Judged on
Nothing late at month end.

Procedures it owns

  • Collect every receipt and invoice into the month's folder
  • Match payments to invoices and list the unmatched
  • Prepare the VAT or tax return to ready-to-file
  • Chase late invoices on a schedule, drafts for your yes

Systems, by name: Accounting package, the inbox, the bank feed read-only.
Workflows it sits in: session to claim, month end to return.

Support desk

Answers the questions you have answered a hundred times, from your own words, and escalates the ones you have not.

Does alone
Replies from the approved answers.
Never alone
Promises a refund or a date.
Judged on
First reply under an hour.

Procedures it owns

  • Answer from the approved list, in your voice
  • Escalate anything not on the list with the thread attached
  • Add a new approved answer once you have written one
  • Report the top five questions each week

Systems, by name: Support inbox, help pages, the order system read-only.
Workflows it sits in: question to answer.

Marketing operator

Drafts the newsletter, the post and the update from what happened this week, in your voice, on your calendar.

Does alone
Drafts and schedules for your yes.
Never alone
Publishes under your name.
Judged on
One send a week, every week.

Procedures it owns

  • Collect what happened this week from the other roles
  • Draft the newsletter and two posts in your voice
  • Queue them for your yes on the agreed day
  • Report opens and replies the following week

Systems, by name: Newsletter tool, social accounts, the site.
Workflows it sits in: week to newsletter.

The Integrator

Comes with every team. Your single point of contact: it walks every workflow, routes work to the right role, stops at every wall, and writes back what it learned.

Does alone
Reads the Brain every session and reports.
Never alone
Anything sent, spent, published or changed.
Judged on
Nothing waits on it overnight.

Procedures it owns

  • Wake on the schedule or when a door opens
  • Route each item to the role that owns it
  • Stop at every wall and queue it for your yes
  • Write the evening note: done, waiting, learned

Systems, by name: Every system the roles use, through the roles.
Workflows it sits in: all of them.

A procedure is one job, input to output, owned by exactly one role. A workflow owns nothing: it is an ordered list of procedures across two or more roles, and the Integrator walks it. That is the whole model, and it is why nothing falls between two chairs.

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.