Most founders don’t have a “content problem.”
They have a systems problem.
- They post when they feel inspired.
- They disappear when the product gets busy.
- They optimize for likes instead of leads.
The fix isn’t “work harder.”
It’s building a Content OS: a lightweight workflow that turns your weekly product reality into high-signal posts—on a schedule—without draining your attention.
This post is the blueprint.
The goal (what we’re optimizing for)
The goal is consistent, compounding trust.
Not virality at any cost.
If you’re a founder, your best content does three things:
- Signals competence (you know what you’re doing)
- Signals taste (you can make good decisions)
- Signals momentum (you’re actively building)
Everything below is designed to produce those signals efficiently.
The Content OS in one sentence
Every week you:
- capture raw inputs → 2) turn them into 3–5 “post primitives” → 3) publish them across channels → 4) recycle winners.
The key is the idea of post primitives.
A post primitive is a small, reusable unit you can remix:
- a hook
- a story
- a framework
- a teardown
- a list
- a strong opinion
- a before/after
Most creators try to ship finished essays.
The Content OS ships primitives, then recombines them into volume.
Step 1: Build your “Input Library” (15 minutes/week)
Your biggest bottleneck is not writing.
It’s having something worth writing about.
So we create an Input Library: a place where raw material lands automatically.
Your Input Library categories
Capture inputs in these buckets (copy/paste into a notes doc):
- Customer language
- objections
- feature requests
- surprising use-cases
- Build log
- what shipped
- what broke
- what you learned
- Decisions
- tradeoffs
- why you said no
- what you’d do differently
- Numbers (even rough)
- conversions
- churn reasons
- onboarding completion
- Beliefs
- spicy takes
- “unpopular but true”
- principles
The only rule
If a week goes by and you didn’t capture inputs, your Content OS is dead.
The easiest habit: write 3 bullets every Friday:
- What did we ship?
- What did we learn?
- What are we saying no to?
That’s enough.
Step 2: Turn inputs into 3 post primitives (45 minutes/week)
Now we convert raw inputs into three primitives.
Not thirty.
Three.
Because the goal is repeatability.
Primitive A: “The lesson”
Template:
I used to believe ___.
Then I learned ___ the hard way.
Here’s what changed:
If you’re building ___, do ___.
Why it works: it’s honest, specific, and teaches.
Primitive B: “The teardown”
Pick one:
- a landing page
- an onboarding flow
- a pricing page
- a competitor
- an ad
Template:
I reviewed ___ so you don’t have to.
What they do well:
What I’d change (and why):
The takeaway: ___
Why it works: it’s concrete and positions you as someone with taste.
Primitive C: “The decision memo”
Template:
We considered doing ___.
We didn’t.
Here’s the decision memo:
✅ Pros:
❌ Cons:
The rule we use now: ___
Why it works: founders relate, and it’s rare signal.
Step 3: Multiply primitives into 30 posts/month (30 minutes/week)
This is the cheat code.
Each primitive becomes 5–10 posts by slicing it into formats.
The “format matrix”
Take one primitive and produce:
- Short post (120–180 words)
- Bullet list (7–10 bullets)
- Framework (3 steps)
- Story (beginning → tension → lesson)
- Opinion + rebuttal
- FAQ (3 Qs)
- Before/after
You don’t need to invent new ideas.
You just reformat.
Example: one lesson → 7 posts
Lesson primitive:
“We doubled activation by removing 2 fields from onboarding.”
Posts:
- Hooked story: “We thought more questions = better personalization. Wrong.”
- Framework: “Onboarding field rule: ask only what you must know now.”
- Teardown: “Here’s why most onboarding flows fail: they’re insecure.”
- FAQ: “Do we lose lead quality if we ask less?”
- Opinion: “Your onboarding doesn’t need personalization. It needs momentum.”
- Metrics post: “Activation +32% after deleting 2 inputs.”
- Lesson post: “If users don’t get value in 60 seconds, they won’t come back.”
That’s one input.
The weekly schedule (2 hours total)
Here’s the schedule that works even in a chaotic build week:
Friday (15 min)
- Capture 3 bullets (ship / learn / no)
Sunday (45 min)
- Turn bullets into 3 primitives
Monday (30 min)
- Split primitives into 10 scheduled posts
Wednesday (30 min)
- Review performance + recycle 1 winner
If you can’t do 2 hours, do 1 hour:
- 15 min inputs
- 45 min write 1 primitive + split into 3 posts
Consistency beats volume.
Hooks that actually convert (steal these)
Most “viral hooks” don’t convert because they’re too generic.
These hooks convert because they’re specific to a builder’s reality:
- “I wasted 6 weeks building ___ so you don’t have to.”
- “We fixed ___ by deleting ___.”
- “If you’re building ___, stop doing ___.”
- “Here’s the decision memo that saved us from ___.”
- “Our onboarding failed until we did this one boring thing.”
- “We tried the ‘best practice’… it made things worse.”
- “This is why your landing page feels ‘fine’ but doesn’t convert.”
Add numbers whenever possible.
Numbers aren’t bragging. They’re proof.
The founder’s content flywheel
If you want content that compounds:
- Post a lesson
- Turn it into a doc
- Turn the doc into a checklist
- Turn the checklist into a lead magnet
- Turn the lead magnet into email onboarding
- Turn the onboarding into product onboarding
Most founders stop at step 1.
That’s why their content doesn’t convert.
What to do if you hate writing
Do this:
- Write ugly drafts.
- Publish after one edit.
- Use a system to format.
Writing is a muscle, but publishing is the habit.
If you want leverage, treat content like shipping code:
- small commits
- frequent releases
- consistent style
- reuse components
The minimalist tool stack
You don’t need 12 tools.
You need:
- a notes doc (Input Library)
- a scheduler (or a simple calendar)
- a template set (hooks + formats)
Everything else is optional.
The hard truth
If your product is good and nobody hears about it, you’re choosing to lose.
A Content OS is not “marketing.”
It’s distribution hygiene.
Start with one rule this week:
Publish even when you feel uninspired.
That’s how you win.
If you want, reply to this post with:
- your niche
- your channels
- your weekly time budget
…and I’ll suggest a 4-week content plan built around your actual product reality.
