A founder we work with has fourteen usable things sitting in his banks right now. Numbers he can publish. Three explanations that landed on sales calls last month. A question his buyers keep asking that nobody in his category has answered properly.
He publishes three times a week. So he needs three of those fourteen by Tuesday.
Ask him how he picks and the honest answer is: whichever one he feels like when he opens the doc. That is not a failure of discipline. It is a missing layer. His capture system works. His calendar works. Nothing in between tells him what goes next, and nothing tells him what the choice costs.
We've written at length about the banks — proof, story, explanation, objection, question, source — and about the operating system that assembles a post once the material exists. The running order is the piece between them. It's the smallest system in the stack and it's the one almost nobody has.
Posts Are Not Independent, and Everyone Treats Them Like They Are
The reason sequencing gets ignored is that every quality conversation happens at the level of a single post. Is this hook strong. Is the number defensible. Does the close land. All good questions, all about one artifact in isolation.
But a reader does not encounter your content in isolation. Three things make sequence matter:
The platform learns from consecutive signals. Distribution is topic-shaped. What you published last week shapes who sees what you publish this week. A run of posts in one narrow lane compounds; a shuffle across four lanes teaches the platform nothing it can act on.
A new follower reads forward, not backward. Someone who follows you off post twelve sees posts thirteen, fourteen and fifteen next. Those three posts are the argument they'll use to decide whether you're worth keeping. In most founder feeds, those three posts have no relationship to each other at all.
Your profile shows the last few. A stranger who arrives from one post lands on a profile where your most recent activity is doing the introducing. Whatever you happened to publish in the last ten days is your positioning, whether you meant it to be or not.
None of that is exotic. It just never comes up, because there's no artifact to review. A bad post is visible. A bad order is invisible — every individual item passes inspection.
The Three Sequencing Errors
We see the same three, in roughly this order of frequency.
Clustering. Three posts on nearly the same sub-topic inside nine days. Each one is fine. Together they read to a regular reader as "he's saying this again," which is the exact perception the specificity was supposed to buy you protection from. The founder doesn't notice because he wrote them a week apart and they felt distinct while he was writing them. Clustering almost always happens after a good week — one topic went well, so the next two came from the same place.
Spending your best proof on a dead week. The strongest receipt in the bank gets published the Tuesday the founder flies to a trade show and can't reply to a single comment for four days. The post that most needed a live author got the one week he was unreachable. This one costs real money and nobody ever traces it, because the post looks like it underperformed on merit.
Altitude whiplash. A deep operational post, then a broad judgment post, then a deep one again. Individually all strong. In sequence, nothing accumulates — the reader never gets two consecutive posts at a level where understanding builds. Founders do this deliberately, thinking they're providing variety. Variety in format helps. Variety in depth mostly just resets the reader.
The Rule: Sequence in Pairs, Not Singles
The single most useful change we make to a client's running order is to stop treating a post as the unit and start treating a pair as the unit.
Every proof post needs a mechanism post near it. A number establishes that something happened. It does not establish that you understood why. Publish "we cut returns from 11% to 7%" on its own and you've spent a strong receipt to produce admiration. Publish it, then publish the mechanism inside two weeks — what specifically changed, why it worked, where it wouldn't — and the pair produces something better than admiration, which is a reader who now believes you could do it on their account.
Every deep post needs a shallower entry point near it. Not a dumbed-down post. An entry point: the same subject at a level a stranger can walk into. The deep post converts the reader who already trusts you. The entry point recruits the reader who doesn't yet.
Every position post needs a proof post near it. If you're going to argue that the industry is wrong about something, the neighbouring post should be the receipt that gives you standing to say so. Order matters less than proximity. A stranger who reads the argument and then scrolls into evidence is a much better outcome than one who reads the argument and scrolls into nothing.
You don't need a rule for all three every week. You need to stop shipping singles.
Set the Shape of the Week, Then Fill It
The practical version fits in fifteen minutes, once a week, and it looks like this.
Decide the shape before you decide the posts. Three slots a week might be: one proof, one mechanism or explanation, one position or observation. Set the shape once, keep it for a quarter. Now the weekly decision isn't "what should I post" — an unbounded question that invites you to pick your favourite — it's "which proof, which mechanism, which position," which is three small bounded questions your banks can answer.
Work on a two-week horizon, not a quarter. A quarterly editorial calendar is a document you'll abandon by week five, because the interesting material arrives from live work and can't be scheduled in advance. Two weeks is long enough to see a pair coming and short enough that you'll actually maintain it.
Keep a hold list. This is the part founders find genuinely useful and never build on their own. Some material is ready and should not ship yet:
- Anything news-pegged that's waiting on its peg
- A proof post whose mechanism partner isn't written yet
- Anything within about ten days of a post on the same sub-topic
- Your strongest material, when the next fortnight contains a week you'll be unreachable
A hold list is not a backlog. A backlog is stuff you haven't got to. A hold list is stuff you've deliberately decided isn't next, with a reason attached. Writing the reason down is what stops you re-litigating the same decision every Monday.
Protect your best week for your best material. Look at the next two weeks and identify which one you'll actually be present for. Put the strongest thing there. This costs nothing and it is the single highest-return move in the whole system.
What Good Looks Like
Two tells.
The first is that you can say what your last six posts were building toward without looking at them. If the honest answer is "they were all good posts," you have a publishing habit, not a running order.
The second is quieter. When a prospect references something you wrote, they increasingly reference two things — the number and the reason, or the argument and the receipt. That's the pair working. One post makes an impression. A pair makes an understanding, and understanding is what survives the three weeks between reading you and needing you.
FAQ
Isn't this just a content calendar? A calendar answers when. The running order answers what next, and why that one. Most founders have the first and think it covers the second. It's the difference between a schedule and a set list — same songs, and the order is most of the show.
What if the best material always arrives at the wrong time? It does, and that's fine. The hold list exists for exactly this. The rule isn't "publish in a fixed order," it's "know what you're holding and why." Material that arrives hot and news-pegged jumps the queue; material that will still be true in three weeks waits for the week you can defend it in the comments.
Doesn't planning two weeks out make the content stale? Only if you plan the posts. Plan the shape and hold the slots. A slot that says "proof, published Thursday" can be filled on Wednesday with something that happened Tuesday.
I only publish twice a week. Is this overkill? It matters more, not less. At two posts a week you get roughly a hundred slots a year, and every clustered pair or badly-timed receipt is a larger fraction of your annual distribution. Lower volume raises the cost of a bad running order.
Who should own this if I have a ghostwriter? We do, and we bring it to the sync rather than executing it silently — because the one input we can't supply is which week you'll actually be around. That's a thirty-second answer from you that changes what we ship.
If your banks are full and your feed still feels random, the missing piece is almost never more material. It's the fifteen minutes that decides which of it goes next. We build that layer with every client we work with — usually in the first month, because it's the cheapest improvement available and it works on the material you already have.