There is a difference between "a use case for $data_platform" and "a data use case for $data_platform". Scope on the first one is the platform in $data_platform" and second is the data specifics requirements in $data_platform.
Working on a non-Fortune100 insurance company in Europe, almost all our use cases can be easily done on traditional RDBMS like SQL Server, or on BI tools like SAS. Thankfully with higher granularity over time, Excel usage is fading out constantly. No big data, no heavy computing necessary - at least from my point of view.
All setups in place today, can be called self-service platforms. With cautious estimations we have at least 100 of such "platforms" running since years, or even decades.
This situation implies direct, we have a use case for a $data_platform itself. Costs are the biggest driver here, mainly due to the hidden costs of keeping these 100 systems up and running. Governance and management of the data, locked-in in all these stores, processed by slow and ugly SQLs nobody understands anymore, and with an unknown state of data quality, is key today.