A webinar built for a school-district buying committee that never meets in one room

Nobody in a school district buys curriculum on their own. An ESL coordinator feels the problem daily and controls no budget. A curriculum and instruction director owns the standard the material has to align to. A principal owns whether the building will actually use it. Title I staff own a funding source with rules of its own. Student services own the children who arrive mid-year with no English at all. Each of them can stop a decision and none of them can make one, and they are rarely in the same meeting about it. A cold email reaches exactly one of those people and asks them to become an internal advocate for something they have not seen. The campaign was built around a live session because it is the one format where several of those roles can look at the same thing at the same time without anybody starting a procurement process.

Five roles can each stop the decision and none of them can make it. An email to any one of them is asking a stranger to go and argue on your behalf.

1. 01

   The session had to teach a system the attendee could use without buying anything

   The WHO / WHAT / HOW / WHEN structure gives a coordinator a planning method they can apply on Monday. That is what makes it forwardable inside a district: a colleague will open a message about how to plan newcomer support and will not open a vendor demo recording.

2. 02

   The value proposition is subtraction, and subtraction does not fit in a subject line

   Standards-aligned lessons, scaffolds, newcomer support, four-domain practice and progress monitoring add up to less planning time and more consistency between classrooms. Both of those are things that stop happening rather than things that start, which reads as generic in text and as obvious in a live demonstration.

3. 03

   Registration data is a map of the buying committee if you count it that way

   The useful number is not how many people registered, it is how many districts registered more than one role. One coordinator from forty districts and three roles from twelve districts are the same registration count and completely different pipelines, and only the second one has committees forming inside it.

4. 04

   The four labels for the same job are a segmentation trap

   ESL, ELL, ML and multilingual learner describe one function and vary by district and by country. Segmenting on the label produces four thin lists; segmenting on the function and personalising on the label that district itself uses produces one list that can be spoken to correctly.

5. 05

   The recording is the asset that travels, so the follow-up has to be built for a forward

   A coordinator who attends and wants to act has to show something to a director who did not attend. The recording plus a summary written for someone who was not in the room — what the session covered, what it means for a planning cycle, what to look at next — is a different artifact from a thank-you email with a link in it.

The session was designed as a free live webinar teaching the WHO / WHAT / HOW / WHEN planning system rather than as a product walkthrough, so an attendee leaves with a method whether or not a conversation follows. Promotion ran through segmented outbound to education-only contacts across the United States and Canada, segmented by function and level — district leadership, building leadership, coordinator, specialist — because those groups attend for different reasons and need different opening lines. The registration page carried the session's structure rather than the product's features. The follow-up was built for forwarding: the recording, a written summary aimed at a colleague who was not present, and a next step a coordinator can pass upward without it reading as a sales handoff. Non-attendees stay in segment for the next relevant session.

1. 1

   Week 1

   Audience and segmentation

   Function and level segments defined across the four common role labels

   Owner: OmniFlow

2. 2

   Weeks 1–2

   Session design

   WHO / WHAT / HOW / WHEN structure, registration page, confirmation and reminders

   Owner: OmniFlow + publisher

3. 3

   Week 3

   Invitation campaign

   Segment-specific invitations, personalised per row, sent by segment

   Owner: OmniFlow

4. 4

   Week 4

   Live session

   Live delivery, recorded, questions captured against the segment that asked them

   Owner: Publisher + OmniFlow

5. 5

   Weeks 4–5

   Forwardable follow-up

   Recording, a summary written for a non-attendee, a next step a coordinator can pass upward

   Owner: OmniFlow

6. 6

   Week 5

   Committee read

   Registrations counted by district and by roles per district, not by headcount

   Owner: OmniFlow

7. 7

   Week 6 onward

   Rollover

   Non-attendees held in segment for the next relevant session

   Owner: OmniFlow

Report this campaign on committee formation rather than on volume. The first number is distinct districts represented; the second is how many of those districts registered more than one role, because that is the only registration signal that resembles a buying committee taking shape. Registration-to-attendance comes from the webinar platform's own report rather than a manual count, and recording views are reported separately from live attendance so the two are never added together. Every figure in this entry is pending verification against the platform export and should not be published before it is pulled.

Measured in the webinar platform and the sending tool, window to be confirmed at publication. Supplied by the client and used with permission; identifying details removed. Cited: ON24 *2025 Webinar Benchmarks Report*. ---.

These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.

5 of the figures on this engagement are not published yet. Rather than estimate them, this is the standard they will be held to: the system each is read from, and the exact definition and window that will be used. Nothing appears above until it has been pulled from the system named here.

We designed the session and the follow-up for the person who attends, and only afterwards built the artifact for the person they forward it to. That is the wrong order in a committee sale: the forwardable summary is the thing that has to exist first, because it defines what the session needs to demonstrate. On the next cycle the summary written for the non-attending director is drafted before the session outline, and the session is built to make that summary true.

Real client work. Every figure is measured in a named system and carries the window it was measured over. See all our work