How a Solo Agency Ships Client Content Without Hiring

The ceiling on a one-person studio is almost never talent. It is that six clients produce six inboxes, six approval threads, six sets of brand rules and six people who all think Thursday afternoon is a reasonable time to ask for something by Friday. The work is fine. The switching between it is what breaks.

A solo agency that serves six clients comfortably is not working faster than one that struggles with three. It has turned the parts that repeat into a system, and kept the judgement for the parts that do not. Here is what that system contains.

The cost is switching, not producing

Time a week honestly and the pattern is always the same. Writing a client's posts takes an hour. Getting back into that client's head takes twenty minutes, and you pay it every time you touch their work. Six clients touched three times a week is six hours a week of reloading context.

That is the number to attack. Not your writing speed, not your tools. Everything below exists to reduce either how often you switch or how expensive each switch is.

One page per client, and it is the source of truth

Every client gets a single page you can read in ninety seconds, and it is the only place their rules live. Not a folder, not a thread, one page.

• Who they sell to, in one sentence, including who they are not for.
• The three things they always want said and the two they never want said. The second list is more useful than the first and nobody ever writes it down.
• Voice, shown not described. Two paragraphs of their own writing that sound right, and one that sounds wrong. Adjectives like friendly and professional tell you nothing.
• The proof they are allowed to claim. Numbers, certifications, named clients. This is what stops an approval round happening over a factual error.
• Where it publishes, with logins or the person who has them, and the sizes that platform needs.

Write it during onboarding, with the client, and get them to agree to it in writing. Half the revisions in agency work are disagreements about something that was never specified, and specifying it is cheaper than arguing about it six times.

Batch by client, not by task

The common advice is to batch by task: write everything on Monday, design everything on Tuesday. For a solo agency that is exactly wrong, because it maximises the number of context switches. Writing six clients' posts in a row means loading six different voices in one morning.

Batch by client instead. One client gets one block, and in that block you do all of their work for the period: the posts, the images, the email, the scheduling, the report. You load their context once and spend it on everything.

Two clients a day, two blocks each of about two hours, gets six clients through a month of content in a week and leaves the rest of the month for the work that is actually bespoke. The blocks go in the calendar as fixed appointments, the same way a client meeting would.

Fix the approval loop, or nothing else matters

The approval round is where solo agencies lose their margin. A client who takes four days to reply and then asks for three changes has cost you more than the work did, and they have done it while you were holding six other things in your head.

Three rules fix most of it. First, one approval window per client per period, on a fixed day, with everything in it. Drip-feeding work for approval creates a permanent open thread with every client at once.

Second, a stated deadline with a stated default. Feedback by Wednesday, otherwise it publishes as written. This sounds aggressive and clients accept it readily, because it is the only version of the arrangement in which they can rely on things going out.

Third, two rounds included, then it becomes new work. Write it into the contract. The point is not to charge more, it is that unlimited revisions make it rational for the client to think out loud at your expense.

Kill the ad-hoc request

A message on Thursday saying can we get something out about the new opening is not a small request. It is a context switch, a research task and a scheduling change, and it arrives free because there is nowhere else for it to go.

Give it somewhere else to go. One intake route per client, whatever form suits them, and everything that arrives there goes into the next batch rather than into today. Genuine emergencies get an agreed rush fee, which converts most of them into non-emergencies.

Every channel a client can reach you through is a channel you have to check. Fewer is not rudeness, it is the reason their work ships on time.

Report in a fixed shape, at a fixed time

Reporting eats solo agencies because it feels obligatory and nobody has decided what it is for. Decide: it exists so the client can see whether to keep paying you, and so you can see which work is worth doing more of.

That needs one page. What went out, the two or three numbers you agreed to be judged on, what you learned, and what you are doing next month because of it. Same shape for every client, filled in during their batch block, sent on the same day each month.

A short report on the same date every month builds more confidence than a long one that arrives when you get to it. Clients are not comparing your report to a better report. They are comparing it to silence.

Price the system, not the hours

Once the work is a system, hourly billing punishes you for every improvement you make. Get faster, earn less. Price by the outcome and the cadence instead: what goes out each month, through which channels, with what included.

That also makes the boundary enforceable, because the package says what is inside it. Extra channels, extra rounds and rush requests sit outside, priced, and the conversation stops being about whether something is reasonable.

It changes what you sell, too. You are no longer selling your afternoons, you are selling a reliable publishing operation. That is worth more per client and it is the thing that lets one person hold six of them.

The order to build this in

Do not build all of it. Start with the client brief page, because everything else gets faster once it exists. Then move to batching by client for one month and see what it does to your week. Then fix the approval window, which is the one clients notice, so it is easier to introduce once they have felt the improvement.

The underlying discipline is the same one that works for a business marketing itself: a fixed slot, a small repeatable routine, and a refusal to do the same piece of thinking twice. The 30-Minute Marketing Week is that idea at one-business scale, and much of the cutting and repurposing logic in Turn One Product Photo Into a Week of Content applies directly to a client batch block.