Authexis
Thought leadership for consultantsPaul Welty

Consistent content publishing for busy consultants: a system that survives a 40-hour billable week

Consistent content publishing is a system problem, not a discipline problem. Here's the weekly rhythm — capture, review, draft, distribute — that produces a real publishing practice on top of a full client load, without grinding the consultant into burnout.

The standard advice is "be consistent." That advice has produced more failed consulting content practices than any other single instruction. The reason is structural: "be consistent" is a goal stated as a method, and it gives the consultant nothing to actually do when an engagement gets busy in week three. So they're inconsistent, again, and conclude they're not the kind of person who can publish.

This piece is for the consultant who has already accepted that they should be publishing — the pillar guide covers why — and is now stuck on how. The honest answer is that consistency is downstream of system design. The consultants who publish on a 40-billable-hour week are not more disciplined than the ones who fail. They have a different structure. The structure is what does the heavy lifting in the busy weeks.

Why "be consistent" is the wrong instruction

"Be consistent" assumes the bottleneck is willpower. For consultants, the bottleneck is almost never willpower. It's three other things that look like willpower from outside.

The first is idea recovery cost. Sitting down to write without a captured raw observation costs you 30-90 minutes of staring at a blank page trying to reconstruct what you knew on Tuesday. Multiply by the number of times you try to publish in a busy month, and you've spent 4-6 hours producing nothing. By the third week you correctly conclude this isn't worth the time, and stop.

The second is quality variance. Consultants who care about their work won't ship something they think is mediocre under their name. So when Tuesday's idea has decohered into Friday's vague gesture, the consultant won't push it through — they'll spike it, and lose the week. The standard fix ("just publish anything; perfect is the enemy of good") is not advice a consultant should take, because their professional reputation is the thing being published. The fix has to come earlier in the process, not later.

The third is single-batching. Each piece is being produced from scratch every time, with no leverage from the last piece. Content creators who publish daily have batched workflows that produce four pieces from one capture session. Consultants treating each post as an independent project will produce one piece for the same effort.

The instruction that actually produces consistency is therefore: separate the work into stages, and put the heaviest stage on the calendar at a time when you can do it well. The rest of the system serves that one decision.

The four-stage week

The publishing rhythm that survives is simpler than most content-marketing playbooks suggest. Four stages, distributed across the week, each in its own context.

Stage 1: Capture (~5 minutes per occurrence, daily)

Right after a client call, send yourself a voice memo or a one-paragraph note. The capture answers: what did I just say or notice that surprised me, and what was the specific shape of it. Not a topic. The specific shape.

This is the single highest-leverage habit in the system. Every later stage is faster when this one is doing its job, and impossible when it's not. The 5 minutes you spend at the moment saves the 60 minutes you would have lost reconstructing the thought on Friday. Build the rest of the system around making this stage frictionless. Voice memo on your phone, a Notion inbox, an email-to-yourself loop — whichever you'll actually use.

We covered the front of this in detail in where consultant content ideas come from. The deeper point: capture isn't ideation. It's recording the thinking you already did during paid work, before that thinking evaporates.

Stage 2: Weekly review (15 minutes, Friday afternoon or Monday morning)

Once a week, read back the captures from the past five days. The point of the review is not to plan content. The point is to notice which captures still pull at you when you read them in a different mood than you wrote them in.

Most weeks, three to five captures will produce one piece worth writing. Some weeks zero. Some weeks two. The captures that don't survive the review get archived, not deleted — old captures sometimes resurface useful when paired with a new one months later.

The review is also the failure-mode filter. A capture that read sharp on Tuesday will sometimes read like consensus by Friday. That's the filter working correctly. The capture has done its job (it surfaced a moment where you might have something to say), and the review has done its job (it confirmed you don't, this time). Move on.

Stage 3: Drafting (60-90 minutes, one block per week)

A consultant who publishes weekly needs one drafting block per week. Not three. Not five short ones. One.

The block produces one piece, drafted from one captured note. The captured note carries the specific shape; the block turns it into something a stranger can follow. If the capture is good, drafting is fast — most of the work is already done. If the capture is thin, the draft session will reveal it within the first ten minutes, and the right move is to abandon and pick a different capture, not to push through.

