this is exactly why we decided to adopt a "Palantir" model for sales
seeing more and more YC companies doing the same:
there is a massive shift right now toward wanting to build products in-house
but despite all the hype around replacing SaaS, there are still some blockers companies have:
they:
1) don't know where to start or what "it" should look like
2) don't know how they should go about building
3) lack the resources to build / maintain it
taking all that into account, we've decided to adopt a Palantir model for sales and will be testing: what if we still sell our data/APIs, but also take care of the building end-to-end?
the results so far of some of the products that came out of it:
- fully automated TAM building and email sequence platform for a Big 4 company
- automated "warmest path" for intros to founders for a private equity fund
and others that are basically a manifestation of the question: "what's your dream state for X?"
(X being sales, marketing, investing, etc.)
It's a lot to promise, but we're excited about the early potential. if you are interested in building your dream state for sales, recruiting, or investing - drop a note and we'll reach out!
Almost every SaaS app inside Vercel has now been replaced with a generated app or agent interface, deployed on Vercel.
Support, sales, marketing, PM, HR, dataviz, even design and video workflows. It’s shocking.
The SaaSpocalypse is both understated and overstated. Over because the key systems of record and storage are still there (Salesforce, Snowflake, etc.)
Understated because the software we are generating is more beautiful, personalized, and crucially, fits our business problems better.
We struggled for years to represent the health of a Vercel customer properly inside Salesforce. Too much data (trillions of consumption data points), the ontology of Vercel was a mismatch to the built-in assumptions, and the resulting UI was bizarre. We generated what we needed instead. When you don’t need a UI, you just ask an agent with natural language.
We’ve also been moving off legacy systems with poor, slow, outdated, and inconsistent APIs, as well as just dropping abstraction down to more traditional databases. UI is a function 𝑓 of data (always has been), and that 𝑓 is increasingly becoming the LLM.