We built our company
an AI brain.

Open-source AI operating system used by a real 8-figure company growing +100%.

€352
/ Month All-In
18:1
Audited ROI
62h
Saved Per Week
6+
Months In Production
The starting point

Knowledge, procedures, systems — and a feedback loop.

Every recurring decision in our business used to live in someone's head. Refund policies in old Slack threads. Pricing exceptions as tribal knowledge. Incident playbooks as the founder's memory.

We extracted all of it. Structured it. Made it executable.

📚
1,341 documents
The knowledge layer

Pulled from email, Slack, support tickets, reports, meeting notes, and 18 months of decisions. Structured. Versioned. Searchable.

🛠️
167 executable skills
The procedures layer

Procedures the brain can run on demand. Close the books. Triage a refund. Run weekly P&L. Documented, parameterized, callable.

🔌
44 integrated tools
The systems layer

Every business system the brain can read or write — e-commerce, helpdesk, accounting, marketing, analytics, warehouse. Governed via ACL. Audited via logs.

🌱
Self-updating
The compound layer

Every decision, fix, and pattern adds to the brain. Month six is not month one. The gap keeps widening.

Y Combinator's Tom Blomfield calls this "the missing layer between company data and reliable AI automation. Every company in the world is going to need one." We call it the brain.

Brain v2 · the operational layer

Not a wiki. A living memory.

Most "company AI" projects build a knowledge base. We built a memory that captures work where it happens, learns from it, and writes back what it learned. Bidirectional. Self-refreshing. With privacy hard-stops.

01
Captures where work happens

Slack threads, Meet/Gemini notes, Gmail, Google Drive. 228 meeting docs auto-captured, 1,019 signals promoted. Privacy hard-stops on HR, payroll, family, health.

02
Bidirectional, not consultive

Agents and employees write back to the brain when they learn, finish, or break something. Every interaction grows the memory. Notion AI reads; this writes.

03
Tasks · outputs · decisions · gaps

Raw input → signal → task → output → decision → world model. Every layer has its own lifecycle. Health checks tell you what's broken before you notice.

04
World model auto-refresh

Current-state, customer-signal, capabilities, gaps, DRI map. Refreshes weekly from real signals. Your AI knows what's true today, not 6 months ago.

Setup

Connect any AI client to your brain in one command.

Master prompt, MCP tools and brain access deployed in ~2 minutes per employee.

macOS
curl -fsSL https://your-mcp.example/setup.sh | bash
Windows
irm https://your-mcp.example/setup.ps1 | iex

Template in the playbook. Adapt to your MCP endpoint, your domains, your master prompt. Full implementation typically takes 6–8 weeks for a consumer SME — talk to us if you want help.

The execution layer

Three things run on top of the brain.

The brain is the substrate. What turns it into an operating system is what runs on top: eight AI agents 24/7, forty integrated tools, and every team member with one command and one shared master prompt. This is the pattern any consumer SME can replicate.

🤖
Agents
The automation layer

Eight domain agents run 24/7 on the same brain. Read context, execute, write back what they learned. All share one memory — the CS agent knows what Marketing decided last week.

🔌
Tools
The systems layer

44 MCP tools wire e-commerce, helpdesk, accounting, marketing, analytics, warehouse, and Slack to the brain. Every read and write logged in the action ledger. Auth observed.

👥
Employees
The human layer

Every team member connects in one command. Same master prompt as the agents. The brain captures their work back from Slack, Meet, Gmail, Drive — no documentation hour, no manual sync.

The LLM is the execution layer of the company. Tools write data. Agents write learnings. Employees write decisions. The brain compounds with every interaction — and that compounding is why month six is qualitatively different from month one.

The company in motion

The company runs on AI. The team steers.

On a typical Tuesday, dozens of operational decisions get made across customer service, retail, finance, marketing, and merchandising. None of them start with a spreadsheet. They start with a question — to an LLM that already has the context.

🧠
The founder
Monday 9:00 AM

"What changed last week and what should I look at first?" Six minutes later, the weekly brief drops in Slack — drawn from the agents' Sunday runs, the meeting notes, and the world model. No tabs opened.

💬
The CS lead
Tuesday 11:00 AM

A customer asks why their refund is late. "Order 8341 — timeline, who promised what, what should I say?" Full thread, policy match, and brand-voice draft in 90 seconds. The decision is captured for the next similar ticket.

