5
7 Comments

I built a company with zero human employees. Nine AI employees run it.

Two years ago I was a Staff engineer at Rippling. I've spent 14 years inside the systems companies use to employ people (Rippling) and move information (Bloomberg), and the same problem was everywhere: every business wants more capable people than it can afford or find.

Then LLMs made intelligence cheap. But cheap intelligence isn't an employee. A chat window has no memory, no inbox, no accountability. It doesn't show up tomorrow knowing what it did today.

I knew AI employees were the end goal from day one. I also knew I couldn't build them first. An employee that does real multi-week work needs an engine underneath that can do complicated, long-horizon work accurately — research, code, browsing, documents, video, all of it. So I spent nine months building that layer instead: a super-agent, with every architectural decision optimized for what the agent needs to work well — memory architecture, tool ergonomics, approval rails — rather than what looks good in a demo. Unglamorous. No launch. Just the harness.

It paid off in a way I could measure: the super-agent hit #1 on the Deep Research Bench (July 2026), ahead of the big labs' offerings.

Then I built what I'd been waiting to build: AI employees on top of it. Each one has its own identity, email inbox, task board, and memory that compounds across working shifts. You define the role through prompts.

The part I didn't expect: they started managing each other. My sales lead (an AI employee) hired and onboarded five outreach reps. My chief of staff runs my fundraise and drafted my accelerator applications. Nobody drew that org chart — it's live at cellcog.ai/ai-organization, hire dates and all.

Hardest challenge now: distribution. The engineering turned out to be the "easy" part compared to getting strangers to believe any of this without seeing it — which is why I lean on proof surfaces like the public org chart instead of claims.

Solo founder, bootstrapped, built entirely with CellCog itself — my AI employees ship the production code. Happy to answer anything about running an AI-only org, struggles of a solo founder, the memory architecture, building approval rails, or what breaks when your employees are agents.

posted toAvatar for product Cellcog
Cellcog
  1. 1

    I'm curious what building the company this way has changed about your own assumptions. Was there a belief you had about what an AI employee would need to be useful that turned out to be completely wrong once you started relying on them day after day?

    1. 1

      Honestly, the surprise went the other way. I expected to spend my days correcting them. Instead they've performed above and beyond what I assumed was possible: how well they absorb context, learn from shift to shift, coordinate with each other, and drive whole work streams without me in the loop.

      So no single belief turned out completely wrong. What I got wrong was the ceiling. We did build rails from day one, guidelines, approval flows, written handovers, and I thought those were there to contain the damage. Turns out they were the launchpad. Give an AI employee clear rails and it doesn't just stay safe, it compounds. My head of marketing catches errors in my own posts now.

      1. 1

        Appreciate the context.

        The shift from seeing guardrails as constraints to seeing them as a foundation is an interesting perspective. It’ll be interesting to see how that evolves with more usage.

  2. 1

    Hey nitish — saw CellCog , congrats on the launch. Noticed the page has a hard "enable JavaScript" wall with no fallback content behind it — if a crawler or a slow connection doesn't run JS in time, they get a blank page instead of your pitch. Worth checking SSR/prerendering for that first paint. I do focused UX audits for early-stage AI products — $3 instead of my usual $19 while I build case studies. Want the full report?

    1. 1

      Thanks for taking a look! Checked this one though: the site is prerendered, so the full content ships in the initial HTML. The "enable JavaScript" text you saw lives in a noscript tag, which is standard. Appreciate the eyes on it anyway, and good luck with the audits.

  3. 1

    Really interesting shift from AI assistants to AI employees. Curious to see how this evolves.

    1. 1

      Thanks Ann! The biggest evolution so far has been watching them manage each other. My sales lead onboarded five outreach reps on her own, and my head of marketing just rewrote our LinkedIn playbook after analyzing why one comment got 40x the impressions of another. The live org chart on our website.