A few days ago I thought this week’s briefing would be a pricing story.GLM-5.2 had dropped, coding was getting cheaper if you wanted it to, and the obvious enterprise question seemed to be: why keep sending every job to the most expensive frontier model if a good open model can do a growing slice of the work?And then Anthropic dropped Claude Tag, and it complicated the whole cheap-intelligence story. Anthropic was not getting cheaper, and its customers were bracing for higher bills and paying them anyway. Back in May, The Information had reported as much: enterprise buyers expected to pay more for Claude, not because Claude was useless, but because Claude was useful enough, and increasingly woven into the work enough, that they did not want to turn it off.And I got stuck on the contradiction. How can intelligence be getting cheaper and more expensive at the same time?The lazy version of the answer is that frontier labs still have market power. Claude is good. Companies want the best tools. Engineers and analysts are expensive. If a $250,000 employee becomes meaningfully more productive, a company will tolerate a surprisingly ugly AI bill for a while.What it doesn’t explain is why the pricing power might survive as open models get better. It also doesn’t explain why Claude Tag feels more strategically important to me than another model launch.The more I sat with it, the less this looked like a token pricing story. It looked like a story about where intelligence is allowed to work.Cheaper intelligence only helps you if you can put it to work. If you can’t, the discount stays on paper, and the expensive tool stays the one your team keeps reaching for. So the real question is whether you can actually capture that discount, or keep paying the premium because nothing else fits the work yet.This briefing covers:Why the cheap option is real now. GLM-5.2 means a growing slice of work no longer needs frontier prices, with a security tradeoff attached to running it yourself.What you are actually paying for. Most companies can buy the model cheaply and still can’t use it, because the context and permissions around it are the part they haven’t built.The Claude Tag move. How a Slack integration becomes context that gets harder to leave the longer your team uses it.Why the obvious fix is hard. Owning your own context is the right answer on paper and a brutal hiring problem in practice.The seven questions to settle now. Settle them, or have them answered for you.