Cross-sector · 5 organisations, 26 installs · installed one module at a time
AI Operating System (AIOS)
Open a part, then hover a box for detail or a button to see it working.
AutomatedAIPersonYes or noSourceDataResult
Six OS modules around you, and the tools they connect to · hover anything, or click it to open that part
Google Drive · ContextOS
Existing plans, strategy documents and exports are imported into the context when the system is set up.
In: the documents the business already has
Connected through MCP.
Notion · ContextOS
Notion pages are imported the same way, so what the team already wrote down becomes context.
In: pages and databases
Connected through MCP.
Google Calendar · DataOS
Today's and tomorrow's events are collected each morning, so the brief knows what the day holds.
In: events, attendees and times
Connected through MCP.
Google Sheets · DataOS
The figures a business already keeps in spreadsheets are collected into the database as a daily snapshot.
In: the numbers, once a day
Connected through a Google service account.
Pipedrive · DataOS
The CRM. Deals, contacts and their history come in, and notes and next steps go back after every call.
In: deals, contacts and history
Out: notes and next steps, once approved
Any CRM connects the same way.
Fireflies · IntelOS
Joins calls on Zoom or Google Meet and transcribes them word for word.
In: every meeting, as a searchable transcript
Connected through MCP.
Slack · IntelOS
Messages from the channels the bot is invited to are stored and searchable alongside the meetings.
In: channel messages, day by day
Connected through MCP.
Telegram · CommandOS
The AIOS on a phone. The 07:00 brief, the reports and the drafts to approve arrive here.
Out: the brief, reports and drafts
In: approvals, voice notes and photos
A Telegram bot with the whole workspace behind every answer.
Gmail · CommandOS
The routines read new threads and leave replies as drafts in the business's own voice.
In: new threads and replies
Out: drafts, sent only after approval
Connected through MCP.
ClickUp · CommandOS
The task manager. Actions from each meeting become tasks with an owner and a due date.
In: open tasks and their deadlines
Out: new tasks, prioritised by deadline
Connected through its API.
Claude Code · BuildOS
The agent every layer runs on. It reads the context at the start of each session, runs the routines and builds each new system.
The model is chosen per task, so each system stays portable across vendors.
VS Code · BuildOS
Where the workspace opens at the desk: every brief, plan, source file and output in one folder tree.
The same workspace answers from a phone through Telegram.
MCP connectors · BuildOS
The connector each tool comes in through. MCP gives the agent a tool, and a skill says how and when to use it.
When a project needs a tool the system lacks, BuildOS connects it once and adds the skill to the bank.
GitHub · InfraOS
A private repository holds a backup of the whole workspace, pushed by /commit at every checkpoint.
Out: every version, off the machine
If a laptop dies, the workspace comes back down in one step.
A · ContextOS
One folder per business, loaded by /prime at the start of every session:
The company and its strategy
Its people and processes
Its numbers and standing rules
A memory that outlives the session
Google DriveNotion
B · DataOS
What gets collected, from which tools, and where it lands. Collectors run at 06:00 into one local database, so every session starts with current numbers.
The inbox and the task list are collected the same way.
Google CalendarGoogle SheetsPipedrive
C · IntelOS
Every meeting and message is transcribed, classified and searchable. Actions and owners are pulled out and fed back into the context.
Summed up each morning in the 07:00 brief.
FirefliesSlack
D · CommandOS
3 named routines run on a clock and report only what changed. Drafts wait in Gmail, tasks land in ClickUp, and approvals come back from Telegram.
TelegramGmailClickUp
E · BuildOS
Every new system gets a brief, a dated plan, synthetic data, source and output, built in Claude Code to the written standards.
Each new capability joins a shared skills bank, so install 4 costs less to deliver than install 1.
Claude CodeVS CodeMCP connectors
F · InfraOS
Underneath everything: git from the first day, /commit at every checkpoint, a living changelog and a private GitHub backup.
Every note, update and version stays retrievable.
gitGitHub
G · FounderOS · you, in the middle
Every layer works for the person in the middle. The agent drafts, and a person sends, submits, deletes and deploys.
Installed for other founders one module at a time:
Context first, because every layer reads it
Then data, so the numbers are live
Then intelligence, then automation
Build last, on foundations that hold
26 installs across 5 organisations and one consulting practice. 19 people use it every day.