Some things are sure. But not most. You wouldn't expect to go to McDonald's and they tell you (or even know) how much the fertilizer to grow the corn that feed the pigs that made the bacon contributed to the price you pay for a burger
That's exactly what's happening to you when you're the prospective buyer in one of those calls.
I'm not in sales, but I've had a job once where I could see all the financials. And we would very often be charging one customer 10x what we charged another for exactly the same tier of service. Sometimes the huge corps would be paying more for a lower service tier than a small corp on a higher tier.
But McDonalds absolutely can tell you an objective measure of what they charge you based on what you're getting. They charge you x per burger and y per fries and ...
The examples contained CPU and ram but that's not what they say everything should be - just some objective measure.
Snowflake charge by time, storage and size of machine - though they never tell you what the machine actually is underneath. I don't know what their "large" is.
Maybe it's by concurrent users, maybe amount of hours of support, maybe API calls.
I think the key thing was "we'd charge you X because you'd use Y" rather than "we'd charge you X because you look like you might pay it"
If McDonald's insisted on having a long sales phone call to sell me a burger, then yeah, I'd expect them to be able to provide me that information.