Opens in a new tab
By Firm Type

How do content studios keep small requests from eating the week?

A dozen small asks nobody scoped will take a content studio's week apart. How to give small work a name, a home, and a share of the month you can actually see.
Marc Pitre·November 18, 2026·8 min read

A client wants the headline changed on a post that’s already scheduled. Someone needs three subject line options before lunch. Legal didn’t like the hero image on the blog piece, so it needs a new one. Two of last month’s articles have to be updated because the product page changed under them. A client asks for “just a quick social cut” of the video that went out last week. Each of those is a small request. Each has a client behind it and a day it’s needed by. None of them is a Deliverable.

A blog post is a Deliverable. A monthly program is a Deliverable. Swapping a headline is nothing, officially. It doesn’t appear on the plan, nobody estimates it, and nobody logs effort against it. So a dozen of them can land in a single week without any of them showing up anywhere, and by Friday the planned work hasn’t started. The only honest account of where the week went is that you can’t fully account for it.

Content studios get this worse than most firms, and not because they’re less organized. Their work arrives in a shape that hides. A web build has a start and a finish. A content program is a river of small things, and small things don’t look like work until you add them up. The way to keep them from eating the week is to make them something you can add up: a named Deliverable with effort logged against it, handled in set windows rather than as it lands.

What the week looks like

On Monday the calendar looks reasonable. Two long pieces to draft, a newsletter, a round of social for the retainer client, half a day held for the pitch deck.

Then the requests start. The headline swap, the subject lines, the replacement hero image. A deck needs four slides for a meeting tomorrow that you’re hearing about now. The client who wanted the quick social cut wants it from the editor who’s halfway through the video that goes out next week.

Every one of those is quick. That’s the word everyone uses, including you. Every one of them is also reasonable, which is what makes this impossible to fix with a policy. You’re not going to tell a retainer client you won’t fix a typo.

By Thursday afternoon one of the long pieces has moved to next week. Nobody missed a deadline on purpose. There was simply never a clear block of time left to write it in.

A small content studio's project board covered in sticky notes for single small requests, with one note visibly multiplying into several.

Why small work hides

Every studio has an unspoken threshold. Above it, work becomes a thing: it gets a name, an owner, a line on the plan, a rough estimate. Below it, work is a favor you do between the real things, and writing it down feels like more effort than doing it.

Your week disappears through that threshold. Work that isn’t named can’t be counted, and work that can’t be counted can’t be planned around. So you end up running two systems at once: the one on the board, which is tidy and wrong, and the one in your inbox, which is accurate and invisible. The team works from the second one and reports against the first.

This is Drift, and it’s worth knowing it by name, because Drift doesn’t look like a problem while it’s happening. Nothing blows up. A gap opens slowly between the plan and what’s really going on, while everybody involved behaves reasonably. Twelve small yeses is exactly the shape it takes in a content studio. Nobody said no to anything, and the planned work didn’t ship.

The retainer is where this bites hardest. A retainer that started as a handful of posts and a newsletter a month quietly grows a second newsletter, a landing page refresh, and a standing Monday call. None of those were ever added to anything, so on paper the retainer looks exactly the way it did the day it was signed, and the person running it is quietly doing half again as much as the plan says.

Give the small work a name and a home

Stop treating small requests as exceptions. Make them a Deliverable.

One standing Deliverable per client per month for the small stuff. Call it whatever your team will say out loud: in-month edits, ongoing requests, small asks. Every quick favor gets logged against that instead of against nothing.

Nobody has to file a ticket to change a headline. The request still comes in by Slack or email the way it always did, and your writers would rather quit than fill in a form for a typo, which is fair. The only new step is that whoever does the work logs the effort against that client’s small-requests Deliverable, which takes a moment.

Log everything against it for a month, then look. What comes back is something you’ve never been able to see before: how much of your studio’s capacity each client’s small work takes, as a share of the month you can say to another person. “We’re always slammed” becomes a specific share of a specific client’s effort, and specific is what lets you act.

Then put it in a window

Once the small work has a name, give it a shape.

Pick a couple of windows a week where small requests get handled, and handle them there instead of as they land. The cost of a quick request was never the request itself. It was the stop, the context switch, and the time it takes a writer or a designer to climb back into the piece they were in the middle of. A developer interrupted for a copy tweak doesn’t just lose the minutes the tweak took. They lose the thread.

Batch the small work and most of that waste goes away. Clients usually can’t tell the difference, which is the quietly annoying part. A lot of “I need this today” requests turn out to mean “I need this before Thursday,” and nobody ever asked. The ones that are genuinely urgent stand out now, because they’re no longer hidden in a crowd of things that weren’t.

You couldn’t have done this before the naming step. Batching requires knowing what’s in the batch.

A large paper wall planner in a small studio with work grouped into a few broad bands of colored tape and several rows left deliberately empty.

Pruning is a decision you can now make

After a month or two of evidence you’ll find a client whose small requests take considerably more of the studio than anyone assumed. Often it’s the client everybody likes.

Now you have a real decision in front of you, with options. Some of that work belongs in the retainer properly, scoped and priced as what it is, with the client told why. Some should move into a monthly block and get handled in one sitting instead of piecemeal. And some of it should simply stop, because it never produced anything the client valued and only continued because yes was easier than the conversation.

None of those calls is possible on a feeling. All of them are straightforward once the pile has a name and a share of the month attached to it. Net Net shows where the effort went, per client and per Deliverable, and leaves the call about what to charge, fold in, or cut to you. Charging, if it comes to that, comes after seeing.

What good looks like

A content studio with this working still gets the same number of small requests. The difference is that they live somewhere.

The planned work ships in the week it was planned for. The team stops guessing which of a dozen things is most urgent, because the urgent ones aren’t camouflaged anymore. When a client asks for more, you know what more costs you in effort before you answer, instead of finding out weeks later from a tired writer.

That’s what Flow looks like in a content studio. Not an empty inbox, just work that moves the way the plan said it would. Pick one client. Make one standing Deliverable for their in-month requests. Log everything against it for four weeks, and let the share tell you what to prune.

FAQ

Why do small requests hurt a content studio more than big projects?

A big project gets scoped, planned, and watched. A small request gets none of that, because each one is too small to justify the paperwork. So none of them appear anywhere, and the pile stays invisible until the week is gone.

Should I start charging for every small request?

Charging comes later. First make the small work visible as a named Deliverable so you can see how much of the month it takes, client by client. Once you can see it, the commercial conversation gets much easier and much less awkward.

How do I group small content requests without adding admin?

Give recurring small work one standing Deliverable per client per month instead of a ticket each. Handle it in set windows instead of as it lands, and log effort against the group rather than against each request.

What’s the sign that small work has taken over?

Your planned work keeps slipping while nothing visibly goes wrong. Nobody misses a deadline on purpose. There’s just never a clear block of time left to do the planned thing in.

See your work before it drifts.

Net Net keeps plan and effort side by side, so you catch the slip while there is still time to act.

Start your free trial