Skip to main content
Download free report
Softblues
Softblues

Claude AI Operating System ยท our own company

We don't demo the Claude Operating System. We run our company on it.

The Softblues Claude Operating System

Most companies adopt AI one chatbot at a time, bolted onto each tool, with nothing shared between them. We did the opposite. Softblues runs on six connected Claude agents, one per function, each with its own operating manual, tools and routines, joined through a shared hub. It is the same system we sell, running live on us.

Softblues (our own company)Claude AI Operating SystemOur own proof caseLive, in-house
See it on a call
6 connected agents
One per function, one shared hub
Six department agents linked to one shared hub, working as a single connected system

The problem

AI bolted onto everything, joined to nothing

Most companies buy AI a seat at a time. A chatbot in the CRM, another in the docs, a third in the inbox. Each is useful on its own, and none of them share anything: no common memory, no shared context, no idea what the others are doing. Sensitive numbers get pasted into tools that were never meant to hold them.

We wanted the opposite. Not a pile of assistants, but one system: each function run by an agent that knows its job, uses its own tools, and stays in step with the rest of the company.

We use it before we sell it, so we can show it live, not in a slide deck.

The idea

An operating system, not a pile of chatbots

Each function is its own space on its own drive, run by a Claude agent. The agent reads an operating manual first, a CLAUDE.md that says how that function works, uses only the connectors it is allowed to touch, runs its routines as packaged skills, and fires them on schedule. A person reviews and decides; the agent does the work.

The manual is the system. A new hire opens the space, reads the manual, and starts. There is nothing bespoke to learn.

Anatomy of an agent: an operating manual, the connectors it may use, the skills that package its routines, and the scheduled tasks that run them

The system

Six agents, one hub

Six connected Softblues spaces, one per function, joined through a shared hub that holds each function's status brief
  1. 1

    Strategy agent

    Holds the vision, direction and targets, and reads every other function's brief before setting them. The space the others align to.

  2. 2

    Finance agent

    Runs the numbers: P&L, balance, payroll and the monthly close, wired to Xero. Access-restricted, it publishes only a sanitised affordability signal to the hub, never raw figures.

  3. 3

    Sales agent

    Works the pipeline in Attio: qualification, deal hygiene and the weekly sales review, with one open next step per deal and won-deal handoffs to Delivery.

  4. 4

    Delivery agent

    Tracks live client projects, risk and capacity from Attio and Gmail, and confirms delivered revenue so Finance and Sales see the real picture.

  5. 5

    Marketing agent

    Runs demand generation end to end: SEO, the blog, outreach and lead tracking, wired to Attio, Supabase and the website, publishing straight to softblues.io.

  6. 6

    System hub

    The shared contract between the agents. It holds the map, the templates and each function's status brief, and nothing sensitive: no P&L, no rates, no client commercials.

Coordination

How the agents stay in step

Each space publishes a short status brief to the hub. Before any agent plans, it reads the briefs it depends on, so sales, delivery, finance and the rest work from one picture. Writes are one way: no space ever edits another's drive.

That is also how sensitive data stays put. Finance and HR are restricted, and Finance shares only a sanitised signal, runway comfortable or tight, never the raw P&L.

On a cadence

What runs on its own

The recurring rituals run on schedule, without waiting for someone to start them.

Weekly sales review
CadenceWeekly
SpaceSales
Weekly delivery status
CadenceWeekly
SpaceDelivery
Monthly close
CadenceMonthly
SpaceFinance
Weekly marketing review
CadenceWeekly
SpaceMarketing
Blog publishing
CadenceDaily
SpaceMarketing

Built with

Platform

Claude (Anthropic)Cowork

Agent building blocks

Per-space CLAUDE.md operating manualsSkillsScheduled tasksStatus Briefs

Connected tools

Google DriveAttio CRMGmailXeroSupabaseBigQuerySmartleadExpandi

What it adds up to

One company, run on agents

6

Connected spaces, one per function plus a hub

3+

Functions already run by agents day to day

4+

Recurring routines on their own schedule

100%

Run in-house on Claude

Sensitive data stays put

Finance and HR are access-restricted and share only sanitised signals, so coordination never means exposing the numbers.

Onboarding in minutes

A new hire opens their space and reads the manual. There is no bespoke system to learn, because the manual is the system.

Why it matters

The proof is that we run on it

This is the system we sell as the Claude AI Operating System. The difference is that we are not describing a plan. We run our own company on it, which is why we can show it live rather than in a slide deck.

We have already made the mistakes, so your team does not have to.

The same pattern, in production

The agents that run our company are the same pattern we build for clients: a function split into specialised agents, wired to real tools, with a person in charge of the call.

Frequently asked questions

It is how we run our own company: six connected Claude agents, one per function (strategy, finance, sales, delivery, marketing) plus a shared hub, each with its own operating manual, tools and routines. It is also the system we deploy for clients under the same name.

Each function is a space on its own Google Drive with a CLAUDE.md operating manual the agent reads first, the connectors it is allowed to use (Attio, Gmail, Xero, Drive, Supabase), the skills that package its routines, and scheduled tasks that run them. The agent runs that function's work, with a person reviewing and deciding.

Each space publishes a short status brief to a shared hub. Before any agent plans, it reads the briefs it depends on, so sales, delivery, finance and the rest work from one picture. Writes are one way: no space ever edits another's drive.

Each function has its own drive with its own access control. Finance and HR are restricted, and Finance publishes only a sanitised signal (for example 'runway: comfortable') to the hub, never raw P&L or client commercials.

The recurring rituals: a weekly sales review, a weekly delivery status, the monthly close across the first few days of the month, a weekly marketing review, and daily blog publishing, each as a scheduled task in its own space.

Yes. This is the Claude AI Operating System we offer: we map your functions, connect your tools, package your routines as skills, and stand up the agents, usually starting with one function and an audit. We run it on ourselves first, which is why we can show it live, not in a slide deck.

Want this for your company?

We map your functions, connect your tools, package your routines as skills, and stand up the agents, usually starting with one function and an audit. Book a call and we will show you ours running first.

Anthropic Partner Network member50+ AI ProjectsGoogle Cloud PartnerTop-5 UK AI Firm
Success Stories

Explore Other Projects

Discover more AI solutions delivering measurable results across industries