The system
Signage software is easy to demonstrate and hard to keep alive. What follows is what the system does, described the way it will behave six months in — when the person who set it up has moved on and somebody else needs to change a slide before lunch.
On this page
01
A media library for images, video and web content, with reusable layouts so a screen can carry more than one thing at once — a main area, a sidebar, a ticker — and still look like somebody designed it rather than assembled it.
Templates matter more than they sound. If a branch manager has to build a layout from scratch to post a notice, they will not post the notice. If they fill in two fields in something you have already designed, they will.
02
Playlists with time-of-day and date-range rules, applied to a single screen or to a group. Breakfast until half past eleven, lunch until three, the evening menu after that — set up once, then correct every day without anyone thinking about it.
The same mechanism handles the things that are easy to forget: the promotion that must stop on the day it expires, the notice that should only appear during an event, the announcement that has to interrupt whatever is playing.
03
Full-screen playback on standard signage hardware, with content cached on the device so a network interruption does not empty the screen. A screen that goes blank in a reception area is noticed by everyone who walks past, which is why this is the part we are least willing to be clever about.
We do not sell hardware and take no margin on it. We will advise on what to buy for the environment you have, and work alongside whichever installer you already use.
04
Two screens is a project. Forty is an operation. Every screen appears in one dashboard — which are online, what each is currently showing, grouped by site or department — with remote actions instead of a walk around the building.
Grouping is the part that pays for itself. Publish once to "all reception screens" or "the Rotterdam branch" rather than twenty-two times, and add a new screen to a group rather than rebuilding its schedule.
Where it runs
Both are normal. The choice is usually made by your IT policy rather than by us, and neither changes what the system does.
HOSTED BY US
We host it in the EU, your screens connect out to it, and you run no infrastructure. The straightforward option for most organisations, and the fastest to get live.
HOSTED BY YOU
The system runs on your own servers, inside your own network, under your own security controls. The right answer when policy says content and user data must not leave the building — and the reason we are asked into some conversations at all.
Security and data
Keep reading
→ Next step
Tell us what the screens have to say and who should be keeping them current. If the honest answer is that you do not need us, we will say that too.