About Present on Time
We build the run-of-show, timing, and screen-control layer event teams reach for when a spreadsheet and a phone timer stop being enough.
Why we built this
Every live event runs on the same fragile setup: a shared spreadsheet, a stage manager's phone timer, and a lot of shouted updates when something runs long. It works, right up until a session overruns, a screen shows the wrong thing, or the one person holding the schedule in their head steps away.
Present on Time exists to replace that fragility with one authoritative clock, one agenda, and one console — so the whole crew is working from the same information, not their own private copy of it. Nothing about running a live show gets simpler just because more people are involved; the goal here is that it doesn't get more fragile either.
What we believe
The clock should never lie. Every countdown is driven by the server, not a browser tab — a refresh or a dropped connection can never desync what a presenter or a screen shows.
Access should match the job. A volunteer running a confidence monitor shouldn't need — or get — access to reorder the agenda. Role-based permissions exist so the right person has exactly the access they need.
Bad Wi-Fi is not an excuse to fail. Venues have unreliable internet. The platform is built to degrade gracefully — polling fallbacks and a low-bandwidth mode keep the show running when the connection doesn't.
Every change should be accountable. Team changes, ownership transfers, and urgent broadcasts are logged, so a crew always knows who changed what and when — not left guessing after the fact.
Where we are today
Present on Time is in launch: every package is free, we're actively building based on real event teams' feedback, and pricing will only be introduced later with plenty of advance notice to anyone already using the platform.
If you're running events and something here would make your show easier to run, we want to hear about it — feature requests from people who actually run live events shape this product a lot more than a roadmap decided in isolation ever could.