Why I built LoopBoard
A TV on the wall showing a poster from last spring. That was the problem. LoopBoard makes updating venue screens take seconds.
Working with hospitality clients, pubs, breweries and bars, I kept noticing the same thing on the wall. A decent TV, in a good spot, running a static poster that was three months out of date.
It was never laziness. It was friction. Updating the screen meant someone opening a design file, exporting a new image, getting it onto a USB stick or into whatever app the screen ran, and remembering to do it again next week. On a busy Friday that never wins against pouring pints.
Make the update take seconds
LoopBoard turns that screen into a proper content system. Venues manage screens, slides and events from one dashboard and push an update in seconds, from behind the bar if they want to. There is AI in there to help generate the adverts themselves, so a new guest ale or a quiz night does not need a designer before it can go up.
Dark mode first, on purpose
One design decision I get asked about: LoopBoard is dark by default. That is not a style preference. It is how these screens are actually viewed, in low light, from across a room, often at an angle. A bright white slide in a dim bar is unpleasant to look at and hard to read. Building for the real viewing conditions rather than the design mockup made a bigger difference than any feature.
The wider point
The tool is only worth anything if it changes behaviour. A screen that is easy to update gets updated, and a screen that gets updated actually sells things. That is the whole product thesis, and it is the same one behind everything else I build.