@vsn-mostafa I’ve worked on Laravel projects of all sizes—from start-ups to Fortune 500s—for over 10 years. The projects that always fall apart are the ones where some team or developer has decided the project is a special snowflake that needs its own, unique directory structure.
My advice is to stick closely to the framework’s defaults. I’ll then create an app/Services directory containing classes for encapsulating business logic and interacting with third-party services (for example, I work a lot with Mux, so I’ll have an App\Services\Mux namespace with Mux-related classes inside that directory).