There is a category of restaurant technology platform whose entire product is the pipe.
They connect to your POS, your labor platform, your inventory tool, your review aggregator, your weather service, and sixty-five more data sources. They normalise the data. They visualise it. They put it all on one screen with automated reports and a demand forecast and a benchmark comparison and, when something looks unusual, they send you a notification that encourages you to act.
The encouragement is the product. The screen is the product. The pipe that fills the screen is the product.
The action is still yours.
The Integration Count Is the Tell
When a platform leads with the number of integrations it supports, pay attention to what that number is communicating.
Seventy integrations means: seventy API connections to platforms you are already paying for, each pulling data on its own refresh schedule, each with its own data model that has to be normalised before it can sit next to the data from the other sixty-nine. The integrations are not features. They are dependencies. Each one is a point of latency. Each one is a potential failure mode. Each one adds to the interval between when something happens in your restaurant and when you see it on the screen.
The integration count is not proof of capability. It is proof of connectivity. Those are different things.
The Logbook Is the Confession
Every data platform eventually faces the same problem: the data has context that the data cannot capture. Why were Tuesday sales low? Why did labour variance spike on Saturday? Why did the benchmark score drop this quarter?
Tenzo solved this problem with a logbook. The logbook is a text field attached to your data. When you notice an anomaly, you open the logbook and write a note. The note explains the anomaly. Future readers of the dashboard can then understand why that week looked the way it did.
Read that again.
The premium analytics platform — the one with seventy integrations, machine learning demand forecasting, and weather data — solved the context problem with a text box. The text box is called a logbook. Notion is a free text box. You are paying enterprise analytics pricing for a Notion doc embedded in a dashboard.
But the deeper issue is not the format. It is the direction. The logbook is retrospective. It documents what happened. It explains why last Tuesday went wrong. It was written on Wednesday, after the damage was already done, so that the next human who looks at the dashboard can understand the data.
The logbook is not an operational tool. It is a historical archive. The context it captures is the context of outcomes that already occurred. No logbook entry has ever prevented anything. Every logbook entry documents something that was not prevented.
The Weather Integration, Plainly
Tenzo integrates with weather data so operators can understand why their sales look the way they do. When it rains, fewer people come in. When it is sunny, more people come in for outdoor seating. The weather is a real operational variable.
The weather on any given Tuesday is available by looking out the window. It is available on every weather app for free. It was available before service started. It did not require an API integration or an enterprise analytics subscription to access.
Tenzo put the weather next to your Tuesday sales number so you could confirm, in one view, that the rain you saw on Tuesday caused the sales decline you saw on Tuesday. That contextualisation is real. The insight it produces — it rained, therefore sales were lower — is not a discovery. It is a confirmation of what any observer already knew.
The Act Feature
Aggregate, Analyse, Act. Three pillars. Tenzo describes the third one honestly, if you read it carefully: Tenzo allows you to make use of the data you collect by actually encouraging action based on your insights.
Encouraging. The platform encourages. The encouragement arrives as a notification. The notification tells you something needs attention. You open another platform — the one Tenzo just aggregated the data from — and you take the action there.
Tenzo is not in the action. Tenzo is in the notification. The notification precedes the action. The action happens elsewhere. The act pillar of their product is a push notification pointed at a human who will go do the thing in a different tool.
Act is not the right word for this. Notify is the right word. They chose Act because Act sounds operational. Notify sounds like what it is.
Seventy Integrations Later
The operators who use Tenzo have better data visibility than the operators who do not. That is true and worth saying plainly. A restaurant operator who can see all their operational data in one place, benchmarked against peers, with automated reports and a demand forecast — that operator is better informed than one who cannot.
Better informed is not the same as better operational. Better informed means the Monday morning meeting is more productive. Better informed means the quarterly review has better data. Better informed means the logbook has more entries.
The Friday night is unchanged. The human who was at capacity before the seventieth integration is still at capacity after it. The notification about labour variance still fires to a pocket on a floor where someone is already executing. The action still requires the human. The human is still the bottleneck.
Seventy integrations. One screen. One notification. One human who has to act.
The pipeline is excellent. The pipeline goes nowhere without the human at the end of it. That human is the product gap no integration solves.