Kill the drag work. Don't add another dashboard.

A second dashboard does not end the morning.

The morning ends when the hand-drag ends: the redecide, the stitch across systems that already hold the pieces, the list assembled by hand because no one owns the join. That work is not a missing tile. It is work the operator still pushes by hand.

We already wrote the sibling cut: a dashboard is not a decision. A chart without a next action is still reporting. This piece is the product cut after that sentence. The answer is not another cockpit. The answer is agents on Spectacle that take the drag work — above the stack you already run — so you get time back, not ROI theatre.

What the drag work is

Drag work is not "looking at numbers." Looking can be honest. Drag work is the labour after the look: re-opening three tools to rebuild what each already shows separately; chasing a figure that lives in ERP, inventory, and a chat thread at once; writing the same Dienstplan change into two places because the join never shipped; deciding again what last week already decided, because nothing carried the release forward.

The lists already exist. The pain is stitching them. The systems already know pieces. The pain is the hand that still joins them before anything reaches the floor.

That is why another dashboard fails as a product answer. A new screen can show the same separated pieces in prettier columns. It does not take the hand off the stitch. More metrics without a recommended action stay reporting — that is the cousin essay's lock. A second cockpit of tiles is the same job with a new login.

Agents take the hand-drag. You keep the switch.

On Spectacle, agents work on objects from the operation: named things and relationships the stack already holds. They assemble a next action from what exists — simulated where the model of the operation allows — and stop at your approval. Without approval the agent sleeps; proposal is not release. The layer sits above the systems, not instead of them. It is not a chat over a bad situation picture, and it is not a switch that writes itself into sealed sources — never write back into the sealed till.

Arithmetic stays in code. The model only writes language. Fluent language that re-asks you to look harder at the same tiles is still drag work dressed as intelligence.

Capacity is not invented either — capacity is already committed before demand clears; agents propose inside that bind. Time back is the want: fewer mornings spent pushing by hand what already lives in pieces. We do not invent hours, ROI, euros, or accuracy bands.

Six bands equal

Hand-drag is not a hospitality thesis. Every band that fits the pattern still pushes joins by hand: a production schedule against material and demand; a warehouse pick against Par-Level and inbound; a maintenance window against parts and labour; a care roster against capacity that will not move tonight; a multi-site retail order against what each branch already shows; a venue Dienstplan against covers that are not yet known.

Six public bands sit as equals. We name them so nobody reads "kill the drag work" as one trade's SKU:

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

Venue ops is last on purpose: equals, not a beachhead story. Pain that spikes when the same hand-drag is copied to a second site is a pattern question — pain at the second site — not a reason to collapse the homepage to one door sign. New sector = configuration on the same core. The fit is still the three-part pattern: demand uncertain, capacity fixed in the short run, labour and material committed before demand is known. Where that pattern holds, the morning often dies in the stitch — not in a missing chart.

What we are not selling

Not another dashboard. Not a second cockpit of tiles. Not a website. Not a chatbot over bad figures. Not restaurant software. Not "AI for hospitality." Not a beachhead SKU with five other bands as footnotes. Not more metrics sold as clarity. Not inventing hours, euros, ROI, or accuracy bands. Not silent write-back dressed as automation. Not replacing the systems you already run.

If your systems already join themselves, mornings are not spent redeciding and stitching, and the next action already reaches the floor without a hand-push, you may already have room. Spreadsheets, chat threads, and experience may be enough. That is not the buyer this essay is for.

FAQ

What does "kill the drag work, don't add another dashboard" mean?
Stop selling a second screen of tiles. Agents on Spectacle take the hand-drag — redeciding, stitching, assembling lists that already exist separately — with your approval.

Is this the same as "a dashboard is not a decision"?
No. That sibling locks chart ≠ decision. This piece locks product answer ≠ second cockpit. Same family; different cut.

Do you replace ERP?
No. The layer sits above the systems, not instead. Agents assemble work from what those systems know.

Do agents invent hours saved by ending the drag?
No. Time back is the want. We do not publish invented hours, ROI, euros, or accuracy bands. See time back, not ROI theatre.

Is this only for hospitality?
No. Six equal bands. Venue ops last. Hand-drag shows up wherever the three-part pattern holds.

Where should I start?
Spectacle. The Insights series is how we write about the operation.

CTA

If mornings still start by opening a second dashboard to finish what the first one left unfinished — that is the drag work. Request an initial analysis. Twenty minutes is enough to see whether agents that take the hand-drag — with approval, above your stack — are worth building. If the data cannot answer the question, we say so.