Back to Blog
substack multi platform publishing
12 min read

My 90-Day Substack Multi Platform Publishing Experiment

You know the pattern. You spend days on a strong Substack post, hit publish, send it to your list, and then watch the same familiar names open, like, maybe...

By Ian Kiprono

You know the pattern. You spend days on a strong Substack post, hit publish, send it to your list, and then watch the same familiar names open, like, maybe reply, and move on. Meanwhile the article still has value, but getting it onto LinkedIn, X, and Medium feels like a second job made of copy-paste, broken formatting, missed posting windows, and guilt. That was my bottleneck. The writing wasn't the problem. Distribution was. So I ran a 90-day Substack multi platform publishing experiment to stop winging it and build a system that moved readers back to my newsletter.

The Hamster Wheel of a Single Platform

For a long time, I treated Substack like the whole business instead of the center of the business.

That sounds subtle, but it changes everything. When I published a new essay, I told myself I was done. In reality, I had only completed the first half of the work. The second half was getting that idea in front of people who had never heard of me.

My breaking point came from the same feeling a lot of writers have and rarely say out loud. I wasn't blocked. I wasn't out of ideas. I was tired of watching good work disappear after one send.

At the start of this experiment, my Substack sat at 450 subscribers. Ninety days later, it reached 1,410, which was 217% growth. I also saw website traffic from social channels rise by 500% during the experiment. Those are the numbers that made me keep the system.

I didn't need more ideas. I needed more surfaces for the same idea to work.

The lesson from those 90 days wasn't that every platform matters equally. They don't. The lesson was that one article can do several jobs if you stop treating repurposing like lazy recycling.

I also learned what doesn't work. Posting a raw Substack link to LinkedIn almost never created momentum. Copying the same article word for word everywhere created friction, not reach. Trying to improvise each post on the day I needed it led to skipped distribution and uneven quality.

What worked was much more boring and much more effective. One core piece each week. Clear adaptations for each platform. A repeatable publishing rhythm. Basic tracking. Then iteration.

That turned Substack multi platform publishing from a vague idea into an operating system.

Building the Multi-Platform Foundation

The first week had nothing to do with writing more. It was about changing the frame.

Substack became the hub. Every other channel became a spoke. That meant the long-form version lived on Substack first, and every adaptation had one job: bring the right reader back to the hub, or at least make them remember the name.

The mindset shift that mattered

This was the single biggest change: stop thinking like “I publish a newsletter” and start thinking like “I run distribution for intellectual property.”

That sounds grander than it is. In practice, it meant each platform needed a role.

  • Substack held the canonical long-form piece and the owned audience.
  • Medium gave the article a second long-form surface with different reader behavior.
  • LinkedIn became the place for professional framing and conversation.
  • X worked best for sharp claims, threads, and fast testing.
  • Substack Notes stayed in the mix, but I treated them as support, not a substitute for external reach.

That last point matters more now because Substack isn't just an email tool anymore. It was founded in 2017 around a creator-owned model that combines blogging, newsletters, and paid subscriptions, with Substack taking a 10% cut of paid subscription revenue. By 2025, independent reporting described it as having more than 5 million paid subscriptions, over 35 million monthly active subscribers, and said its Notes and app discovery features added 32 million new free subscriptions and nearly 500,000 new paid subscriptions in a three-month period reported in late 2025, according to this Substack statistics breakdown.

That growth changed how I thought about distribution. If the platform itself has discovery, the smart move isn't to abandon outside channels. It's to use a hub-and-spoke model so internal and external reach reinforce each other.

My one-time setup checklist

Before I touched a repurposing workflow, I tightened the basics.

  • Unify your positioning. I used the same profile photo, similar bio language, and the same topic promise across Substack, LinkedIn, X, and Medium.
  • Make the path obvious. Every profile linked back to my Substack, not to a generic homepage with too many choices.
  • Pick one content promise. Mine was simple: practical systems for writing, audience growth, and content operations.
  • Create a source-of-truth folder. Each weekly article got one folder with draft, headline options, pull quotes, CTA variants, and platform notes.
  • Define naming conventions. I labeled everything by date and topic so I could find posts fast.
  • Set a syndication rule. Substack first. Then adapt, don't duplicate.

A lot of writers skip this because it feels administrative. It is administrative. That's why it works.

For a broader framing of this kind of setup, this guide on content syndication strategy is useful because it forces you to think in systems instead of isolated posts.

The profile test I used

I asked one simple question on each platform: if a stranger sees one post, can they immediately tell what I write about and where to go next?

If the answer was no, I changed the profile until it became yes.

Practical rule: Discovery breaks when identity is fuzzy. A reader should not need to guess what you publish.

Once that foundation was set, the repurposing itself got much easier because every post pointed back to the same clear home.

My Content Repurposing Templates for Each Platform

Most advice on repurposing dies at the phrase “turn one article into many assets.” That sounds helpful until you're staring at a finished essay and still have no idea what to post.

