Pluto TV

Overview

Context

Pluto TV is a free, ad-supported streaming platform with over 80 million active viewers across web, mobile, and connected TV devices. Unlike subscription platforms, Pluto leads with instant TV. No account required. No paywall. This freedom is good for growth but not optimal for monetization.

Objective

Registered users generate more viewing minutes, better personalization, stronger CRM performance, and higher ad revenue per minute. When I joined, only ~10% of viewing minutes came from registered users.

Architecture

Over three years, I owned and redesigned the end-to-end account and identity ecosystem across web, mobile, and connected TV:

• Registration entry points
  • Registration Wall
  • Unlock Content
  • Unlock Personalization Features
• Second-screen Authentication
• Email Checkpoint
• On-device Sign-In/Sign Up
• Federated identity
• Onboarding
• User profiles
• Settings
• Kids Mode and Brazil Parental Controls
• Account system convergence with Paramount+ (2025)

Outcomes

Between December 2023 and September 2025:

• Registered users increased from 10% → 43%
• Registered viewing minutes increased from 10% → 57%

This is the system-level story behind those numbers.

---

The Core Problem

Pluto TV’s product promise was simple: “Stream now. Pay never.”

Accounts are free. There is no subscription tier. Registration, however, was optional. Viewers could watch for years without ever creating an account and still access features like watch history and bookmarking. The system delivered value without requiring identity. As a result, there was little structural reason to register.

At the same time, the registration experience introduced friction, particularly on connected TVs, which account for the majority of viewing:

TV remotes amplify effort. Text input is slow.
Every additional decision adds weight at the exact moment users just want to start watching. Users were asked to decide:

• Sign in or sign up?
• Complete the process on TV or switch to a secondary device?

These decisions appeared before users fully understood the benefit of registering. The system asked for cognitive effort before offering visible payoff.

Even after completing registration, the experience felt nearly identical to anonymous viewing. Personalization was limited. The value exchange was unclear.

Layered on top of this were structural constraints:

• Accessibility standards varied by platform
• Regulatory requirements differed by region (including parental controls)
• Input patterns were inconsistent across ecosystems

The challenge ran deeper than funnel performance. Identity had evolved in fragments, where incentives, interaction models, and platform constraints were pulling in different directions rather than operating as a unified system.

---

Strategic Framework: Top → Mid → Retention

We reframed identity as a multi-stage system:

---

Cross-Platform System Ownership

This work spanned:

• Web
• iOS / iPadOS / Android
• Smart TVs (Samsung, Vizio)
• Streaming TVs (Roku, Amazon Fire)
• Apple TV
• Android TV
• Gaming consoles

Partners include:

• Product
• Engineering (Backend and platforms)
• Data Insights
• Accessibility
• Legal
• Security
• Marketing

This work required balancing:

• Platform constraints
• Accessibility requirements
• COPPA and regional parental laws
• Engineering feasibility
• Business revenue goals
• Paramount+ convergence roadmap

Design decisions were rarely isolated. Each initiative required navigating platform constraints, regulatory requirements, and business objectives while preserving coherent identity patterns across the ecosystem.

The complexity lived in the interdependencies between platforms, stakeholders, and compliance environments. Design became the tool for clarifying tradeoffs and maintaining system coherence over time.

---

Convergence: Pluto TV & Paramount+

In my final months, I worked on registration convergence between Pluto TV and Paramount+.

The goal was to align identity systems across both platforms: merging tech stacks while preserving each product’s entry mechanics, regulatory differences, and platform constraints.

Rather than simply adopting one system, we evaluated patterns from both sides, identified points of friction, and aligned on shared identity flows. This required close collaboration across product, engineering, and platform teams to reach agreement on just-in-time integration decisions and bring design into implementation early.

Convergence became less about interface changes and more about aligning assumptions, constraints, and long-term system direction.

---

What I learned

1. Growth does not come from a single redesign. It comes from aligning incentives across the system.
2. Identity must be treated as infrastructure. When it is handled as a feature layer, fragmentation follows.
3. The hardest work is invisible:
   • Error states
   • Edge cases
   • Security logic
   • Compliance nuance
   • Platform inconsistencies
4. Durable patterns outlive experiments.

---

---