This is also where AI fits cleanly into the workflow. Voice-fidelity drafting tools — the kind that have read a corpus of your existing writing and can take a structured note and turn it into a draft in your voice — collapse the drafting block from 90 minutes to 30. You spend the saved 60 minutes editing, which is where the differentiation happens anyway. (We discuss this more honestly in the pillar guide's tools section; the short version is that AI is useful for capture transcription, argument testing, and voice-fidelity drafting, and counterproductive for idea generation and final-stage polishing.)

The block needs to be on the calendar before it needs to happen. Block it weekly, treat it like a client meeting (i.e., don't move it casually). The biggest predictor of whether a consultant publishes consistently is whether they reliably attend their own drafting block.

Stage 4: Distribution (15-30 minutes, when the draft is done)

Distribution is where most consultants lose the most time for the smallest gain. The mistake is treating each piece like a launch — multi-thread teaser, comment-bomb, ask three friends to share. That math doesn't break even at a fractional executive's hourly rate.

The minimum-viable distribution that actually works:

  1. Publish the long-form piece on a destination you own (your own site, ideally; a Substack as a defensible second).
  2. Write a 200-300 word LinkedIn breakdown of the same piece, ending with a link. (Not a teaser; the breakdown should make sense to someone who never clicks the link.)
  3. Comment substantively on three other consultants' pieces in the same orbit, that week.

That's the entire distribution side. Total time, including writing the LinkedIn breakdown: 30-45 minutes.

The temptation to do more — repost on Twitter, cross-post to Medium, build a thread — should be resisted unless one of those channels is producing measurable inbound. Most of the time the additional channels are producing peer reach, not buyer reach. (Peer reach is fine as a side effect; it's not what the system is for.)

For the LinkedIn-specific moves that do compound — what to post and when, how to handle comments, the algorithmic patterns that have changed in 2026 — see the LinkedIn thought leadership guide for consultants.

How one capture becomes three pieces

The reason this rhythm works on a busy week isn't that the four stages are short individually. It's that one good capture can produce three to five pieces over a few weeks, which means the capture stage carries most of the load and the rest of the stages are amplification.

A worked example. A fractional CMO captures, after a Tuesday call: "Client kept reframing their growth problem as a 'positioning' issue, but every example was a sales-comp incentive that pre-paid the AEs to discount. Three weeks of brand workshops would not fix this. The CFO already knew."

That single capture, well-shaped, can produce:

  • A 1,500-word long-form piece on why "positioning problems" are usually pricing problems wearing a costume.
  • A 300-word LinkedIn post that opens with the reframe ("Most positioning workshops solve the wrong problem") and closes with the specific tell — pre-negotiated AE discount authority.
  • A short methodological piece on how to diagnose pricing-vs-positioning in the first 30 days of a fractional engagement.
  • A reply post a month later when someone in your network posts about brand strategy without addressing pricing.

That's four pieces from one capture. The hour spent on the long-form draft did most of the underlying work. The other three pieces are extracts and angles, each costing 30-60 minutes including distribution.

This is how consultants who publish weekly are actually doing it. They're not generating four ideas a week; they're generating one good capture every two-to-three weeks and extracting from it. The publishing cadence outpaces the capture cadence by 3-5x.

The technical name for this is repurposing, but consultants who do it well don't think of it as repurposing. They think of it as following the implications of one captured observation through to the different audiences it speaks to. The LinkedIn post is for the buyer scrolling on their phone. The long-form piece is for the prospect who saved the LinkedIn post and clicked through. The methodological piece is for the peer who quotes you in a year. Each piece is the same observation reshaped for the audience that needs that shape.

What "consistent" actually means

"Consistent" is one of those words that sounds objective and isn't. For a consulting practice, the meaningful definition is not "publish on a fixed cadence forever." It's "the gaps between pieces are short enough that the audience doesn't decohere."

In practice, that's a piece every 7-14 days for the long-form, and 2-3 LinkedIn posts a week (most of which are extracts from or commentary on the long-form). A piece every 4-6 weeks is too slow; the audience that started forming has moved on by the time the next piece arrives. Daily is too fast; you're producing content-creator volume on consultant economics, and the unit cost stops working.

There's also a distinction worth drawing between consistent and predictable. You don't need to publish on Tuesdays. You need to publish often enough that someone in your network thinks of you as someone who publishes, which is a much lower bar than "publishes on a schedule." A 10-day average gap with a long-form piece dropped on a random Wednesday produces the same effect as a rigid weekly cadence, with much less burnout.

The consultants who fail at this almost always fail by trying to be predictable when they should have been trying to be consistent. They commit to "every Monday at 9am" and then a client engagement runs hot in week three and they miss it and break the streak and stop. The streak was the wrong target. The 10-day rolling average is the right target.

How to know the system is working

The signal that the system is working is not the volume of pieces. It's that publishing happens on weeks where you're busy. If your output drops to zero the moment a hot engagement starts, the system isn't doing its job — the consultant is, and the consultant is too expensive to do this work.

Three diagnostic questions to ask yourself a month in:

  • Did I publish during a week where I billed 35+ hours? If yes, the system is carrying the load. If no, the system isn't designed correctly yet — something needs to be moved earlier (probably capture) or moved off your plate (probably some part of drafting).
  • Did the pieces I published this month come from captures, or from staring at a blank page on a drafting block? If the latter, the capture habit isn't real yet. Fix that before anything else.
  • Was the drafting block protected, or did it get moved twice this month? If moved, treat the block like an external client meeting next month and see if that fixes it.

A working system doesn't require willpower in the moment. It requires that you set up the rhythm in a calm week so that the busy week has the structure to fall back into. That's the entire trick.

Summary

Consistent content publishing for consultants is a system problem. The system has four stages (capture, review, draft, distribute), each in its own context, each protected from the others. The capture habit does most of the work. The drafting block does the visible work. Distribution is minimum-viable on purpose, because the math only works if it stays small. One capture produces three to five pieces. "Consistent" means a 10-day rolling cadence, not a fixed schedule. The diagnostic is whether you publish during your busy weeks.

If you'd like a tool that runs the drafting stage in your voice from your captured notes, start a free trial of Authexis — that's the part of the system most consultants find hardest to do well at speed, and it's what we built specifically for. For the broader frame on why thought leadership is a different category for consultants than for content creators, the pillar guide is the load-bearing piece. For where the captures themselves come from, content ideas for consultants is the companion.