Prepare a Series Pitch for a Public Stage, Not a Private Sales Meeting

By pitch.dogFoundation14 min read20 September 2026

Television

A public pitch and a private buyer meeting can be about the same show. They cannot use the same deck, the same running order, or the same closing sentence.

The buyer meeting ends when you leave the room. The public pitch ends when the recording stops circulating, which may be never. That single difference — the audience is larger, the information is narrower, and the artifact outlives the occasion — decides almost everything else: what you say first, which details you withhold, how the clip is introduced, what you do when the moderator asks a question you can't fully answer, and what you ask for at the end.

The mistake isn't oversharing for its own sake. It's treating a stage as a sales meeting with worse acoustics. A moderator, three panelists, and a few hundred ticket-buying strangers are not a commissioning conversation. They're a chance to make your show legible to people who have never heard of it, some of whom might later be useful in ways the event itself cannot arrange.

Establish the event you are actually entering

Before you choose a single line, get the participant brief. Not the event page. The brief — the document the organizer sends the people who are appearing. If you only have the public page, you have marketing copy, not instructions.

Six things need answering, and you should be able to point to where each was answered:

Who is in the room. A general audience, a room of other creators, invited industry guests, or some mix. The mix changes your opening, because the person who needs the situation explained is usually the majority.
The live format. Solo presentation, panel, interview, or a short pitch followed by moderated conversation. These are different performances with different preparation.
The slot, exactly. Seven minutes on stage plus ten minutes of questions is not the same as a seventeen-minute slot. Find out whether the moderator's introduction counts against your time. It often does.
Clip handling. Whether clips are allowed, how long they may run, who plays them, and off which machine. "Bring it on a USB stick" and "email it to us by Tuesday, we play it from the desk laptop" produce different rehearsals.
The question route. Whether questions come from the moderator, the floor, index cards, a submitted list, or all of them. Who decides when questions end.
Recording. Whether the session is recorded, whether clips are published afterward, whether you see a clip before it goes out, and how long the organizer keeps the material.

Where the brief is silent, write the question to the organizer rather than filling the gap with a reasonable assumption. A reasonable assumption is how creators end up planning for a clip that the venue's laptop refuses to play, or answering a question on camera that they thought was off the record.

It helps to separate three things that feel similar on the night. Panel feedback is a reaction from people who may or may not know your genre; useful, occasionally sharp, and not a decision. Public exposure is strangers learning the show exists; it compounds slowly and is the actual product of most events. A private development conversation is a real next step with someone who can do something concrete. They have different immediate tasks: for feedback you want a clear, describable premise; for exposure you want one image people can retell; for a development conversation you want a route to the follow-up that doesn't depend on catching someone at the bar.

Choose a public story, not a censored private deck

A private deck can be structure all the way down — logline, comparables, market, budget, attachments. It works because the person across the table has asked for it in that form.

A stranger in a rented auditorium has not. They need a situation they can enter: who is doing what, why it's hard, and what happens next. That's the whole engine. A premise stated as a category ("a workplace drama set in a regional theater") is not a situation, and audiences do not remember categories.

Here's a worked example. Everything below is invented — the event, the show, the people, the budget, the recording arrangements. It exists so the decisions are visible, not because any real pitch night works this way. Before using any of it concretely, you'd need the actual event's participant brief and recording policy in front of you.

The show. Strike is an eight-episode finite series about the overnight crew of the Halstead Playhouse, a community theater. Each episode is one shift: the last curtain comes down at 10:00 p.m., the audience is out by 10:30, the crew starts at 10:45, and a rental company's truck arrives at 7:45 a.m. Nine hours to strike a set. The season follows one theater through one closing season and ends when the building goes dark. Only one piece of footage exists: a teaser scene shot with the real crew on a strike night, which is what the clip in the running order below is drawn from. The four-week access window mentioned later is for a separate proof-of-concept shoot that hasn't happened yet.

The situation the creator opens with. Closing night. At 1:20 a.m., a caster shears off the upstage rolling platform — the piece that carries the second-act balcony. The platform is too heavy to drag, and it's now wedged where the loading door path runs. The house carpenter, Wes, makes the call: cut the cross-bracing, split the platform into two halves, carry it out in pieces, and leave a written note for the rental company's technical director. The platform belongs to the theater's stock and the next production needs it in three weeks. So the shift ends on two questions the episode actually cares about: who tells the production manager that the platform is now scrap, and who eats the rebuild.

