Ongoing maintenance-as-a-service for MVPs

I think the old software development dynamics are still in play. They don't decide what gets made (very easy to make MVPs now), but they still do decide what keeps improving and has support long term. Anyone can make an MVP for a product idea, but the old dynamics around stable software that is supported long term will win. After the MVP stage, you can't be vibecoding everything. The QA still needs to happen; the design and planning still need to be there. They are even more so important since the devs can push 10x more code. For example, a big company can see some AI browsers getting traction and they launch their own. But the MVP is not the hard part. They have to now maintain that product on top of their main IP. Can they justify doing that? Can they keep putting in efforts over the long time? Do they care enough? A company whose main IP is an AI broswer, will care and will keep on improving it (for survival). I don't think another company for which the AI browser is a side project will do the same.