Skip to content
DemoSchedGet started

Use cases

Every meeting where the team is the speaker list

DemoSched was built for the engineering demo day. What it actually fixes — a session that comes round whether or not anybody signed up to fill it — turns up in a lot of other rooms.

Design crit, lunch and learn, journal club, paper club, deal review, knowledge share, incident review.

Where else it fits

Five rooms with the same empty slot

Each of these is a standing meeting that the people attending it are supposed to fill, and each one fails the same way: it comes round, nobody has volunteered, and somebody spends the week asking.

  • Lunch and learns and brown bags

    People and L&D teams, company-wide

    The calendar hold is permanent; the speaker isn’t. Whoever owns the program spends every week in DMs finding next Thursday’s talk, and the same four people keep volunteering. DemoSched opens the slots to the whole company, asks somebody who hasn’t spoken yet — privately, so saying no costs nothing — and files each recording on the session it came from, which is the library the program was supposed to leave behind.

  • Design critique

    Product design and brand teams

    Crit runs whether or not anyone brought work, and when it runs on volunteers it runs on the confident ones. The designers whose work would gain most from an hour of eyes can go a whole quarter without putting anything up. Claiming a slot is what puts you on the agenda, and the invitation goes to whoever has gone longest without one — so the agenda comes from the whole team rather than the loudest third of it.

  • Deal reviews and call teardowns

    Sales and customer success

    The Friday review runs on whoever the manager thinks of, which is the reps closing big and the reps in trouble. Everyone in the middle is never on the agenda. Here a rep claims the slot with the deal they want looked at, the register shows who has actually been through one this quarter, and the recording stays on the session for the half of the team who were on a call.

  • Journal clubs and paper reading groups

    Hospital departments, research groups, ML teams

    A reading-group rota is a shared doc somebody keeps by hand, and it slips the first week they are on leave — so “who’s presenting?” arrives on the morning. The rota here is the register the app has been keeping anyway, and the person who has gone longest gets a quiet direct message instead of a name-check in front of the department.

  • Agency and consultancy knowledge shares

    Agencies, consultancies, professional services

    The internal Friday share is the first thing to lose to a client deadline, and what goes with it is the only record of what the last engagement taught anybody. Slots the whole studio can claim, a count of who has presented at all, and every recording kept beside what it was about — so the next team on a similar brief has something to watch.

The test

Three things they all have

It recurs on a fixed cadence. What fills it comes from the people who attend, not from a speaker budget. And nobody’s job title says “make sure someone signed up” — so it lands on whoever minds most, every week, forever.

DemoSched isn’t the meeting and it isn’t the video call. It is the list of who’s on next, the record of who has been on before, and one private message when the list still has a hole in it.

Upcoming session#journal-club

Thursday 3 September 2026

Two slots, 20 minutes each

  1. Dr Amara OkonkwoSGLT2 inhibitors in acute heart failure
  2. Open slotClaim

Nobody keeps the rota. Whoever has gone longest gets asked, privately, once.

Where it doesn’t fit

When the speakers come from outside

A conference track, an external speaker series, a customer webinar: the speakers aren’t your team, there is no register to keep, and nobody to nudge. DemoSched has nothing useful to do there.

Same for a meeting with one standing presenter. If the answer to “who’s on?” is the same person every time, you don’t have the problem this solves.

The long tail

Same shape, different room

Every one of these is a recurring session that the group fills itself. If yours is on this list, the five above are describing your week too.

SRE incident reviewsArchitecture and RFC reviewsSecurity threat briefingsUX research share-outsData and analytics showcasesSupport case of the weekAll-hands team spotlightsAI enablement guildsSales enablement sessionsInvestment idea pitchesGrand rounds and tumor boardsUniversity seminars and lab meetingsTeacher PLC and instructional roundsEmployee resource group speaker seriesBootcamp project demo daysAccelerator cohort practice runsHackathon and innovation-day showcasesGame studio playtest reviewsKaizen and continuous-improvement talksOpen source community callsMeetup lightning talksSpeaking clubs and practice groups

Start with the room you already have

Free for teams of up to 5 — every feature, whatever your meeting is called. Bigger teams pay from $5 a month, for all of it.

Get started

An email address is the whole of it.