This breaks down Salesforce's rise from 1999 to a cloud giant. The guest says its success wasn't tech but the 'No Software' message that clicked with customers tired of expensive on-premise software, and making 'trust' the top value to get them to store data in the cloud. Three key holdings: Snowflake (cloud data warehouse that could erode Salesforce's data lock-in), Twilio (developers build marketing tools from the bottom up, just like Salesforce disrupted Siebel), and Slack (acquired by Salesforce as a future collaboration hub).
Salesforce was founded by Marc Benioff in 1999 and is the global leader in the CRM market (valued at $100 billion), serving 150,000 customers, including 90% of the Fortune 500, with a current valuation exceeding $270 billion. In this episode of Business Breakdowns, former Salesforce Ventures head Ma
Matt Garratt (former head of Salesforce Ventures, now a partner at CRV) deconstructs Salesforce’s growth trajectory from its founding in 1999 to the present. Core thesis: Salesforce’s success did not stem from technological originality, but from Marc Benioff making "trust" the top value, and through the clear messaging of "No Software," the V2MOM prioritization tool, and the Hawaiian "Ohana" culture, solving the trust issue of customer data hosting in the zero-base era of SaaS—this is the foundation upon which all subsequent SaaS companies have relied.
Matt Garratt argues that the key to Salesforce's early success was not technological leadership, but finding a messaging hook that customers could instantly grasp.
In 1999, all enterprise software was on-premise: customers bought CDs, installed servers, and signed large service contracts. Benioff had to convince clients to entrust their most valuable customer data to the "cloud"—a concept almost no one understood at the time. His solution was the "No Software" slogan.
> "When they kind of said 'no software', they understood the pain of dealing with the incumbents."
This message worked because it did not explain "what the cloud is," but instead directly targeted customers' pain points with traditional CRM systems like Siebel: expensive, rigid, cumbersome to upgrade, and tied to service contracts. Salesforce's early sales strategy was also extremely simple—call the CFO directly, drop the price from millions of dollars for traditional CRM to tens of thousands per year, and even proactively target the SMB market (an area ignored by large companies at the time).
Matt points out that the lesson for entrepreneurs is: when your product is highly disruptive, the message must be radically simplified. If Benioff had tried to explain a host of advantages like "continuous updates," "managed services," and "real-time data," the message would have been diluted. A single selling point—"cheaper"—was enough to open the market.
Matt emphasizes that Salesforce's "trust" is not a slogan but an operating system embedded in product design, customer relationships, and corporate governance.
The Trust Challenge of Data Custody: In an era when AWS was not yet mature, convincing enterprises to entrust their customer data to a third party was the biggest obstacle Salesforce faced. Benioff's response was to list "Trust" as the company's first value and reflect it in every decision.
The Trust Experiment of Dreamforce: The first Dreamforce had only 250–300 people and was held at a hotel in San Francisco. Benioff insisted on letting customers take the stage, hold the microphone, with no rehearsals and no topic restrictions—even proactively asking, "What's not working?" Matt recounts Jim Steele's (early sales leader) recollection:
> "Mark said, 'No, no, you don't understand. Trust is our number one value and we need to hear honestly from the customers.'"
The Evolution of Dreamforce: It grew from a small gathering of a few hundred people into a massive event with 100,000 attendees on-site and millions watching online. Matt points out that Dreamforce is not just a sales tool but also a means of unifying internal culture—the entire company must attend and listen to Mark discuss product direction. When the company expanded from a few thousand to tens of thousands of employees, this mechanism of "forced information alignment" was extremely rare.
Ohana Culture: Benioff introduced the concept of "Ohana" (family) from Hawaii—customers, partners, platform developers, and even Salesforce administrators are considered "family" rather than transactional counterparts. Matt believes this culture has driven customer retention rates above 90% and net retention rates above 100%, because customers feel "treated like family."
Matt describes Salesforce’s transformation from a “builder” to a “buyer,” and the unique role Salesforce Ventures plays in this shift.
The Acquisition Trilogy:
1. Early Stage (2000s): Small-scale talent acquisitions, such as the purchase of Instranet (whose founder Alex Dayon later became CPO and built Service Cloud on this foundation).
2. Mid Stage (2013): The first large-scale acquisition—acquiring the publicly listed company ExactTarget for $2.5 billion, laying the groundwork for Marketing Cloud.
3. Later Stage (2018–2020): Acquiring MuleSoft (data connectivity), Tableau (analytics), and Slack (collaboration), entering new product categories.
Strategic Positioning of Salesforce Ventures: The investment unit led by Matt grew from $10–20 million annually to $1 billion per year, managing $4 billion in assets. Its core mission is not “to feed the M&A pipeline,” but rather “to accelerate and expand the Salesforce ecosystem.”
> “Our goal was to help accelerate and grow the ecosystem around Salesforce.”
The Relationship Between Investment and Acquisition: Matt emphasizes that Salesforce Ventures has invested in 300–400 companies, but only a few were acquired. The real value lies in building relationships, understanding the business, and assessing cultural fit through investments. When an acquisition occurs, the CEO’s primary concern is often not the price, but where the team will go—a trust that takes years to cultivate.
Matt reminds readers that this is a position-holder’s perspective. Acquisition integration is one of Salesforce’s core risks—the cultural integration and product synergies of large acquisitions like Slack and Tableau have yet to be fully validated.
Matt argues that V2MOM is the key tool enabling Salesforce to maintain focus while scaling.
V2MOM stands for: Vision, Values, Methods, Obstacles, Measures. Benioff starts by drafting his own V2MOM each year, then cascades it down to every employee level by level. The core rule: the priority list must be short and must be ranked.
"Hack the V2MOM": Each year, the executive team holds a "Hack the V2MOM" session — broadcast live to the entire company. Employees at any level can stand up and critique any aspect of the business, including "What should we stop doing?" and "What have we lost?" Benioff personally takes notes and discusses them with the executive team.
> "There were no sacred cows. You could be a reasonably junior person, stand up and say, 'I think this is dumb and we shouldn't be doing this.'"
Matt points out that this mechanism solves the "information filtering" problem common in large companies — when a company has tens of thousands of employees, senior management often only hears filtered information. V2MOM's open "hack" mechanism allows grassroots voices to reach the CEO directly.
Matt identifies three layers of risk facing Salesforce, two of which carry asymmetric disruption potential.
Short-term (within 5 years): Largely safe. The SaaS model, sales team, and existing product suite are sufficient to sustain growth. Competition is mainly in the SMB segment but "won't shake Salesforce."
Medium-term risk: Data gravity shift
Traditionally, data has been Salesforce's "gravity"—customer data stays on the Salesforce platform, creating switching costs. However, the rise of cloud data warehouses (Snowflake, Databricks) changes this: enterprises can pull all application data into a unified data warehouse, run analytics on it, and push results back to applications. This weakens Salesforce's data lock-in effect.
> "That kind of erodes a little bit of the value and the data gravity that those things have."
In a more aggressive scenario: platforms like Snowflake allow developers to build applications directly on the data warehouse, with customer data never leaving it. If this model matures, Salesforce's dual moat of "platform + data" could be bypassed.
Long-term risk: Developer-driven disruption
Traditional enterprise software follows a "top-down" sales approach (selling to CIOs/CFOs). But companies like Twilio and Vercel take a "bottom-up" route—developers discover, trial, and build on their own, then tell the business unit, "We no longer need to spend $10 million on Adobe."
> "The engineers can start to use that. They can build their own marketing automation, their own CRM stuff, and then give that to their line of business."
Matt believes this "asymmetric attack" is exactly how Salesforce disrupted Siebel back in the day—Siebel had an on-premise business model and could not disrupt itself. Salesforce faces the same dilemma of "disrupt or be disrupted," albeit on a longer time horizon.
| Position | Guest Sentiment | Key Data |
|---|---|---|
| Siebel Systems | Historical Benchmark (Disrupted) | Former CRM market leader, reliant on on-premise deployment model |
| Snowflake | Risk Warning (Potential Disruptor) | Cloud data warehouse, may weaken Salesforce's data lock-in |
| Twilio | Risk Warning (Developer-Driven Disruption) | Enters enterprises bottom-up via developers, offers call center/marketing automation |
| Slack | Bullish (Strategic Acquisition) | Acquired, positioned as future enterprise collaboration entry point |
| Tableau | Bullish (Strategic Acquisition) | Acquired, positioned as analytics layer |
| MuleSoft | Bullish (Strategic Acquisition) | Acquired, positioned as data connectivity layer |
| ExactTarget | Historical Acquisition | Acquired for $2.5 billion in 2013, laid foundation for Marketing Cloud |
| Vercel | Risk Warning (Potential Disruptor) | Disrupts Adobe AEM via JAMstack and developer community |
| DocuSign | Neutral (Platform Ecosystem Case) | Third-party application on AppExchange |
| Vlocity | Neutral (Platform Case) | Loan system company built on Force.com platform, later acquired |
| Zoom | Neutral (Investment Case) | Portfolio company of Salesforce Ventures |
| Workday | Neutral (Unentered Domain) | HR domain Salesforce considered but did not enter |
1. Matt Garratt: The key to Salesforce's early success was not technology, but the subtractive message of "No Software." When customers did not understand what "the cloud" was, directly pointing to their pain points with existing vendors—expensive, rigid, service contract lock-in—was 100 times more effective than explaining technical advantages.
2. Matt Garratt: Dreamforce is not just a sales tool, but also a means of unifying internal culture. The entire company must attend and must listen to Mark discuss product direction—when a company grows from a few thousand to tens of thousands of people, this mechanism of "forced information alignment" is extremely rare.
3. Matt Garratt: The core mission of Salesforce Ventures is not to feed M&A targets, but to build relationships and assess cultural fit. Only a few of the 300-400 investments are acquired, but the trust built through investments makes CEOs care more about "where the team goes" than the price when selling.
4. Matt Garratt: The V2MOM "open critique" mechanism solves the information filtering problem in large companies. Employees at any level can criticize any business in a company-wide live stream—this mechanism allows bottom-level voices to reach the CEO directly, avoiding "senior management only hearing filtered information."
5. Matt Garratt: Data gravity is shifting from the application layer to the data warehouse layer. Cloud data warehouses like Snowflake allow companies to extract all application data, run analytics on it, and push it back to applications—this weakens Salesforce's data lock-in effect.
6. Matt Garratt: The biggest long-term risk Salesforce faces is developer-driven "bottom-up" disruption. Companies like Twilio and Vercel allow engineers to discover, trial, and build on their own, then tell the business department, "We don't need to spend another $10 million on Adobe"—this is exactly how Salesforce disrupted Siebel back in the day.
7. Matt Garratt: Salesforce's Ohana culture creates a compounding effect where "every $1 in revenue drives $6 in ecosystem revenue." IDC research shows that ecosystem partners such as system integrators and platform developers generate six times the revenue of Salesforce itself—this ecosystem lock-in is harder to replicate than product lock-in.
8. Matt Garratt: Salesforce's acquisition discipline is a "religious focus on front-office business." Despite a large number of potential acquisition targets in the market (such as Workday), Salesforce has consistently adhered to the core of "customer data + customer touchpoints"—from sales to service to marketing, and then to MuleSoft (data connectivity) and Tableau (analytics), all acquisitions stack in the same direction.