The Solo Chief: running a one-person business with a team of agents

A new kind of business is becoming common: one person, no staff, and a growing collection of tools and AI agents doing work that used to need a small team. The owner is not a freelancer taking on more than they can handle. They are running a real operation, with marketing, delivery, admin and finance all happening, except that most of the doers are software. Jurgen Appelo, who writes about this shift, coined a term for the person at the centre of it, the Solo Chief, and the name is doing real work. You are not a sole trader any more. You are the chief of an operation whose staff happen to be agents.

That changes the job in ways worth thinking about before you build a tangle you cannot maintain. The skills that matter shift from doing the work to directing it, and the risks shift with them. Appelo puts the accountability plainly: as a Solo Chief, "you're the strategist, the operator, and the single wringable neck." Everything that goes right and everything that goes wrong stops at you.

What a Solo Chief actually is

The distinction that matters is between doing and orchestrating. A traditional sole trader sells their own hours: they do the work, and the business grows only as far as their time stretches. A Solo Chief still has judgement at the centre, but the hours come increasingly from software that drafts, sorts, researches, schedules and chases on their behalf. The owner sets direction, defines what good looks like, and supervises. The agents do the volume.

This is why Appelo talks about a business that can "look and behave professionally from day one," producing the kind of output that used to require several people. The headcount is one. The capacity is not.

From doing to orchestrating

The hardest part of becoming a Solo Chief is psychological, not technical. Most owners got good at their business by doing the work themselves, and doing it well is a source of pride and identity. Orchestrating feels less like working. You spend more time briefing, checking and deciding, and less time producing, which can feel oddly idle until the output makes the point for you.

The shift is worth making deliberately. Pick the work that genuinely needs your judgement, the client relationships, the calls that shape the business, the things only you can decide, and protect them. Then push as much of the rest as you safely can to agents and tools, and accept that your job on those tasks is now to direct and approve, not to do. An owner who refuses to let go of the doing simply caps the business at their own hours again, which is the constraint the agents were meant to lift.

A Solo Chief stops selling their hours and starts directing a system that produces them.

A simple layered setup

The failure mode of a Solo Chief operation is sprawl: agents and automations bolted together until nobody, including you, can say what runs where or why a thing broke. Appelo's advice is to keep the setup in clean layers rather than one knotted mess, and a small operator can hold a simple version of that in their head.

Think of three layers. The front layer is what you talk to: the chat, the assistant, the place you give instructions. The middle layer is the work itself: the sequences of steps that get a job done, the routines that draft and sort and chase. The bottom layer is memory: where your business context, your house style and your records live, so the work above always has something to draw on. Keep those layers separate in your mind and your build, and when something goes wrong you can find it. Mix them, and you have a single tangle to untangle every time.

You do not need to build all three at once, and you should not. Start with one routine in the middle layer that clears a real job, give it just enough memory to do that job well, and grow from there.

Where the single wringable neck still matters

The agents do the work, but the accountability does not move. When an agent sends a client the wrong figure, the client does not blame the agent. They blame you, and they are right to. This is the part of Appelo's framing that keeps a Solo Chief honest: convenience does not transfer responsibility. Every routine you stand up is one you are answerable for.

In practice that means the things you would never skip with a human assistant matter more, not less, when the assistant is software. Know what each agent is allowed to do. Keep a human glance on anything that reaches a customer, moves money, or changes a record. And be able to switch a misbehaving routine off without the whole operation falling over. The single wringable neck is yours. Build so that you can actually see what your neck is on the line for.

The honest limits

The real danger for a Solo Chief is out-building your own ability to supervise. It is easy, and quite fun, to keep adding agents until the operation is more complex than one person can hold in their head. At that point the time the agents save is eaten by the time you spend working out why they did something strange, and the whole advantage quietly reverses.

So grow the operation only as fast as you can keep understanding it. If you cannot explain, roughly, what each routine does and where it would break, you have one too many. A smaller setup you fully grasp beats a larger one you merely hope is working. The point of becoming a Solo Chief is to get more done than your own hours allow, and capacity you cannot supervise is just risk with extra steps.

A useful test is whether you could rebuild the operation from memory if it all vanished tomorrow. If you could sketch every routine, what triggers it, what it does, where it would break, you are still the chief. If parts of it have become a black box you are afraid to touch, the operation has started running you. Pruning back to what you understand is not a step backward. It is what keeps the whole thing yours.

What to do this week

Write down your operation as it is now: the work that genuinely needs your judgement in one column, and everything else in another. From the second column, pick the single routine that costs you the most time and the least thought, and build a small agent for it, with you approving the output. Then resist adding a second one until the first has run cleanly for a fortnight. Becoming a Solo Chief is a series of those small, supervised steps, not one big build.

Designing that setup so it stays understandable, and deciding what should never leave human hands, is the kind of work the AI Lessons for Leaders sessions are built around for owners running lean. If you are building an operation that is mostly software, book a personal lesson and we will shape it so you can still run it.

Sources and further reading

• Jurgen Appelo, "The Solo Chief", 2025. Where the Solo Chief idea comes from, including the line about being "the strategist, the operator, and the single wringable neck".
• Jurgen Appelo, "Widesizing: AI Creates More Businesses, Not Fewer Jobs," The Solo Chief, 2025. More on how a one-person operation can now punch well above its headcount.