Skip to content
DemoSchedGet started

Features

A schedule that keeps itself, and asks around

DemoSched holds your sessions and their slots, keeps every past one with its stats and its recording, and privately invites whoever has gone longest without presenting.

Whatever your team calls the meeting — sprint demo, demo Friday, show and tell, showcase, lunch and learn, brown bag. Or a crit, a journal club, a deal review.

The record

Your sessions, your slots, and who has presented

DemoSched holds the schedule. Not a doc somebody keeps in sync — the actual list of upcoming sessions, who is in which slot, and what each person has shown before.

Create a session, say how many slots it has, and anyone on the team claims one. Nobody maintains the record: it is what running the sessions leaves behind.

  • Sessions with slots. Set a date, a slot length, and how many. Anyone on the team claims one.

  • A roster that holds its order. Reorder by dragging; positions stay tidy.

  • Recording links. Add one afterwards and DemoSched posts it to your channel.

  • A weekly heads-up. What’s coming next week, in the channel you pick.

PresentersVisible to everyone on the team
  • Priya RamanNightly export pipeline, 26 Jun 20257 demos
  • Tom ByrneFlaky test triage, 14 Aug 20254 demos
  • Wei LiangQuery planner rewrite, 18 Sep 20256 demos
  • Sofia MarchettiIncident review tooling, 16 Oct 20252 demos

Sorted by who has gone longest without a slot. That is why the invitation goes to Priya.

The history

Past sessions, stats and recordings

A session doesn’t disappear once it has happened. It keeps who presented, what they showed, and the link to watch it back.

Paste a recording link afterwards and DemoSched posts it to your channel and files it on the session. There is no folder to curate and no index to keep: the archive is what running the sessions leaves behind.

Team statsSince you started
  • 24Sessions held
  • 61Demos given
  • 11/12People who have presented
Past sessionsNewest first
  • Query planner rewriteWei Liang · 21 Nov 2025Watch
  • Incident review toolingSofia Marchetti · 16 Oct 2025Watch
  • Flaky test triageTom Byrne · 14 Aug 2025Watch
  • Nightly export pipelinePriya Raman · 26 Jun 2025No recording

The nudge

It asks one person, privately

Most slots get claimed without any help. For the ones that don’t, DemoSched picks a single person and direct-messages them. Not a channel blast.

  1. One person, not the channel.

    It works out who’s gone longest without presenting and messages them alone. No @here, no public callout, no list of who’s behind.

  2. It quotes their own history back to them.

    “Nothing since the nightly export pipeline in June” is harder to scroll past than “anyone got something?”. People who’ve never presented get asked to start.

  3. Only when there’s something to take.

    No nudge unless a real session has a free slot between three business days and seven days away. Sooner and they can’t prepare. Further out and they’ll forget.

  4. In their hours, in their timezone.

    Monday to Friday, 9 to 5, wherever they are — and never while Do Not Disturb is on. If now is a bad moment it waits and checks again in an hour.

And it nags less than you do. At most one DM per team per day, and never the same person twice inside a fortnight. Anyone presenting regularly never hears from it — and if they book a slot on their own first, the pending nudge is cancelled, never sent.

Fairness

Democratize your team’s demos

It knows who to ask because it has been keeping the register all along — every session, every slot, every presenter, since the day you started.

Being asked counts, whether or not you say yes. Ignore the DM and it simply moves on to the next person — no chase, no second ask, nothing recorded as a miss.

A nudge counts as a touch

It moves on

  1. Asked week 1PriyaDidn’t reply → asked again later
  2. Asked week 2TomBooked the 5 December slot
  3. Asked week 3WeiHadn’t been asked yet — so now they are

Nobody gets asked twice while somebody else has never been asked at all. Priya gets asked again — after the people who haven’t been asked once.

What it replaces

Five chores that go away

If your demo day currently runs on a shared sheet and a Monday-morning @here, these are the parts nobody has to do any more.

  • The demo sign-up spreadsheet

    No rows to add for next month’s sessions, no formula to break, no tab that two people edited at once. Sessions and slots live in the app and anyone claims one in a click.

  • Chasing people for the empty slots

    No @here on Monday, no reminder you have to remember to send, and no DM you have to write yourself — which also means no being the person who nags.

  • Working out who to ask

    You would have to remember who presented in March. DemoSched has the register, so it asks whoever has gone longest — and asks the people who have never presented before it comes back round.

  • Hunting for the recording afterwards

    Every recording link sits on the session it belongs to, next to who presented and what they showed, and gets posted to your channel when you add it.

  • Guessing whether demos are catching on

    Sessions held, demos given, and how many of your people have presented at all — counted as you go, so you can tell a habit from a good month.

Get your demo sessions back

Free for teams of up to 5 — every feature, no expiry date and no trial to run out. Bigger teams pay from $5 a month, for all of it.

Get started

An email address is the whole of it.