Sign inGet started
Skills / Content-creation

Content Operating System

Systems are there when motivation isn't. We've all woken up in the morning before and not wanted to write content, not wanted to produce videos, not wanted to record our podcast. That's where systems are there. Systems are the safety net for when motivation is not there.

The Content Operating System is a 9-step hub-and-spoke framework for solopreneurs and creators who want to publish consistently without burning out. Each week, one long-form hub piece — a newsletter, blog post, or video script — becomes 6 to 12 short-form social posts through a structured set of spoke templates. The system runs on roughly four hours a week and is designed to de-platform your audience: moving followers from social media onto your website, where you own the relationship.

By Justin Welsh · Free
Specimen 01 · Live diagnosisContent Operating System
Input

“I have a topic in mind — I want to write about how I stopped relying on referrals and built an inbound pipeline. I'm a B2B consultant and LinkedIn is…”

Diagnosis
Let's build your content for the week.
Full transcript ↓
Calibrated referenceagent-skills.ai
The gap

One hub, six spokes, thirty pieces — your content engine on four hours a week

The Content OS is a 9-step weekly cycle anchored by a hub-and-spoke model. Every week, one long-form 'hub' piece — written using Welsh's Problem/How-Most-Handle-It/How-I-Handle-It framework — becomes the raw material for 6 to 12 short-form 'spoke' posts built from six distinct templates: Story (PAIPS: Pain, Agitate, Intrigue, Positive Future, Solution), Observation, Contrarian Take, Listicle, Past vs. Present, and Thread. Spokes are staggered over 6 to 12 weeks so a single hub idea generates months of content without topic fatigue. Each spoke ends with a link-back CTA driving traffic from social to the creator's owned website — the de-platforming strategy that converted 1.8 million page views into $700K in course and coaching revenue for Welsh in six months. The full weekly cycle — ideation, research, hub writing, spoke generation, and editing — takes approximately four hours.

The problem

Most creators post sporadically — bursting out content when inspired and going dark when they're not. They start from scratch every time they sit down to write, burning mental energy on ideation instead of execution, and still end up with a trickle of posts that drive no meaningful traffic to anything they own. The Content OS targets the root cause: without a repeatable system, motivation alone cannot sustain a consistent content presence or a real audience-building strategy.

The solution

You'll leave each session with a finished hub piece and a ready-to-schedule set of six spoke posts — enough content to run for weeks — built from a single idea and a set of proven templates, in about four focused hours of work.

You bring
  • Your area of expertise, niche, or the topic you want to be known for
  • The platform(s) you publish on — LinkedIn, Twitter/X, newsletter, YouTube, etc.
  • A rough idea or topic you want to develop this week (or willingness to ideate one)
  • A sense of how many hours per week you can realistically dedicate to content
You get
  • A fully structured hub piece with problem framing, key takeaways, and a built-in subscriber CTA
  • A six-spoke content pack — Story, Observation, Contrarian Take, Listicle, Past vs. Present, and Thread — ready to schedule
  • A stagger calendar that maps your 6+ pieces across the next 6 to 12 weeks with hub link-backs built in
  • A reusable weekly system — not just this week's content, but a repeatable engine you can run every week
In action

Watch the methodology work.

Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.

Fig.01The same situation, two ways
Specimens A · B
Specimen AVague
Unaided

“You post when you feel inspired — sometimes three times in a week, then nothing for the next two. Every time you sit down to write, you stare at a blank screen trying to figure out what to say. You've published maybe 40 posts in the past year, most of them one-offs, and your website gets almost no traffic from social media.”

×Vague — nothing concrete to act on.
Specimen BCalibrated
With Content Operating System

“Every Tuesday, you spend 90 minutes turning last week's newsletter into six scheduled posts. Your content calendar is full six weeks out. Each post links back to your hub, and your website traffic has doubled in three months. You haven't had writer's block since you built the Idea Bank — you already know what next week's hub topic is.”

