It reminds me of when Apple switched to their own silicon in the iPhones and we had year after year of hardware with 1.5-2.5x performance compared to the previous year. We very rapidly got to the point where the processor in my phone was more power than I would ever need (unless apps got more and more bloated and inefficient, which they obviously did).
Fun fact - Enterprises are just big groups of people.
If none of your people have ever used a tool because it's expensive, locked away in a some walled garden, and obscure then none of the enterprises will have demand for it. Management might force them to use some cheap model, but users will all be pushing for the models with mindshare, and Microsoft will lose marketshare as a consequence.
Apple knew this when they put Apple IIe's in schools. It's still paying dividends. Today, Anthropic and OpenAI know it and are actively hemorrhaging money trying to become synonymous with AI. Microsoft seems to think that this is all a race to the bottom. I think they're wrong.
There is a lot of choice...
one is not true, the other is not all that relevant considering disparity in pricing local vs API even subsidized.
Even if both were true, this is Microsoft. There's negative chance of them producing anything close to frontier anytime soon or at all. They've been absent altogether and relied on others; The little they did is not even in also ran category like grok is for example.
they will happily use a microsoft model that is slightly less capable at fraction of the cost.
FWIW it is worth noting that the GP's suggestion is more in line with Microsoft's own stated belief in the future of "unmetered AI".
At the moment, Microsoft is arguably meeting that claim with their support for and encouragement of Nvidia Nemotron Bolt, which is an actually pretty good, quite interesting, unusually-trained-and-sized-to-fit MoE model that was designed to go with the launch of the Nvidia/Microsoft RTX Spark machines.
(Good Sam Witteveen video about it: https://www.youtube.com/watch?v=WJpeW9lCSUM )
But it would be good to see Microsoft themselves distilling an open weights model.
Like any vendor with a profit motive they do have to decide the obvious, though: how do you make money from it, when right now it could cost several hundred million dollars to train (even if you adjust the training of a larger proprietary model so you can distill the smaller one from it)?
There is, essentially, no way to keep an open weights model from being copied/distilled/extracted, and IMO what that tends to suggest is that open weights models will essentially gravitate to sort of uncontroversial, "standard library" tasks.
So I think it also means that Microsoft's approach on open weights will ultimately be the same as Apple's: they will focus their efforts on LLMs that meaningfully add function to their OS and can be decapitated to make similarly useful decision models.
Put another way: given the geopolitical angle of the last few weeks, I think it is possible that the open weights coding models we have now may be among the best we will ever get, until the nearly inevitable GPU/tensor hardware glut arrives.
I think we are not far off this with Pi, Muse Glimmer, Qwen, Gemma etc., but sooner or later we will all have to work out how to put money behind it.
The main problem is that the open source movement has trouble even raising the money to properly pay linchpin individuals like Harlan Stenn (NTP).
Even Omarchy, which is uncomfortably effective at raising money for what amounts to a barely differentiated Linux distribution, is not raising LLM-training money; it’s barely even raising the kind of money it would take to post-train Qwen, I think.
We're in the 80s era in the OS analogy.
Gotta wait until there's a race to the bottom, prices drop and a bunch of these projects to build an AI model turn out to lose money. Then people will realize it's financially more sensible to pitch in and collaborate on one good model instead of building their own.
Not to nitpick, but Windows Phone also failed because Microsoft released the first generation of devices with Windows Phone 7, convinced a bunch of people to buy them, and then released a second generation of devices with updated Windows Phone 8, a version that the first generation couldn't upgrade to meaning that anyone who got in on the ground floor got locked out immediately.
When you go out of your way* to screw the people most interested in your new product it doesn't really engender large amounts of trust in what would have been your second wave of customers.
* Well, to be specific, WP8 was based off of the NT kernel and WP7 was based off of the WinCE kernel so it was probably 'the right choice' on some level, but making the entire first generation of a new product line EOL immediately rather than making an effort to ensure those people get... something... is still a dick move.
But Windows Phone history is a long list of things they should have done
The final build of WM10 was actually not awful... too bad it came 2 years after launch. :P
How do they compare with the fuzzily-priced only-our-agent cheap tokens you get on a Claude Pro or Max plan?
In this case there is huge demand from companies who consume API tokens at currently high prices who do not want to buy from the labs and who find that existing open source models are starting to lag the frontier too much, or are not actually that cost effective once accounting for the amount of tokens they consume.
The audience here is enterprise looking to save money, and there is no natural monopoly preventing this from gaining traction.