How Much Content Can You Actually Make?

Creators make promises about content constantly — a posting cadence, a launch schedule, a custom turnaround, a commitment to subscribers — and then break them, not because they are unreliable people but because they promised from a number they never actually calculated. They estimated how long the shoot would take and quietly assumed the rest was free. This guide is part of our content operations hub, and it is about working out the one number that stops you from over-promising: how much content you can actually make in the hours you actually have.

Capacity is a number, and you should know it before you promise

Content capacity is your realistic output — how much finished, postable content you can produce in a normal week, given the time you genuinely have. It is a number you can calculate, and calculating it before you commit to a cadence is the difference between a schedule you keep and one you apologise for. Most creators run it backwards: they decide on an ambitious schedule first and then try to hit it, discovering the hard way that their capacity was lower than their ambition. Capacity planning just puts the number first, where it belongs.

The reason to do this on purpose is that the cost of getting it wrong is not neutral. Over-promise your capacity and you do not just work harder — you break commitments to the people paying you, which costs trust that is far more expensive than the content itself. Knowing your capacity is how you make promises you can keep, and keeping them is a large part of what a subscriber is actually paying for.

The cost is the whole pipeline, not the shoot

Here is the mistake that hollows out almost every capacity estimate: counting the shoot and forgetting everything after it. The shoot is the visible, fun, fast part — and it is a fraction of the true cost of a finished piece. Every deliverable also has to be edited, culled, named, captioned, and often approved before it can go out, and that finishing work routinely costs more than the shoot did. A "quick shoot" is not a quick deliverable; it is a quick start to a much longer job.

So capacity has to be measured in full-pipeline hours — the total time from raw idea to postable asset — not in shoot time. This is the same finishing tax that shows up in batching and in content runway, and it is the reason all three of those numbers come out lower than people expect. Count the whole pipeline, and your capacity number gets smaller and, for the first time, true.

Capacity varies by format — price each one

You cannot compute capacity in generic "posts," because a post is not a unit of consistent effort. A simple photo set, a produced video, a custom, a livestream — each has a completely different full-pipeline cost, sometimes by a wide margin. Promising a flat number of posts a week treats these as interchangeable when they are not, and the promise breaks the first week the mix tilts toward the expensive formats.

The fix is to price each format you make in full-pipeline hours, then plan your week as a mix against the hours you have — so many of the cheap format, so many of the expensive one, summing to something that fits. This is more work than "I'll post five times a week," and it is the difference between a plan and a wish. It also tells you something strategically useful: which formats give you the most sellable content per hour, which is worth knowing when you decide where your limited production time should go.

Promise from a normal week, not a heroic one

The final discipline is which week you plan against. There is a version of you that, on a great week with nothing going wrong, can produce a lot — and if you promise from that week, you will miss the promise on every normal one. Capacity for planning purposes is your sustainable output: what you can do on an ordinary week, with the usual friction, leaving margin for the days that go sideways. Promise from that, and treat the great weeks as upside you bank rather than baseline you owe.

This is just under-promise, over-deliver applied to production. A cadence you comfortably beat builds trust every week; a cadence you miss spends it every week, and a subscriber reads a slipped schedule as a page that stopped caring — one of the quiet drivers behind why subscribers cancel. The creators who look effortlessly consistent are usually the ones who promised a number below their capacity, not above it.

Capacity and runway: the two production numbers

Capacity and runway are the pair that together describe your production health. Capacity is a rate — how much you can make per week. Runway is a stock — how much you have banked right now. You need both: capacity tells you whether you can sustain a cadence going forward, and runway tells you whether you can survive a bad month while you do. A creator with high capacity and no runway is one bad week from a gap; a creator with runway but capacity below their cadence is slowly draining the buffer they built. Watch both, and you can tell the difference between a sustainable operation and one quietly running down.

Work out yours

Do the calculation, because it only works as a number. List the formats you make, estimate the full-pipeline hours each one costs, look honestly at the hours you have in a normal week, and see how much actually fits. That figure — usually humbling, always useful — is your real capacity, and every promise you make about content should sit comfortably underneath it. From there, batching is how you raise it, the operator's week is how you schedule production against it, and the rest of the content operations hub is how you turn a realistic number into a page that never has to break a promise.

This is general operational information, not a guarantee of results. Your real capacity depends on your workflow, your formats and factors outside anyone's control. Treat this as a framework to adapt, not a promise about your output.