ChiefOS turns a one-page definition of your AI assistant — who it is, what it does daily, what it can touch — into a running Chief of Staff on the AI platform you already use.
No code required. Set up in a day, not a month.
Most AI helpers are chat apps on someone else's platform. ChiefOS treats your assistant like a job description: write it once, run it anywhere.
Answer a guided setup — or paste your own — covering nine fields: persona, voice, priorities, daily rituals, integrations, routing rules, and approval guardrails. It's a plain JSON file. You own it.
ChiefOS compiles your spec into a working setup on the AI platform you already use — Hermes today, Claude Code next, more after. Swap platforms later and recompile; nothing is rewritten by hand.
Your CoS doesn't wait to be asked. Morning checks, end-of-day wraps, weekly reviews, invoice nudges — on your schedule, with human approval built in before anything sends, posts, or spends.
Answer a few short questions about your business — the Builder interviews you, then hands you the spec for your own Chief of Staff. Takes about 10 minutes, right here.
Regulated business (healthcare, legal, financial)? The Builder will route you to our managed tier — self-hosted, from $2,000/mo.
Not a chatbot prompt. A complete operating definition — versioned, diffable, and portable between platforms.
| # | Field | What it captures |
|---|---|---|
| 1 | Persona | Name, role, who it serves, operating principles |
| 2 | Voice | Tone, length, formatting rules — how it talks and writes |
| 3 | Memory policy | Where durable facts live — declared, never locked in |
| 4 | Priorities | What matters more than noise — and what's off-limits |
| 5 | Rituals | Recurring work: morning check, evening wrap, weekly review |
| 6 | Integrations | Email, calendar, CRM, chat — declared, not hardcoded |
| 7 | Routing | Sensitive work stays local; cloud only when it's safe |
| 8 | Guardrails | What needs a human yes before it happens |
| 9 | Tools | What it can touch — and what it never can |
The spec is an open JSON Schema. Download it: spec.schema.json
Every plan starts the same way — chat with the Builder, get your spec, and you own it. The only difference is who runs your Chief of Staff.
A chatbot answers when you ask. A Chief of Staff runs on its own: it checks in every morning, watches your inbox and pipeline, drafts the follow-ups, and stops to ask before it sends anything. ChiefOS just makes that setup portable — so you're not rebuilding it every time a platform or model changes.
No. On Hosted ($99/mo) your AI usage is included up to a fair-use limit — no API keys to set up, and we'll tell you before anything ever costs extra. On Self-serve (DIY) you bring your own model key, which means you control that cost directly. Either way, ChiefOS is the definition layer — your spec, your data, no lock-in.
Hosted ($99/mo) is fully automated — we deploy your Chief of Staff, keep it running, and fix things when platforms change. Managed (from $750/mo) adds a human in the loop: monthly tune-ups where we review what your CoS did and improve it, plus strategy guidance — and it's the tier for regulated businesses.
It stays where it already lives — your email, your CRM, your calendar. ChiefOS doesn't store your business data, and our spec never captures it. For regulated industries we offer fully self-hosted setups where nothing leaves your server.
Yes — that's the whole point. Your spec is a plain, portable definition. Recompile it on a new platform and your CoS shows up with the same persona, priorities, and daily rituals. Only the plumbing changes.
No. ChiefOS self-serve is for general business data. If your work touches regulated data — patient records, client files, or account information — it belongs on our Managed tier: fully self-hosted (data never leaves your server), HIPAA BAA where required, run and monitored by our team, from $2,000/mo. Book a call and we'll scope it properly.
Pilot slots are limited. Book a 30-minute call and we'll map your spec live — you keep the file either way.
Book your call