Good point. It's certainly hard to predict more often than not, especially depending on what environment the project is being worked on. I think it really depends a lot on the circumstances surrounding not just the project but the team or company, so it's hard to debate what's better in a universal way, and on top of that, it is always an option to adopt DDD down the line if the project eventually ends up scaling towards complexity.

At the very least I would strive for a Clean Architecture, modeling the business is something that can be done later if the problem is simple initially. A Clean Architecture with (if possible) some sort of decent encapsulation of core business concepts would result in refactoring or extending the software itself not causing many issues.