Eight figures a year on a database nobody could query well.
One anonymized example, because it is the common case rather than the exception.
We have seen a funded company spending eight figures a year on a database it could not query well.
That sentence is the case against assuming storage is the hard part. Spend on storage and compute does not buy answers. The gap sits between the data and the person with the question, and closing it is the list above: queries planned correctly, figures checked before they return, access decided per user, and a record of all of it.
Scale is not the excuse it used to be either. In one enterprise grocery deployment, Ward queries 5 TB and 5 billion records on a 16 GB server, because the work happens in an engine built for it, Parquet storage on a custom fork of Apache DataFusion with its own index format, rather than in the model.