Time back. Not ROI theatre.

The SERP is full of savings theatre. Invented hours. Invented ROI. Invented accuracy bands dressed as proof. We will not publish that.

The commercial want is simpler: time back in the Betrieb. Not a landing-page number. Not a case study we fabricated. Time the Inhaber still spends redeciding, coordinating, and assembling work the systems already know.

This Saturday closes the week on that line. Agents on Spectacle take Schlepperei. A person releases what matters. We do not invent the proof.

Time vs invented ROI

Time back is the want. ROI theatre is the shortcut.

Adjacent search invents weekly hours saved, euro deltas, and accuracy percentages so the pitch sounds finished. Useful category noise for other products. Wrong ending for this one.

If the Inhaber still owns the morning re-rank — Dienstplan that did not move, Wareneinsatz already in the Warenwirtschaft, a late BWA that cannot change the week — the product conversation is about that work. Not about a made-up return curve.

We withhold rather than guess. Arithmetic stays in code. The model only writes language. A number we did not measure does not become a claim.

What we refuse to publish

We will not publish invented hours saved, invented ROI, invented euros, or invented accuracy bands. We will not dress a scaffold as live. We will not write the Kasse. Tax, Buchführung, and Jahresabschluss stay with the people who own them. Silent auto-rostering is not the job. Illness prediction is not the job.

This is not a dashboard. Not a website. Not a chatbot. Not restaurant software. Not “AI for hospitality.” Not a gastro SKU.

If a demo needs a fake number to close, we do not run that demo.

Agents and Freigabe

Spectacle is the layer over the Betrieb you already run: ontology as objects and relationships; forecast and simulation in code; agents that take Schlepperei; actions with Freigabe.

Agents assemble what ERP, Warenwirtschaft, and Zeitwirtschaft already hold into a named measure. A person releases it. Logged. Reversible where the source system allows. You keep the switch.

Co-CFO, Co-HR, and Co-CEO are lenses on that stack — not separate SKUs. The useful output on a live day is often small: one ranked move for the hours left. Call in. Send home. Hold.

This week’s series

Same-series cuts already live: the material cut (Wareneinsatz is a decision); the category (one core, every kind of business); the release gate (Freigabe holds the switch); the stack law (above the systems, not instead); the fit test (the three-part pattern); the offer (agents take the work). Arithmetic stays in code. This Saturday closes the week against ROI theatre.

Six public bands sit as equals. Venue operations last on purpose:

• Manufacturing and production
• Warehousing, logistics and distribution
• Technical service and maintenance
• Health and care
• Retail and multi-site
• Venue operations

A named account is not a category. Gastgewerbe is one band among six, never the product story. Time back is the want in every band — not a finished ROI slide.

If the Inhaber still owns that morning work, twenty minutes is enough to see whether agents on Spectacle have a job. That is the Erstanalyse — start at Spectacle. We will not invent ROI to close it. If the data cannot answer the question, we say so.

FAQ

Do you publish hours saved, ROI, or accuracy bands? No. Time back is the want. We do not invent hours, ROI, euros, or accuracy bands so the pitch sounds finished.

What is the commercial want if not ROI? Time the Inhaber still spends redeciding, coordinating, and assembling work the systems already know. Not a landing-page number. Not a fabricated case study.

Why withhold a number instead of guessing? A number we did not measure does not become a claim. Arithmetic stays in code. The model only writes language.

What do agents do, and who keeps the switch? Agents assemble ERP, Warenwirtschaft, and Zeitwirtschaft into a named measure. A person releases it. Logged. Reversible. You keep the switch.

Is this a dashboard, chatbot, or restaurant software? No. Not a dashboard, website, chatbot, restaurant software, “AI for hospitality,” or a gastro SKU. Six equal bands. Venue operations last.

Where should I start? Spectacle — Erstanalyse. We will not invent ROI to close it. The Insights series is how we write about the operation.