That's the public story. It has a time, a physical problem, a decision, and a cost. A stranger can follow it while eating a sandwich.

The finite promise. Eight episodes, one arc, a definite end. Saying "eight and done" is itself a pitch decision — it tells the room what shape of thing they'd be watching, and it prevents the vaguest possible question later, which is what happens after this ends.

Now the part that isn't the private deck's fault. Withholding every turn can make the whole thing unintelligible. If you refuse to say how the platform problem resolves, the audience never learns what kind of show this is — is it a procedural about fixing things, or a show about who gets blamed? The revelation that earns its place on stage is the one the explanation needs. The revelation that stays home is almost always about the package:

Not for the stage, the clip, or a recorded answer:

A director, Lena Marsh, has taken two meetings. No agreement, no name clearance. Do not name her.
A draft budget assumption of $310,000 across eight episodes. Provisional, built for a scale nobody has offered.
An assumed eight-episode order — the same number as the creative shape, but an assumption, not a commission.
A submission to one specific platform that has not been made yet.
Wes's reason for leaving the crew in April. He has agreed to appear and to be named in the series. That's a different permission from discussing his life on a stage.

That list is a document you maintain, not a feeling you keep in your head. It should be one page, separate from the pitch, and the person running your questions should know what's on it.

Write the handovers as part of the pitch

A clip dropped into a presentation without a handover is the most common way a good seven minutes becomes confusing. The audience doesn't know what they're about to watch, then they don't know what they just watched, and the two gaps cost you about forty-five seconds of attention you can't buy back.

Three moments, written and rehearsed: before the clip, after the clip, and the moderator's return at the end.

The fictional event allows one clip of up to 90 seconds. Here's a seven-minute running order that holds together:

Moderator's introduction (60–90 seconds, before the seven minutes begin — supplied in writing in advance, with the show's title and how to say your name)

0:00–0:45 — the situation. 1:20 a.m., the caster, the nine-hour clock.
0:45–2:15 — who the crew is, what the series is, the eight-episode finite shape.
2:15–2:45 — hand-in: what the clip is, and specifically what to watch for. Not "here's some footage" but "this is the forty seconds where the decision gets made, and you'll hear Wes count twice."
2:45–4:00 — clip plays (75 seconds).
4:00–4:30 — hand-back: one sentence naming what the clip added, then straight into the next thought. Do not recap the clip. The audience just saw it.
4:30–6:00 — where the season goes; what is confirmed and what isn't.
6:00–6:45 — the ask.
6:45–7:00 — closing sentence, then hand back to the moderator by name: "That's my seven — thank you, and I'll take anything you've got."

Rehearse the last fifteen seconds more than the first fifteen. Most creators over-prepare the opening and let the ending dissolve into "…yeah, so, that's it." The moderator then has to improvise a transition, and the whole thing sounds less finished than it was.

Now write the failed-clip version. Clips fail for ordinary reasons: wrong file format, the house laptop is on a different profile, an audio cable is dead, someone skipped your email by Tuesday. The replacement is not an apology — it's the same information, spoken, at roughly the same length so nothing downstream shifts.

For Strike, that's about 75 seconds of talking that covers exactly what the clip was supposed to add: the physical work, the pace, and Wes's manner. Something in this shape: it's a quarter past one and the platform's front corner is four inches off the ground where the caster used to be; two of the crew are crouched at the brace bolts; Wes is quiet for a while, which is how you know it's bad; then he says they're not going to save it, they're going to split it, and he starts assigning people to the halves while someone else is already writing the note for the morning. Same caster, same 1:20 a.m., same decision, same unanswered questions. The episode example survives; only the medium changed.

If you don't have that paragraph written before you walk on, you don't have a fallback. You have a hope.

Give public questions a useful boundary

The moderator's question that stops most creators is the attachment question. In the invented example, it arrives as: "So who else is attached?"

The public answer states confirmed things and stops. In this case that's the house carpenter, who has agreed to appear and to be named, and the theater board's written four-week access window for a proof-of-concept shoot. Everything else is a conversation with someone who hasn't agreed to be named. So the answer is roughly: "Wes is in it — the carpenter is a real carpenter and he agreed to let us film the shift. The theater's given us a four-week window. Beyond that, everyone I'd name hasn't agreed to be named yet, so I won't. If that's the part you want to talk about, there's a follow-up table by the bar and an address in the program — I'll be there after."

