Who Can You Pitch a TV Show To? Check the Submission Route Before Sending

The short answer: a company is only a destination if its own current instructions describe a route that fits both your project's stage and you as a submitter. Everything else — a familiar name, a catalog full of shows that look like yours, an email address someone posted in a forum — is a lead. A lead is not a route, and the gap between the two is where most first pitches die.

So the work of choosing who to pitch starts with two things you already control: what you actually have, and what job the person you're writing to performs.

Match the kind of conversation to the material you have

There are four conversations a new creator usually confuses, and they run on different currencies.

A producing or development conversation. Someone who develops material alongside you and takes it to a buyer. Their currency is relationships and time, and you are asking them to spend both on a project that may not sell.

A representation inquiry. An agent, manager or lawyer considering you as a client. This conversation is about you and your body of work over years, not about the one script in your bag this month.

A commissioning proposal. A buyer considering a project for its own slate. This is the conversation most people mean when they say "pitching," and it's the one most often closed to unsolicited material.

An acquisition. A distributor or channel buying finished programs. This is a purchasing conversation, not a development one.

One company can run several of these conversations in different departments, with different people and different rules. That's why "do they take pitches?" has no single answer. "Which of their doors is open, to whom, and for what?" does.

Sort your own material before you sort anyone else. An idea is a premise, sometimes a paragraph. A developed package is usually a pilot script plus a series bible, sometimes a deck. Produced episodes are episodes that exist — a self-funded pilot, a web series, a finished documentary.

Now the mismatch that eats the most time: a buyer of finished programs is not a slower, more patient version of a development buyer. Someone who purchases completed shows has a use for a completed show. Your unmade project isn't a smaller version of that product. It's a different category of thing, and no amount of enthusiasm converts one into the other.

Read the recipient's instructions before building a contact list

Before a name goes on your list, find the page where that organization says how it wants to be approached, and write down seven things.

• The organization and the exact page you read, with the full URL, so you can find it again.
• The date you read it. Policies change. A route you confirmed in March may not exist in September.
• The geography it serves. A page can describe a route for one country's producers and say nothing about anyone else.
• Who may submit. Agents, independent producers, production companies and members of the public are separate classes, and a route open to one is often closed to the others.
• The relevant form, genre or slate. A route that exists for documentaries may not exist for scripted comedy.
• The project stage required. Some doors want a finished program. Some want a proposal. Some want a produced short first.
• What is requested first. More on this below, because it decides what you send.

That last field does most of the practical work. Recipients ask for different first items: a form, a short summary, a signed release before anyone reads anything, a full proposal with a stated budget range. What they ask for first is your package's first item. Not your best document — their requested document.

Two shortcuts that feel like research and aren't:

A catalog match. Watching a platform's slate, noticing they have three shows in your genre, and concluding they'd want yours is a fit hypothesis. A good one, worth keeping — it's the kind of observation that makes a later conversation specific instead of flattering. But it tells you nothing about how to get in. Fit was never the missing piece.

A published address. A contact email found on a site, in a directory or in a thread is a delivery mechanism. Deliverability is not permission. If the page next to that address says the organization doesn't accept unsolicited material, the address doesn't override it; it just gives you a faster way to make a bad impression.

When instructions are missing, stale or contradictory, the corrective action is a clarifying question through an authorized channel — where an organization publishes a general contact or a form with a question field, that's what it's for. Asking "how should an independent producer approach you?" is a different act from sending a bible to the same address. One requests the route; the other assumes it.

Separate a published route from personal eligibility

Netflix's help page, "How ideas are pitched to Netflix" (help.netflix.com/en/node/100386), checked 18 September 2026, states that the company does not accept unsolicited pitches, and describes a route that runs through specified representatives who already have an existing Netflix relationship. The same page separately mentions buying finished works. Two doors, different rules, one policy page.

Neither door is a mailbox for an unmade show. That's what the page says. It describes a class of submitters — representatives with an established relationship — and a class of material. It does not certify that you belong to either. And the correct reading isn't a puzzle to solve. The relationship isn't an obstacle parked in front of the door. It is the route. If you don't have one, the honest conclusion is "not this door, not today."

This is where the introduction state and the wrong move most resemble each other, so the boundary is worth drawing exactly. Asking someone who already knows you and your work, and is placed to vouch for it, whether they'd be willing to make an introduction is a permitted next action — a question, and no is a permissible answer. What isn't permitted is approaching a representative you have no relationship with, or a well-connected stranger, in order to get behind a door keyed to a relationship you don't hold. That isn't requesting an introduction; it's asking to borrow access, and the page already named the result when it said unsolicited. An introduction request doesn't convert this route into a door you may knock on. It can only place you on the route if the person making it already stands there. So for a door keyed to an existing relationship, an introduction request is a next action only when the person you'd ask already knows you or your work. With nobody in that position, the row doesn't move.

That distinction in one sentence: "accepts proposals" tells you the shape of what they'll read, not that they'll read yours. It says nothing about your geography, your stage, your genre, or whether you personally qualify.

For contrast, Blue Ant Media's "How to Pitch Us" page (blueantmedia.com/global-media/how-to-pitch-us/), checked the same day, separates independent-producer proposals — which require the recipient's own form and stated materials — from acquisition of fully completed work, and lists what a proposal needs. It's a clean example of the fork sitting on one page, and it's Canadian. Read it to understand how a documented route is structured; don't read it as a US destination. The linked form, the personnel behind it and any given project's eligibility weren't verified, and a page that instructs producers how to pitch says nothing about who will answer.

