Clean architecture vs pragmatic architecture: where's the line?

My current team is quite strict about following clean architecture principles. While I appreciate the separation of concerns and testability, it feels like even a simple CRUD operation requires 6-7 files, which can feel like a lot of boilerplate for relatively straightforward business logic. My previous team used a more pragmatic approach, often just controllers and services, and we seemed to ship features faster. Where do you draw the line between architectural purity and pragmatic development velocity? When is clean architecture genuinely beneficial, and when might it be overkill? I'm trying to understand if there's a middle ground or if it largely depends on the project's scale and team's maturity.