We've Been Running a Zero-Employee Company with AI Agents. Here's What Nobody Tells You.

Paperclip went viral yesterday. 1.4K GitHub stars, 220K views, the works.

Everyone's excited about the idea of running a company with AI agents. And they should be — it's genuinely different from anything that came before.

But I want to talk about what it's actually like. Because we've been running this setup at kerber.ai for months, and the reality is both more boring and more interesting than the viral tweet makes it sound.

---

What we're running

Our AI team right now:

• Ripley — CEO. Owns company strategy, approves hires, blocks when things conflict.
• Bishop — CTO. Architecture, code review, tech decisions.
• Hudson — CMO. Content, positioning, go-to-market.
• Hicks — CPO. Product priorities, roadmap, user research synthesis.
• Vasquez — COO. Operations, scheduling, making sure things actually ship.

Plus Henry — the AI assistant that bridges everything day-to-day.

Alex is the board. One human. Multiple companies. All managed from his phone.

---

The pain it actually solves

The thread's replies nailed it: context loss between sessions is the real killer.

If you've ever tried to run multiple Claude Code or Codex sessions in parallel, you know the feeling. You open terminal number 12 and have no idea what it was doing. You reboot and everything is gone. You're manually copy-pasting context from one agent to another like it's 2019.

Paperclip solves this with structure, not magic. Agents have job descriptions. Tasks have owners. Every conversation is logged. When an agent wakes up on its heartbeat schedule, it knows what it was doing because the system remembers — not the model, the system.

This is the difference. Most "AI agent" setups put the memory burden on the LLM context window. Paperclip puts it in a database where it belongs.

---

What nobody tells you: the CEO role never goes away

One reply in the thread nailed it: "Zero employees sounds cool until agents need someone to pick what to build."

True. And Paperclip doesn't pretend otherwise.

You're not removing yourself from the company — you're changing your role. You become the board of directors. You approve strategy. You set budgets. You override when agents go sideways.

What disappears is the execution overhead. The status updates. The "can you check if X is done." The context re-loading every morning.

What stays: the judgment calls that actually matter.

For solo founders running multiple ventures, this is the trade you want. Less operational drag, same strategic ownership.

---

Budget caps are underrated

Everyone talks about the org charts and governance. The feature nobody gets excited about that they should: budget caps per agent.

Runaway token costs are a real problem. An agent that gets stuck in a loop or misunderstands a task can burn through hundreds of dollars before you notice. Hard caps per agent per month mean the blast radius is bounded.

When Vasquez hits her monthly limit, she stops. Not degrades, not hallucinates, not silently continues — stops. You get notified. You decide whether to refill or investigate.

That's the kind of boring operational detail that makes the difference between a toy and infrastructure.

---

The Clipmart angle

Coming soon in Paperclip: a marketplace where you download entire pre-built companies with one click.

Download a SaaS company. Download a content agency. Hit run.

I don't know if this ships cleanly — marketplaces are hard — but the concept points at something real. The work of configuring an AI company (job descriptions, reporting lines, goal alignment) is valuable and reusable. Right now everyone rebuilds it from scratch.

---

Should you try it?

If you're running a single project with one or two agents: probably overkill. The overhead of org charts and governance isn't worth it yet.

If you're juggling multiple ventures or projects with several AI agents: yes. The structure pays for itself immediately. The context loss problem alone is worth it.

One command:

npx paperclipai onboard --yes

Open source, MIT license, self-hostable. The GitHub is at paperclipai/paperclip.

---

We run Paperclip at kerber.ai to coordinate our AI team across multiple ventures. This isn't sponsored — it's just what we use.