Build Your AI Operating System: The 4C Framework That Scaled to $100K/Month

Get AI income methods before they spread.

Free weekly intelligence newsletter.

Nate scaled an AI automation agency to $100,000 per month by organising every tool, connection, and process around four categories: Context, Connections, Capabilities, and Cadence. The 4C Framework is not a product — it is a mental model for building an AI operating system that runs your business, and it works regardless of which AI tools you use.

What Are the Four C's?

Each C addresses a different layer of how an AI system interacts with your business:

Context — what Claude knows about your business. This lives in CLAUDE.md for session-level context and Obsidian for long-term knowledge. Without context, every session starts from zero.
Connections — which external services Claude can access. Gmail, Slack, Stripe, Google Drive, ClickUp — connected via MCP. Every connected service is a capability multiplier.
Capabilities — what Claude can do. Skills, slash commands, Playwright scripts, API integrations. This is your custom toolbox built on top of the base model.
Cadence — when things run. Daily loops, scheduled tasks, weekly reviews. The rhythm that keeps the system producing output without manual triggering.

A business with all four in place runs largely on autopilot. Most AI setups have Context but weak Connections, or strong Capabilities but no Cadence.

How Do You Build the Context Layer?

Start with CLAUDE.md. This file tells Claude what your business does, who your clients are, what tools you use, what your conventions are, and what it should never do without checking with you first. Write it once, update it when something significant changes, and every session benefits from it.

Obsidian handles the knowledge that grows over time: client notes, project history, research, meeting summaries. Connect Obsidian to Claude via MCP so Claude can read and write notes without you switching contexts.

Strong context means Claude gives better advice, makes fewer wrong assumptions, and asks fewer clarifying questions.

Which MCP Connections Have the Most Impact?

Start with the tools you use every day. For most builders:

Google Workspace — Gmail and Google Docs cover email handling and document creation
Slack — Claude can send messages, read channels, and post summaries without you switching to Slack
Stripe — revenue visibility, invoice creation, subscription status
ClickUp or Linear — task management, project tracking, automated ticket creation
QuickBooks — financial tracking if you run a business with meaningful revenue

Each connection you add multiplies what Capabilities can do. A capability that generates a proposal is more powerful when it can also create the Google Doc, send the email, and create the follow-up task — all in one command.

How Do You Set Up Cadence?

Cadence is the scheduled layer. Daily loops check email and surface priorities. Weekly reviews pull together client project status. Monthly reports aggregate revenue and pipeline data. Each cadence item is a Claude Routine or a Claude Code skill running on a schedule.

The test for whether something belongs in Cadence: if you do it on a predictable schedule and it follows a consistent pattern, automate it. If the answer changes every time you do it, keep it manual.

At $100,000 per month, Cadence is what frees Nate to focus on client relationships rather than operations. The system runs the repetitive work. He handles the judgment calls.

How Do You Prove the Framework Is Tool-Agnostic?

Nate ported the complete AIOS from Claude Code to Codex in two minutes. He copied the CLAUDE.md, reconnected the MCP connections, moved the skills folder, and reset the Cadence schedules. The framework transferred because the value is in the structure — the four categories — not in any specific tool that implements them.

If Claude Code is replaced by a better tool next year, the 4C Framework survives the switch.

Frequently Asked Questions

How long does it take to set up the full 4C Framework?

A minimal working setup — CLAUDE.md written, two or three MCP connections active, three to five skills installed, one Cadence task running — takes one focused afternoon. A fully built-out system with ten or more connections, a deep skills library, and multiple Cadence loops takes two to four weeks of iterative building. Start minimal and add as you find gaps.

What is the 20% productivity dip Nate mentions during adoption?

The first few days of using any new system, you spend time setting it up rather than producing output. The system is unfamiliar, skills need testing, connections need debugging. Nate found the break-even point — where the system saves more time than it costs — at day three to five. After that, productivity compounds as the system handles more of the routine work.

Can the 4C Framework work for a solo freelancer, not just an agency?

Yes, and it works faster to set up at solo scale. The Connections layer is smaller (fewer tools to integrate). The Capabilities layer is more personal (skills built for your specific workflow). The Cadence layer covers your own schedule rather than a team's. The same four categories, simplified for one person.

What is the most common mistake when building an AI operating system?

Building Capabilities before Context. Skills and automations built without a strong CLAUDE.md produce generic outputs that need heavy editing. Invest the first session in writing detailed context, then build capabilities that work on top of it. The order matters.

Watch Nate's full AIOS breakdown: Nate Herk on YouTube