CEOS, an AI chief of staff
A chief-of-staff platform for a UK property group, where six AI director agents run the admin across email, calendars and business data, and nothing important happens without a signed approval.
Solo architect and developer
6 director agentsbehind one chief of staff, with signed approval on every action that matters

- Chief of staff + 6 directors
- Agents
- Signed approval tokens
- Approvals
- Client's own Azure tenant
- Hosting
- Installable PWA
- App
- FastAPI
- Python
- Next.js 14
- TypeScript
- Microsoft Graph
- Dataverse
- LiteLLM
- OpenRouter
- Azure Container Apps
- KEDA
- Key Vault
- Bicep
The problem
The leadership of a growing property group was running the business from their inboxes. Email, calendars, tenancy and operational data lived in different places, and every decision meant someone gathering the facts by hand before anyone could act. They wanted the admin handled for them, without handing an AI the keys to the business.
What I built
CEOS is a chief-of-staff platform, built against a detailed product spec and delivered in milestones.
- A chief of staff and six director agents. The chief of staff takes each request and hands it to the right director, each one responsible for its own area of the business.
- Connected to the tools they already use. Email, calendars and files through Microsoft Graph, and the business’s records in Dataverse.
- Nothing important without sign-off. Every action an agent takes is checked against what it’s allowed to do, anything that matters needs a signed approval token, and the whole trail is written to an audit log.
- Any model, one gateway. Language models sit behind a LiteLLM gateway, so a model can be swapped without touching the agents.
- Inside the client’s own cloud. All the infrastructure runs in the client’s Azure tenant (Container Apps that scale on demand, secrets in Key Vault), defined as code so it can be rebuilt exactly.
- An app for the team. A Next.js progressive web app that installs on phones and laptops. Its types are generated from the backend’s API contract, so the two can’t drift apart.
The foundations and the director agents are signed off. The integration and the app are being completed now.
The result
The directors get a chief of staff that prepares, drafts and chases across the business, while every decision that matters still waits for a person. Because it runs entirely inside the client’s own Microsoft cloud, their data never leaves infrastructure they own.
This build is covered by a non-disclosure agreement, so I can't link to the live system. Happy to walk you through it on a call.
Similar problem? Book a call
Tell me what you are trying to fix. If a Blueprint is the right next step, I will say so; if not, you leave with a straight answer.