The shared close
Everyone heard it at the same moment and it passed for all of them at once. Its credibility came from being witnessed collectively — nobody had to take your word for it.
Not the funnel — the recording and the offer around it. Which run to use, what comes out, what gets re-recorded and what stays exactly as it was, and what has to change once there is nobody in the room to react. Written to work with any webinar tool; where a tool decision genuinely changes the plan, it says so.

The biggest room is the one you remember, and it is rarely the one that sold. Attendance is a fact about your promotion; what happens after minute forty is a fact about the session, and only the second one survives automation.
Put your runs side by side and compare four things: how many of the people who joined were still there when the offer started, how many clicked it, how many bought, and what the questions were like. Rank on the middle two. Use the questions as a tiebreaker, because a run where people asked buying questions is a run where the argument tracked. Use attendance last, if at all.
A room of thirty that produced four purchases is a better master than a room of four hundred that produced two. The first tells you the session works and needs traffic; the second tells you the promotion works and the session does not, and automating it converts a bad hour into a bad hour that runs unattended.
A conversion pass cannot rescue a session that has never sold anything — it just makes the same result repeatable. Go back to running it live until people stay to the offer and some of them buy at the price you intend to charge evergreen. The three tests that decide whether a session is ready are in the automated webinar build guide.
A live recording carries a room, a date and a set of mechanics that assume both. Each of them quietly tells the viewer that they are watching something that already happened to somebody else — which is fine if you say so, and corrosive if you pretend otherwise.
Dead air is the easy pass and the one that returns the most minutes. Waiting for latecomers, the promise to give it another two minutes, poll-result pauses, the tech hiccup, the gap before the first question arrives. None of it is content, and all of it is expensive: a viewer alone at a screen has nothing socially holding them there, so silence is where they leave.
Live-only mechanics are harder, because they are load-bearing sentences rather than gaps. Anything that asks the room to act, names an attendee, or references how many people are present reads as a lie when the room is one person. Some cut cleanly. Some are wrapped around the point you were making, and those become re-record candidates rather than snips.
Anything that dates it is hardest, because it hides in plain sound. A season, a specific date, a recent announcement, a current price, a product version, a tool that may not exist next year. This is a credibility problem rather than a maintenance one: the moment a viewer works out they are watching something old, everything else you said becomes older too.
In most live runs the last ten minutes contain the best material in the session and the least usable footage in the file. The answers are excellent; the questions are addressed to named people, half of them are specific to one business, and the whole block is stitched together with waiting.
Cut all of it, then re-record the three questions that came up in every run as a short, deliberate block. It will earn more than the raw footage ever did, because it answers what everybody wondered rather than what two people typed. The question queue you kept from the live runs is the source material.
The instinct after a first edit is to re-record the whole thing properly, in a quiet room, without the mistakes. Resist it. The version with the room in it is the version that converted, and the empty-room version reliably sounds like one.
The mechanism is simple enough: you already know where the argument goes, so you deliver it faster, drop the pauses that earned their keep, and stop selling the parts you are bored of. Everything that made the live run persuasive was a response to a room that is no longer there.
So the default is keep, and four things are exceptions: the open, any transition that spoke directly to the room, the offer section, and the FAQ block you are building to replace the raw Q&A.
A live open managed arrivals. An evergreen open has to do three different things: say what this is, say how long it takes and what the viewer will be able to do afterward, and say when the offer arrives. That third line costs nothing and buys back every minute people would otherwise spend waiting to find out whether they are about to be sold to.
Welcome, and thanks for making the time. This is a recording of a session I originally ran live for [audience]. Nothing has been added to make it feel live — it is the session, tightened up, so you get the useful hour without the part where we wait for people to arrive. Here is how the next [45] minutes go. First, [the first thing]. Then [the second thing]. Then [the third thing], which is the part most people came for. At around [00:42] I will tell you about [the offer], and you will have [72 hours] from today to decide. If that part is not for you, everything before it still stands on its own.
Say it in your own words rather than reading that; the point is the four moves, not the phrasing. And note what it does not do — it does not claim anyone else is watching, and it does not apologise for being a recording. Neither is necessary.
Same room, same microphone at the same distance, same lighting, same clothes if you are on camera. If you cannot match it, do not try: cut to slides or a full-screen deck for the re-recorded segments and let the change read as deliberate. Nearly-right is worse than different — a jump in audio tone makes the viewer notice the edit, and noticing the edit is the first step to wondering what else was constructed.
Live, the offer runs on feedback: questions arriving, chat moving, somebody asking the price out loud so you can answer it for everyone. None of that exists now. Every job the room used to do has to be done by the recording, in advance, in order.
Then write down the timestamp the offer begins at, because three separate things key off it: the persistent offer element on the page, the milestone that marks a viewer as having reached the offer, and the follow-up branch that treats “left before the offer” differently from “heard it and passed”. Get the timestamp wrong and all three point at the wrong people, quietly, forever.
Those branches, and the emails that run off them, are written out in the evergreen email templates. Why the split matters more than any single message in it is the argument in the evergreen funnel playbook.
This is the translation people get wrong most often, and the one that costs the most when they do — because a deadline nobody believes devalues every deadline you set afterward, including the honest ones.
Everyone heard it at the same moment and it passed for all of them at once. Its credibility came from being witnessed collectively — nobody had to take your word for it.
Everyone starts on a different day, so a fixed date either expires and kills the funnel or gets extended forever and means nothing. A window per registrant is the only version that stays true.
Four decisions make the window real. Pick the anchor — registration time or viewing time. Viewing time is fairer and matches what the person experienced; registration time is simpler and keeps a clock running for people who never watched. Either is defensible. Not saying which one, in the emails and on the page, is not.
Pick a length you can hold, and hold it. Make expiry real, which means the checkout stops honouring the price rather than the timer merely reaching zero above a working purchase link. And decide what an expired link shows — a real page saying the offer has closed and what is still available, because some of those people come back at full price later and will not if the last thing you showed them was an error.
One more thing the live version never had to handle: the same person registering twice. Decide now whether a second registration restarts the window, and be aware that if it does, you have built a deadline that anyone can reset by using a second email address. The deadline mechanics guide works through the anchors, the timer behaviour and the edge cases in full.
One shared close date is a line in an email. A window per registrant is a value on a record that the offer page, the checkout and the follow-up all have to agree about — and across separate products they agree by accident, when they agree at all. In Agorix the registration, the watch behaviour, the offer and the purchase sit on one customer record — see how evergreen webinars work.
A live campaign leaves a pile of assets, most of them reusable and a surprising number of them carrying a date. The recording gets all the attention; the emails and the pages are where the live version actually leaks through.
Work the list below before you switch anything on. Every item is either reused, rewritten or retired — and writing that decision down for each one is faster than discovering in week three that the post-purchase email still thanks people for joining you live.
You now have a master, a versioned cut, a re-recorded frame, an offer section that stands on its own, the timestamp it starts at, and a deadline rule. That is the conversion job finished.
What remains is the funnel around it: the schedule model, the email branches that key off watch time, the three QA passes and the maintenance interval that keeps the whole thing true. Those are the remaining phases of the build guide, and the first decision waiting there is which schedule model the recording is going to run on.
One last thing worth knowing before you flip the switch: the first month is when evergreen funnels break most quietly. Nothing reports a dead link, a stale reference or a checkout that stopped taking payments — the funnel simply produces less, and less looks exactly like a slow month. Put the maintenance checklist in a calendar on the day you launch, not on the day you first suspect something is wrong.
The run that converted, not the one with the most people in it. Rank your runs on how many people stayed through to the offer and how many bought, treat the quality of the questions as a tiebreaker, and treat attendance as almost irrelevant. A small room that bought tells you the session works. A large room that did not tells you the promotion worked, which is a different fact about a different problem.
Three kinds of thing, in ascending order of difficulty. Dead air: waiting for latecomers, poll pauses, tech hiccups, the silence before the first question. Live-only mechanics: instructions to the room, name-checks, references to how many people are present. And anything that dates it: seasons, specific dates, recent news, current prices, a tool that may not exist next year. The third category is the one that hides, which is why the pass that finds it is a read of the transcript rather than another viewing.
No. The teaching converted at the pace it was delivered, and re-performing it alone usually makes it worse — you know where it goes, so you rush the parts that earned their pauses, and the version with no room in it sounds like one. Re-record the frame instead: the open, any transition that spoke to the room, the offer section, and a short FAQ block covering the questions every live run produced.
Every objection the room used to raise out loud has to be answered inside the recording, in order, because nobody is going to raise it where you can hear it. The price gets said aloud rather than only shown on a slide. The link needs a persistent place on the page, since there is no chat to paste it into. And any scarcity that depended on the room being full has to go — the second viewer of the day can do the arithmetic. The build guide covers how the offer element and the watch-time milestone get wired to the timestamp.
Translate the shared close into a window per registrant, anchored either to their registration or to their viewing. Pick one anchor, pick a length you can hold, and make expiry real — the checkout has to stop honouring the price, not just the timer. Decide in advance what an expired link shows, because some of those people come back at full price later and will not if the last thing you showed them was an error. The deadline mechanics go through the anchors and the timer behaviour properly.
Say it is a recording, or say nothing that implies otherwise — those are the two defensible positions and there is no third. Simulated chat, invented viewer counts and a presenter greeting people who are not there get discovered by exactly the person you least want to lose: the one paying close enough attention to buy. A scheduled start time and a real deadline supply all the urgency the mechanism needs, without requiring the pretence.
The registration page, the schedule, the session, viewer-level watch behaviour, the timed offer, the checkout and the follow-up — on one customer record, so the deadline, the branch and the buyer all refer to the same person.
14 days · $0 due today · Payment method required · Cancel before first charge and pay nothing