Skip to content

Runner, an independent concept for

Ready before the live moment.

Runner drafts the announcement and countdown for one live event. Your regional team checks the details and publishes through its existing tools.

One live event. Every message ready for review.

Give a regional marketing team an AI drafting team for the run-up to one live event. Runner prepares the announcement, countdown and day-of posts from your approved brief. Your people make the editorial decisions and publish through their existing tools.

The public context behind this proposal

Netflix’s public fan-event guides combine local dates, venues and attendance instructions. Its recent Tudum launch in Brazil also puts local editorial coverage at the centre of the fan experience.

Sources reviewed October 22, 2026. The first project above is Runner’s proposal.

The wider example below is scoped separately: live delivery needs connected channels, recorded permissions and a verified reporting source.

Less busywork. More showtime.

From title launches to ad sales, every Netflix team has more to say than hours to say it. Runner gives each one an AI team of its own. It drafts. Your people approve. Start with one example, live events, and put a price on those hours below.

“…we're going to continue to build out that global live event calendar…”

Ted Sarandos, Co-CEO of NetflixFrom Netflix's Q2 2026 earnings interview, July 16, 2026

Put in your events, your countries, your hours. Watch it add up.

Example numbers. Make them yours.

From Netflix's Q1 2026 letter to shareholders: more than 70 live events in one quarter.

Event campaigns a quarter
140
Hours of marketing work
840
What that time is worth
$63,000

These are your numbers, not a promise. Your @runners draft; your people still review and approve every piece. The figure is what the hours are worth, not a saving.

A writers' room for every team.

Live events, regional marketing, ad sales, partnerships: each team at Netflix gets this crew, inside its own limits. Each member has one job. Your people approve what goes out.

  • Drafting

    Social lead

    Drafts the posts for Instagram, Threads and LinkedIn. Your team approves each one, or lets a trusted channel run.

  • Writing

    Email lead

    Writes the emails, reminders and follow-ups. Sends only to people who asked to hear from Netflix.

  • Pacing

    Budget keeper

    Plans paid posts inside the budget you set, and asks before it goes up.

  • Counting

    Growth lead

    Puts every week's results against the target, channel by channel. You know where you stand.

  • Checking

    Guardrails

    Checks consent, how often anyone hears from Netflix and quiet hours in each person's own time zone, before anything goes out.

Before the big night.

  1. Two weeks out

    The announcement

    Drafted by your @runners. Edited and approved by each country's team. Then the date goes out.

  2. Event week

    The reminders

    Only to people who asked for one. Only inside allowed hours, in their own time zone. Nobody gets two.

  3. The morning after

    The follow-up

    A thank-you, and the next date on the calendar. For everyone who asked to hear more.

  4. Every Monday

    The count

    Every channel's results against the target, for each country's team. Each team knows where it stands.

Your role. Your call. Your runner.

Choose your role. See what you'd hand one of your @runners, what comes back drafted, and the decision that stays with you.

Your brief

Fill the run-up to a live event, in every country it plays in.

Your runner drafts

Your runner drafts the announcement, the countdown posts and the reminders, country by country, for your team to edit.

Your call

You choose the countries, the moment and what a good night looks like.

Or let it run. When a channel’s drafts keep going out as written, your team can switch it to run on its own, inside the same limits. Any edit switches it back to asking.

Your team starts at the edit.

  • Drafts arrive ready to edit

    Announcement, reminders, posts, the note to advertisers: each one arrives written. Your team edits and approves instead of starting cold.

  • Monday's count, already counted

    Results against the target, channel by channel, for each team. Put together for you, every week.

  • Your limits work the night shift

    Quiet hours, how often anyone hears from Netflix, the budget: held while nobody's watching. Pause it, and everything stops.

Built for how a big company works.

  • Visitor intelligence, in a waterfall

    Company first. The person only where the law and their own consent allow, and never past a jurisdiction's limit.

    More
  • A record nothing can edit

    Every proposal, approval and send is kept on an append-only record. Nothing in it can be edited or deleted.

    More
  • Your model, your key

    Anthropic, OpenAI, Google, xAI or Ollama, on your own agreement and your own rate limits.

    More
  • Hard limits, one stop switch

    Caps on spend, sends and quiet hours that hold when nobody is watching. One switch stops all your @runners.

    More
  • Many teams, one organisation

    Each team gets its own crew, its own limits and its own numbers, under one account.

    More

Bring one live night. We'll bring the drafts.

Bring one event brief. We’ll show your editor the drafts and the review steps.

The small print.

An independent concept by Runner, built from public information. Not affiliated with or endorsed by Netflix. No Netflix titles, talent likenesses, viewing history, account access or streaming integration are used. The lifestyle scene depicts fictional adults watching an unseen screen.

Live in Runner today

  • A team of AI marketers for every team, each member with one job.
  • Posts, emails and ad plans drafted for your people to approve.
  • Channels that run on their own once trusted, and stop at the first edit.
  • Hard limits on spend, sends and quiet hours, and one switch to stop it all.
  • The results, counted against your target, every week.
See how it works

Built for Netflix

The team’s setup, the role views and the flow on this page. We build them with your team in a pilot, and no result is promised.

Runner’s security page
How visitor context stays within permission

These are separate states, not an automatic ladder from anonymous visitor to named person.

An arrival
Collection follows the site’s consent policy. A visit is not a contact.
A returning browser
An anonymous identifier can relate allowed visits. It does not establish who the person is.
Possible company context
Jurisdiction and stricter operator limits govern identification. This is a provider claim with a source, not proof of employment.
An explicit known relationship
Linking anonymous history requires an explicit identify event. Identification itself grants no permission to send marketing.

In the US, person identification requires the customer’s own connected provider account and key. EU and UK identification stops at the organization. In South Korea, traffic-derived identification stops at the company, never the person. A visitor who identifies themselves or explicitly turns Recognition on is a separate, permission-based case. Accepting the general notice does not turn Recognition on. Global Privacy Control suppresses person identification everywhere. Nothing in the product can raise a jurisdiction limit.

Read the identification boundaries
What a pilot covers with your security team
  • Scope and access. Which teams and products, and who may approve. A senior job title grants nothing by itself.
  • Data and permission. The data sources, processors, retention, jurisdiction and consent evidence for the work.
  • Limits and stopping. The owner controls and approval steps. Approval never overrides eligibility or local law.
  • Sign-in. Sign-in is an email link, a password or a passkey. If your security team needs single sign-on, it comes with an Enterprise plan: your people sign in through your own identity provider over SAML, and your admin connects it in Settings.
  • Agreement. The use case and who reviews what, before any access. No SLA or certification is promised here.
Start with Runner’s security page