Strategy · November 21, 2026 · 8 min read
How to Keep a Business Blog Going With a Full-Time Job
Set the cadence your worst month can carry, keep two finished posts in the queue, and standardise the format so you stop deciding. Missed slots are a scheduling fault, not a discipline one.
By FluxWriter
Blogging with a full-time job fails on scheduling, not on willpower, and the fix is to shrink the job rather than find more hours. The usual pattern is a weekly cadence set in January, a bad fortnight in March, two missed slots, then nothing. The blogs that last are built around your worst month, not your best week. This covers how to set a cadence that holds, why a two-post buffer matters more than any productivity system, how to standardise the post so you stop deciding, and what to do the week you miss.
The Hours Are Not the Binding Constraint
Add up what a post actually costs you. For someone who already knows the subject, a 1,200-word post lands somewhere between two and four hours end to end, and most of that is not typing. It is choosing the topic, settling the angle, working out the headings, then formatting and publishing. Assume three hours as a working figure. Twelve posts a year is thirty-six hours, which is roughly forty minutes a week.
Almost nobody with a full-time job is short forty minutes a week. What they lack is forty uninterrupted minutes at a predictable time, plus the setup cost of picking up something last touched a month ago.
That setup cost is the real bill. Every restart means re-reading what you published last, re-deciding what to write about, re-finding the login to your own site, and re-remembering how you formatted the headings. That re-entry tax can run close to an hour before a single useful sentence gets written, and it is charged every time the gap grows long enough to forget.
So the constraint is not the writing hours. It is that an irregular schedule pays the setup cost on every post and a regular one pays it once.
Pick the Cadence Your Worst Month Survives
Most people choose a cadence from their best week. A quiet Sunday, two posts written, weekly feels obviously doable. Then the busy season arrives, or a client blows up, or the children get ill, and weekly is the first thing to go.
Choose from the other direction. Think of the worst month you had last year and ask what you could have published in it without heroics. For most owners with a day job the honest answer is one post, sometimes two. That is your cadence. Monthly is not a compromise, it is the number that does not break.
Publishing less has a real cost: fewer posts means fewer entry points into your site and slower accumulation. Twelve useful posts a year will do less than fifty would. But twelve a year for three years beats eleven followed by two years of silence, because the second pattern leaves a blog that looks abandoned to everyone who lands on it.
Two Finished Posts in Hand Is the Whole Insurance Policy
The change that separates blogs that last from blogs that stop is publishing from stock instead of from today. Write ahead. Keep two finished, scheduled posts in the queue at all times, publish from the back, and top it up from the front.
At a monthly cadence a two-post buffer buys two clear months of cover. A bad fortnight becomes invisible, because the site publishes whether or not you wrote anything that week. Nobody reading can tell, which removes the guilt spiral that usually does more damage than the gap itself.
Building the buffer is the hard part, and it is a one-off: a month where you write two posts and publish one. Do it once, in a quiet stretch, then defend it. The rule is simple: you may publish from the buffer, but you refill it before you write anything for any other channel.
If the buffer hits zero, that is your early warning, not the missed post. A missed post is a lagging indicator; an empty queue is a leading one.
One Format, Used Until It Bores You
Most of the cost in a post is deciding, not producing, and the decisions repeat. What it should be about. How long it should be. What the headings are. Where the internal links go. Answer each of those once, write the answers down as a template, and every post after that skips the deliberation.
Pick one shape and reuse it: a plain question in the title, the answer in the opening paragraph, four to six sections with statement headings, one table or worked example, and a closing paragraph with a next step. It will feel repetitive to you long before it feels repetitive to someone who sees one of your posts a month.
The figures below are illustrative rather than measured, and yours will differ, but the shape holds. Standardising cuts the deciding far more than it cuts the writing.
| Stage | Ad hoc, per post | With a fixed format | Where the saving comes from |
|---|---|---|---|
| Choosing the topic | 35 min | 5 min | pulled from a standing list, not decided fresh |
| Outlining | 30 min | 10 min | the same heading skeleton every time |
| Drafting | 110 min | 90 min | fewer structural rewrites mid-draft |
| Editing and formatting | 35 min | 20 min | one checklist, no formatting decisions |
| Publishing and linking | 15 min | 10 min | a saved template and two internal links |
Ad hoc totals three hours forty-five; standardised, two hours fifteen. The drafting row barely moves, which is the point: writing is the part that cannot be compressed much, so compress everything around it.
Keep the standing topic list in one file, and add every question a customer asks you, in their words. Thirty real questions removes the most common cause of a missed post: sitting down with the time free and no idea what to write about.
Batch the Deciding, Not the Writing
Batch drafting rarely works with a day job. Three posts in one sitting tends to produce one good post and two tired ones. What batches well is everything that is not drafting.
Run one ninety-minute planning session per quarter. Pick the three topics from your standing list, write the title and the five headings for each, and note the one internal link each should carry. That is a quarter of deciding done in a single block, and every writing session after it starts from an outline rather than a blank page.
Protect a fixed slot rather than hunting for time. A recurring calendar entry at an hour your job does not reach, early morning or a weekday evening you already treat as yours, beats any system that depends on finding a gap. One two-hour block a month, defended like a client meeting, plus that quarterly session, covers twelve posts a year.
A Missed Week Is a Scheduling Bug, Not a Character Flaw
When a slot gets missed, the instinct is to treat it as a discipline failure and resolve to try harder. Resolving to try harder changes nothing, because the schedule that just failed is still the schedule.
Diagnose it instead. Missed slots usually trace to one of four causes, each with a different fix. The cadence is higher than your real capacity, so lower it. The slot sits at the wrong hour, so move it. The topic was still undecided when the slot arrived, which means the quarterly planning session did not happen. Or the buffer was empty, so an ordinary bad week turned into a visible gap.
Then make the smallest change that stops the recurrence and carry on from the next slot. Do not write two posts to make up the missed one. Catching up is how a small failure becomes an abandoned blog: the debt makes the next session bigger, the bigger session gets postponed, and a month later the blog is over.
What Twelve Posts a Year Actually Buys You
A monthly blog behaves more like inventory than like a growth channel with a switch on it. The early months look like nothing much. Search results move slowly, a new post on a site with little history can take weeks or months to settle, and no cadence guarantees a ranking or a visitor.
What it does reliably buy is that inventory. Thirty-six posts after three years is thirty-six answers to real customer questions, thirty-six pages to link internally, thirty-six things to send to a prospect who asks. A few will quietly do most of the work, and you will not know which in advance. That uncertainty is the argument for continuing rather than stopping.
FAQ
Is it better to publish one post a month or batch a quarter's worth when I get a free weekend?
Batch the writing if that suits you, but schedule the output monthly rather than publishing three posts on one day. The queue is what you are protecting. A weekend that produces three drafts and fills the buffer is a good weekend; one that publishes them all that afternoon leaves nothing in reserve.
How long should each post be if I only have a couple of hours?
Long enough to answer the question and no longer. As a rough rule, 1,000 to 1,500 words fits a two-hour session for someone writing about their own field, because the research is already in your head. A short post that answers fully is worth more than a padded one that circles.
Should I hire a freelance writer instead?
It depends on whether your bottleneck is hours or knowledge. A freelancer removes drafting time but adds briefing, reviewing and correcting time, and for a specialist business the review can cost nearly as much as writing would have. Try it on two posts and decide from your own numbers.
The Practical Takeaway
This week, spend about two hours on three things. Write down the worst month you had last year and set your cadence to what that month could have carried, which for most people with a full-time job is one post a month. List every question a customer has asked you in the last six months, in their wording. Then put a recurring two-hour block in your calendar at an hour your job does not reach. Do the calendar entry first, because the cadence and the list are worthless without a slot to spend them in.
If FluxWriter is the insurance rather than the writer, a monthly schedule on any paid plan keeps publishing through a bad stretch, and the Pause button on the Schedules page stops it in the months your own buffer is full.