The seven core business data domains that should be connected to an AI Operating System. Connecting all seven gives the AIOS enough context to act as a fully informed executive assistant rather than a generic chatbot.
The seven domains
| Domain | Example tool | Data type |
|---|---|---|
| Revenue | QuickBooks, Stripe | P&L, cash flow, runway |
| Customer | CRM, community platform | Members, deals, activity |
| Calendar | Google Calendar | Events, deadlines, availability |
| Comms | Gmail, Slack | Emails, messages, threads |
| Tasks | ClickUp, Notion | To-dos, projects, owners |
| Meetings | Fireflies | Transcripts, decisions, action items |
| Knowledge | LLM wiki, Obsidian vault | Articles, notes, SOPs |
Key points
- All seven domains map to the Connections step (C2) in the Four C’s of an AI Operating System [src-013]
- Prioritise by pain: start with the domain that wastes the most time or causes the most friction [src-013]
- Each connection should use a direct API with a curated reference markdown file where possible, not necessarily an MCP server [src-013]
- “A company where every operator runs a personal AIOS is a company that is truly AI ready and all the data is AI ready.” [src-013]
Related entities
Related concepts
- Four C’s of an AI Operating System — C2 (Connections) is where these domains plug in
- Scoped API Key Pattern — security model for each domain connection
- MCP vs CLI Token Trade-off — preferred integration method
Source references
- [src-013] Nate Herk — “Build & Sell Claude Code Operating Systems (2+ Hour Course)” (2026-05-01)