Qpoint Design

Pages

Landings — Beyond Today's Data

Source: qdash landings — c100 bake-off #8, 2026-09-30

Nine ideas the ruling opened up ("explore possibilities, even if outside current data abilities"). None is served today. Each is one sketch: the question it answers, the image, the data it would need, where it would live, and my keep-or-kill read. The point is to decide which are worth a backend ask, not to polish them.

Period

Scale

State

keep 4 · maybe 4 · kill 1

X1What kind of work is AI doing for each team?

Team · Home Engineering lens

NeedsWork-type classification per session — from tool and file activity, never promptsServesEngineering manager

killCan't be derived honestly without prompt mining (the c67 line).

X2Are we paying for seats nobody uses?

Team · Home Finance lens

NeedsSeat / license counts per provider and team (billing or IdP group)ServesFinOps / CFO

keepThe one number a CFO acts on this month.

X3Which data classes reach which destination?

Fleet loading dock · Inventory · Home Security

to →	Anthropic	OpenAI	Azure OpenAI	Google	Mistral	OpenRouter	Personal accounts
Source code	1.2B	349.4M	131.7M	91.9M	40.6M	6.5M	3.5M
Docs & tickets	374.9M	113.0M	42.6M	29.7M	13.1M	2.1M	1.2M
Customer data	85.2M	25.7M	9.7M	6.8M	3.0M	480k	586k
PII	51.1M	15.4M	5.8M	4.1M	1.8M	288k	410k
Secrets & keys	6.8M	2.1M	775k	540k	239k	38k	176k

NeedsDLP classification on outbound payloads, aggregated by destinationServesSecurity · Compliance

keepThe brand's first question — "where is my data going?" — in one grid.

X4Who approved this?

Inventory arrivals

Needs`asset_vetting` — a per-asset review state machineServesSecurity · IT

maybeFolds into the arrivals card once vetting exists; not its own view.

X5Where is spend heading this month?

Home Finance lens · Cost Center

NeedsDaily spend series + a budget / ceiling per team or orgServesFinOps / CFO

keepPeterson's "could we predict the month's spend?" — always labelled as a projection.

X6Is adoption spreading, or stuck in one team?

Team · Home Engineering lens

Platform89%

Payments96%

ML Research100%

Mobile89%

Data Eng81%

Web86%

Support28%

Security63%

NeedsActive-people-per-day series per team (sessions API is capped at 200)ServesEngineering manager

maybeStrong image; blocked on a per-day series.

X7Is the floor healthier than last month?

Fleet

30 days ago 90/109 seen

now 143/160 seen

NeedsInstall / coverage snapshots over timeServesIT · Security

maybeBetter as a time control on the Fleet floor than a separate view.

X8How fresh is our proof?

Home Compliance lens · Proof exhibit

NeedsEvidence collection timestamps per controlServesGRC / CISO

maybeWaits on the controls backend; the shelf reads instantly.

X9Is everyone on a current version?

Inventory · Home IT lens

NeedsInstall versions (already scanned) + a "current" per harnessServesIT admin

keepCheap: the install scan already has versions.

Read

My read

Four are worth a backend ask now: X3 (data class × provider — the brand's first question, "where is my data going?", as one grid), X5 (spend forecast — Peterson's CFO ask, and the Finance lens has nothing honest without it), X9 (version drift — cheap, already half in the install records), and X2 (seats vs active — the single number a CFO acts on).

Two are worth keeping as sketches: X6 (adoption curves) waits on per-day people series; X8 (evidence shelf) waits on the controls backend. Both are strong images once the data exists.

Kill X1 as drawn. Work-type mix sounds useful but can't be derived honestly without reading prompts — the line c67 drew. If it comes back, it comes back from tool and file activity, and as a per-team fingerprint, not a mix chart. X4 and X7 fold into others: the approval ribbon is the Inventory arrivals card with a state machine; before/after is a time control on the Fleet floor, not its own view.