Clean architecture is not about making code look academic. It is about keeping business rules, interfaces, and infrastructure separate enough that teams can change one area without breaking another.
For growing products, this reduces regression risk, makes onboarding easier, and keeps new features from becoming slower every month.
The business benefit is direct: fewer rewrites, clearer ownership, faster debugging, and a product that can evolve without expensive rebuilds.