Product Hunt launched an entire "AI Chief of Staff" category in 2025. Bond raised $3M. Alfred_ and Ambient started charging $50-300 a month. Everyone agrees that founders need an AI that manages operations, not just answers questions. But nobody built one that's free, runs locally, and covers email, CRM, invoices, proposals, content, and meetings in a single tool.
So I built one. It's called Founder OS. It runs inside Claude Code. And it has 82+ slash commands across 33 namespaces, all open source, all free.
Key Takeaways
- Founder OS is a free, open-source Claude Code plugin with 82+ commands that acts as an AI chief of staff for solo founders
- Covers 4 pillars: Daily Work, Code Without Coding, MCP & Integrations, and Meta & Growth — replacing 6+ SaaS subscriptions
- A human chief of staff averages $167,954/year and rising (Chief of Staff Network, 2025); SaaS tools cost $600-3,600/year; Founder OS costs $0
- Connects to Notion, Gmail, Calendar, Drive, Slack, and web search through 7 MCP integrations
- Install in under 5 seconds:
npx founder-os@latest --init
What Is an AI Chief of Staff (And Why Do Founders Need One)?
Bond AI secured $3M in seed funding in December 2025 to build an "AI Chief of Staff for CEOs" (SignalBase, 2025). The category is real. Investors are writing checks. And the reason is simple: founders are drowning in admin work they shouldn't be doing.
Entrepreneurs spend 36% of their work week on administrative tasks (email, scheduling, bookkeeping, follow-ups), according to a survey of 251 US entrepreneurs (Time Etc / Censuswide, 2023). That's more than a third of your week that never touches product, sales, or strategy.
A traditional chief of staff solves this. They triage your inbox, prep your meetings, track your follow-ups, and keep the operational machinery running. But the average Chief of Staff salary hit $167,954 in 2025, up 8.5% from the prior year (Chief of Staff Network, 2025). With bonuses and equity, Glassdoor puts the total compensation at $217,399 (Glassdoor, 2026).
An AI chief of staff does the same job. Not as a chatbot you ask questions to, but as a proactive system that triages, prepares, tracks, and reports on its own. The difference between Founder OS and a SaaS tool? Your data never leaves your machine. There's no monthly subscription. And you can see exactly what every command does, because it's all markdown.
How Is Founder OS Different From Other AI Chief of Staff Tools?
Bond's $3M raise valued a 5-feature product at millions, while tools like Ambient and Alfred_ charge $30-50 per month for fewer than 10 features each (SignalBase, 2025). Founder OS ships 82+ commands for $0. Most AI chief of staff tools are hosted SaaS platforms where you send your data to their servers and get summaries back. Founder OS runs entirely inside Claude Code on your machine, connects directly to your tools through MCP (Model Context Protocol), and gives you the actual commands instead of a dashboard you can't customize.
Here's what that looks like in practice. Where Ambient says "we'll handle your follow-ups," Founder OS gives you /founder-os:followup:check. You can read the command file, see exactly what it does, and modify it. Where Alfred_ says "AI email management," Founder OS gives you a four-agent pipeline: triage, action extraction, response drafting, and archive recommendations. You choose the speed-quality tradeoff with a --team flag.
Quick Comparison
| Feature | Founder OS | Ambient | Alfred_ | Bond |
|---|---|---|---|---|
| Price | $0 (MIT license) | ~$50/mo | ~$30/mo | Custom |
| Commands | 82+ | ~10 features | ~8 features | ~5 features |
| Integrations | 7 MCP servers | 3-4 APIs | 3 APIs | 2-3 APIs |
| Open source | Yes | No | No | No |
| Local-first | Yes | Cloud-only | Cloud-only | Cloud-only |
| Extensible | Full plugin system | No | No | No |
| Dual mode | Fast + --team | Single mode | Single mode | Single mode |
The extensibility gap is the real differentiator. Every SaaS tool gives you a fixed feature set. Founder OS gives you a plugin architecture. Don't like how inbox triage works? Open the command file (it's markdown) and change it. Need a workflow that doesn't exist? The same factory system that built the original 33 namespaces is available to extend them.
Entrepreneurs who are "expert delegators" are 82% likely to have seen revenue growth, compared to 66% for non-delegators (Time Etc / Censuswide, 2023). The question isn't whether to delegate operational work. It's whether to delegate it to a $168K hire, a $50/month SaaS tool, or a free plugin you own.
What Does the Daily Work Pillar Actually Do?
The Daily Work pillar covers 8 namespaces and handles the tasks most founders waste their mornings on. Each command runs in under 30 seconds. Knowledge workers spend 28% of their workday (roughly 2.6 hours) just reading and answering email (McKinsey Global Institute, 2012). That's before meetings, follow-ups, or the actual work.
Here's what Founder OS automates in Pillar 1:
/founder-os:inbox:triage— Scans Gmail, categorizes by urgency, extracts action items, drafts responses. Four-agent pipeline: triage, action extraction, response drafting, archive recommendations./founder-os:briefing:briefing— Pulls Gmail, Calendar, Notion tasks, and Slack mentions into one structured morning summary. Parallel gathering pattern — all sources fetch simultaneously./founder-os:prep:today— Generates meeting prep documents for every meeting on today's calendar. Includes attendee context, open items, and framework-based talking points./founder-os:followup:check— Scans your sent folder for emails awaiting response, tracks aging, and prioritizes nudges. Smart defaults: 3-day scan window, age-based tone selection./founder-os:review:review— Compiles a weekly review from completed tasks, meetings attended, and emails sent. Highlights wins, flags stale items./founder-os:actions:extract— Paste any text and it pulls out action items, creates Notion tasks with due dates and priorities./founder-os:meeting:analyze— Feed it a meeting transcript and it extracts decisions, follow-ups, topics discussed, and a one-paragraph summary./founder-os:morning:sync— The all-in-one: gathers from every source, synthesizes priorities, saves to Notion, and displays your day.
A Typical Morning With Founder OS
Before Founder OS, my mornings looked like this: open Gmail, scan 40 emails, open Calendar, check today's meetings, open Notion, review tasks, open Slack, check mentions. Four apps, four context switches, 45 minutes before I started real work.
Now? Three commands:
/founder-os:morning:sync # Everything in one summary
/founder-os:prep:today # Meeting prep for the day
/founder-os:inbox:triage # Email handledDone in under 5 minutes. That's 40 minutes recaptured every single day.
How Does Founder OS Handle Documents and Business Operations?
Seventy-five percent of SMBs are now experimenting with AI, and growing businesses adopt at even higher rates (Salesforce, 2025). The Code Without Coding pillar turns Claude Code into a back-office processor: invoices, proposals, SOWs, contracts, expense reports, competitive intel, and newsletters. No coding required.
Here are the 8 namespaces in Pillar 2:
/founder-os:invoice:batch— Drop a folder of PDF invoices and get structured data back: vendor, amount, date, line items, 14-category expense taxonomy. Pipeline+Batch pattern processes each invoice independently, then generates a summary table./founder-os:proposal:create— Generates a 7-section client proposal with 3 pricing packages (conservative, balanced, ambitious). Reads your business context files so every proposal sounds like you, not a template./founder-os:sow:generate— Statement of Work with 3 scope options. Uses the Competing Hypotheses pattern: three agents propose different scopes independently, then a lead agent synthesizes the best elements./founder-os:contract:analyze— Extracts key terms from a contract, detects risks, and compares against standard freelancer/agency benchmarks. Highlights what's unusual so you know what to negotiate./founder-os:report:generate— Feeds data sources through a 5-agent pipeline: research, analysis, writing, formatting, and QA review. Output is a polished report with charts./founder-os:expense:report— Aggregates invoice data and local receipts into a comprehensive expense report for any date range./founder-os:compete:research— Web research synthesized into a structured competitive intelligence report./founder-os:newsletter:newsletter— Full pipeline: research a topic across web, GitHub, Reddit, and changelogs, then outline and draft a newsletter.
Before I built these commands, a single client proposal took 2-3 hours. Write the scope, structure the pricing, format the document, review it. Now I run /founder-os:proposal:create, review the output for 10 minutes, and send it. The SOW generator is even faster; the three competing scope options consistently surface angles I wouldn't have considered on my own.
What Integrations Power the System?
MCP (Model Context Protocol) crossed 97 million monthly SDK downloads across Python and TypeScript by December 2025, with over 10,000 active servers in the ecosystem (Anthropic, 2025). Founder OS is built on this protocol layer, with 7 MCP integrations connecting to the tools founders already use.
Here's the integration stack:
- Notion CLI (21 namespaces) — The CRM backbone. 22 interconnected databases store everything: clients, tasks, meetings, invoices, content, goals. Companies is the central hub — every client-facing command relates back to it.
- gws CLI for Gmail, Calendar, and Drive (20 namespaces) — Email triage, calendar parsing, meeting prep, document access. One authentication command (
gws auth login) unlocks three services. - Filesystem MCP (8 namespaces) — Local file processing and document generation. Invoices, contracts, proposals, and reports all read and write through this.
- Slack MCP (2 namespaces) — Team communication digests and catch-up summaries.
- WebSearch MCP (1 namespace) — Competitive research, content research, trend analysis.
Every optional integration fails silently, not loudly. If Slack isn't configured, your morning briefing still runs; it just skips the Slack section and notes the gap. This is a design principle across all 33 namespaces: graceful degradation over hard failures.
The 22-Database Notion HQ
The Notion integration isn't just a data dump. Founder OS ships with a pre-built workspace template containing 22 interconnected databases organized into 5 sections:
- CRM — Companies (hub), Contacts, Deals, Communications
- Operations — Tasks, Meetings, Finance
- Intelligence — Briefings, Knowledge Base, Research, Reports
- Content & Deliverables — Content, Deliverables, Prompts
- Growth & Meta — Goals, Milestones, Learnings, Workflows, Activity Log, Memory
The consolidation matters. Eleven of those databases are merges: Tasks combines P01 email tasks + P04 action items + P06 follow-ups. Briefings combines daily, weekly, Slack, and morning sync outputs. Each entry carries a Type field so they're filterable. One database, four use cases, zero duplication.
Read how I built this architecture from scratch in 6 days.
How Do 33 Namespaces Work Together as a System?
It takes an average of 23 minutes and 15 seconds to return to a task after an interruption, with workers encountering 2.3 intervening tasks before refocusing (Gloria Mark, UC Irvine, 2008). Individual AI tools create exactly this problem: you switch from your email tool to your CRM to your invoice processor, losing context at every jump. Founder OS eliminates it. Every namespace shares memory, CRM context, and business data through a unified architecture.
Namespace chaining means commands feed each other automatically:
- Inbox Zero → Follow-Up Tracker: emails flagged for follow-up flow directly into tracking
- Invoice Processor → Expense Report: processed invoices feed into expense aggregation
- Client Context ↔ CRM Sync ↔ Client Health: a three-way loop that keeps client data fresh
- Meeting Intel → Action Items: transcript analysis produces tasks in your Notion database
The Memory Engine injects context before every command runs. When you triage your inbox, the system already knows your client names, project status, and recent interactions, because it queried the local memory store and injected the top 5 relevant memories. You don't configure this. It just works.
The Intelligence Engine goes further. Hooks capture events across all namespaces, a learning module detects patterns (your preferred email tone, your typical meeting prep depth), and a self-healing module recovers from errors automatically. Three tiers of learning: taste preferences after 3 confirmations, workflow optimizations after proven patterns, and confidence-gated automations that always notify before acting.
Workflow automation lets you chain any namespaces into scheduled sequences. Run /founder-os:workflow:create and define a morning routine that syncs everything, prepares your meetings, and triages your inbox, all on a timer.
What About Content Creation and Growth?
Content marketing costs 62% less than traditional marketing and generates approximately 3x as many leads (DemandMetric / Content Marketing Institute, 2024). The Meta & Growth pillar tracks ROI, manages goals, and powers a full content engine. And yes, this blog post was planned, outlined, and drafted using Founder OS commands.
Here's the meta-narrative: I ran /founder-os:engine:plan april-2026 to generate a monthly content plan with keyword research and pillar balancing. Then /blog outline to build a SERP-informed outline with competitive gap analysis. Then /blog write to generate this draft with sourced statistics, SVG charts, and citation capsules. The content engine ate its own cooking.
The growth namespaces:
/founder-os:engine:plan— Monthly content plan with keyword research, pillar balancing, and cascade rules for derivative content/founder-os:engine:cascade— Takes a published blog post and generates derivative content: 2-3 LinkedIn posts, 3-5 tweets, and a newsletter/founder-os:social:compose— Template-driven social content with 29+ proven templates and 8 rhetorical techniques. A/B testing built in./founder-os:savings:weekly— Time savings report showing hours and dollars saved across all active namespaces/founder-os:goal:report— Goal progress dashboard with RAG status (Red-Amber-Green) and Gantt timeline/founder-os:learn:log— Capture a learning insight with auto-tagging and related insights surfaced from your history
The content engine isn't an afterthought. It's a full editorial system: strategy definition, content calendars with decay detection, SEO keyword tracking, cascade planning for derivative content, and performance reviews. Every blog post becomes 6-10 social posts automatically.
Read the architecture pivot that consolidated 30 plugins into one.
How Do You Get Started?
Ninety-one percent of SMBs using AI report that it has boosted their revenue, according to a survey of 3,350 SMB leaders (Salesforce, 2025). The question isn't whether AI operations tools work. It's which one to use. Here's how to start with Founder OS:
One command. Under 5 seconds. No runtime dependencies beyond Claude Code itself:
npx founder-os@latest --initWhat happens when you run it:
- CLAUDE.md merge — Founder OS instructions get injected between
<!-- founder-os:start -->markers, keeping your existing CLAUDE.md content intact - settings.json deep-merge — Plugin permissions and MCP server configs merge without overwriting your current settings
- .env scaffold — Creates a template for API keys (Notion, etc.) with clear instructions for each
- .gitignore update — Adds Founder OS runtime files to your ignore list
The install is idempotent. Run it again when updates ship; it uses SHA-256 checksums via a manifest.json to update only changed files. Safe to re-run anytime.
After installation:
/founder-os:setup:context # Guided interview to set up your business info
/founder-os:setup:notion-cli # Connect to Notion (recommended)
/founder-os:morning:sync # Your first morning briefingThat's it. 82+ commands ready to go. Free forever. MIT license, no freemium gates, no upsell.
Frequently Asked Questions
Is Founder OS only for technical founders?
No. Every command uses natural language through Claude Code's slash command interface. Type /founder-os:inbox:triage and it runs. Seventy-five percent of SMBs are already experimenting with AI tools (Salesforce, 2025). If you can type a slash command, you can use Founder OS. No coding required.
How does Founder OS compare to Alfred_ or Ambient?
Those are hosted SaaS platforms charging $30-50 per month. Founder OS is free, open source (MIT license), runs locally on your machine, and has 82+ commands versus their 5-10 features. Your data stays in your terminal; nothing goes to a third-party server. And you can read, modify, or extend every command because it's all markdown.
Can I use Founder OS without Notion?
Yes. Notion is the recommended CRM backbone: 21 of 33 namespaces use it for storing outputs, tracking tasks, and managing client data. But every Notion integration degrades gracefully. Commands still run without it; they just won't persist data to a database. You can add Notion later without re-installing.
Does Founder OS work with teams?
It's designed for solo founders and small teams of 1-5 people. Each team member runs their own Claude Code instance with shared Notion databases as the collaboration layer. No multi-tenant server required. The Memory Engine and Intelligence Engine run locally per user, while Notion provides the shared state.
How do I add my own commands to Founder OS?
Create a namespace directory under commands/, add a markdown file for each command with YAML frontmatter, and run /reload-plugins. The same plugin architecture that powers the original 33 namespaces is fully extensible. Everything is markdown: no APIs, no build process, no compile step.
Lukas Halicki is the founder of NaluForge, where he builds AI automation systems for SMB founders. He built Founder OS in 6 days using Claude Code and now runs his entire business on it. When he's not shipping plugins, he's writing about the intersection of AI tooling and founder productivity.
The AI Chief of Staff You Don't Have to Pay For
The AI chief of staff category is real. Investors are backing it. Product Hunt categorized it. And founders are paying $50-300 a month for tools that give them 5-10 features behind a cloud dashboard.
Founder OS gives you 82+ commands across 33 namespaces. Four pillars covering daily operations, document processing, platform integrations, and growth automation. Seven MCP connections to your existing tools. Twenty-two interconnected Notion databases. A memory engine that learns your preferences. An intelligence engine that adapts to your patterns.
All free. All open source. All running locally on your machine.
npx founder-os@latest --initOr if you want someone to build custom AI automations for your business with the same approach and speed, book a call with NaluForge.
Next week: the architecture story, how 33 plugins became one, and why throwing away the first day of code was a feature, not a bug.
Read how I built 30 AI plugins in 6 days, or dive into the architecture pivot that changed everything.