What's a runtime for technical talks?
Most slide tools treat decks as documents — once you finish, the work is done. SlideChum treats them as talks — and a talk has a runtime. It runs end-to-end: from the source you started with, to the room you presented in, to the people who came back to it on Monday.
Intake — where the talk starts.
A talk doesn't start at slide one. It starts at the README, the blog post, the design doc, the postmortem. SlideChum's intake takes a URL or a markdown blob and outputs a draft you can edit in 15 seconds.
Build — where the talk takes shape.
Markdown is the source of truth. The AI sidebar refines a slide, the polish agent runs the whole deck once, and your code blocks look like your IDE because they're syntax-highlighted with the same engine.
Deliver — where the talk happens.
The same URL you edit on is the URL you present from. B/W blank keys work the way they do in Keynote. Speaker notes, audience Q&A, share link — all in the browser, all without losing your place.
Feedback — where the next talk gets better.
Every share link records anonymous per-slide dwell. You see, on Monday morning, exactly where Friday's pitch lost the room. Then you fork it, edit slide 7, ship the next version.