Yeah, that’s basically the enterprise default pattern. Everyone adds requirements from their own risk perspective, and individually they all make sense, but together they completely change the purpose of the MVP. We had a similar situation where marketing wanted analytics, legal wanted logging, and ops wanted extra admin controls, and suddenly the “small test version” looked like a production system. What helped us a bit was introducing a strict rule that anything not tied directly to validating the core assumption gets explicitly pushed out of scope, even if it feels important. It’s uncomfortable at first, but otherwise the MVP silently grows until it’s no longer an MVP at all.