Show a TV Series' Production Model Without Turning the Deck Into a Budget
Show a TV Series’ Production Model Without Turning the Deck Into a Budget
Most pitch decks answer the first question very well. Why would anyone watch this? Here is the town, here is the woman who runs it, here is what happens when the door opens. Then the deck stops, and the producer is left to answer the second question alone: how would you make this every week, and what would you need?
A production model is your answer to that second question. It says what work repeats across ordinary episodes, what changes with each new one, and which of those changes you cannot yet speak to. It is a proposition a producer can argue with. It is not a budget, a schedule, a capacity promise, or evidence that the show would be easy to make.
The usual failure is turning that page into a cost document. You don't have rates, and a rate you invented is worse than no rate — it gives a producer something to disbelieve before they've read the good part. What you do have is the shape of the work. That is genuinely more useful to them.
To make this concrete, I'll use an invented series, because I have no real production account in front of me. Everything that follows is a paper example. Treat it as a method, not a report.
Start from the episode you'd make eleven times
The opening statement and the ordinary episode are different objects, and the deck needs both.
The opening statement is what you'd build if nothing had to repeat: the big piece, the public reveal, the crowd, the location nobody else can get. It is a legitimate thing to put in a pitch, and it can be wonderful. It is also useless as a model, because it is the one episode where every resource is at its maximum and nothing is at its ordinary setting.
The production page describes the episode you'd make eleven times. Choose a representative story, not the easiest one. Choosing the cheapest possible idea because it looks affordable mostly tells a producer that you don't know which episodes you're actually proposing to make. An ordinary episode is ordinary because it uses the show's standard complement of people, places, and preparation — not because it's thin.
Here is the invented example. Ticker is a workshop series. Each episode, a mechanical display arrives broken or unexplained. Four people work out what it was and what it did. By the end it moves again, in front of the person who brought it in.
Four recurring roles: the lead restorer, a fabricator who makes replacement metal parts, an apprentice, and a researcher who works out provenance and period. Four recurring spaces inside one building: the workshop floor with its benches and hoists, the finishing room, the parts store, and the front room where objects are handed over and revealed. Recurring preparation: the arrival survey, the tear-down, the hunt for what's missing. Recurring post: cutting workshop material into the same three beats — object arrives, object is understood, object moves.
Keep the viewing engine separate from that. The viewing engine is why episodes matter: something broken is understood and then it moves. The production pattern is how you'd make that happen repeatedly. They're related, and they are not the same sentence. A deck that conflates them ends up claiming that a returning location is what makes the show moving, which is not true and reads as a dodge.
Two columns, and three honest labels
The production page itself can be one page. Two columns, plus a line at the bottom.
Left column: what returns. Returning cast or contributors, standing spaces, designed elements that persist, the recurring research method, the recurring edit shape.
Right column: what changes. The subject of the episode, the object or case, the specific research it demands, any new access it requires, any outside contributor it brings, and whatever fresh work sits inside a repeating workflow.
That last point matters more than it sounds. A repeating workflow is not the same as repeated work. The restorer's method is the same every week — survey, tear down, identify, remake, test. The knowledge required to use it is new every week, because the object is new. A producer reading "recurring workflow" without that sentence will hear "no fresh preparation," and they will be right to be suspicious.
Then mark each row with one of three states:
- Have. Confirmed now. An option, an attachment, a secured location.
- Want. Designed into the show, not yet secured.
- Don't know. The dependency you're handing to the producer.
Three states, applied honestly, will do more for your credibility than any amount of confident phrasing. In Ticker, the four roles and the four rooms are all marked want, because none of it is attached and the workshop building hasn't been identified. Say so. "Workshop: standing set or secured premises, not yet identified" is a stronger line than a photograph of a beautiful building you have no claim on.
The reason to be this careful is that a recurring element can be intended rather than available. A returning location in the script is a plan. A returning location in the schedule is a lease or a build. The gap between those two is exactly what a producer is trained to find, and it is much better for you if they find it in your own labelling than in their own reading.
What each returning thing buys on screen
An inventory of equipment tells a producer nothing about the show. The useful version explains what each recurring element permits, so the producer can see what would change creatively if a dependency changed.
Take Ticker's first ordinary episode. A compact window automaton — a small animated shopfront scene, small enough to sit on a bench — arrives in a box. It fits inside the workshop. It can be surveyed, taken apart, rebuilt, and tested without leaving the building. The research is narrow: one maker, one period, one street's worth of shopfront history. One missing figure has to be carved and painted. The reveal happens in the front room, at the end, in front of the owner.
Now trace what the model is buying.
The four recurring roles are what make the bench scenes possible. Four people around one object, disagreeing about a spring, is the show's signature scene, and it needs all four people in the same room. The recurring spaces mean the object can move through the building — arrival in the front room, work on the floor, finishing somewhere clean, back to the front room. That geography is the episode's shape. The recurring edit shape means the audience knows from episode one that the last scene is the reveal, so the middle can spend its time on the puzzle instead of on orientation.
The variable demand in this episode is the research: one maker, one period, and a figure that has to be made because no original survives. That isn't a complication bolted on to make the page interesting. It's the episode. It's why the researcher is a regular and not a guest.
Write it that way and a producer can see what a change would cost you. If the front room disappeared, the reveal would have to move and the show's closing beat would change. If the researcher became a guest, the bench would lose its argument. Those are creative statements, and they're the ones a producer can actually work with.
A second ordinary episode changes one dependency
One episode can't tell you what repeats, because everything looks like a pattern when there's only one of it. Compare a second.
Ticker's second ordinary episode concerns a large animated display built into the wall of a former department store — a moving scene set into the wall itself, part of the building. It cannot be removed without taking the wall apart.
Most of the model holds. Same four roles. Same research method, though this time the subject is a different maker in a different period and the building has its own history, so the research has a building inside it rather than only an object. Same three-beat shape. Same bench work: the fabricator makes the replacement parts at the workshop, at the same bench, exactly as before.
What changes is where the job finishes. The fitting, the first full test, and the reveal all happen at the site, in a building the production does not control. That isn't a restriction someone invented to create a dilemma; it's the ordinary condition of a display that is part of a wall. You also cannot fully test a wall-mounted tableau at a workshop bench, so the first moment everything runs together is the moment it runs on site. Which happens to be the reveal. Which happens to be the last scene.
Notice what that does to the signature. The four-around-the-bench scene doesn't vanish — it splits. Two people stay with the bench and the parts; two are at the site measuring. The scene survives in a changed form, and the edit has to make one continuous job out of two places. That's a real production consequence, and it's also a real creative one: the reveal now happens in the object's own building, among the building's own people, rather than in the front room. It might be a better episode. It is definitely a different one.
Which brings up the honest comparison. Neither episode is being presented as cheaper than the other. Whether a returning space costs less than a new one depends on what you're returning to — premises held for a run, a build, a lease, a location that was only ever available for three days. That judgement belongs to a producer with actual numbers. Your job is to make the difference visible so they can price it.
That difference, stated plainly, is the largest unresolved dependency across both episodes: how much of the series can be planned around one building you control, and what happens to the episodes that can't be.
Hand over one question, not a promise
The bottom of the production page is one line. Not a claim of efficiency, not a schedule, not a promise about capacity. One question a producer is equipped to answer.
For Ticker, it would read something like: how many ordinary episodes can be planned inside a workshop the production controls, and what should we do about the ones whose objects can't leave their own buildings?
That's a question with an answer. Compare it with the version that sounds confident and gives the producer nothing: "the returning workshop makes the series efficient to produce." The first tells them what you understand about your own show. The second tells them you haven't thought about it and are hoping they won't either.
The pitch paragraph itself can then be short, because the work behind it is already on the page:
Ticker is a workshop series. Four people, one building, one object at a time. Each episode, something broken arrives and leaves moving. The workshop floor and its benches, the finishing room, the parts store and the front room repeat. The team's method repeats. What changes is the object and what it asks for — the maker to research, the parts to remake, and whether it can be brought in at all. One of the two episodes we'd point to has a display built into a wall, so the bench work happens in the shop and everything else happens in a building we don't own. We'd want a producer's view on how much of the series can be planned around a workshop we control, and how to treat the episodes that can't.
Nothing in that paragraph claims access, cost, crew capacity, a safe procedure, or a date. It also doesn't pretend the second episode is a problem. It's a variation, and the variation is where the show gets interesting.
That's the model doing its job: a producer finishes the page knowing what repeats, what changes, what you have, what you want, and what you don't know yet — and holding one question they can actually answer. Everything else on the subject of how the show gets made, including whether a chosen look can survive an ordinary episode, is a separate conversation with its own page.
The last thing worth saying is about ambition. Describing your production model plainly is not the same as lowering your sights, and it isn't a concession to the people who fund things. The showpiece episode can stay in the deck, labelled as the showpiece. The ordinary episode is what you're asking someone to build a run around. Naming the difference between the two is what makes the rest of the pitch believable, and it's the part of the conversation where a producer stops reading and starts talking.
Frequently asked questions
What should a production model page establish in a TV pitch?
It should say what work repeats across ordinary episodes, what changes with each new one, and which dependencies cannot yet be answered. It is not a budget, schedule, capacity promise, or proof the show would be easy to make.
Why choose an ordinary episode rather than the opening statement as the model?
The opening statement is built when every resource is at maximum and nothing is at an ordinary setting. The model describes the episode you would make eleven times, using a representative story and the show's standard complement of people, places, and preparation, not the cheapest idea.
How should a recurring workflow be described so it does not sound like repeated work?
Say that the method repeats while the knowledge required is new each week: in the workshop example, survey, tear down, identify, remake, and test stay the same, but the object and what it demands change. Otherwise a producer may hear that no fresh preparation is needed.
What do the labels Have, Want, and Don't know do?
They mark each row honestly: Have means confirmed now, such as an option or secured location; Want means designed but not yet secured; Don't know means the dependency handed to the producer. The labels distinguish an element intended in the script from one available in a schedule.
What should each returning element explain in the treatment?
It should explain what that element buys on screen, so a producer can see the creative consequence if a dependency changes. For example, four recurring roles make the bench scenes possible, recurring spaces give the object a geography, and a recurring edit shape fixes the reveal as the closing beat.