Specific, grounded, and ends with one clear next step.
Fig.02A real session, unedited
In-app · assistant
Content Operating SystemClaude
Content Operating System
Let's build your content for the week. The Content OS runs on one hub idea that turns into six short-form spokes — Story, Observation, Contrarian Take, Listicle, Past vs. Present, and a Thread. First: do you have a topic you're already thinking about, or do we need to run an ideation pass through your recent posts and reading first?
I have a topic in mind — I want to write about how I stopped relying on referrals and built an inbound pipeline. I'm a B2B consultant and LinkedIn is my main platform.
Strong topic — clear transformation, immediately relevant to your audience, and rich enough to produce six distinct angles. Let's build the hub first using Welsh's core framework: Here's the problem → Here's how most people handle it → Here's how I handled it.
Here's a draft outline for your hub:
Problem: Most consultants build a referral-dependent business and call it a pipeline. It feels stable — until two clients leave in the same quarter.How most handle it: They network harder, ask existing clients for introductions, and wait. The funnel fills by accident, not by design.How you handled it: You built an inbound system through consistent LinkedIn content — and in 90 days, ideal clients started finding you.
The 90-day timeline is a key proof point to include explicitly: 'Nothing happened for 60 days. Then, around week 10, inbound DMs started.' That specificity is what makes the hub credible. Does this capture the arc? Anything to adjust before we write the full piece?
That's exactly right. I'd also add that the quality of inbound leads is much higher than referrals because they've already read my content and know my thinking.
Perfect — that detail goes into the 'How I handled it' section as a second benefit after the volume point: inbound leads are pre-sold because they've been reading you for weeks. That becomes a spoke angle too.
Here's your full Six-Spoke Content Pack:
1. Story (PAIPS)Pain: For three years, 90% of my revenue came from referrals. I told myself that meant I was doing great work. It didn't — it meant I had no pipeline.Agitate: When two anchor clients left in the same quarter, I had no backup. No inbound. No list. Just silence.Intrigue: So I tried something I'd been dismissing: showing up on LinkedIn every day and writing about what I actually knew.Positive Future: Ninety days later, three inbound DMs. Six months later, referrals were under 30% of revenue — and every inbound lead had already read my work before reaching out.Solution: Here's the exact system I use. [link to hub]
2. ObservationMost B2B consultants with full pipelines share one trait:They're findable.Not louder. Not more credentialed. Just consistently visible on the platform where their buyers spend time. That's it.
3. Contrarian TakeReferrals aren't a pipeline strategy. They're a vanity metric.A referral means someone else controls your revenue.Inbound means you do.The shift takes 90 days of consistent content. Most people quit at day 30.
4. Listicle5 things I wish I'd done in year one of consulting:1. Started publishing on LinkedIn immediately2. Written about client problems, not my credentials3. Built an email list from day one4. Stopped waiting for referrals to 'just happen'5. Defined my niche before I needed to
5. Past vs. PresentMe in 2021: 90% referral revenue. Checking email hoping someone passed my name along.Me today: 3-5 inbound leads/month from LinkedIn. Pipeline I built, pipeline I control. Leads who've already read my thinking before they reach out.The only difference: I started writing.
6. ThreadHook: How I replaced referrals with inbound in 90 days — and why every lead is better quality. 🧵[Hub newsletter broken into 280-character increments]
Six pieces, one topic. Want me to build the stagger calendar and Pre-Hub CTA next?
Yes, and can you also show me the Pre-Hub CTA I'd post the day before the newsletter goes live?
Here's your Pre-Hub CTA for LinkedIn (Welsh's template: opener → context → numbered takeaways → subscriber count hook → CTA):
---Most B2B consultants don't have a pipeline problem.They have a visibility problem.
Here's what 90 days of consistent LinkedIn content taught me:1. Referrals feel safe — until they don't2. Inbound starts slow (nothing for 60 days)3. Then it compounds fast4. Inbound leads arrive pre-sold — they've read your work already
Tomorrow, I'll show [X] people the exact system I use to generate 3-5 inbound consulting leads per month without a single cold outreach.
If you want the full breakdown, subscribe here: [link]---
And your Content Stagger Calendar:
Week 1, Tuesday — Story (PAIPS) → link to hubWeek 2, Thursday — Observation → link to hubWeek 4, Monday — Contrarian Take → link to hubWeek 6, Wednesday — Listicle → link to hubWeek 8, Tuesday — Past vs. Present → link to hubWeek 10, Thursday — Thread → hub as final post
That's 10 weeks of LinkedIn content from one 45-minute writing session. After week 10, run the second loop — a second Story, second Observation, second Contrarian Take — and you have 12 total pieces from this single hub topic.
This is honestly a little mind-blowing. I've been treating every post as a separate creative project. I didn't realize one topic could go this far.
That's the core leverage of the whole system. As Welsh puts it: 'I can produce 30 pieces of content with much fewer ideas.' The constraint isn't how many ideas you need — it's how much you extract from the ideas you already have. One solid hub topic, six angles, staggered over weeks: that's a content calendar, not a content grind. Next Wednesday, we run the same cycle on a new topic and add six more spokes to the calendar.
Reply to Content Operating System
What the skill is doing
01Hub Content Architecture
02Six-Spoke Template Generation
03Weekly Idea Bank Building
Fig.03The same skill, in the channel you already use
WhatsApp · live
9:41
COContent Operating Systemtyping…
Messages are end-to-end encrypted. No one outside of this chat can read them.
Today
I have a topic in mind — I want to write about how I stopped relying on referrals and built an inbound pipeline. I'm a B2B consultant and LinkedIn is…9:14✓✓
Let's build your content for the week.9:14
The Content OS runs on one hub idea that turns into six short-form spokes — Story, Observation, Contrarian Take, Listicle, Past vs…9:15
First: do you have a topic you're already thinking about, or do we need to run an ideation pass through your recent posts and read…9:15
Message