My system started with one Substack article each week. From that one piece, I built a Medium version, a LinkedIn post, an X thread, and several Notes or short social posts pulled from the strongest lines.

A diagram illustrating how to repurpose Substack article content into various social media and website formats.

Experienced creators explicitly recommend this one piece, multiple platforms approach: publish the long-form version on Substack, republish or adapt it on Medium, then atomize the strongest ideas into social posts to keep message consistency while extending reach, as described in this piece on Medium vs Substack publishing workflows.

The article I used as a test case

One of the essays in the experiment was about asynchronous work. The Substack version was the full argument. It had the nuance, examples, and the full subscriber CTA.

I didn't ask, “How do I promote this?”

I asked, “What is the best native expression of this idea on each platform?”

That question changed the output immediately.

My Medium adaptation template

Medium readers will tolerate depth, but the framing has to earn it faster. I changed two things every time: the headline and the opening.

My template looked like this:

  1. Headline with broader curiosity
  2. Opening paragraph rewritten for non-subscribers
  3. Shorter section intros
  4. Light cleanup of newsletter-specific language
  5. End with a soft invitation back to Substack

Example shift:

Substack headline: “The Future of Remote Work Is Asynchronous”

Medium headline version: “Most Remote Teams Don't Have a Communication Problem. They Have a Timing Problem”

That difference mattered because Medium rewarded a stronger premise-led headline, while Substack readers already had some relationship context.

My LinkedIn post template

LinkedIn was the surprise winner in terms of quality of conversation. The posts that worked best were not article summaries. They were argument snapshots.

I used a simple three-part structure.

  • Hook. One opinion or tension in the first two lines.
  • Body. Three to five short paragraphs with one useful breakdown.
  • Close. One discussion prompt or one low-friction CTA back to the essay.

A typical format looked like this:

Remote teams don't fail because people are in different places.
They fail because everyone still works as if communication must happen live.

Then I'd add a short breakdown of what asynchronous decision-making changes, finish with one practical takeaway, and mention that I wrote the full essay on Substack.

The mistake I made early was trying to preserve all the nuance of the article. LinkedIn didn't need the entire essay. It needed the sharpest edge of the essay.

My X thread template

X was best when I stripped the argument down to claims and sequence.

My thread template:

  • Tweet 1. Strong opinion with stakes
  • Tweets 2 to 5. Breakdown of the main points
  • Tweet 6. Counterpoint or mistake people make
  • Tweet 7. Practical takeaway
  • Tweet 8. Link to the full Substack post

For the asynchronous work piece, the opening became something like this in structure:

Most remote teams don't need more meetings.
They need better writing, clearer ownership, and slower defaults for non-urgent decisions.

That worked better than “New essay up today” every single time.

The atomization rule

I kept a note under every article draft with these prompts:

  • What sentence can stand alone?
  • What paragraph can become a post?
  • What argument can become a thread?
  • What objection can become a Note?

That note saved me from reopening the whole article every time I needed a post.

For more practical ways to build these adaptations, this collection of content repurposing strategies is useful because it focuses on turning finished writing into platform-specific assets instead of generic snippets.

A good repurposing system doesn't make one article smaller. It makes one article more portable.

The 7-Day Publishing Cadence That Prevented Burnout

The first month of the experiment was messy because I had templates but no rhythm. I still made decisions too late, and late decisions create bad posts.

The weekly cadence fixed that.

A 7-day content publishing schedule chart designed to help creators maintain a sustainable and burnout-free workflow.

The exact cadence I used

Day 1 was the Substack article. I published the long-form piece and pulled out three lines that could become short-form posts later.

Day 2 was Medium adaptation day. I rewrote the headline and intro while the idea was still fresh.

Day 3 was LinkedIn. I created one main post from the article and drafted one follow-up variation with a different hook.

Day 4 was for X. I turned the core argument into a thread and wrote two standalone posts from leftover points.

Day 5 was Notes and cleanup. I posted one short idea natively to Substack Notes, then checked comments and replies across platforms.

Day 6 was engagement. No major publishing. Just replies, relationship-building, and observing what language people repeated back.

Day 7 was planning. I reviewed what resonated and outlined the next article with repurposing in mind.

This rhythm made a huge difference because it separated creative work from formatting work. I wasn't trying to write a polished essay and an X thread and a LinkedIn post all in the same sitting anymore.

A lot of writers reach a point where the issue isn't whether to distribute more widely. It's whether they can do it without turning the process into a clerical job. That's the core scale question. As some publishers found, Substack's native tools have limits for more advanced scheduling and marketing needs, which is why the better question becomes when distribution needs its own operating system, as discussed in this analysis of publishers hitting Substack's limitations.

What manual scheduling got wrong

