Ellie Do
Case study · automation

An AI team that knows who's boss.

I built my own business operating system: an AI chief of staff that takes every task, pins down what “done” means, hands it to the right specialist, checks the work, and brings it to me for the final say.

6
Specialist agents
5
Specialists ran real tasks end to end on day one
5 max
Questions asked before work starts
01

The problem

When you run a business alone, you're the whole team: content, sales, strategy, research, tech and admin. Work starts without a clear finish line, so it grows. Generic AI drafts don't sound like you.

And the work you finish never makes it into your portfolio, your CV or your content, so nobody sees it.

02

How it works

AI business operating system flow I give a task In plain words, any size Chief of staff runs intake Fills in what's known, asks only what's missing Definition of done + the proof The number that shows it worked Content Sales Strategy Research Portfolio Architect Chief of staff checks the work Facts, rules, and that changes landed I decide The founder always has the final say Decision logged My corrections become new rules Something shipped? One record → content, portfolio, CV

Every task follows the same path. The specialist does the work, the chief of staff checks it, and I make the call.

03

What I built

It runs in Claude Code with sub-agents, on plain Markdown files kept in Git, connected to the Notion workspace I already use. No new subscriptions.

01

Intake before effort

Every task starts with intake. The chief of staff fills in what the files already say and asks me only what's missing, five questions at most, in one message.

02

A finish line for every task

Before any work starts, the task gets a definition of done and the number that proves it. Scope creep gets flagged instead of quietly absorbed.

03

Six specialists, one standard

Content, Sales, Strategy, Research, Portfolio and a Systems Architect who reviews every build before it starts. Each one reads my voice guide and my rules before it writes anything.

04

It learns from my edits

When I change a specialist's work, the correction is logged against that role. A fix that comes up twice becomes a standing rule, so I stop making the same edit.

04

Result

5 of 6
On day one, five of the six specialists (content, sales, strategy, research and the systems architect) ran real tasks end to end. This page was drafted by the Portfolio Keeper and checked by the chief of staff before I approved it. Longer-term results are in progress: after four weeks I'll measure tasks run through intake, corrections turned into rules, and shipped systems that reached the portfolio and CV.
05

Stack

Claude Code (sub-agents) Prompt + context engineering Markdown in Git Notion (CRM, content calendar, CV) Process design Quality control
06

What this means for your business

If you're a founder or a small team, AI can take real work off you without you losing control or your voice. You stay the decision maker; the system handles the briefing, the drafting and the checking.

For an agency, the same pattern works for client delivery: a clear intake, a definition of done on every job, a specialist per task, and a review step before anything reaches the client.

Open to collaborate

Book a 30-minute strategy call