Member-only story

Paid Subscriptions Aren’t Enough. Why Substack Should Build An App Store

Helping Writers Monetize Their Free Readers More Effectively By Opening The Platform Up (and Taking a Cut)

Hunter Walk
4 min readOct 10, 2022

Consider me a fan of Substack. Yes, I disagree with aspects of their content policies (and occasionally wince at the arguments they make to defend said choices), but the company founders fundamentally want to see writers do their best work and make a great living in the process. Getting creatives paid is a mission I’ll always support.

a happy writer, sitting on a pile of money, digital art (DALL-E)

Beyond the aforementioned community standards questions they inspire a lot of public debate for something which is basically a CMS, email list management tool and Stripe integration. One way to understand the coverage is via Aaron Zamost’s important narrative clock metaphor. The fact Substack raised large amounts of capital during a particularly bullish time in our industry (and the people they raised it from) made them a particularly delicious topic.

A company’s narrative moves like a clock: it starts at midnight, ticking off the hours. The tone and sentiment about how a business is doing move from positive (sunrise, midday) to negative (dusk, darkness). And often the story returns to midnight, rebirth and a new day.”

But this isn’t a post about any of that. At least not directly. Instead consider it a companion to my “Why a Paid Newsletter Won’t Be Enough Money for Most Writers.”

So long as Substack offers a great publishing platform (and helps grow audiences) they will have enough writers. Yes, Author Development will still be a staffed function and various incentives (such as the well-covered Pro guarantees) may exist, but I’m actually not worried about the ‘supply…

--

--

Hunter Walk
Hunter Walk

Written by Hunter Walk

You’ll find me @homebrew , Seed Stage Venture Fund w @satyap . Previously made products at YouTube, Google & SecondLife. Married to @cbarlerin .

Responses (4)

Write a response