From raw material to a posting habit
“I want to post consistently about something worth being known for, without inventing statistics.” Content fails at the material stage, not the writing stage. This workflow starts with the position, then builds the capture habit that feeds it, and only then writes — which is why it produces posts in week six as well as week one.
Each step's output is the next step's input
Read the In and Out lines down the page. Where they do not line up, the workflow has a gap — that is the test, and it is why these are written this way rather than as a diagram.
Decide the claim30 min, once a year
- In
- Your last 5–10 posts and what you sell
- Out
- One defensible claim, three themes, and the not-list
Set up capture20 min, once
- In
- The claim and themes
- Out
- CONTENT-ENGINE.md, naming where material comes from and who logs it
Set up the assistant10 min, once
- In
- BRAND-VOICE.md and the claim
- Out
- A Project that drafts in your voice and refuses to invent facts
Draft from material5 min per post
- In
- A call, a result, a mistake, an analysis
- Out
- A post, two alternative openings, and the pinned comment
Get more from one source15 min per source
- In
- A long piece: webinar, report, transcript
- Out
- The posts the source honestly supports — an honest count, not ten
Be visible without reach10 min daily
- In
- Posts from the accounts your audience reads
- Out
- Comments that earn a reply from the author
What you end up holding
Each step leaves something behind. These are the things worth keeping between runs.
One defensible claim, three themes, and the not-list
CONTENT-ENGINE.md, naming where material comes from and who logs it
A Project that drafts in your voice and refuses to invent facts
A post, two alternative openings, and the pinned comment
The posts the source honestly supports — an honest count, not ten
Comments that earn a reply from the author
The reference behind this workflow
Every figure sourced, every limitation stated in the piece rather than in the replies.
Run it with the context already loaded
Every step goes faster inside a Project that already knows your ICP, your product and the platform limits. That is what the packs are.