How to Do the Work of Five People as One Person

The phrase sounds like a productivity boast, but for a solo founder it is a description of the actual job. You are the head of delivery, the head of sales, the head of marketing, the support desk and the finance department. Five titles, one calendar, and no version of time management that makes 45 hours cover 200.

So stop measuring the workload in hours and start measuring it in kinds of work. Almost every function contains a small core that genuinely requires you and a large shell of repetition that only requires someone. The shell is what makes five jobs impossible. It is also the part that can leave.

That split is what Sistava is built around. You hire an AI employee per function, give it the shell of that function, and keep the core. A sales employee chases and drafts while you take the calls. A support employee answers the routine tier while you handle the hard ones. Nobody is doing five jobs. Five jobs are getting done.

Why does working harder never get you to five people's output?

Because the limit is not effort, it is switching. Moving between five roles costs you a re-entry tax every time, and the tax is heaviest on the work that pays. Ten interruptions from the support role can destroy a morning that was supposed to produce billable output, and no amount of discipline recovers that morning.

There is also a quality floor. A person doing five jobs does all five at roughly the standard of a distracted amateur, including the one they are genuinely expert at. Clients feel it, even when they cannot name it. The fix is not to get faster at switching. It is to stop being the one switching.

How do you split a job into judgment and repetition?

Take one function and write down everything you did in it last week. Then mark each line with one question: if a smart new assistant had my notes, could they do this without asking me? If yes, it is repetition. If no, it is judgment. Do not overthink the borderline cases, because you will find most lines are obviously one or the other.

The result is uncomfortable in a useful way. Most founders discover that their sales function is 15 percent conversations and 85 percent chasing, and their marketing is 10 percent opinion and 90 percent production. Once you see that, hiring becomes obvious: you are not replacing the function, you are removing its shell.

A worked example: a solo fractional CFO with three clients too many

Marcus runs a fractional CFO practice for e-commerce brands. He was serving four clients and had turned down three, not because he lacked the skill but because each client generated a tail of work he could not compress: monthly reporting packs, chasing bookkeepers for missing receipts, prep notes before every board call, and a stream of small questions between sessions.

He mapped one client's month. Eleven hours of it was analysis and advice, the part he is paid for. Nineteen hours was the tail. Same skill on paper, completely different value, and the tail scaled linearly with every new client he took.

So he hired two AI employees. An operations employee that assembled each monthly pack from the same sources, chased the missing documents on a schedule, and produced the draft commentary he then rewrote. A support employee that answered the between-session questions it could answer from prior notes and forwarded the rest with the numbers already pulled.

The tail dropped from 19 hours to about 7 per client, and most of the remaining 7 was him editing drafts rather than building them. He took two of the three clients he had turned down. His revenue went up by roughly 45 percent on the same working week, and he did not add a single person.

What does this approach not solve?

It does not multiply the work only you can do. If your revenue is capped by your own billable hours, removing the shell gives you more of those hours but not infinite ones. At some point growth requires either a different pricing model, a product, or an actual person. AI moves the ceiling. It does not remove it.

It also does not help if the offer is unclear or the demand is not there. Five functions running smoothly on a product nobody wants is just an efficient way to discover that. Fix the offer first, and treat any capacity you gain as a way to test it faster rather than a way to shout louder.

• Your expertise does not scale by itself. Removing the shell buys hours, and those hours still have a limit.
• Bad inputs stay bad. If your notes, docs and pricing rules are not written down, the output will be generic.
• Review never goes to zero. Expect about an hour a week, forever, and more in the first fortnight of each new role.
• Some tails should be deleted, not delegated. Before automating a report nobody reads, try stopping it.

How do you actually build this capacity?

Do it function by function, starting with the one whose shell is thickest. The point of each step is to remove your hands from the repetition without removing your eyes from the result, so keep an approval step until the output stops surprising you.

1. Log one week honestly — Every task, roughly timed, tagged by function. Do not tidy it up. The messy version is the one that shows you where the hours actually go.
2. Mark judgment or repetition on every line — One question per line: could a smart assistant with my notes do this without asking me? Total the repetition column per function.
3. Hire for the thickest shell first — Whichever function has the most repetition hours gets the first AI employee. Give it that shell, not the whole function.
4. Write down what you never wrote down — Pricing rules, tone, ideal customer, red lines. This half page is what separates useful output from generic output.
5. Approve for two weeks, then move to the next function — Correct with one line per rejection. When rejections get rare, drop to weekly review and repeat the whole loop on the next function.

The point of all of this is not to look impressive on a founder podcast. It is to make five functions run at a decent standard while you work a normal week and stay good at the one thing clients actually pay you for. If the schedule side is what breaks first for you, how to run a one-person business without burning out covers the routine that holds it together.

FAQ