AI SYSTEMS & CO-DESIGN
What’s an AI operating system?
It’s the layer that runs your repeatable work. Everything that comes into the business — enquiries, bookings, jobs, paperwork — flows through one system: it comes in, a decision gets made, the action happens, and a record is kept. Nothing that speaks in your voice goes out without your say-so.
Pick your kind of business, and watch a made-up working day run through it.
An owner-operator whose evenings keep disappearing into admin.
RULESprogrammatic, deterministic — same input, same result
AIreading, drafting, filing the messy stuff — never sending
HUMANdecisions and approvals — anything written in your voice, anything sensitive
THE WHOLE DAY — STEP BY STEP
Every activity a day might bring. Pick any one to see exactly what touches it, in order, including where the path splits and who chooses.
6:58 AM — OVERNIGHT ENQUIRY — WEBSITE FORM
Web form
INBOUND
- TAKES
- A submission from your website at 6:58 AM.
- HOW IT WORKS
- No interpretation needed — the fields decided the shape when you built the form. What arrives is exactly what was typed, so there is nothing here to get wrong.
- HANDS ON
- “Overnight enquiry — website form” — already structured, because the fields asked the questions.
Intake processor
RULE
- TAKES
- Everything captured from your website form, plus who it came from and when.
- HOW IT WORKS
- Bundles and timestamps, and that is all. Deterministic — no model runs here — and it makes no judgement about what the item is. Capture and interpretation are separate on purpose, so a bad read can never lose the original.
- HANDS ON
- One item in the queue: “Overnight enquiry — website form”, 6:58 AM.
Router
RULE
- TAKES
- “Overnight enquiry — website form”, and the fact it arrived by your website form.
- HOW IT WORKS
- Three roads out, tested in your order. First: is it on your sensitive list — complaints, disputes, anything legal, anything about a person's safety? Then straight to you, untouched. Second: does it match a shape your rules already handle — a form field, a date threshold, a scheduled check? Then the rules engine. Otherwise it's a person's own words with nothing for a rule to match on, and the model reads it. First test to match wins, and the list and the order are yours.
- HANDS ON
- To the rules engine. It didn't match the sensitive list, and it does match a shape your rules already handle.
Rules engine
RULE
- TAKES
- “Overnight enquiry — website form” — a shape your rules already recognise.
- HOW IT WORKS
- Checks the item against the rules you've written — sender, form type, date thresholds, amounts — and each rule names what happens next. No model, no per-item cost, same answer every time. If nothing matches it doesn't guess or fail quietly: it falls through to you.
- HANDS ON
- Classified without a model, and ready for: reply drafted → you approve → sent.
Lookup
LOOKUP
QUERIES
- Your services list, to know what they're asking about
- Your reply templates
- Any history for this email address
- TAKES
- The understood item, and nothing else yet.
- HOW IT WORKS
- Reads before anything is built. Every source it queries is one you already keep — the system reads them live rather than holding a second, stale copy. If a lookup comes back empty or ambiguous it stops and asks you; it does not fill the gap with a plausible guess.
- HANDS ON
- 3 sources read, and nothing written yet.
Draft builder
RULE
- TAKES
- The tagged item, plus your own templates, rates, hours and rules.
- HOW IT WORKS
- Assembles from your own templates, rates, hours and booking rules. Where a model writes the prose the figures still come from your rate card, never from the model. It has no ability to send — a draft is all it can produce.
- HANDS ON
- Reply drafted → you approve → sent. Saved, not sent.
Approval gate
PERSON
- TAKES
- Reply drafted → you approve → sent — with the original “overnight enquiry — website form” beside it.
- HOW IT WORKS
- Three ways out and only you can pick: approve it as it stands, edit then approve, or reject it. Rejecting keeps the draft so the reason is on the record. Nothing here times out into sending — an unanswered draft simply waits.
- HANDS ON
- Your decision, recorded either way.
THE DECISION
You read the draft. Two ways out, and only you can choose:
APPROVE OR EDIT
Send engine
OUTBOUND
- TAKES
- Reply drafted → you approve → sent, approved by you.
- HOW IT WORKS
- Sends exactly what you approved, to the address or number it arrived from. It cannot compose, edit or re-address — if the wording is wrong, it was wrong when you approved it.
- HANDS ON
- Sent under your name. Logged as: enquiry logged, follow-up set.
REJECT
Nothing sends
RULE
- TAKES
- Your rejection.
- HOW IT WORKS
- Stops. The draft is kept so you can see what was proposed, and why you said no.
- HANDS ON
- A closed item — with the decision on it.
Either way, the next step is the same — both routes are recorded.
Records
RECORD
ALSO UPDATES
- Job & client records
- A follow-up date on the calendar
- TAKES
- “Overnight enquiry — website form”, every decision made about it, and whatever went out.
- HOW IT WORKS
- Append-only: it cannot overwrite or delete. A correction is a new entry beside the original, not a replacement — which is what makes the record answer “what did we actually do” months later.
- HANDS ON
- Enquiry logged, follow-up set — permanent, searchable, yours.
Daily summary
OUTBOUND
- TAKES
- The day's filed items.
- HOW IT WORKS
- Collects everything filed since the last run and reports it. It has no ability to act on what it finds — if something needed doing, a rule or a person did it hours ago.
- HANDS ON
- One line in tonight's summary: enquiry logged, follow-up set.
That's the admin that used to happen after dinner — done in the gaps, with you approving what matters.
End of day: 8 items handled — 4 sorted by rules, 3 read by AI, 1 straight to a person.
6 needed your tap before anything went out. 2 were filed without leaving the business. Nothing sent itself.
THE ECOSYSTEM
Every function stands alone. Linked, they compound.
The eight master functions — each one a working product on its own. The small chips are the shared plumbing each one brings with it.
AI voice answering
AI MODEL
Answers the calls you can't take, has a real conversation, captures who / what / where — and hands over a structured message, not a missed call.
Works on day one with just your phone number — every integration it uses comes with it.
HOW IT PLAYS OUT
01 · A caller needs a tradie. Dave's on the roof — the phone rings out.
FED BY — nothing — this is where work enters
FEEDS — Transcription
Want this one running in your business — on its own, or wired into the rest?
PRINCIPLE 01
Deterministic first
Deterministic first. AI only where it beats a rule on cost or speed. If a rule can do the job, a rule does the job — cheaper, faster, and it never hallucinates.
PRINCIPLE 02
Designed with the people who’ll use it
Designed with the people it's for. Their vocabulary and workflow, not an assumed version. The vocabulary and workflow in the system are theirs, not the software’s.
PRINCIPLE 03
Humans hold the keys
Intake, decision, action, record — with a human approving anything that goes out. And when it’s handed over, the credentials, records and documentation are yours.
WHO WE WORK WITH
Small Australian businesses
Owner-operators and small teams across the Hunter and Central Coast who need the thing built and running, not a retainer and a roadmap.
Community organisations, NGOs and funders
Programme work where the system has to survive poor connectivity, shared devices and real accountability — and where the community, not the vendor, owns the record.