📊
The finance lead
Friday 4:00 PM

"Reconcile last week. What's off?" Accounting, bank, and Shopify checked in one pass. Two anomalies flagged with the receipts. Weekend starts on time.

🧶
The merch lead
Tuesday 10:00 AM

"Sell-through by size. Anything to act on?" Three SKUs flagged for transfer, one for markdown. Decision made before lunch. The Marketing agent sees the markdown plan in its next run.

None of these moments started with a spreadsheet, a query, or a tab switch. They started with a sentence — to an LLM that read the brain, executed against the right system, returned the answer, and wrote what was decided back. The work happens; the memory accumulates; the company gets quieter while doing more.

Automation layer · deep dive

Eight agents run the operations that don't need a human.

Each agent owns one domain. All eight share one brain and one master prompt. They read context, execute against the real systems, and write the patterns they learn back to the brain. Replace each agent's domain with yours — the pattern transfers.

🧠
Strategy Agent
Orchestration · Briefings

Morning briefings, cross-domain synthesis, competitive scans, knowledge mining. Refreshes the world model weekly from real signals.

💬
CS Agent
Tickets · Drafts · Escalation

Ticket triage, WISMO replies, brand-voice drafts, pattern detection, escalation routing. AutoResearch loop tunes prompts on its own.

📊
Finance Agent
P&L · Reconciliation · Cash

Weekly P&L, AR follow-ups, invoice reconciliation, treasury, variance alerts. Reads accounting, bank, and commerce in one pass.

🏪
Retail Agent
Traffic · Staffing · Channels

Daily store reports, staffing signals, transfer flags, store comparisons. Pulls POS and traffic data, writes the daily brief.

📣
Marketing Agent
Campaigns · Copy · Attribution

Campaign analysis, segmentation, copy patterns, SEO opportunities, attribution. 1,114 historical campaigns indexed in the brain.

🧶
Merchandising Agent
Sell-through · Allocation · Markdown

Sell-through, variant audits, markdown candidates, pricing, wholesale ops. Flags risk before it shows up in the P&L.

👥
HR & People Agent
Onboarding · Leave · Payroll

Absences, payroll prep, vacation balances, onboarding, expenses. Hard privacy stops on health, recruiting, and personal contexts.

⌨️
Command Center
Founder interface

Claude Code with all 44 MCP tools and the full brain. The founder operates every agent and every system from one prompt.

All eight share one memory. All eight write back what they learn. When the CS agent detects a pattern in refunds, the Merchandising agent sees it on Monday.

The Math

Honest ROI — with every assumption on the table.

Most AI vendors quote numbers they can't defend. "10× productivity." "50× return." "Pays for itself in a week." Then you ask how they calculated it and the conversation gets vague. Here's exactly how we get to 18:1.

Hours Saved Per Week — Audited Across 6+ Months
CS Agent — triage, drafts, policy lookups20h
Founder time freed — briefings & decisions10h
Finance — P&L, AR, reconciliation8h
Merchandising — sell-through & sizes6h
Retail — daily reports & staffing5h
Marketing — campaigns & segments5h
Strategy — synthesis & knowledge5h
HR — admin & payroll prep3h
Total hours offloaded weekly62h
62h/week × 52 weeks = 3,224 hours/year
Valued at €21/h loaded operational labor + €40/h founder opportunity cost
= €77,584 / year in reclaimed labor value

System cost (all-in): €4,224 / year (€352 / month)
RATIO: 18.4 : 1 · Payback: ~20 days

€21/h loaded labor derived from personnel budget ÷ headcount ÷ ~2,000 working hours × role mix. Conservative. No revenue impact claimed — every number here is a cost avoided.

Living System

This playbook is updated from verified production learnings.

This is the operating manual of a company running on it now: tickets, books, stock, weekly learnings, shipped back into the playbook.

Daily
Agents run, crons extract patterns, and new learnings land in the brain.
Weekly
The best weekly patterns are promoted into the shared library.
Monthly
Failure modes get documented as lessons. Every reader gets them in the playbook.

Not a course. Operating documentation, updated only when production teaches something worth shipping.

Live Right Now

See the system running.

Production activity feed, honest ROI breakdown, real cost data, and a governed public snapshot of the swarm. No mockups, no vanity KPI theater, and no hidden spreadsheet math.

