Lead-In

Program a FAST channel by audience flow: every show hands its audience to the next.

1 · Your library

Pick a library below to start.

2 · The day

Your 24-hour channel appears here

Pick a library, then plan the day. Lead-In lays every show on a dial from morning to night and marks where viewers stay or leave.

Pick a library first.

Asking Qloo how each show's audience overlaps with the others…

Welcome to Lead-In

Keep viewers watching from one show to the next

Free streaming TV channels (FAST, like Pluto TV, Tubi or Samsung TV Plus) lose viewers whenever the next show doesn't suit the audience of the last one.

Lead-In asks Qloo how much each show's audience likes every other show, then orders a 24-hour day so each show hands its audience to the next, and shows where it can't.

1
Pick a libraryOne of three demo libraries, or add your own shows.
2
Plan the dayLive Qloo data builds the 24-hour dial in about 10 seconds.
3
Fix the weak spotsAsk the Claude agent, and see in Insights how the day compares with AI alone.

On the three demo libraries, Lead-In's days beat the same Claude model scheduling without Qloo, e.g. audience flow 0.82 vs 0.66 on Classic TV Mix (scored on Qloo's audience overlap).

Insights

Plan a channel to see weak dayparts and titles to license.

Plan a channel first, then compare it with the same day built without Qloo.

Plan a channel to see how much each show's audience overlaps with every other.

Plan a channel to see every Qloo call behind it.

What comes from where

Qloo says: How strongly fans of one show also like another (Qloo affinity, shown raw in the matrix tooltips), each show's aggregate audience skew (age, gender), and titles that share an audience with your library. These are aggregate affinities, never facts about an individual viewer.
Our read: The handoff score: Qloo's affinities sit in a narrow band (about 0.76 for unrelated shows to 0.97 for close neighbours), so Lead-In maps 0.86 and below to 0 and 0.975 to 1; a raw affinity under about 0.90 reads as a weak handoff. Also who typically watches in each daypart, how a show's skew fits that, the cut-off for a weak handoff, and the scheduling itself. These are Lead-In's assumptions, open to argument.
Agent: Claude (Anthropic) decides what to investigate and what to test, using only the tools above: Qloo lookups and what-if re-plans. It must quote only numbers the tools returned, and it files them under "Qloo says" or "Our read".
TMDB: Episode runtimes, which set slot lengths (runtime plus about 12% ad load, rounded up to half hours).

How the day is built

Resolve each title to a Qloo entity. Ambiguous titles ask you to choose.
Get each show's audience skew and score its fit for every daypart.
Build a one-way overlap matrix: for each show, ask Qloo how much its fans like every other show in the library (one call per show).
Search for the 24h loop with the best total of handoffs plus daypart fit. Every show airs at least once (when the library fits), and runs of the same show are capped.
Flag weak handoffs and dayparts the library serves poorly, then ask Qloo which titles would fill them.

Ask the agent

Claude reads your goal, asks Qloo for titles that bridge weak spots, tests what-ifs on the schedule and recommends a change, or none.

Your goal for the channel

Add a show

Search TMDB so the show joins with its real episode length and first-air year.

Show title

Search results from TMDB.

Qloo results are aggregate audience affinities, never facts about any individual viewer. No personal data is sent to Qloo.

TV data from TMDB. This product uses the TMDB API but is not endorsed or certified by TMDB.