Milestone map
Milestone map
3 milestones
Define the show concept and publish episode 1
3–6 weeks
Define the podcast concept — topic, format, target listener, and episode length — and publish episode 1. A podcast concept that is too broad ('a podcast about everything') will not build a loyal audience; a concept that is too narrow ('a podcast only about 1970s Bulgarian cinema') will not find enough listeners to sustain itself. The sweet spot is a concept specific enough to be distinctive and broad enough to generate 50+ episodes. Episode 1 must be published on a public podcast hosting platform — not a private file, not 'coming soon'.
Proof required
Share the podcast's public URL (Apple Podcasts, Spotify, Podbean, Buzzsprout, or similar). State the concept (topic + format + target listener + episode length). Write one sentence on what makes this podcast different from other podcasts on the same topic.
What gets checked
- Episode 1 is live on a public podcast hosting platform — the URL must work.
- Concept covers topic, format, target listener, and episode length.
- Differentiation is stated — what makes this show distinctive.
Common mistakes
- Episode recorded but not yet published: 'I'm still editing' — the milestone requires publication.
- Concept is too broad: 'I talk about interesting things' — this is not a concept.
- Differentiation absent: 'there are lots of podcasts on this topic and mine is similar' — even a small differentiation (format, perspective, guest type) should be articulated.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- The URL must be live — visit it directly to confirm the podcast is publicly accessible and episode 1 can be played.
- Concept: ask what the target listener does or thinks about after listening to one episode — this reveals whether the concept has a clear value proposition.
- Differentiation: ask why a listener would choose this podcast over the 3 most popular podcasts on the same topic.
You'll sign in first, then come straight back here.
Publish 5 episodes and establish a release schedule
5–20 weeks (depending on cadence)
Publish 5 episodes and commit to a release schedule by publishing at a consistent cadence — weekly, bi-weekly, or monthly. Consistency is the primary driver of podcast growth: listeners subscribe to podcasts they can rely on to show up in their feed. Episode 5 is the threshold at which a podcast has demonstrated a release pattern, not just a launch. The 5 episodes should reflect the concept defined in M1 — if the format has changed significantly by episode 5, that should be noted and the reason given.
Proof required
Share the podcast's public URL showing 5 published episodes with dates. State your release schedule (weekly / bi-weekly / monthly). Write one sentence on what changed between episode 1 and episode 5 in terms of format, content, or production quality.
What gets checked
- 5 episodes are live with visible publication dates.
- Release schedule is stated — the dates should reflect a consistent pattern.
- What changed between episode 1 and episode 5 — demonstrates active development of the show.
Common mistakes
- 5 episodes published in one week: 'I batch-released them all at once' — this is not a release schedule; the episodes should be dated across at least 3 weeks.
- Release schedule not stated: '5 episodes published' without a committed cadence.
- What changed is absent: 'nothing, I kept it consistent' — even small format changes (episode length, intro structure, question order) are worth noting.
Powstik Guide
Five episodes released on a steady schedule.
Steps
- Choose weekly, fortnightly or monthly, and stick to it.
- Batch record if you like, but release on schedule.
- Keep a running note of what you change each episode.
- List the show on Apple Podcasts and Spotify.
Template
Release schedule: | Ep | Record date | Release date | Length | What I changed | |----|-------------|--------------|--------|----------------|
What gets sent back
- All five episodes released in one week.
- No schedule stated.
- No note on what changed from episode 1 to 5.
Resources
Foundationstart here
What a verifier looks for
- The publication dates on the 5 episodes should reflect a consistent cadence — ask what the intended schedule is and whether it was maintained.
- What changed: ask specifically about production quality — is the audio better in episode 5 than episode 1? What changed in the editing process?
- Release schedule: ask whether the creator has future episodes already recorded or in production — a backlog is a sign of sustainable production pace.
You'll sign in first, then come straight back here.
Reach 100 downloads and understand the audience
4–16 weeks after episode 1
Reach 100 cumulative downloads across all episodes and understand where those downloads came from. 100 downloads is a modest threshold — many successful podcasts start small — but it is enough to give a real signal about who is listening and how they found the show. The audience understanding milestone is about analytics: which episodes had the most downloads, what the listener geography looks like, and whether any listener reached out with a comment or question.
Proof required
Share a screenshot of your podcast analytics showing 100+ cumulative downloads. State which episode had the most downloads and your hypothesis for why. State whether any listener has reached out — a comment, a review, a message, or a social media mention — and what they said.
What gets checked
- Analytics screenshot shows 100+ cumulative downloads.
- Top-performing episode is identified with a hypothesis for its performance.
- Listener contact is addressed — even 'no contact yet' is a real answer.
Common mistakes
- Analytics not shared: 'we have over 100 downloads' without evidence.
- Top-performing episode identified without a hypothesis: 'episode 3 got the most downloads' without any reason.
- Listener contact absent entirely from the proof — even 'no one has reached out' should be stated.
Powstik Guide
A hundred downloads and a note on who is listening.
Steps
- Pull downloads per episode from your host's analytics.
- Find the top episode and guess why it won.
- Check where listeners are and which apps they use.
- Ask listeners for a reply or review in one episode.
- Record any listener contact, even if there is none.
Template
Total downloads: Top episode and my guess why: Top listener locations / apps: Listener contact (who, what they said) — or 'none yet':
What gets sent back
- A download claim without an analytics screenshot.
- A top episode with no reason given.
- Listener contact not mentioned.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- The analytics should come from the hosting platform dashboard — ask which platform and whether the numbers include self-plays.
- Top episode hypothesis: ask whether the creator tested the hypothesis by promoting that format or topic in later episodes.
- Listener contact: if no one has reached out, ask whether the creator has included a clear call to action in any episode — 'reply to this episode' or 'leave a review'.
You'll sign in first, then come straight back here.
Part of