Ask a TV Producer for Development, Not a Promise to Sell the Show
Ask a TV Producer for Development, Not a Promise to Sell the Show
“Help us take this to streamers” is not a development request. It is a wish made large enough to sound like a plan.
A potential producer cannot promise a buyer, a sale, or a future room. What you can ask is whether they see a useful piece of development work at the project’s actual stage: a production assumption worth testing, a package that needs shaping, or a creative problem that benefits from a producing perspective. The invitation becomes stronger when it names that work.
Show what exists—and what does not
Consider a fictional series, Night Signal. Its completed pilot stays inside a city emergency-dispatch control room. Operators hear a caller trapped in a stalled elevator; through headsets, maps, and partial information, they decide which voice to trust. The drama comes from hearing consequences before anyone can see them.
The creator has three later-episode outlines. Each sends the story citywide: an operator follows a caller to a bridge, a dispatcher visits a family after a false alarm, a night supervisor rides with an ambulance crew. Those outlines may contain good scenes. They also put pressure on the pilot’s formal promise. Each one carries the story outside the control room. If the show leaves that room, what remains distinctive about its way of knowing?
That is a development problem. The available material is a completed pilot plus three outlines. The citywide action is proposed, not a confirmed production plan. The creator should not call the package fully assembled while that central choice remains unresolved.
Ask for a contribution, not access magic
The vague request is familiar: “Would you take Night Signal to streamers?” It asks for an outcome nobody controls and tells a prospective producer nothing about why their thinking is needed now.
Try this instead:
Night Signal is a control-room drama about operators who must act on partial information before the city reveals what their choices have set in motion. The pilot is complete, with three later outlines. I am testing whether the citywide episodes protect or dilute the show’s central experience of hearing events before seeing them. I would value a conversation about the production and story questions that comparison raises: what can remain offscreen, when an exterior consequence earns a departure, and what package material would let that intention be assessed honestly.
The request has a project, a present strength, a task, and a bounded reason to talk. It does not assume the producer will solve the outlines, secure access, or make introductions. The creator’s intention is held; the episode approach is open.
Make the first conversation proportionate
Share the pilot, short series overview, and the three outline summaries if the person has agreed to receive them. Ask whether the project and question fit their interests. A first conversation can test whether someone sees the same problem, or a more useful one. It cannot silently assign a free rewrite, a location study, a budget, or a buyer list.
Scriptnotes hosts John August and Craig Mazin discuss general meetings in a 2023 transcript, cautioning that a request for “what else you got?” can become a cost-free fishing expedition for new ideas; they advise keeping the meeting focused on the project that brought the writers in. That practitioner discussion is not a contract rule or a statement about every producer. It does support the smaller distinction here: a real task can be discussed; vague speculative labor should not be treated as the price of being taken seriously. Scriptnotes, Episode 588 transcript
The project brief can stay this short:
| What exists | Held intention | Open task | Conversation sought |
|---|---|---|---|
| Completed control-room pilot; three outline summaries | The audience experiences consequences first through sound and incomplete information | Decide when, if ever, citywide action belongs | Explore whether the episode approach supports the premise and what next material would clarify it |
The table is not a deal memo. It is a way to make the conversation legible before anyone owes anyone work.
Record only what actually happens next
Two follow-ups are possible.
If the producer says, “Send the pilot and the three summaries; I will read them against the control-room premise,” the creator can write: “Agreed next step: producer will read the supplied material and respond to the episode-location question. No attachment, development work, or buyer approach has been agreed.” The project remains at its actual stage.
If the producer says, “I like the idea; keep me posted,” the accurate follow-up is thanks and a record of that interest—nothing more. No one is attached. Development is not underway. The deck does not acquire a new name.
A good producer conversation may reveal that the citywide material is exactly what makes the show bigger, or that it should be rebuilt around the control room. It may reveal no fit at all. The value of the invitation is not that it guarantees a result. It gives the right person a real question to consider without making a promise on their behalf.
Ask for the work that exists: a conversation about whether the later episodes still honor Night Signal’s defining experience, and what should be developed next. Leave the sale where it belongs—in the future, if it comes.
If you need help preparing a TV development package that makes the present question clear, pitch.dog offers Film/TV pitch-deck work. Share the project, current materials, intended recipient, and deadline at [email protected].
Frequently asked questions
What distinguishes a real development request from asking a producer to sell the show?
A real development request names a specific piece of work suited to the project's current stage, such as testing a production assumption, shaping a package, or addressing a creative problem. Asking someone to take the show to streamers asks for an outcome nobody controls and gives the producer no reason their thinking is needed now.
In the Night Signal example, what is the unresolved development question?
The completed pilot stays inside the dispatch control room, where operators act on partial information. Three later outlines send the story citywide, so the creator must decide whether those episodes protect or dilute the show's central experience of hearing consequences before seeing them.
What should be included in a first conversation with a producer?
The creator can share the pilot, a short series overview, and the three outline summaries once the person agrees to receive them. The ask should state the project, a present strength, the open task, and a bounded reason to talk, without assuming the producer will solve the outlines, secure access, or make introductions.
How should a creator follow up after a producer expresses interest?
If the producer agrees to read supplied material and respond to the episode-location question, record that as the agreed next step and note that no attachment, development work, or buyer approach has been agreed. If the producer only says to keep them posted, thank them and record that interest—nothing more. No one is attached and development is not underway.
Does a useful producer conversation guarantee a sale or attachment?
No. It may reveal that the citywide material makes the show bigger, that the show should be rebuilt around the control room, or that there is no fit. Its value is giving the right person a real question to consider without making a promise on their behalf.