STRONG agree. Most devs, if they can see their costs, try. Even just putting it in a starship prompt goes a long way!
Observability supports effective, responsible, and accountable use, "cost controls" (as typically enterprise defined) supports bean counters. Ensuring Observability is recognized as a valid Control™ should be on every engineering executive's TODO list.
> the cache is the dominating cost reduction force
TY for the rich reply. As you're very aware of the cache issue, it might have been nice to have the word "cache" more prominent on your "Key Techniques" image (currently Lower Cost Models, Smart Routing, Spend Controls, Context Optimization; cache tuning buried at the end) or higher in the body sections.
It was mostly the image that prompted (ha) me to call out the marketing driven angle.