A speaking tour where the audience answers back, and the course behind it

The situation

A good speaker with a real message and a standard deck. The presentation worked. It also ended the way every presentation ends, with a room of people who nodded, clapped and left, and no way to tell which of them had been moved by any of it.

The material deserved better than that, and so did the credit unions hosting it. A sponsor paying to put a speaker in front of its members wants to know what the members did, not how many chairs were filled.

What we built

The presentation became a live room.

The audience scans one code on the second slide. From then on their phone follows whatever slide the projector is on. On the slide about knowing your why, they type what they are actually saving for, and it goes up on the screen behind the speaker as a wall of answers, with duplicates folded together and counted, so the room watches itself agree in real time. On the giving slide they name who they want to help. In the middle there is a guessing game with a reveal, and at the end each person gets their own page built out of what they typed during the presentation.

Getting there took throwing several good ideas away. The phone stopped being a copy of the deck, because a second deck in somebody’s hand is a thing to wander through instead of a reason to look up. On slides that ask for nothing, the phone goes dark and says look up. Every slider came off the slides, because a speaker holding a clicker cannot drag one. What the room types is moderated with a single control, because it is being projected in front of somebody’s members.

Behind the tour sits the rest of it. A twelve module course, scripted, filmed and cut with animation and a scored title sequence. An email wall and a code login on the door. A certificate at the end. Twelve interactive calculators and quizzes that live outside the lessons and get shared on their own. And the whole course running in four separately branded editions, including one built as an employer benefit, all from one codebase and one configuration object.

Then the commercial layer: a partner portal, per-partner reporting, and proposal decks for the credit unions that sponsor a tour stop.

Why it works

A sponsor is not buying impressions. It is buying a room that did something, and a list of the people who did it.

Every host is one row of configuration carrying their mark, their landing page and their own tracking, so a new sponsor cannot change what any existing sponsor sees. When somebody leaves an email at the end of a presentation, the signup is tagged to the host it came from. That is the difference between a sponsorship and an ad read: at the end of the night the credit union can see what happened in its own analytics, not just in ours.

That tagging is also what makes the number above checkable. The 64 subscribers are not a RUKUS estimate, they are the count the newsletter platform itself attributes to the room software rather than to the website, and the rooms independently logged 66 people asking for the takeaway on the night. Two systems counted the same thing and landed one apart.

The part nobody sees

None of it is allowed to depend on the venue. The deck is a single self-contained file with the fonts, the images and the codes baked in, so it opens off a thumb drive with the network unplugged. Every interactive slide has a valid state with no room open: the poll becomes a show of hands, the calculator becomes a worked example, and nothing ever renders as four bars pinned at zero.

That constraint is the reason the tour can be handed to a speaker and just work.