Project: Screen Scout

Screen Scout

Which theaters should play this film, and how hard?

Team Project CMU Heinz Capstone · Fall 2026 Live · internal sign-in only

A national number hid where the demand was.

TL;DR
ProblemProgrammers book international films off one national forecast. BuiltA score per film per theater, plus live buzz from five public sources. Product callRebuilt the output around the sponsor's real decision, and cut every signal that failed a held-out test.

Summary

Tells a programmer which theaters should play a film, and how many shows.

9 languages 5 live public sources 10 film subreddits Runs daily, no laptop

Context

Product & Data Lead Team of 6 · CMU Heinz

Owned data, scoring and validation on a capstone for a national US cinema chain.

I owned data, scoring, validation and the dashboard. Teammates led Brandwatch research and the presentation.

Data layer Scoring model Social listening Dashboard Excel tool

Who decides

A programmer gets a pitch for an Indian-language film weeks before release, often with only a title, a cast and a trailer. They decide which theaters get it and how many shows, before any sales exist.

Has

Title · Cast · Trailer

Decides

Which theaters · How many shows

Missing

Sales

The Problem

International titles are booked on gut feel and one national forecast.

National viewLooks small
Theater viewConcentrated

Small nationally, so drop it everywhere

→Book it where its audience lives

Illustrative · not to scale

What I Built

One score per film, per theater.

Film strength

Language Cast and director record Genre Runtime Pre-release Wikipedia

Theater multiplier

Its history in that language Its other languages Census demographics

Demand score

Play Weekends Skip

Thin history borrows from other languages and Census data

  • High / Medium / Low film ratings and theater tiers, with cutoffs the programmer can change
  • Buzz search for any title, released or not: Reddit, Wikipedia, YouTube, TMDB
  • Guardrails: Names are never scored as films. Re-releases and Bengali titles are flagged, not shown as zero.
  • An Excel version for planners who live in spreadsheets

Product Approach

→Levers, not verdicts: Programmers set the cutoffs.

→Test a signal before adding it.

→Free, legal, repeatable sources only.

→Put it in front of the decision-maker every week.

Outcomes

1 reframe

Output rebuilt around how bookings are decided, after the sponsor's feedback

Screen Scout · weekly sponsor check-ins · Oct 2026

2 of 3

social signals dropped after testing on held-out films

Screen Scout · Reddit and YouTube cut, Wikipedia kept · Oct 2026

1 week

from a teammate's audit finding a leak to the fix shipping

Screen Scout · validation log · Oct 2026

5

live public sources, refreshed daily with no laptop

Screen Scout · GitHub Actions + Vercel · Nov 2026

The dashboard is private to the sponsor. Every number on this page comes from public data or our own process.

The turning point

"A national number hid where the demand was."

We started by forecasting revenue. In a weekly check-in, the sponsor's programming lead explained why that fails: A film that looks small nationally gets dropped everywhere, including the few theaters where it would sell out. We rebuilt the output around his decision.

One revenue forecast per film

→A High / Medium / Low film rating

→A tier for every theater

→Play / Weekends / Skip, with cutoffs his team controls

Screen Scout · sponsor check-in · Oct 2026

Skills: Data Product Forecasting Social Listening Prioritization Build vs Buy User Discovery Experiment Design Stakeholder Mgmt