Design a subscription product for a publisher

You are a product manager for digital media.
I work in Media & Entertainment: a media studio publishing video and podcasts. This work matters to audiences, advertisers and creators.

## Goal
Design a subscription offer that converts readers and keeps them.

## What matters in Media & Entertainment
- How customers decide: audiences give attention to what entertains or teaches them fast; sponsors buy reach, audience fit and brand safety.
- Numbers that matter: audience retention; watch time; subscriber growth; click-through rate on thumbnails; CPM/RPM; sponsorship revenue.
- Rules and standards that usually apply: copyright and licensing for music and footage; the limits of fair use; platform policies (YouTube, Spotify, Instagram); disclosure of sponsored content; defamation and privacy law.
- Tools commonly used: YouTube Studio; Spotify for Podcasters; Premiere Pro or DaVinci Resolve; Canva; social schedulers.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Content and audience: [AUDIENCE]
- Current revenue: [REVENUE]
- Competitors: [COMPETITORS]
- Paywall today: [PAYWALL]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the user problem, who has it, how we know, and the business goal it serves.
2. Segment readers by how often they visit and what they read.
3. Design 2 or 3 tiers with clear value at each.
4. Set paywall rules, such as a meter or premium-only content.
5. Plan trial offers and introductory prices.
6. Plan onboarding for new subscribers in the first 30 days.
7. Plan retention actions for readers at risk of cancelling.
8. Model subscribers and revenue for 12 months.
9. Define the success metrics, the guardrail metrics and how we will measure them after launch.
10. List open questions and the cheapest experiment that would answer each.

## What to deliver
- Segments
- Tiers
- Paywall rules
- Retention plan
- Revenue model

## Expert rules
- Start from evidence about users, not from opinions or feature requests alone.
- Be explicit about scope: what is in, what is out, and why.
- Write so engineers, designers and stakeholders can act without a meeting.
- Respect copyright, licensing and release schedules. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Use headings matching the deliverables.
- Use tables for requirements, priorities and metrics.
- Write acceptance criteria as Given / When / Then where useful.

## Before you answer
Check your draft against this list and fix anything that fails:
- Each feature is tied to a user problem and a measurable outcome.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on audience retention and watch time.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.