Block the AI-cost workstream on complete per-individual measurement before any optimization - so each persons correct plan can be determined

July 24, 2026 at 8:30 PMoperationalmedium

Situation

In the 7/23 Steve Wallace 1:1 Steve reported several threads coming out of Mondays AI meeting: efficiency coaching for heavy users, model-switching guidance, and usage reporting to department heads. Peter cut across all of it and set a sequencing requirement - first get a dashboard that shows every individual in the company, including himself. His evidence was his own absence from it: he shows as zero on every cost dashboard despite Claude running 8 to 10 hours a day, with CIQ apparently paying around 200 dollars a month for him. He rejected the manager-level rollup as a starting point and rejected pushing justification down to department heads. All of the costs, not just some of them.

Reasoning

The question the instrumentation has to answer is how do we measure so we know what plan each person should be on - including the high-spend engineer. Peter is not starting from a conclusion about which plan is right; complete per-person measurement is what makes per-person plan assignment decidable at all. Every downstream action Steve described requires knowing who the heavy users actually are, and with Peter himself missing entirely the data is known-incomplete, so any optimization would target whoever happens to be visible - worse than doing nothing because it would look like management. He rejected delegating justification to department heads not because delegation is wrong but because a judgment call cannot be handed to managers working from the same broken data. Using himself as the proof case does double duty: it is the cleanest demonstration that the data is wrong, since he knows his own usage, and it pre-empts the objection that this is executives auditing engineers.

Additional Context

Corrected during review - the initial hypothesis narrowed the intent to migrating one engineer onto Peters plan. Steve reported AI spend at 60 to 80 thousand a month; Ryan reportedly burned 7 thousand using fast mode; all-you-can-eat and per-token plans coexist. Neither Peter nor Steve can get a clear read on the billing - Steve noted he cannot even get Claude to explain Anthropics billing. Steve confirmed complete cost visibility was already the first step out of the AI meeting, so this is partly Peter reinforcing an existing plan and partly him refusing the shortcuts layered on top of it.

Observed Evidence

Direct transcript. Peter used the phrase strong recommendation for a first step, repeated the completeness requirement twice, and supplied his own missing data as the demonstration.

Matching Patterns

60%
Lead by Example with New Tools(3 keyword matches (AI, tooling, cost), same category (operational), personally adopts the tool and puts himself in the measured population first)
30%
Protect Engineering Focus Through Process(same category (operational), refuses a process that would put engineers under partial-data scrutiny)

Confidence Breakdown

34/35
Evidence
22/30
Pattern
19/20
Source
6/15
Corroboration

Reasoning Depth Analysis

Org Signal:Measurement completeness precedes optimization, and the executive goes into the measured population first. This is not a cost crackdown - it is a refusal to act on partial data and to make engineers the visible half of an invisible whole.
Who Affected:Steve Wallace owns delivery; Moody and Michelle Novicio were named as doing the work; every department head who would have received the rollup and now will not be the entry point; Ryan Smith as a likely visible high-spend case; Greg Kurtzer, who is separately projecting a million-dollar AI bill by year end.
Precedent:Peter will block a workstream on data completeness rather than let it proceed on partial coverage. Expect this cited against future let-us-start-with-what-we-have proposals.
Consequences:Real sequencing constraint - the coaching and model-switching threads wait on the dashboard.
Timing:Now because Greg is escalating both hardware spend and the AI bill toward board-adjacent visibility, and Peter would be asked to defend engineerings number without being able to see it.

Source

reflection

AI Confidence

81%

Related Context

🎥
Steve <> Peter Weekly 1:1 - 7/23

fathom

If you can show me what each of my people is spending, yes. Let us start with that. Let us get a dashboard up that shows what individuals in the company are spending. And I know we have tried to do that before, but things like, I am not on it. And I know I am spending tokens. / So my strong recommendation for a first step would be get a dashboard that actually shows everybody. / All of the costs, not just some of them.

💬
#distinguished-leaders - 7/24

slack

Greg Kurtzer: Also, our AI bill might be a million dollars by end of year

Outcome

Still incomplete a month on - every single time I have asked for an understanding of spend, I have gotten a dashboard that shows some people and not others. Per-user notification being wired, comprehensive view still owed.

Rating: 3/5

Decision ID: 3af1550d-bada-417f-9c12-30ad9001b598