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

our current team follows clean architecture pretty strictly. for even a simple CRUD feature, we end up with controllers, use cases, interactors, entities, and repositories, which can easily translate to 5-6 files just to add a new field to a resource. i understand the benefits of separating concerns and testability, but it feels like it slows down development significantly. my previous team used a more pragmatic approach: simple controllers, service classes, and data access objects, and we shipped features much faster. i'm trying to find the right balance between architectural purity and shipping speed. where do you draw the line? for a typical mid-sized application with moderate complexity, when does clean architecture become an overhead rather than an enabler, and when is it truly indispensable?