Two things make that answer work. It gives the room real information rather than a coy non-answer, and the boundary is stated as a boundary rather than a tease. "I can't say yet" invites another question. "I won't name people who haven't agreed to be named" closes the topic without pretending the topic is boring.

Then the bridge. The follow-up route needs to exist before the event — an organizer-approved table, a sign-up, an address printed in the program. Inventing one on stage ("email me at…") puts a private contact route into a recording that will still be circulating in eighteen months.

And remember what the recording does. A friendly room softens an answer: people laugh, the moderator nods, someone in row three says "sounds great." Strip the laughter out and the same sentence can read as a claim you never made. If you say "we're talking to a streamer," the clip says you have a streamer. If you say "the budget's around three hundred," the clip says the budget is three hundred. The test isn't whether it's true in the room. It's whether it's still true with the room removed.

Two more boundaries worth setting in advance. A panelist's participation in your session doesn't mean they can acquire the show; they were invited to react, and treating the question period as a commissioning meeting will read badly both live and in the clip. And nobody claps for a business plan. Applause means the room enjoyed ninety seconds of your company. It is not evidence of demand, and it's not something to quote to anyone afterward.

Close on an action the event can support

The ask has to fit the event. A public pitch night can support one honest next step, usually a route to a development conversation that the organizers have already set up. It cannot support "so, who wants to buy this," and addressing a mixed audience as if every seat were a buyer is the fastest way to make the room feel like it's being sold to.

In the invented example, the closing sentence is about thirty seconds of the seven. It names what exists — an eight-episode finite season, a teaser scene, a confirmed access window, a real crew — and then points at the follow-up route: "If you work with independent series, or you just want to see the proof-of-concept when it exists, the organizers have a table by the bar and my email's in the program. Thank you." Then the moderator's name, then stop.

Rehearse the ending as a single unit: closing sentence, moderator's return, and whatever contact display the event provides. If the organizers put a slide up with your details, know whose job it is to advance it, and whether you're supposed to stay on stage while it's up. The ending is the part the room remembers and the part most likely to be in the clip, and it's the part that most often runs straight into the first question because nobody rehearsed the seam.

What you walk in with

Two documents, not one.

The first is the public sequence: a situation, the series promise, a clip with a hand-in and a hand-back, a spoken replacement for the clip if it fails, answers to the two or three questions you can predict, and a closing sentence you've said out loud at least five times. The second is the private-information list: the unconfirmed names, the draft numbers, the assumed order, the unmade submission, the personal detail that isn't yours to tell on a stage. Keep it on one page and keep it somewhere you can find it during the question period.

And read the participant brief before you use any of this. That's not a formality. The brief is where the actual audience, actual slot, actual clip rules, and actual recording policy live, and this article's example is invented specifically so it can't be mistaken for any of them.

Frequently asked questions

What document should I get before preparing a public pitch?

Get the participant brief, not just the event page, because the public page is marketing copy. The brief is where details like audience, live format, exact slot, clip handling, question route, and recording policy live. Where it is silent, ask the organizer rather than filling the gap with an assumption.

How does a public pitch differ from a private buyer meeting?

A private buyer meeting ends when you leave the room and can be structure-heavy. A public pitch ends when the recording stops circulating, so the audience is larger, information narrower, and the artifact outlives the occasion. A stage should get a situation a stranger can enter, not a censored private deck.

What should I do if my clip fails during a public pitch?

Have a spoken replacement ready at roughly the same length so nothing downstream shifts. It is not an apology; it is the same information the clip was supposed to add, delivered orally. Without that paragraph written beforehand, the fallback is a hope.

How should I answer a public question about who is attached?

State confirmed things and stop. Name only people who have agreed to appear and be named, and state the boundary as a boundary, rather than teasing. Then point to an organizer-approved follow-up route that existed before the event.

What two documents should I walk in with?

One public sequence: situation, series promise, clip hand-in and hand-back, a spoken replacement if the clip fails, predictable answers, and a rehearsed closing sentence. One private-information list: unconfirmed names, draft numbers, assumed order, unmade submission, and personal detail not yours to tell on stage.