The same skill, where the work happens.

No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.

Reads the situation, names the pattern, returns one concrete next move.
Delivered in seconds, inside a conversation that already exists.
Specimen · WhatsApp Business API · live
Capabilities

What it does, specifically.

Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.

CapabilityC-01

Hub Content Architecture

Guides you through writing your long-form hub piece using Welsh's two-part framework: define the problem, show how most people handle it, then show how you handle it differently. The hub exists on your website — not inside a social platform — and becomes the destination every spoke drives back to.

Based on Welsh's Step 3 hub creation template (Problem → How Most Handle It → How I Handle It), designed to be repeatable in 45 minutes with practice and built around Typeshare-style newsletter structures.
CapabilityC-02

Six-Spoke Template Generation

Takes your hub topic and produces six distinct short-form pieces, each built on a specific template. Story uses the PAIPS arc (Pain, Agitate, Intrigue, Positive Future, Solution). Observation surfaces a notable pattern. Contrarian Take challenges a commonly held belief. Listicle curates tools, books, or resources. Past vs. Present shows before-and-after transformation. Thread converts the hub into 280-character increments with a strong hook.

Directly maps to Welsh's Steps 7 and 8 — the six spoke formats he has used to generate 30+ pieces of net-new content per week from LinkedIn and Twitter since 2019.
CapabilityC-03

Weekly Idea Bank Building

Structures your ideation hour: systematically scanning YouTube channels sorted by most popular, curated newsletters like Morning Brew, your own top-performing posts, and peers' content to surface one strong hub topic. Builds and maintains an ongoing Idea Bank so you are never starting from zero.

Based on Welsh's Step 1 ideation process — a dedicated 1-hour Wednesday block at a fixed time (10:30am Central in his own schedule) to remove the decision of when and how to find ideas.
CapabilityC-04

Stagger Publishing Calendar

Builds a distribution schedule that spreads your 6 to 12 spokes across 6 to 12 weeks rather than publishing them back-to-back. Maps each piece to a specific day and week, and prompts a second-loop variation after the first six posts — squeezing 12 unique pieces from one hub topic.

Implements Welsh's Step 9 stagger strategy — his technique for making one hub topic generate months of non-repetitive social content while consistently routing traffic back to the hub through a link-back CTA on every spoke.
CapabilityC-05

De-platforming Funnel Design

Helps you write Pre-Hub and Post-Hub CTA posts that promote your hub content the day before and after it publishes, training your audience to visit your website rather than just consume within the social feed. Turns social followers into an email list and owned audience you control regardless of algorithm changes.

Based on Welsh's Steps 5 and 6 (Pre-Hub CTA and Post-Hub CTA) — the strategy behind 1.8 million page views and $700K in revenue from Twitter and LinkedIn in six months, with website traffic growing from 8K to 16-18K weekly visits.
Tested

Graded before it shipped.

Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.

What it produces
OutputD-01

Hub Content Brief

A structured document containing your hub topic, supporting research links, and the full Problem/How-Most/How-I outline — ready to write from or publish directly as a newsletter or blog post.

OutputD-02

Six-Spoke Content Pack

Six finished short-form posts — Story (PAIPS), Observation, Contrarian Take, Listicle, Past vs. Present, and Thread — each built from your hub topic and each ending with a link-back CTA to the hub.

OutputD-03

Content Stagger Calendar

A 6-to-12-week publishing schedule that assigns each spoke to a specific day and week, with second-loop prompts for generating 12 total pieces from a single hub topic.

OutputD-04

Idea Bank Entry

A formatted record capturing your hub idea, its inspiration source, supporting research links, and a quality-check note — ready to queue for a future week's Content OS cycle.

The source

Grounded in the original work.

Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.

Source authorA-01

Justin Welsh

Justin Welsh is a former startup executive who built two $50M+ ARR companies and raised $300M+ in venture capital before leaving corporate life in 2019. He built a seven-figure one-person business — $2.7M+ annual revenue at 95% profit margins — entirely through organic content, accumulating 270,000+ LinkedIn followers, 180,000+ Twitter followers, and 350 million annual impressions without a single paid ad. His Content OS course has enrolled 17,000+ students and holds a 4.98 out of 5 rating.

Status · Inspired by Justin Welsh’s work — not yet claimed. Are you Justin Welsh?
Primary sourceS-01

The Content Operating System 2.0

by Justin Welsh

Former startup executive (two $50M+ ARR companies, $300M+ raised); $2.7M+ annual revenue at 95% margins; 17,000+ students; 270K+ LinkedIn followers built organically since 2019.

Read the original ↗
Citationyoutube.com
In the build queue

Be first to run it.

Content Operating System is being built right now. Leave your email and we’ll tell you the moment it goes live.

Notify meEmail
At launchI want to set up the Content OS for my situation. I'm a [role/niche] and I mainly post on [platform]. Should we start by finding a hub topic for this week, or set up the full system first?