Sounds like you’ve never had a prototype become foundational infrastructure before, or dealt with someone else’s.
you can always change it later. this is exactly the dogmatism i'm speaking about - you need to prioritise pushing things. the clean up can come later.
ironically it is your camp that advices to not use microservices but start with monolith. that's what i'm suggesting here.
I have many times and if you spend too long over architecting a prototype you start to get annoyed looks and tons of questions from PMs who just want something that looks right today (we can fix it/optimize it later)