Why I built Cadence Prompt

Draft in Brad's voice, built from the founder survey. To rewrite in his own words before it goes live.

I have worked in live events for eighteen years. I started by cleaning the office of a neighbor who ran a teleprompter company, and I ended up running prompters, graphics and media servers on shows of every size. Today I run prompter full time.

The software I used most was a great tool once. Over the years I learned its bugs by heart. I built shortcuts around them with a Stream Deck and a pile of macros. Then I caught myself building tools to make a broken tool work, and I decided to build the right tool instead.

The first thing I fixed was coloring text. It took five clicks for every cue. Now it takes one. That is how Cadence Prompt started: one small, annoying thing, fixed for real.

What I believe

A prompter should help three people at once: the operator at the desk, the presenter on stage, and the crew who need to know what is coming. It should keep up with last-minute changes, tell the crew how much longer, and get out of the presenter's way. If it does its job, nobody notices it.

I am not trying to be the loudest tool in the room. I want to be the one that is there, every show, doing what I said it would.

What I will do for you

Tell me what is working and what needs fixing. I will fix it.