Potential customers for this fall into a few categories, including:
1. Parents who don't know a lot about tech, but whose kids need "a laptop" for school.
2. Kids & young adults who want a macbook to run something like GarageBand but have a very limited budget *and* also don't otherwise know much about tech.
3. Schools.
4. School-like programs, like software dev clubs & summer camps.
These customer types need a low price, but they also need A LOT of *support*. The support is the product here.
Yes, you could personally get a more powerful computer by getting a refurb 16GB M1 MacBook Air somewhere by bargain hunting. But you will need to hunt; right now on the official refurb store the cheapest MacBook Air is $929. If you're shopping on eBay, now you've got a machine with a ton of wear cycles on the SSD, and dubious amounts of damage.
If you, personally, have the time & energy for that, it *IS* a better choice.
So, back to the MacBook Neo and why it is interesting.
If you're reading this, you probably shouldn't buy it. But you should be aware that so many people *are* going to buy it, that it's going to set a consistent new minimum standard for software. For one thing, lots of apps are going to want to start targeting "fits into a MacBook Neo's memory envelope", which is to say, 8GB minus macOS overhead. Cheap hardware exists now, but not enough of it deployed consistently enough for app devs to care.
@glyph In both cases, something like these:
They were provisioned with DeployStudio (RIP), and later Munki with a ton of custom packages. Student logins were provisioned as needed. No Active Directory or anything.
@glyph It very depends. You need a lot of things in place to make this work. First and foremost, a faculty willing to give it a go. If the machines can't easily do what students and teachers need, that's the ballgame. Forget your principles for a second. If the damned things can't print or run the necessary apps, you're donezo with the experiment (and probably looking for a new job).
But if there is an appetite, then you want to lean into it as much as possible. I never got to go as far as Charlie Reisinger did, but that was always the goal.
But yeah everything must proceed first from curriculum. What the students need should drive tech decisions, not whatever flights of fancy the IT department might have. And that gets complicated, because you'll have some folks claim that proprietary applications are necessary for "preparation." And of course there are some testing regimes that require specific OSes to function. Chromebooks have obviated that somewhat, but it's still true to some degree.
But if all that comes together, I would first explore identity management, followed by provisioning by Ansible or Puppet, followed by Wireguard-enabled networking for always-available resources and support.

@glyph There's a potential future after the AI bubble pop that leads to some RETVRN action and a focus on fundamentals. It's by no means guaranteed.
I'm kind of thinking of my role as keeping the fires of knowledge lit while we endure an age in which people would rather not know how things work.
@theorangetheme @glyph It was very popular in my Catholic all boys prep school.
I tend to reach for "Foundation" for this metaphor, but I getcha.