One fictional creator, three candidate routes

Say a US-based creator has a pilot script and a development bible, no produced episodes, and no existing relationship with any buyer or with a representative who has one. Fictional, but a common starting position. Here's how three candidate routes sort under the method above.

Read the rows in order and the method shows itself.

The first row is a boundary, not a challenge. The published policy tells this creator something useful — that the door is real but keyed to a relationship — and the next action is to stop, which saves the email, the follow-up and the small erosion of confidence that comes from sending into a stated no. The introduction state is recorded in that same row, and it has nobody to attach to.

The second row is where most lists quietly lie. It's a placeholder for a route that hasn't been found yet, and it must stay marked unresolved until someone has actually read a full set of official terms: who may submit, from where, in what genre, at what stage, in what window, with what attached. If no call passes that reading, the row becomes "no route available now" — written down, honestly, rather than swapped for a plausible-sounding opportunity that hasn't been checked.

The third row is included because it's the clearest illustration of the stage mismatch, and it stays explicitly Canadian. Everything in that row would change if the project held a finished series; nothing in it changes because the pitch is good.

Notice that the table ends with no green rows. That's a normal outcome. A comparison that produces two "no" results and one open question has still done its job: you now know where not to spend the week, and exactly what would have to be true for a row to move. Forcing three send actions out of three rows would have produced three ways to waste a contact.

The table records published policy as of those check dates. It establishes no eligibility, verifies no contact, and reflects no submission of any material.

Select the smallest permitted next action

Every candidate should end in one of four states, and none of them is "send everything and hope."

An eligible submission, meaning you match what was asked for, through the channel they described, as a submitter they accept. This is the only state where material actually goes out, and it goes out in the requested shape.

An appropriately requested introduction, meaning you asked someone who already knows you or your work, and is placed to vouch for it, whether they'd be willing to make an introduction — and they agreed. An introduction can be requested. It can't be assumed, implied, or written as though it already happened — and it can't be invented, because the person on the other end will check.

A development conversation, where a producer or production company engages with the project on the understanding that you're building something together, not asking them to buy it.

No submission yet. The underrated state. Nothing about collecting names obliges you to use them.

Two habits make this section easier. First, resist sending the full package when a shorter item was requested — the requested item is the item, and extra documents create work for a reader who may already be constrained by what they're allowed to open. Second, treat any paid intermediary as a question rather than a shortcut. A service can be described as introducing you to someone. It cannot be described as guaranteeing access or consideration, and whether a given intermediary's relationship satisfies a recipient's stated route is a question you answer by reading that recipient's words, not a directory's.

Recheck at the point of sending

Keep three records apart, because they expire at different rates.

The dated policy finding — what the page said, and when you read it. This is the one that ages least gracefully. Open calls close, windows shift, requirements change.

The contact relationship — who you're writing to and why this approach is one they've asked for. A policy page can describe a route; it can't tell you that this particular person is still in that role.

The permission to circulate private material — whether you're actually cleared to send the deck, and to whom. This one matters more than the other two, because a bible sent to the wrong reader can't be recalled.

Before the actual send, reopen the recipient's current instructions and re-read them against your table. If something changed, update the row and the decision changes with it. An old table is a record of what was true once, never an enduring authorization.

End each candidate with one of two things: a documented next action, or a clear reason not to send. Both are results. A list of recognizable names becomes a plan the moment every row says which one it is — and until then, it's just names.

Frequently asked questions

What makes a company a destination rather than just a lead?

Its own current instructions must describe a route that fits both the project's stage and you as a submitter. A familiar name, a catalog match, or an email address found online is only a lead. Deliverability is not permission, and a catalog fit tells you nothing about how to get in.

Why is a buyer of finished programs not a slower version of a development buyer?

Someone who purchases completed shows has a use for a completed show. An unmade project is not a smaller version of that product; it is a different category of thing, and enthusiasm does not convert one into the other. That is a stage mismatch, not a judgment on the pitch.

What does the Netflix policy page show about unsolicited pitches and introductions?

Checked on 18 September 2026, the page states that Netflix does not accept unsolicited pitches and describes a route through specified representatives who already have a Netflix relationship, while separately mentioning buying finished works. The relationship is not an obstacle in front of the door; it is the route. An introduction request is a permitted next action only if the person you would ask already knows you or your work and is placed to vouch for it; with nobody in that position, the row does not move.

How should missing, stale or contradictory submission instructions be handled?

Use a clarifying question through an authorized channel, such as a general contact or a form with a question field. Asking how an independent producer should approach the organization is different from sending a bible to the same address. Record the organization and exact page, the date read, geography, who may submit, relevant form or genre, required stage, and what is requested first; recheck before sending.

What are the possible end states for a candidate, and why is 'no submission yet' useful?

A candidate can end in an eligible submission, an appropriately requested introduction that was agreed, a development conversation, or no submission yet. No submission yet is underrated because collecting names does not oblige you to use them. Every row should end with a documented next action or a clear reason not to send; both are results. A paid intermediary cannot be described as guaranteeing access or consideration.

Further reading

• Your Best-Written TV Script Is Not Your Most Representative. Which Should You Send? — Before choosing which of your scripts to send, read this to work out the object the request is actually buying rather than your strongest sample.
• How to Email a Film Pitch Deck — When an eligible route finally permits a send, read this to write the covering email around the true route, one sentence about the project, and a bounded ask.