One assistant that knows 1,200 buildings.
Tom designed and built an AI operations platform for a strata management business across New South Wales and Queensland. Twelve specialist agents work inside Microsoft Teams and Outlook, connected to the management system, SharePoint and the shared mailboxes, and more than 50 staff use them every day.
Morning briefing for my portfolio, please.
Three things need you today.
Building A: the annual fire safety statement is due in 21 days and no contractor is booked.
Building C: the committee approved the lift quote overnight. The work order is drafted for you to release.
Seven owner emails came in since yesterday. A reply is drafted for each.from the compliance register, maintenance and the shared mailbox
Can the owner of Lot 12 in Building C keep a dog?
The building's by-laws allow a pet with the committee's written approval. Here is the clause, and the application form to send.General FAQ specialist, from the building's own documents
Illustrative screen. Buildings, people and figures are invented.
- 50+staff using it every day
- 12specialist agents
- 30+tools they can call
- 464compliance items tracked
Figures as at November 2026. The client is a strata management business operating across New South Wales and Queensland, unnamed at its request.
The situation.
A strata manager looks after hundreds of buildings, each with its own owners, committee, by-laws, contractors, insurance and compliance dates. The information to do the job existed; it was spread across the management system, SharePoint, shared mailboxes and people's memories.
- The same owner questions, answered from scratch, hundreds of times a week.
- Notices and emails drafted by hand from templates that lived in different places.
- Compliance dates tracked building by building, with no portfolio view.
- Legislation that differs between New South Wales and Queensland, and changes.
- Experienced managers carrying the procedures in their heads, and new staff learning by asking.
What Tom built.
Not a chatbot bolted onto a website: an operations platform, designed and built end to end, that sits inside the tools the team already uses and works from the business's own systems.
An assistant in Microsoft Teams
Managers ask questions in plain English where they already work. An orchestrator holds the building context, picks the right specialist and remembers what it has been told. Each specialist has a written runbook that says exactly what it does, what it must not do, and which tools and data it may use.
An email agent on the shared mailboxes
Owner and tenant emails are read as they arrive, matched to an owner and lot, classified, and answered with a draft from the right template. Managers see a queue of drafts to approve, with unknown senders and anything sensitive held back for a person.
Building knowledge, reviewed by people
Facts about each building are extracted from email, SharePoint and the management system and put in front of managers to approve or reject. Approved knowledge feeds every later answer, so the assistant gets more accurate the longer it runs.
A compliance register for the whole portfolio
Fire safety statements, insurance, electrical and pool certificates, stair pressurisation and more, across 464 tracked items: what is overdue, what is due in 30 and 90 days, which supplier does it and who owns the follow-up.
Mission Control
One screen for the operations lead: escalations waiting for a person, approvals pending, compliance alerts and open maintenance, with every agent's activity visible.
The platform underneath
An agent registry and message bus, shared memory, circuit breakers that stop a misbehaving agent, analytics on conversations, response times, fallbacks and escalations, and a review tool for every conversation.
- Pet request, Lot 12, Building CReply drafted from the pet enquiry template, form attacheddraft ready
- Levy balance query, Lot 4, Building ABalance and due date from the management systemdraft ready
- Water leak in the car park, Building BWork order drafted for the building's plumberdraft ready
- Sender not recognisedNo matching owner or lot: nothing draftedheld for a person
- Dispute between neighbours, Building ASensitive: summary only, no reply draftedheld for a person
Agent activity
- Email drafting14 replies drafted, 11 approvedrunning
- ComplianceTwo fire safety statements moved to due within 30 days2 alerts
- DocumentsCould not find a by-law for Building D: passed to a personescalated
- Levies and finance36 questions answered, none escalatedrunning
Illustrative screens: the managers' review queue and Mission Control. Buildings, people and figures are invented.
Watch a manager's morning.
A 46-second film, with no sound to turn on: a question in Teams, a drafted reply approved in the shared mailbox, and what the operations lead sees in Mission Control.
Read what the film shows
- In Teams. A manager asks for a morning briefing in plain English. An orchestrator picks the specialists the question needs (briefings, compliance, maintenance and email drafting) and answers with the three things that need her today, each with its source. A second question, whether an owner can keep a dog, is answered from the building's own by-laws.
- In the shared mailbox. Owner emails arrive with a reply already drafted. The manager opens a pet request, reads the drafted reply and its attachment, and approves it. Only then is it sent. An email from a sender the system doesn't recognise and a dispute between neighbours are held for a person, with nothing drafted.
- Mission Control. The operations lead sees escalations waiting for a person, approvals pending, compliance alerts and open maintenance, and what each agent did, including a question the documents specialist could not answer and passed to a person.
Twelve specialists, one conversation.
A manager never picks an agent. The orchestrator reads the question, resolves which building it is about, and hands it to the specialist whose runbook covers it. Each one knows what it is not allowed to answer, and who to pass it to.
Legislation
Answers NSW and Queensland strata law and by-law questions, with citations to the Acts.
Documents
Finds the by-laws, AGM notice, inspection report or levy notice for a building and hands over the file.
Owner services
Looks up owners, committees, contacts, insurance and contracts in the management system. Read-only.
Levies and finance
Levy balances, arrears, budgets, fund balances and who pays the insurance excess.
Compliance
Fire safety statements, insurance renewals, electrical and pool certificates: what is due and when.
Maintenance
Open work orders, defects and which contractor the building uses for what.
AGM
Assembles the AGM pack, drafts motions from approved templates and runs the post-meeting actions.
Email drafting
Drafts notices and emails from the firm's templates straight into the manager's Outlook.
Internal process
How the business does things: onboarding a building, work order procedure, agency agreements.
General FAQ
By-law and procedure questions that don't fit a specialist, answered from the building's own documents.
Routine enquiries
Inbound owner emails such as pet requests, answered from configured, approved responses.
Briefings and portfolio
Morning briefings, portfolio summaries, attachment analysis and change-of-owner processing.
Legislation
Answers NSW and Queensland strata law and by-law questions, with citations to the Acts.
Documents
Finds the by-laws, AGM notice, inspection report or levy notice for a building and hands over the file.
Owner services
Looks up owners, committees, contacts, insurance and contracts in the management system. Read-only.
Levies and finance
Levy balances, arrears, budgets, fund balances and who pays the insurance excess.
Compliance
Fire safety statements, insurance renewals, electrical and pool certificates: what is due and when.
Maintenance
Open work orders, defects and which contractor the building uses for what.
AGM
Assembles the AGM pack, drafts motions from approved templates and runs the post-meeting actions.
Email drafting
Drafts notices and emails from the firm's templates straight into the manager's Outlook.
Internal process
How the business does things: onboarding a building, work order procedure, agency agreements.
General FAQ
By-law and procedure questions that don't fit a specialist, answered from the building's own documents.
Routine enquiries
Inbound owner emails such as pet requests, answered from configured, approved responses.
Briefings and portfolio
Morning briefings, portfolio summaries, attachment analysis and change-of-owner processing.
How it is built.
Four layers. The team works in the top one and never sees the rest, which is the point.
- Where the team worksMicrosoft Teams, Outlook, Portal, Owner web assistant
- The assistantOrchestrator, 12 specialist agents, Runbooks, Shared memory
- Tools and dataManagement system, SharePoint & mail, Document search, Legislation
- GuardrailsApproval before send, Escalate to a person, Analytics & audit, Circuit breakers
Production, not pilot
Read-only where it matters
The specialists that look up the management system can read, not write. Changes still go through the system of record, by a person.
Nothing sent without approval
Every email and notice is a draft until a manager approves it. The assistant never speaks to an owner on its own.
Runbooks, not vibes
Each specialist's scope, exclusions, tools and data sources are written down and versioned. When it doesn't know, it says so and escalates.
Watched in production
Fallback and escalation rates, response times and knowledge-base health are measured, and a circuit breaker isolates any agent that starts failing.
Watch it work.
Three runs that mirror what the platform does every day. The buildings and figures are invented; the tools and the flow are the real ones.
What changed for the business.
The work didn't disappear. It moved from finding and drafting to deciding and approving, which is what the managers are paid for.
- Managers ask Teams instead of searching four systems and a shared drive.
- Owner emails arrive with a reply already drafted, so the job is to read and approve.
- Compliance across the whole portfolio is visible on one register, with owners and due dates, rather than in each manager's head.
- New staff get the business's own procedures and the legislation answered the same way, with citations, on their first day.
- AGM packs are assembled from the systems rather than compiled by hand.
- The operations lead can see what the agents did, what they escalated and what is waiting for a decision.
Led by Tom, from architecture to production.
The architecture, the agents and their runbooks, the integrations with the management system, SharePoint and Outlook, the email agent, the compliance register and the portal the operations team uses to run it. Built to work inside a business he knows from the inside, and now running every day. It is the approach Spurbuck Advisory now brings to every client: agents designed around how the work actually flows, built into the systems already in place, and measured on the time and cost they take out.
About TomQuestions people ask us
What did Tom Buckley build for the strata management business?
An AI operations platform with an orchestrator and twelve specialist agents in Microsoft Teams and Outlook, an email agent on the shared mailboxes, building knowledge reviewed by staff, a portfolio compliance register and a Mission Control screen, connected to the management system, SharePoint and email.
How big is the platform?
As at November 2026 it covers more than 1,200 buildings, tracks 464 compliance items, gives its 12 specialist agents more than 30 tools, and is used daily by more than 50 staff.
Can Spurbuck Advisory build something similar for another business?
Yes. The same approach, an orchestrator with specialist agents, runbooks, read-only access to systems of record and human approval, applies to any business whose staff spend their days finding information across several systems.