← marketing

Distribution & funnel strategy — graphene.fm vs Spotify, and driving people back to the site

Written 2026-05-28. The "where does distribution happen and where does value/monetization happen" doctrine for Graphene. Read this before optimizing any directory-feed or cross-platform decision — it reorders what's worth the effort.

TL;DR

  1. Spotify/Apple are a destination, not a discovery engine. Being on them is table stakes (so people who hear about you can listen where they already are), but they will not find you listeners. Don't over-invest in feed configuration.
  2. graphene.fm is the owned platform and the moat. Listener letters, the subscription, reading/karaoke, and the creator funnel only exist there. Treat the open platforms as the free taste; funnel everyone back to the app for the differentiated experience + the money.
  3. Per-show feeds are the right architecture (already built), but secondary. Promote one flagship, not the whole catalog.
  4. Listeners before creators. A creator tool with no audience is a commodity TTS app. Distribution + an audience is what makes EmberKiln differentiated. The creator pitch writes itself once listeners exist.
  5. Short-form video is the actual top-of-funnel. The vertical trailers + per-chapter hook lines (Clip Kit in the share kit) are the assets. Lead with the interactive angle, never "AI fiction."
  6. Publish as you write (drip), and funnel back with a spoken outro CTA — public feed only. The live, still-writable edge is the wedge; a baked-in "come to graphene.fm" nudge belongs only in the distribution audio (never on-site, never the paid feed), is state-aware (in-flight vs completed), and is capped to one-per-show in the mixed network feed.

The reframe: directories don't discover, they host

Podcast directories (Spotify, Apple) have no meaningful organic discovery for unknown shows — their recommenders surface shows to users who already listen in that genre, based on existing behavior/social proof you don't have yet. They are where people subscribe to shows they already heard about elsewhere, not where strangers stumble onto you.

Consequence: the Spotify-feed-configuration question (individual shows vs one umbrella feed) is a ~5% optimization. The 95% is demand generation upstream — making someone want to hit play in the first place. Get the upstream right and feed structure barely matters; get it wrong and a perfect feed reaches nobody.

Per-show feeds vs one umbrella "Graphene" podcast

Per-show is correct, and we already built it (/api/podcast/rss/show/:seasonId). Industry pattern (QCODE, Realm, Wondery): each show is its own feed; the network is a brand + cross-promo layer, never one combined feed.

  • Directory ranking is per-show, per-genre — a thriller ranks in thrillers. A mixed-genre umbrella feed confuses both the algorithm and the listener (a noir-android fan gets unrelated sci-fi chapters interleaved).
  • Reviews, ratings, follower counts, and "new episode" signals concentrate per show instead of diluting across everything.

But don't submit all 6+ shows and split attention. Pick one flagship (currently The Client, the #1 trending show), push it as its own Spotify/Apple listing, keep the umbrella /api/podcast/rss as a sampler. Per-show feeds are right; Spotify is still just a destination you point people to. (Feed mechanics + the 500-item/free-window behavior are documented in docs/setup-guides/PODCAST_ACCOUNT_SETUP.md §8.)

Drive people back to the app — the funnel

Spotify is a commodity listening surface: no letters, no subscription revenue, no reading/karaoke, no creator funnel. Everything that makes Graphene Graphene — and everything that makes money — only happens on graphene.fm. So:

Open platforms (Spotify/YouTube) = the free taste. graphene.fm = the real thing.

The 7-day free-window mechanic already implements this: chapters age off the public feed into the subscriber feed. Reinforce it with an explicit app CTA on every episode (shipped: the RSS item descriptions in season-distribution.ts now append "Shape what happens next — send a letter to the cast and read along at graphene.fm/seasons/…").

The wedge is listener letters. "The show that writes back — your letters bend what happens next" is a hook no other audio fiction has. It's interactive, novel, and shareable in a way a passive podcast isn't. Market the experience, not the production method — "AI-generated fiction" reads as commodity/slop to exactly the communities (r/audiodrama, fiction-podcast Discords) we're courting, and several are actively AI-hostile.

The spoken outro CTA (the audio funnel)

The text CTA in the show notes (above) is real but weak — most Spotify listeners never read show notes. The stronger funnel is a spoken outro baked into the audio: "...come to graphene dot f m to hear the whole story, and a letter from you can shape where it goes." Shipped 2026-05-29 (technical detail in docs/ai/INDEX.md under "Spoken graphene.fm outro CTA"). The doctrine behind the design decisions:

  • It must never play on graphene.fm itself. The on-site reader and the podcast feed used to serve the same MP3, so a baked-in "come to graphene.fm" would tell an on-site listener to go where they already are. The fix is a separate distribution-only audio variant used only by the public feed — a structural guarantee, not a runtime flag. Rule: anything that addresses the listener as "off-platform" lives only in the distribution audio, never the on-site file.
  • Public feed only, never the paid subscriber feed. A paying Graphene+ subscriber doesn't need to be re-sold the app. Open-platform free listeners are the only audience the nudge is for.
  • The copy is state-aware, because the wedge is. An in-flight story can still be shaped, so the CTA is "the next chapter is being written — come shape it" (urgent, true, agency-driven). A completed story can't be shaped, so it pivots to "more stories." Never promise interactivity a finished story can't deliver — that's the difference between the hook being true and being a lie.
  • One CTA per show in the mixed network feed. The umbrella "Graphene" feed plays shows back-to-back; a CTA on every chapter repeats the same destination over and over in a binge. So in the network feed the CTA rides only the newest chapter per show (the live edge); the per-show feed keeps it every chapter. Repetition fatigue is a real cost; the cap trades a little reach for not sounding like an ad break.

