Same with replacing parts vs customizing them on equivalent "standard" laptops. I've had to replace the keyboard on my laptops due to failure/damage once in the last 10 years, each time it took less than 15 minutes. Would it be nice if it was 3 minutes? Sure, but how much is 12 minutes really worth paying for and what do I lose for it in terms of the sturdiness problems with Framework.
Barring the decision to go with something like the 395 where standard RAM wouldn't make sense for it anyways (which is why Framework didn't make the RAM modular in the desktop version) there is nothing special about Framework that lets you reuse RAM between upgrades giving Framework an advantage. Every other normal x86 laptop I've ever used has had swappable RAM I've taken advantage of without paying $1800 for even the entire laptop, let alone the upgrade board.
There is some subjective preference in it all of course, but it seems that is just for a lot fewer people than it might have seemed. I.e. I don't see average people buying $500 laptops ever going for this and it almost feels like it has already reached its peak interest in the tech crowd too.
I can't even begin to think about how a laptop screen upgrade would go. Who's manufacturing them? How do I get just one? How do I make sure I don't spend a month waiting for shipping and get a fake? How do I make sure the housing is going to fit right? How do I make sure the pin outs match?
... and etc etc. An official upgrade pathway eliminates all of that. Sure, it's not bringing you back to "average person", but Framework have been super clear that's not who they're after. They want people in my bracket. To be honest, as a cohort, we've proven we're willing to (over)pay for this kind of thing, too. It's why the PC Market still exists despite graphics cards being overpriced by about double.
For instance, if an agent only has to be concerned with one task, its context can be massively reduced. Further, the next agent can just be told the outcome, it also has reduced context load, because it doesn't need to do the inner workings, just know what the result is.
For instance, a security testing agent just needs to review code against a set of security rules, and then list the problems. The next agent then just gets a list of problems to fix, without needing a full history of working it out.