Issue #17 July 5, 2026

AI Infrastructure Economics, Wealth Management's Move From Tools to Workflows — a Car Cost Calculator to Share, and a Stakeholder Change-Management Playbook

Editor's Take

Two AI-news pieces this week — the supply-and-demand economics of AI compute, where a power-gated supply meets compounding demand, and how wealth management is moving from AI tools to AI workflows. Plus a car cost-of-ownership calculator worth sharing, and an Org playbook for the problem a lot of us keep hitting: the same AI fact has to be framed differently for every stakeholder to actually land.

🚗 A Tool to Share: an AI-Built Car Cost-of-Ownership Calculator

A quick aside from the AI-and-workflows theme. Most car cost calculators miss two things. First, they ignore the time value of money on a car loan — the interest you pay, and the opportunity cost of the cash you tie up, materially change which car is actually cheaper. Second, a lot of people still run the old rule of thumb that a two-year-old car beats a brand-new one. Since COVID, the supply/demand shift in used-car pricing has repeatedly broken that rule: in two of my own recent car purchases, a new car actually penciled out cheaper than a two-year-old CPO once financing and total cost of ownership were modeled properly.

So I built a calculator that factors those in. Sharing it in case it helps your own decision-making:

Open the Car Cost Calculator →

Disclaimer: This calculator is provided for informational and educational purposes only, not financial advice. Figures are estimates and may contain errors — verify every number and assumption independently and at your own responsibility before making any purchase decision.

This Week's Briefing

Framing AI for Every Stakeholder: A Change-Management Playbook

The same fact, framed for each audience — a playbook to help navigate AI change management.

Heads-up: A short TL;DR, then the interactive playbook embedded below — a stakeholder lens map plus 24 talking-point tables: how to frame AI when presenting to each stakeholder (T01–T12), and ready-to-deliver messages from each leader (F01–F12), decomposed line by line.

TL;DR

A recent run of conversations kept landing on the same realization: AI has many stakeholders, and each one hears "AI" through a completely different lens. The CEO hears competitive strategy and board accountability; the CFO hears capital allocation and ROI; the CISO hears data leakage and agent risk; the middle manager hears a threat to their team's value; the frontline employee hears a replacement notice. A single enterprise AI message will fail most of them.

So to get an AI idea across, you frame the same fact differently for different stakeholders — each framing truthful and aligned to the strategy, but calibrated to that audience's specific fears, motivations, and proof requirements. The governing rule: the framings differ; the facts underneath them must be identical. Get caught with a gap between what you told one group and another, and every narrative loses credibility at once.

The playbook below is built to be used. Navigate the stakeholder lens map, then open the specific table for whoever you're about to present to (T01–T12) or the ready-to-deliver message for whoever's doing the talking (F01–F12). It's grounded in verified evidence — workflow redesign as the #1 driver of AI EBIT impact, the shadow-AI breach premium, the 54% who'll use unauthorized tools anyway, and the Klarna/CBA cautionary cases on leading with headcount.

Interactive Playbook

The playbook below — Framing AI for Every Stakeholder — opens with the central thesis and the twelve-audience lens map, then the CFO scorecard, the champion-network rules, the 2026 regulatory floor, and the cautionary line on substitution-first framing. Underneath are the two full sets of talking-point tables. Open it in a new tab if it loads slowly.

Run one strategy with many messengers. Name the financial metric before the pilot, on both value tracks. Brief managers before their teams. Make the governed platform better than the shadow alternative rather than banning it. Publish what AI will not be used for, and honor it. And never lead with headcount — the framings differ by audience, but the facts underneath them are identical, and the moment a stakeholder catches a gap, every narrative loses credibility at once.

Get the newsletter in your inbox

A weekly, curated digest on AI and organizational design.