Serve Data When It Matters (Concierge Alerts)

A concierge doesn't hand you a binder of everything the hotel offers and wish you luck. They notice it's raining and have an umbrella waiting by the door. The value isn't the inventory. It's the timing — the right thing, at the moment it matters, without you having to ask.

Most data teams build the binder. A hundred dashboards, always available, waiting for someone to come looking. The opposite of a binder is a concierge: a system that doesn't make people fetch data, but serves it to them exactly when it changes what they'd do.

The binder is always open and rarely read

An always-on dashboard asks the reader to do the work: remember it exists, open it, scan it, notice the one number that moved, and connect that to a decision. Every step is a chance to not bother. So the dashboard sits open in a tab nobody looks at, technically available and functionally invisible.

Availability is not service. A number that's there if you go get it is doing none of the work of getting itself in front of the person who needs it. The binder optimizes for coverage. A concierge optimizes for the moment.

Serving data when it matters

A data concierge flips the model. Instead of a place people visit, it's a system that watches the numbers that carry decisions and reaches out when one of them does something worth acting on.

The unit isn't a chart. It's a served moment, and a good one carries three things: what changed, why it changed, and what to do about it. Not "NRR is 107.4%" on a tile, but "NRR just crossed below your 108% line — here's the cohort driving it, and here's the play you ran last time it happened." That's the difference between a data service you have to operate and data that serves you.

The mechanics of a good alert

The hard part isn't sending messages. It's sending the right ones, because an alert system that cries wolf becomes another binder — noise you learn to ignore.

So every served moment earns its interruption. It's tied to a real threshold, not a wiggle. It goes to the one person whose decision it feeds, in the channel they already live in. And it arrives with enough context to act, not just enough to worry. Get that discipline right and people stop tuning you out, because every time you reach out, it was worth it.

This is the operational other half of pushing instead of providing: the mindset says deliver the number before it's asked for; the concierge is the system that actually does it.

Build one served moment

Don't build an alert platform. Build one concierge moment and earn the right to build the next.

Pick a single number that carries a real decision, define the line it shouldn't cross, and wire it to reach its owner — with the why and the what now attached — the instant it crosses. The first time someone acts on it before they'd have noticed on their own, you've stopped running a data service and started running a concierge.