Most download sales are asynchronous: a stranger pays at 2 a.m., a file arrives, and neither of you is awake for the other. A paid live workshop breaks that pattern completely. You announce a date and an hour, people clear their diaries, and the download stops being the whole product and becomes the scaffolding around a live event — the pre-work they were supposed to open beforehand, the workbook they fill in while you teach, and the pack they expect afterwards with the slides, the templates, and the replay. The sellers who run these well do not work harder on the day. They split the delivery into its three real moments weeks earlier, reconcile two lists that never quite match, and rehearse the whole chain while there is still time to fix it. This guide is that playbook.
Split the download into three deliveries, not one
The single biggest workshop mistake is treating "the download" as one file sent once. A live session actually needs three distinct deliveries, each with a different job and a different deadline. The first is pre-work: the short setup file attendees need before the session — software to install, accounts to create, a worksheet to print. Keep it small, completable in under half an hour, and deliver it at payment; its deadline is the evening before, not the session. The second delivery is the in-session workbook: the file they work in while you teach, mirroring the session section by section, sent with the joining instructions a day or two ahead — early enough to print, late enough to be current. The third delivery is the after-pack: final slides, completed examples, templates, and the replay link, sent within a promised window after the session ends. Each fails differently — late pre-work means setup during teaching, a workbook buried in a giant bundle gets lost, an after-pack with no timing promise means a day of chasing emails. Name the three deliveries separately on the sales page, and attendees will judge each one against the right expectation instead of judging all of them against the session start.
The buyer list and the attendee list will not match — plan for it
Every other download you sell has one person in it: the buyer. A workshop routinely has two or three. An assistant buys a seat for a manager. One partner buys two seats on a single payment. A company buys five seats with one card and sends you five names in an email three days later. If your delivery assumes buyer equals attendee, each of those normal cases becomes a support incident: the joining link and the workbook land in the purchaser's inbox, and the people actually attending have nothing. Solve it at registration, not on the day. Collect, for every seat, the attendee's own name and email as a required part of buying — plainly labelled as where the joining instructions, pre-work, and after-pack will be sent. State what happens if those details change ("email us the replacement name up to 24 hours before; seats are transferable, not shareable") so substitutions arrive as tidy emails instead of panicked chat messages at start time. Keep a simple count you trust — seats paid, seats named, seats sent joining details — and do not consider the workshop ready until the three numbers agree. The live session is the worst possible place to discover they do not.
Registration is a promise about timing — write it down
An asynchronous product page has to answer "what do I get?" A workshop page has to answer that plus "when, exactly, at every step?" — because attendees plan real diaries, childcare, and time zones around your answers. Write the timing promises down as part of the offer, not as replies you improvise later. The list is short: when the joining instructions arrive (and from which sender, so they are not filtered as a surprise), when the pre-work is available and roughly how long it takes, when doors open relative to the stated start, how long the session runs and whether there is a break, when the after-pack and replay will be sent, and how long the replay stays available. And set a registration close time and honour it: the seller who accepts a payment an hour before the session has sold someone a seat whose pre-work, joining details, and list reconciliation all have to happen while they are also trying to start teaching.
Rehearse the delivery, not just the teaching
Teachers rehearse content. Workshop sellers also need to rehearse logistics, because the logistics are what attendees experience first. A few days out, run the full chain as a stranger: buy a seat with a fresh email address, and note every message that arrives, in what order, from which sender, with which subject line. Open the pre-work on a phone as well as a laptop. Click the joining link from the actual email, not from your calendar invite, and check where it lands someone who arrives ten minutes early and someone who arrives ten minutes late. Download the workbook and confirm it is the current version — the classic rehearsal find is a delivery still pointing at last month's file, discovered by your test purchase instead of by forty attendees at once. And write the failure plan while you are at it: if the meeting platform fails, where attendees hear from you, and a backup route for the workbook link you can paste into the chat. Backups invented live, on camera, are the one kind of support you cannot do well.
During the session: delivery has to work without you
Once you start teaching, you are unavailable — and that is precisely when delivery questions peak. Someone arrives late and cannot find the joining email. Someone's workbook will not open. Someone is in the session under a different name than the one on your list. You cannot teach and run a support desk at the same time, so the session needs delivery that answers without you. Three things carry most of the load. First, a pinned or opening-slide panel with the three links attendees need — workbook, shared exercise document if you use one, and the help address — shown at the start and again after any break, so a latecomer can self-serve instead of interrupting. Second, one named human who is not you, even if it is only for the session's first fifteen minutes, watching the chat and the support inbox for access problems; most live delivery failures cluster at the start, and a helper who can resend a link or confirm a name frees you to teach through them. Third, a rule you state out loud at the beginning: access problems go to that help address or chat, content questions go in the session — said once, kindly, it stops the chat becoming a queue of "I never got the email" that buries the teaching.
The replay and the after-pack are a second delivery wave
When the session ends, a second sale effectively begins: everything you promised afterwards now has to arrive, for attendees and — the easy group to forget — for the people who paid and never showed up. No-shows are not edge cases; for paid online sessions they are a normal slice of every cohort, and they are owed exactly what the page promised them, usually the after-pack and the replay for its stated window. Send the after-pack as its own delivery, not as a reply buried in a long thread: a clean message naming what is inside — slides, templates in usable formats, any completed examples from the session, and the replay link with its expiry date stated again. Timing matters more than polish here. An after-pack sent the same evening, slightly plain, beats a beautifully assembled one sent four days later to people who have already emailed twice asking for it. If editing the replay will take longer than the rest, split the promise: pack today, replay by a named day — and then hit the named day.
Live workshop delivery checklist
- The offer names three separate deliveries — pre-work, in-session workbook, after-pack with replay — each with its own timing promise.
- Pre-work is small, completable in under half an hour, and delivered at payment, not at session time.
- Registration collects each attendee's own name and email per seat; seats are stated as transferable, not shareable.
- Seats paid, seats named, and seats sent joining details are reconciled a few days out — and the three numbers agree.
- The page states joining-email timing and sender, doors-open time, session length, after-pack timing, and the replay window and its end date.
- Registration closes at a stated time that leaves room for pre-work, reconciliation, and joining details.
- A stranger test-buy has been run end to end: purchase, pre-work on phone and laptop, joining link from the email, workbook version confirmed current.
- A written failure plan exists: where attendees hear from you if the platform fails, and a backup route for the workbook link.
- During the session, links are pinned or on an opening slide, one named non-teacher watches access problems, and the where-to-ask rule is stated once at the start.
- The after-pack goes to no-shows as well as attendees, as its own delivery, within the promised window — and what was sent, to whom, is recorded.
A closing note on delivery tooling, because a live session is the delivery deadline you cannot move: attendees are present at a fixed hour, and a file that arrives late has missed the event it was bought for. FileFreight is the tool behind this site — flat-rate download delivery with personal expiring links, per-buyer PDF stamping, and licence keys, at $19/mo on Pro with 0% per-sale fees, or free at 5% per sale; payments go through your own Stripe account and it never holds your money. Full caveats, stated plainly: it is new and small, it is not a merchant of record and does not handle sales tax or VAT for you, it has no importer yet (there is free white-glove migration help for the first 20 sellers), and it is not a Shopify app — it is delivery only, with no marketplace and no buyer library. It also does not run your workshop for you — no tool does; the teaching, the timing promises, and the rehearsal are the work. If your current setup already lands the right file with the right attendee before, during, and after you teach, keep it. If buyers and attendees keep ending up as two lists that meet for the first time in your inbox on the day, that gap is the first thing to close — a live audience notices it together, all at once.
Top comments (0)