Strategy · November 20, 2026 · 8 min read
How Many Hours a Week Does a Business Blog Take?
One finished blog post takes roughly four hours, so one a week costs four to six hours, two costs eight to nine, and four costs fifteen to seventeen. Drafting is under half of that.
By FluxWriter
How many hours a week does blogging take? For one finished post a week, budget four to six hours, and expect the drafting to account for less than half of it. Two posts a week runs to eight or nine hours, and four posts is fifteen to seventeen, which is most of two working days. This breaks the weekly total into the six tasks that actually consume it, shows which ones quietly expand, and gives you three budgets to hold against your own calendar.
A Blog Post Is Six Jobs Wearing One Name
Most owners price a blog as writing. Writing is one of six tasks, and it is the only one anybody thinks to put on the calendar. The other five happen anyway, in gaps, at the end of the day, and they are the reason the two hours you budgeted turned into a Saturday.
The six are these. Deciding what the post is about and what it argues. Drafting it. Editing it and checking the facts. Making or finding the images. Formatting and publishing it in your CMS. Looking at what the last few posts actually did. Each one fails differently. Topic selection fails by indecision. Editing fails by being skipped. Publishing fails by rebuilding the same layout by hand every week. Results checking fails by never happening at all.
None of this is difficult work. All of it is time, and it arrives in awkward shapes, which is why the honest weekly number is usually higher than the one in your head.
Deciding What To Write Costs More Than Owners Expect
The topic decision is short if you have a list and long if you do not. With a planned queue, picking the next post and settling its angle takes something like half an hour: check that people search for it, check you have not already covered it, decide what the post claims. Without a queue, that same decision can eat a morning, because you are not choosing a topic. You are re-deciding your entire content plan in order to choose one.
It is also the decision that governs everything downstream. A weak topic wastes the three and a half hours that follow it. A strong one makes the draft easier to write, because you already know what you are arguing before you open the document.
The fix is dull and it works. Choose a quarter's worth of topics in one sitting, write them in a list with the angle next to each, and never make the decision on the morning you write. That single change usually takes the weekly topic cost down to a few minutes.
Drafting Is The Largest Single Task And Still A Minority Of The Total
The split below is illustrative rather than measured. It assumes a 1,200 to 1,500 word post on a subject you already understand, written by the owner rather than a professional writer, and your own times will differ by an hour in either direction.
| Task | Typical time per post | Share of the four hours | What blows it out |
|---|---|---|---|
| Choosing the topic and angle | 40 min | 17% | Deciding from scratch on the day |
| Drafting | 100 min | 42% | Researching while writing rather than before |
| Editing and fact-checking | 50 min | 21% | A draft written from thin knowledge |
| Images and screenshots | 25 min | 10% | Hunting for a stock photo that fits |
| Formatting and publishing | 25 min | 10% | Hand-building the layout in the CMS |
| Checking results | 30 min, weekly not per post | n/a | Rebuilding the same report each time |
Four hours a post is the anchor to hold on to. Drafting is the biggest single line in it, and it is still only about two fifths of the work. The five tasks arranged around the writing add up to more than the writing does.
That ratio is the part worth sitting with, because it changes what is worth fixing. If you doubled your writing speed tomorrow, you would save roughly fifty minutes a post and the week would still cost you more than three hours. The savings that actually move the number are in the boring tasks: a topic list you decided in advance, a publishing routine you do not reinvent, a results check that is quick because the report already exists.
Three Honest Weekly Budgets
One post a week is four hours of post work plus about half an hour of looking at results, so call it four and a half hours, or four to six once real life gets involved. This is the budget most small businesses can genuinely hold. It suits an owner with one protected morning, and it produces roughly fifty pages a year, which is a real asset even if no individual post does much.
Two posts a week is eight hours plus the same overhead, and batching the topic and image work claws back a little, so eight to nine hours is the honest figure. That is a full working day, every week, permanently. It cannot live in spare time. Either it has a fixed slot in the diary or it quietly becomes one post a week and you stop trusting your own plan.
Four posts a week is sixteen hours of post work plus about an hour of admin. Batching trims perhaps a tenth off that, which lands you at fifteen to seventeen hours. That is not a side task by any reading. At this volume the work is a part-time job, and the only sane versions of it are a hired writer, a freelance team, or software doing the first draft and the publishing while you keep the editing.
There is one number that does not appear in any of these budgets, and it matters more than the rest. Consistency is what makes the hours compound. A blog that takes four hours a week for a year beats one that took sixteen hours a week for two months, and it is not close.
Delegating Changes The Shape Of The Hours Rather Than Removing Them
The instinct when the number looks too big is to hand the writing away. That helps, but less than the arithmetic suggests, because you only ever hand away the drafting. Someone still has to choose the topic, brief the writer, and check that the finished thing is true and sounds like your business.
Say drafting drops from a hundred minutes to twenty-five, which covers briefing plus a first read. Editing goes the other way, because editing someone else's draft is slower than editing your own, so call it sixty-five minutes rather than fifty. Everything else is unchanged. The post now costs three hours instead of four. That is a real saving of about an hour per post, and at one post a week it is an hour, not an afternoon.
The same maths applies to AI drafting, and it applies to a junior hire. What is being removed is the two fifths, not the whole. The tools and the people who cut the number properly also take on the formatting, the publishing and the repetitive checks, because that is where the other three fifths sit.
Four Things Reliably Push The Number Higher
Approval chains are the first. Every reviewer adds a round trip and usually a calendar day, and two reviewers add considerably more than two. The hours worked barely change; it is the elapsed time that breaks a weekly schedule.
Subject matter you do not personally hold is the second. If it needs an expert interview, add the scheduling and the write-up, then treat that post as two. The third is anything image-heavy: original screenshots, annotated diagrams and product photography are their own project, and a post needing eight of them is not a four-hour post.
The fourth is restart cost. Come back after six weeks off and the first post tends to take closer to six hours, because you have to re-read what you were doing and re-find your voice before you can write a word. That cost is invisible when you decide to skip a week, which is exactly why it is worth naming before you skip one.
FAQ
Is one post a week enough to be worth doing?
It depends entirely on your market and the topics you pick, and nobody can promise you a ranking at any volume. What one post a week reliably buys is around fifty pages a year, each aimed at a question someone actually types. Whether that turns into traffic depends far more on whether you chose topics with real demand and a chance of competing than on whether you published fifty or a hundred.
Should I write longer posts less often, or shorter posts more often?
Look at the fixed costs before deciding. Roughly ninety minutes of the four hours is length-independent: choosing the topic, making images, formatting and publishing. A 600-word post therefore does not cost half of a 1,400-word post, it costs perhaps two thirds, so short posts carry a worse overhead ratio than people expect. That argues for fewer, more substantial posts if your hours are tight.
Does batching actually save time?
For some tasks, yes. Choosing six topics at once is much cheaper per topic than choosing one six times, and making images in one sitting saves the setup each time. Drafting and editing barely batch at all, since they are the tasks that need fresh attention. As a rough rule, expect batching to take around a tenth off a multi-post week, not a third.
The Practical Takeaway
Do not estimate your own number, measure it. This week, put a stopwatch on one post and record the six tasks separately rather than logging one total at the end, because the total tells you nothing about what to fix. Then hold that figure against the hours you can actually protect every week for the next year, not the hours you can find once. If the post costs five hours and you have three, the answer is not to work faster but to publish less often, delegate a task, or drop the blog on purpose rather than by attrition. The first action is the stopwatch: six numbers, one post, this week.
In that table, FluxWriter mostly takes out the images and publishing rows: a generated post can arrive with its featured image and goes into your CMS already formatted, though screenshots of your own product still have to be taken by hand.