My manual workflow had predictable failure points:

  • Formatting drift. Paragraph breaks looked fine in one editor and clumsy in another.
  • Missed timing. Good posts sat in drafts because I didn't want to log back in later.
  • Context switching. Writing energy got consumed by publishing mechanics.
  • Inconsistent Notes usage. I'd remember Notes only after the main momentum window had passed.

I didn't need more discipline. I needed fewer moving parts.

This short video captures the shift from scattered posting to a repeatable system.

Where a dedicated tool helped

This was the point in the experiment where I started using one dashboard instead of juggling separate editors. Buffer was fine for lightweight social scheduling. Drafts in Notion helped with batching. But once I wanted article-level distribution plus Substack Notes scheduling and cross-posting, I needed a tool built for writers.

I used Narrareach for that part of the workflow because it let me schedule Substack Notes, Medium articles, LinkedIn posts, and X content from one place, and handle cross-platform distribution without the copy-paste loop. That wasn't a magic growth button. It just removed the operational friction that made consistency harder than it should've been.

If you want the writing side of this process to stay clean, this piece on write to publish workflows is worth reading because it treats publishing as a repeatable editorial process, not a burst of inspiration.

How I Tracked Growth and Found Winning Content

I made one rule for measurement: if a metric didn't help me grow the email list or improve the next piece, it wasn't important enough to review every week.

That eliminated a lot of noise.

A table showing social media growth tracking metrics with views, engagement, and Substack sign-ups for different platforms.

My simple dashboard

I tracked three categories in a spreadsheet for each platform:

Metric What it told me Why I kept it
Reach Did people see it? Good for testing hooks
Engagement Did it resonate? Good for testing angle
Clicks to Substack Did it convert? The metric that mattered most

I also added one notes column: what was the framing? Not the topic. The framing.

That mattered because “remote work” is a topic. “Most remote teams have a timing problem, not a trust problem” is framing. Framing is what carries across platforms.

What the data changed

One of the clearest lessons from the experiment was that on-platform engagement can fool you. A post can get replies and still do very little for audience expansion.

That's why I treated Substack Notes carefully. Notes helped me stay visible inside the platform and keep conversations warm. But I didn't assume that internal activity was the same as cross-platform reach. That tradeoff matters, and it's often underexplored. Many creators focus heavily on Notes, even though growth often comes from getting in front of other people's audiences on platforms like LinkedIn and X, as discussed in this analysis of Substack's social layer and distribution behavior.

Useful lens: Engagement inside one network is not the same thing as audience expansion across networks.

The tagging system I used

I tagged each post with a few qualitative labels:

  • Format such as thread, text post, adapted article, or Note
  • Angle such as contrarian, tactical, narrative, or opinion
  • CTA type such as direct subscribe, soft read-more, or comment prompt
  • Source article so I could trace every result back to one long-form piece

That made reviews much easier. I could see not only which platform worked, but which combination of framing and format kept leading people back to the Substack.

For X in particular, I found it helpful to pair my own spreadsheet with a more structured data-driven X content strategy so I wasn't just guessing based on vibes and a few visible likes.

The review habit that found winners

Every week, I asked four questions:

  1. Which hook got attention fastest?
  2. Which post generated thoughtful replies, not just shallow reactions?
  3. Which format sent readers back to Substack?
  4. Which topic should become a bigger future essay?

That last question was underrated. Good short-form data didn't just help me distribute better. It helped me write the next long-form piece with more confidence.

If you want a cleaner system for this, a dedicated social media tracking workflow helps because the hard part isn't collecting numbers. It's connecting those numbers to editorial decisions.

My Final Playbook and 217% Growth Results

By the end of the 90 days, I stopped thinking about promotion as “sharing my newsletter.” I was running a repeatable distribution system around one strong article each week.

The results were simple and clear. Substack subscribers grew from 450 to 1,410, which was 217% growth. Website traffic from social channels went up 500%. The gain didn't come from writing more pieces. It came from giving each piece more chances to work.

A marketing playbook infographic showing growth results for Substack subscribers and website traffic social metrics.

My final playbook is short:

  • Publish one strong canonical article on Substack each week
  • Adapt it for Medium instead of duplicating it blindly
  • Turn the sharpest idea into a LinkedIn post
  • Break the core argument into an X thread
  • Use Notes to reinforce momentum, not replace outside distribution
  • Batch scheduling so distribution doesn't eat writing time
  • Track which framing drives clicks and subscribers
  • Repeat what earns attention and conversion together

If you're building your own Substack multi platform publishing workflow, start there. Keep it small enough to sustain and structured enough to repeat.

For the review side, this social media audit template is a solid companion because it helps you spot what deserves more distribution and what should be cut.


If you're ready to stop copying and pasting every article into four different platforms, try Narrareach. It helps writers schedule Substack Notes, Medium articles, LinkedIn posts, and X content from one workflow while tracking what drives distribution. If you're not ready for that yet, stay connected by joining my free weekly newsletter for writers who want better systems for audience growth.

Related Posts

Ready to scale your content?

Write once, publish everywhere with Narrareach