Earlier quoted context omitted.
Plenty of companies don't "need to exist". A company exists because someone decided to start it (usually to make some money) and lasts until someone decides to end it (usually when it stops making money). If you're asking why Palantir (and Salesforce, Jira, etc) continue to make money despite not having any novel or complex technologies, my experience has been that these are not prerequisites for solving the vast maj…
This discounts the value of user experience, which people will pay a premium for. A good design is valuable, and this applies to business processes as well. How would you design the user experience of constructing a submarine? Good design IS technological superiority.
But I'm unsure why you feel that my response pointing out that a product's user interface is typically a more important factor in success than the product's underlying technologies was discounting the value of user experience?
> Good design IS technological superiority.
Hmm, I was attempting to respond to someone who wrote "It feels like a big pile of nothing... Big fat database schemas with big fat CRUD atop and layers of snazzy sparklines" which seemed to dramatically undervalue good schemas, CRUD implementations, or sparklines as "nothing". So to contrast those I used "technical superiority" as a catchall for the sort of challenging technical implementations that some developers lionize. Does that make sense? Is there a different term you'd suggest for that? For now I've changed to "(non-UX) technological superiority".