Laravel is great for when you know you're gonna onboard/offboard a bunch of developers over months/years, and you want them to feel right at home as fast as possible.
For more long-term business, I'd always recommend go "chosen libraries put together well" over "framework everyone knows", as the developer churn will be lower, and having more control over your design and architecture tends to be more important (and applicable) when people stick around for longer.
For more long-term business, I'd always recommend go "chosen libraries put together well" over "framework everyone knows", as the developer churn will be lower, and having more control over your design and architecture tends to be more important (and applicable) when people stick around for longer.