Live activity feed
Real cost breakdown
Try the demo yourself
Open the dashboard →
The Depth

15+ capabilities you won't find anywhere else.

Most AI demos show one capability at a time. A system running for six months accumulates depth: corner cases, weird customer behaviors, recovery patterns, decisions that are too specific for a sales deck but too valuable to forget.

01
AutoResearch

Self-evolving prompts. The CS agent mutates weak prompts and auto-promotes winners. 94.7% accuracy after 3 months.

02
LLM Council

Six domain agents plus blind peer review for high-stakes calls. Strategy, finance, CS, marketing, ops, merchandising, ~€1 per deliberation.

03
Pattern Library

Cross-company pattern library with strict anonymization. New deployments start at 70%+ autonomy instead of zero.

04
Invoice Pipeline

Inbox → OCR → classify → reconcile → approve. Five minutes per invoice drops to <30 seconds.

05
Profitability Engine

Real-time CM3 per product across commerce, inventory, ads, analytics, and accounting. Every SKU gets a live margin number.

06
Copy Engine

1,114 campaigns analyzed for subject line, body, CTA, and performance. Learned rules drive future drafts.

07
Taskmaster Protocol

Contract-based execution for multi-step work. Every step has acceptance criteria and rollback rules.

08
GEO Optimization

Tracks visibility across ChatGPT, Perplexity, Claude, and AI Overviews. Mention rate improved from 35% to 60%.

09
Agent With Its Own Credit Card

The strategy hub has a capped corporate card. It buys approved tools and files receipts automatically.

Compounding

Month six is not month one.

The brain isn't a snapshot. It's a system that learns. Every decision, fix, refund, campaign result, and customer message gets captured. The longer it runs, the more your AI knows what your company would do — and the less you have to explain.

M1
Month one

Generic AI. Asks for context every time. Most decisions still need a human in the loop.

M6
Month six

Pattern-aware AI. Knows your refund policy, your tone, your vendors, your reasons. Most routine decisions execute themselves.

You can fork the playbook and the skills. The memory of your company has to be built — by your company.

What this is

What this is, and what it isn't.

The "AI for business" category is loud and mostly indistinguishable. It helps to be precise about what Compai is and isn't.

Compai is the operating manual for running a consumer SME on AI agents. Eight months in production. Free to read, fork, adapt. Every claim auditable.

What's in the repo

Everything we built, open and executable.

The actual playbook, skills, prompts, templates, patterns, and lessons. Written inside an 8-figure consumer brand running on AI.

License: Free to use, attribution requested. Updated as production learnings are verified.

FAQ

Things you're probably wondering.

Because we wish this had existed when we started. Most readers will self-serve from the playbook and the repo; a few will want hands-on implementation help — and that's the only thing we charge for.
Consumer SMEs in beauty, food, home, wellness, pet, outdoor, fashion, or retail — typically €2-20M revenue, 20-80 people, operationally complex. You need someone technical enough to deploy, and discipline to use it past month one.
A structured filesystem of documents, executable skills, MCP tools, and a world model that captures the operating state of your company — and a set of pipelines that keep it alive by capturing work from Slack, Meet, Gmail, and Drive.
Yes if you deploy it yourself — command line, a small server, API keys, debugging, monitoring. The setup script covers the employee side; the company side needs operational engineering. If you don't have that, read the playbook to scope the work or write to us.
An employee connects in 2 minutes. The basic brain takes 2-4 weeks. The full system — captures, agents, world model, master prompt, employee onboarding — typically 6-8 weeks for a consumer SME with one engineer. Six months to get to the ROI numbers we show.
62 hours offloaded per week, valued conservatively against €4,224/year all-in system cost. No revenue uplift claimed. Full breakdown.
Yes if you run a consumer SME with repeated operational decisions across multiple domains. The examples in the playbook are fashion-heavy; the architecture is vertical-agnostic. Replace each agent's domain with yours — the pattern transfers.
Yes. The playbook, the repo, and the live dashboard are everything. The implementation work we do isn't proprietary knowledge — it's experience and execution speed. Some companies want help, most don't need it.

Any questions, write me.

If you're stuck on the playbook, want feedback on what you're building, or want help wiring this into your company — I read every email. hello@usecompai.com.

Read it. Fork it. Build your own.

45 chapters. 75 skills. 38 prompts. 32 production lessons. Free to use, attribution requested.