The hard screens, one system.

For revenue, finance and BI teams

Revenue against plan, the pipeline behind it and an analyst on call.

For supply-chain, fleet and field-operations teams

Open exceptions, the network map and the shipment behind every late promise.

For account, success and CRM products

One account before the call: health, usage, people and next actions.

For support, service and helpdesk products

A ticket queue, the conversation and a reply drafted from past tickets.

For reliability, observability and platform teams

One live incident: error rate, blast radius and a runbook that runs.

For utilities, industrial energy managers and grid operators

Eight sites on the grid: who buys above contract, the alarms and an analyst over the meters.

For security operations teams, incident responders and detection engineers

The alert queue, the assets it fires from and an analyst waiting for the go to contain.

For pricing, trading and treasury products

A market tape, a watchlist and an order ticket with a review step.

How is the quarter going, and what decides it?

A revenue desk in one block: a MetricGrid of four headline numbers that each name their baseline and carry a 13-week Sparkline, a ComposedChart of weekly revenue with its trailing average against a labelled plan rule, a donut PieChart of the service-line mix, a BumpChart of which line is climbing, and the accounts that decide the quarter with a Meter each. Container-query layout, so it holds in a dashboard column and on a full page.

Where does the volume flow, and which lane is late?

A network on the map it runs on: MapCanvas in globe projection with one MapArc per lane, its width bound to volume through a paint expression, hubs as MapMarkers with tooltips, and a panel that ranks the lanes with a Meter and calls out the late ones. Selecting a lane on the map or in the list dims the rest and redraws that arc heavier.

Where do they drop off?

"Where do they drop off?" — a SankeyChart from the channel a request came in on, through what happened to its quote, to how it ended, with a FunnelChart beside it that counts each step. The headline names the channel that loses the largest share of its own requests.

What did the agent do, and what is it asking me?

One agent run, reviewable end to end: a Plan with its decision contract, an AgentTimeline whose last step follows your answer, a Tool call with arguments and result one click away, a ToolResultCard hosting the chart the run produced, TokenUsage in the header and an ApprovalCard for the one side effect that waits for a human. Reports the decision through onDecision and never performs it.

Where is everyone, and who is late?

A fleet where it is: each vehicle's planned route as a dashed MapRoute, the part already driven solid, the vehicle's MapMarker at the join and the depot marked; the list shows stops done on a Meter and minutes against plan, and selecting a vehicle fades the others.

Where is the market, and what moved it?

A rate desk: a tape of lanes across the top with price, move and a 20-day Sparkline each, over a CandlestickChart of the index and a BarChart of daily volume. Every move carries an arrow and a sign as well as a colour; the chart title is computed from the first open and the last close.