What needs you today,ranked by money.
Alerts and proposed decisions land in one place, ordered by the money at stake — and they come to you, so nobody has to go hunting.
A brief in the inbox is opened and questioned: marql ranks the store against its like-for-like peer group, shows which categories carry the revenue gap down to single products, and lists the actions in priority order.
Decision inbox · demo network
today · 07:10
- now
- 6
- chronic
- 3
- upside
- 2
Margin down 4.2 pp on dairy
5 locations · money summed · gross margin
Discount leakage above plan
Westside · average basket
Stock-out risk on 340 SKUs
North Park · stock-out share
Ana · due in 7 days
Labour cost drifting up
Harbour · labour cost %
Lunch combo outperforming
City Center · repeat rate
From a signal to a decision
Four steps, and none of them is a dashboard.
The point of the Inbox is that nobody has to go looking. The work arrives already sorted, and leaves with a name and a date on it.
Detectors read your data
Cloud connectors land data every few minutes, events become signals hourly, and the full scans and the decision cycle run daily. Honest intervals, not a claim of real time.
One problem becomes one row
A repeat of the same problem at the same location updates the row it already has instead of printing a new card, and when a whole family repeats across the network it collapses into a single line with the money summed.
Money and persistence decide the order
Rows are ranked by money at stake, severity and how long the problem has been running — with a separate lane for the chronic ones so a two-month state stops looking new every morning.
You take control of it
Assign an owner and a horizon of 3, 7 or 14 days and the row becomes a task with the metric captured before it. Decisions with a measurable target metric go on into the proof loop and end up in the Impact Ledger.
Not the alert you already get
Scored against this location, not a flat rule.
MonTueWedThuFriSatSun
Monday, below a flat threshold
Mondays are quiet here and always have been. The value sits inside this location's own normal, so nothing is raised — a flat rule would have woken someone up.
Thursday, above a flat threshold
A 6% dip, well inside any threshold, but outside what this location does on a Thursday and it is stable enough for that to mean something. A flat rule never sees it.
What makes it a shortlist
Everything here exists to make the list shorter.
An inbox nobody can finish is a feed, and a feed gets ignored. Collapsing, lanes and ranking are the product, not the decoration.
Now, chronic, upside
Unread critical items surface on their own; long-running problems move to a chronic lane; positives sit apart from problems instead of competing with them.
What is genuinely new stops being buried under what has been true for two months.
An owner and a date
Taking control assigns a person and a horizon, creates the task, and captures the metric before and after it.
Every decision has a name against it, and you can see what happened after.
It comes to you
Web and mobile push, Telegram with charts, email, a morning briefing, and one reminder if a critical row sits untouched for three days.
You find out without opening a dashboard.
one problem · five locations · one row
Margin down 4.2 pp on dairy
5 locations · gross margin
4 900 €
at stake, on one row
A twenty-location chain gets a short list instead of the same alert twenty times.
signal passport · how it was computed
Margin down 4.2 pp on dairy
Westside · 1 100 € at stake
- actual
- 26.4%
- expected here
- 30.6%
- gap
- −4.2 pp
what moved it
detector · margin_drift v2 · scored against this location's own normal for the weekday
data freshness · POS synced 6 min ago · accounting 4 h ago
A manager can argue with the finding instead of guessing whether to believe it.
Where the line is
What the Inbox does not do to your business.
An operator who has been sold automation before wants to know exactly how much control it takes. This is the honest answer.
- It proposes; it does not write to your POS. Prices, orders and stock stay in the systems that own them.
- Hands-off acceptance is off until you switch it on, and even then it is capped: a fixed list of decision types, a money ceiling, a daily limit and a kill switch.
- Detectors are switched on per organisation rather than all at once, so what a new network sees on day one is the core set, not the full catalogue.
- A row with no measurable target metric stays a task. It is tracked and assigned, but it does not enter the proof loop.
- The Decision Inbox is in beta and labelled as such inside the product.
Decision Inbox FAQ
The questions that come up in the first demo.
A threshold alert fires on a flat rule — the same number for a kiosk and a flagship. Here each location is scored against its own normal, which the section above draws. Rows are then ordered by money, collapsed to one per problem, and most carry a proposed action rather than only a notification. Your own threshold rules can still be added on top, and they arrive in the same place.
Cloud connectors bring data in every few minutes. Events turn into signals hourly. The full scans, the network patterns and the decision cycle run daily, and some pattern detection is weekly. We publish those intervals rather than calling it real time, because an operator who is told 'instant' and sees a four-hour-old number stops trusting everything else on the screen.
Because the design target is a list you can finish — the collapsing above is most of the answer. Chronic issues also move out of the way of what is new, and the cap limits rows rather than incidents, so one loud detector cannot take the whole list. Nothing is hidden: every participant keeps its own detail page, and muting or retuning a detector stays a human decision.
Roles decide it. An owner and a COO see the network; an analyst has read-only access; a store manager sees their own locations; a franchise partner sees theirs, read-only. Read-only roles see the state of a decision — who owns it, when it is due — without the controls to change it.
Yes. Signals are stored language-neutral and rendered per user in six languages, including Romanian and Bulgarian, so the same row reads correctly for a head office and a local manager.
It becomes a task with an owner and a due date, and the location's metric is captured as it stood at that moment. When the horizon closes, the metric is read again. Where the row was a measurable decision, the outcome goes through the proof loop into the Impact Ledger — and a task that was never completed is closed as inconclusive rather than credited.
Talk to us
Tell us about your business. We'll call you.
Tell us a bit about your business and your data sources. We'll tailor the walkthrough, then you pick a time that works for you.