When a show hits the open platforms (serial publishing)

We publish before a story ends, by design — once a show is published, each newly-rendered chapter drips into the feed; there is no "story complete" gate. This is not incidental, it's load-bearing:

  • Drip (publish as you write) keeps the wedge real. "Send a letter, shape chapter 5" is only true while chapter 5 is unwritten. A completed story published all at once has nothing to shape — the single biggest differentiator evaporates and the app CTA collapses to "read along."
  • Binge (finish, then dump) is better for completion/reviews but kills interactivity. Only choose it for a show you've explicitly decided is non-interactive/evergreen.
  • The recommended middle path is trailing-edge: Spotify lags the app's live edge. The open platforms carry "the story so far" as the free hook; the still-writable edge stays exclusive to graphene.fm. The chapter_free_until window is the lever (chapters age off the public feed). (Trailing-edge is doctrine here but not yet built as an automated control — flagged out of scope on the CTA PR.)

The trade is the classic serial tension: drip earns recency + anticipation + algorithmic "active show" signals but loses binge-listeners who bounce off an unfinished series ("I'll come back when it's done" — they won't). For the interactive flagship, that trade favors drip; the trailing-edge cap recovers some of the binge satisfaction without sacrificing the live edge.

Posting as the maker, not a fan (community channels)

When posting to r/audiodrama and similar craft communities, post as the author, transparently — never as a "fan" of your own show. Astroturfing violates Reddit's rules and these communities' culture; if a sockpuppet is ever connected to the creator you lose the community, and the downside is uncapped while the upside (looking organic) is tiny. "Maker sharing the thing they made" also simply outperforms fake-fan in craft spaces. (Copy-ready post draft + the canned "is this AI?" replies live in the share kit's Post-today pack.)

  • Check each sub's self-promo + AI-content rules first. Some ban AI content outright; honesty doesn't save you from a content-policy violation, so don't post there at all.
  • Lead with the interactive hook, never "AI." Same rule as everywhere else — the letters mechanic is the story, the production method isn't.
  • If asked "is this AI?", answer honestly in the first sentence, then pivot to the human editorial role + the letters mechanic. A smaller honest claim survives follow-up questions; an inflated one ("I write every word") gets caught and is fatal.

Listeners before creators (sequencing)

They feel like parallel funnels; they're sequential. A creator tool with no audience competes head-on with ElevenLabs/Descript — commodity, no moat. What makes EmberKiln differentiated is the distribution: "publish into a network with real listeners + Spotify/Apple done for you." That pitch doesn't exist until listeners do.

So: build the listener side first; keep the Studio waitlist warm but spend no marketing energy there yet. Once there's even a small audience + 1–2 traction case-study shows, the creator pitch writes itself. (Pricing for the eventual creator side is in docs/product/EMBERKILN_ROLLOUT.md § "TTS unit economics + pricing decision".)

Concrete next steps (priority order)

  1. Short-form video is the real top-of-funnel. Vertical trailers + auto-captions are built; the per-chapter hook lines are now surfaced in the Clip Kit on /dashboard/admin/share-kit/[id]. Pick the flagship, cut 3–5 hook clips, post to TikTok/Reels/Shorts consistently for ~30 days, watch which line lands.
  2. Nail the one-line pitch. "It will not be televised" is a great tagline but cryptic as a hook — pair it with a clear "an interactive audio thriller where your letters change the story."
  3. Concentrate on the flagship. One show, one genre, one pitch until it has real returning listeners. Catalog breadth (the writer fleet) is for the library, not for marketing attention.
  4. Spotify/Apple = table stakes. Submit the flagship as its own show, keep the umbrella as a sampler, then stop optimizing there.
  5. Seed the communities that exist: r/audiodrama, r/podcasts, fiction-podcast Discords, Bluesky (autopost already live). Lead with the interactive experience + writing quality, not the generation method.

The one metric

Not total shows or chapters generated — weekly returning listeners + letter submissions on the flagship. Engagement depth on one show proves the model. When that curve bends up, scale breadth and turn on the creator pitch.

2026 05 28 Distribution And Funnel Strategy — Docs | HiveJournal