The $50-a-Month Heresy
In the spring of 2000,
Marc Benioff rented a warehouse on the San Francisco waterfront and threw a party to celebrate the end of software. Not a metaphorical end — a literal one. He printed "NO SOFTWARE" on buttons, on stickers, on banners draped across the venue, the universal prohibition symbol slashed through the word in red. The Ghostbusters logo, repurposed for enterprise computing. Guests — venture capitalists, Oracle executives who still took Benioff's calls, a handful of early customers paying $50 per user per month to access a sales-tracking application through their web browsers — mingled in what felt less like a product launch than an act of theological provocation. Software, in Benioff's cosmology, was not merely a flawed business model. It was original sin. The multi-million-dollar on-premise installations, the eighteen-month implementation cycles, the armies of consultants, the upgrade treadmills — all of it was a system designed to extract value from customers under the guise of serving them. His alternative was so simple it sounded like a trick: deliver the application over the internet, charge by the month, and handle everything else.
Twenty-five years later, Salesforce generates roughly $37.9 billion in annual revenue. The 61-story tower bearing its name dominates the San Francisco skyline — the tallest building in the city, visible from virtually every approach. Marc Benioff, now sixty-one, remains chairman and CEO, an improbable tenure in an industry that eats its founders. The company he started in a rented apartment on Telegraph Hill with three co-founders and a conviction that enterprise software was ripe for demolition has become, by some measures, the most important business software company of the last quarter century — not because it built the best product (a claim even its partisans would find debatable), but because it proved that a new
model could unseat the old one. The subscription, the cloud, the platform, the ecosystem, the annual conference-as-religion — Salesforce didn't just sell
CRM. It sold the architecture of modern SaaS.
And now Benioff is betting the entire edifice on a proposition at least as audacious as the one he pitched from that warehouse: that autonomous AI agents will perform the work currently done by his customers' employees, and that Salesforce — a company whose core product has been a database of customer records with a workflow engine bolted on top — is the natural platform on which that future will be built.
By the Numbers
The Salesforce Machine
$37.9BFY2025 revenue (ended January 2025)
~$262BMarket capitalization (May 2025)
~73,000Employees (as of January 2024)
150,000+Customers worldwide
$27.7BSlack acquisition (2021), largest software deal of its era
~$60BTotal M&A spend since founding
NYSE: CRMTicker symbol — the category itself
A Salesman's Son in Oracle's Court
The origin story of Salesforce is, at its core, the story of a salesman who grew up inside the most formidable sales machine in enterprise software — and then turned its weapons against it. Marc Russell Benioff was born in San Francisco in 1964, the son of a retail-store owner. He started programming as a teenager, sold his first software — a game called "How to Juggle" — for $75, and by the time he was an undergraduate at USC was already running a small software company. At fifteen, he was writing code for Atari. At twenty-three, he joined Oracle.
Larry Ellison's Oracle in the late 1980s and early 1990s was the West Point of enterprise sales culture — aggressive, confrontational, wildly profitable. Benioff thrived. He rose fast, becoming Oracle's youngest vice president at twenty-five, overseeing product development for desktop PCs. He spent thirteen years there absorbing two lessons that would define his later career: first, that the enterprise customer was trapped in a system that punished them with complexity, and second, that the force that moved enterprise deals was not superior technology but superior storytelling. Ellison became his mentor, his investor, and eventually his most complicated frenemy — a relationship that would oscillate between paternal affection and open rivalry for two decades.
By the late 1990s, Benioff was restless. A sabbatical took him to India, where he studied with a guru, and to Hawaii, where he absorbed the concept of ohana — the extended family network — that he would later embed into Salesforce's corporate vocabulary. He returned with a conviction that the internet would do to enterprise software what it was already doing to media: flatten the distribution, destroy the incumbents, create something new in the wreckage. He recruited three co-founders — Parker Harris, Dave Moellenhoff, and Frank Dominguez — engineers who could build what he could sell. They started in a rented apartment at 1449 Montgomery Street in San Francisco's Telegraph Hill neighborhood. The date was March 8, 1999.
Parker Harris was, in many respects, Benioff's photographic negative: quiet, technical, allergic to the spotlight. Harris had been building web-based enterprise tools at a company called Left Coast Software, and what he brought to the partnership was the engineering conviction that multi-tenant architecture — a single codebase serving all customers from a shared infrastructure — was not merely possible but essential. This was the architectural decision that made everything else work. Unlike the application service providers (ASPs) of the era — Corio, USinternetworking — that rented out existing software and mostly went bankrupt, Salesforce would write its own code from scratch, purpose-built for the browser, with every customer running on the same platform and receiving upgrades simultaneously. "I don't like being front and center," Harris would say years later. "I like being behind the scenes." But it was his architecture, not Benioff's charisma, that was the company's true structural advantage.
The End of Software and the Start of a Category
The early years were a masterclass in asymmetric competition. Salesforce had no chance of matching Siebel Systems — the dominant CRM vendor, founded by Tom Siebel, another Oracle alumnus — on features, depth, or enterprise credibility. What it had was a radically lower barrier to adoption. For $50 per user per month (later raised to $65), a company could be running Salesforce's CRM within days, not months. No servers to buy. No software to install. No database administrators to hire. No upgrade cycles to manage. The product was demonstrably inferior to Siebel's on virtually every dimension except the ones that mattered most: speed of deployment, cost of ownership, and the absence of risk.
We're seeing the end of software as we know it.
Benioff understood, instinctively or analytically, that the way to attack an entrenched enterprise incumbent was not to build a better product but to change the buying process. Siebel's sales cycle was six to twelve months. Salesforce's was a credit card swipe. Siebel required board-level capital expenditure approval. Salesforce was an operating expense line item that a VP of Sales could approve without asking anyone. This was Clayton Christensen's disruption playbook executed with unusual precision: enter at the low end of the market with a product that is "worse" by every traditional metric, serve customers the incumbent ignores (small and mid-market companies), and then ride improvements in the underlying technology — in this case, internet bandwidth and browser capability — upmarket until the incumbent's advantages evaporate.
By 2001, Salesforce had 2,900 customers and $14 million in revenue, doubling year-over-year while the rest of Silicon Valley imploded in the dot-com crash. Benioff told Forbes he expected to reach $50 million in sales in three years — a pace he noted had taken Microsoft and Oracle nine years each. The comparison was revealing. Even then, he was not benchmarking against other startups. He was benchmarking against empires.
The company's S-1 filing, submitted to the SEC on December 18, 2003, described Salesforce as "the leading provider, based on market share, of application services that allow organizations to easily share customer information on demand." The IPO, priced at $11 per share on June 22, 2004, raised $110 million through Morgan Stanley. The stock closed at a premium on its first day. Salesforce was public, listed on the New York Stock Exchange under the ticker symbol CRM — a move of breathtaking audacity, claiming the abbreviation of the entire product category as its corporate identifier. It was as if Google had listed under SEARCH.
📈
From Telegraph Hill to Wall Street
Key milestones in Salesforce's first act
1999Founded March 8 in a rented apartment on Telegraph Hill, San Francisco. Four co-founders: Benioff, Harris, Moellenhoff, Dominguez.
1999Prototype demonstrated at Monte Carlo conference. $50/user/month pricing announced. $17 million raised from Ellison, Halsey Minor, Magdalena Yesil (USVP).
2000"No Software" launch party. Pilot program with 400 users at 30 companies.
2001Revenue doubles to $14M amid dot-com crash. 2,900 customers.
2003S-1 filed December 18. Total raised: $65M in venture funding.
2004IPO: June 22, NYSE ticker CRM, $11/share, $110M raised.
The Platform Turn
If the first act of Salesforce was proving that SaaS worked, the second act was something more consequential and less often credited: proving that a SaaS company could become a platform. This was the strategic pivot that separated Salesforce from dozens of other cloud CRM vendors — UpShot, NetSuite's CRM module, RightNow Technologies — and laid the foundation for a durable competitive moat.
The insight was deceptively simple. Salesforce's CRM was a single application. A platform would be hundreds or thousands of applications, all built on Salesforce's infrastructure, all keeping customers locked into the ecosystem. In 2005, Salesforce launched AppExchange, a marketplace for third-party applications built on its platform. Two years later, it released Force.com, a platform-as-a-service that allowed customers and independent software vendors to build custom applications on Salesforce's multi-tenant infrastructure without writing traditional code.
This was the moment Salesforce stopped being a CRM company and started being something far more defensible: the operating system for business applications. Every custom app built on Force.com was another root driven into the customer's technology stack. Every integration created by a third-party developer on AppExchange was another strand in the web of switching costs that made leaving Salesforce not merely inconvenient but organizationally traumatic. By the time a large enterprise had built fifty custom objects, two hundred workflow rules, and connected twenty third-party applications through the platform, the "cost" of Salesforce was no longer $65 per user per month. It was the cost of ripping out the nervous system.
The platform strategy also solved a problem that haunted every enterprise software company: the tension between standardization and customization. On-premise vendors like Siebel and SAP made fortunes from customization — but customization created fragility, upgrade headaches, and consultant dependency. Salesforce's multi-tenant architecture meant that every customer ran on the same codebase, received the same upgrades, and benefited from the same reliability improvements. Customization happened on top of the platform through configuration and declarative tools, not through changes to the underlying code. This was operationally elegant and financially brilliant. It meant Salesforce could improve the product for everyone simultaneously while customers retained the illusion — and in many cases the reality — of a tailored solution.
The Acquisition Machine
Marc Benioff's approach to M&A is best understood not as a series of opportunistic deals but as a systematic strategy to fill every adjacent square on the enterprise chessboard before Microsoft, Oracle, or SAP could occupy them. Between 2016 and 2021, Salesforce executed a string of acquisitions that reshaped its product portfolio and competitive position — spending roughly $60 billion across its history, with the three largest deals arriving in rapid succession.
The first was Demandware, acquired for $2.8 billion in 2016, which gave Salesforce an e-commerce platform and created what would become Commerce Cloud. Then came MuleSoft in 2018 for $6.5 billion — an integration platform whose back-end software connected data stored in disparate enterprise systems. MuleSoft was not glamorous. It was plumbing. But it was exactly the kind of plumbing that enterprise CIOs needed to connect their Salesforce CRM with their SAP ERP, their legacy databases, their marketing platforms, their warehouse management systems. It was the connective tissue that made Salesforce's platform stickier by an order of magnitude.
Then Tableau in 2019 for $15.3 billion — the data visualization company whose drag-and-drop analytics had become the tool of choice for business analysts worldwide. And finally, the crown jewel:
Slack, acquired for $27.7 billion in December 2020, announced just as the pandemic was permanently reshaping how enterprise workers communicated.
As you know, they're basically entering from the $1 billion to $2 billion phase, which I know extremely well, and this is a moment where we can offer a lot of value. We've been there. We've lived that life.
The Slack acquisition illuminated both the ambition and the risk of Benioff's strategy. The $27.7 billion price tag — over 24 times estimated revenue — was enormous, making it one of the largest software deals in history, trailing only IBM's $34 billion acquisition of Red Hat and comparable to Microsoft's $27 billion purchase of LinkedIn. The strategic logic was clear: Slack gave Salesforce a communication layer, a persistent workspace where conversations about deals, customer issues, and projects happened in real time. Combined with Salesforce's CRM, Service Cloud, and Marketing Cloud, Slack would make Salesforce not just the system of record but the system of engagement — the place where work actually happened.
But the deal also put Salesforce in direct competition with Microsoft Teams, which had been growing explosively during the pandemic and had the advantage of being bundled with Microsoft 365 — the same bundling strategy that had proved lethal to so many Microsoft competitors over the decades. Dan Ives at Wedbush wrote that the deal would be "a major shot across the bow at Microsoft," and he was right — but shots across bows invite return fire.
Salesforce's largest deals, building the enterprise cloud stack
| Year | Target | Price | Strategic Purpose |
|---|
| 2016 | Demandware | $2.8B | Commerce Cloud — e-commerce engine |
| 2018 | MuleSoft | $6.5B | Integration platform — connecting enterprise systems |
| 2019 | Tableau | $15.3B | Data visualization and analytics |
| 2019 | ClickSoftware | $1.35B | Field service management |
The acquisition strategy had a compounding logic. Each deal added a product cloud. Each product cloud added another subscription line. Each subscription line deepened the customer relationship. But the compounding worked in both directions: each acquisition also added integration complexity, cultural friction, and the risk that Salesforce's product suite would feel less like a cohesive platform than a loose confederation of bolted-on products, each with its own UX language and its own engineering culture. This tension — between the ambition of the platform vision and the entropy of the acquired portfolio — would become one of the defining challenges of the 2020s.
Dreamforce and the Theology of the Platform
No analysis of Salesforce is complete without reckoning with Dreamforce, the company's annual conference, which has evolved over two decades from a modest customer gathering into what is arguably the most extraordinary corporate event in technology — a week-long occupation of downtown San Francisco that at its peak draws 170,000 attendees, generates an estimated $80 million in hotel bookings, and features celebrity keynotes (Will.i.am, Matthew McConaughey, Al Gore), live musical performances, a meditation zone, and Marc Benioff delivering a keynote with the cadence and emotional temperature of a revival preacher.
Dreamforce is simultaneously a sales tool, a brand exercise, a customer retention mechanism, a recruiting event, and an act of cultural self-definition. It is the physical manifestation of Salesforce's most underappreciated competitive advantage: the ecosystem. The tens of thousands of ISV partners, system integrators, independent consultants, and Salesforce-certified administrators who attend Dreamforce represent a distribution network and switching-cost multiplier that no amount of product innovation by a competitor can easily replicate. When a company has fifty Salesforce-certified admins, twenty AppExchange applications, and ten consulting relationships with Salesforce implementation partners, the decision to switch to Microsoft Dynamics or HubSpot is not a technology decision. It is an organizational upheaval.
Benioff understood this with the intuition of a man who had spent thirteen years watching Larry Ellison build Oracle's partner ecosystem. But he added something Ellison never had: a quasi-spiritual dimension. The "ohana" culture, the 1-1-1 philanthropic model (1% of equity, 1% of profits, 1% of employee time donated to community causes), the Trailblazer identity for Salesforce practitioners — these were not decoration. They were load-bearing walls. They turned a customer base into a community and a community into an identity. People didn't just use Salesforce. They were Salesforce people. They wore the hoodies. They earned the badges on Trailhead, the company's free learning platform. They introduced themselves at networking events as "3x certified Salesforce Architect." This is the kind of organic loyalty that money cannot buy and competitors cannot copy.
The Activist Winter
For all the mythology, Salesforce in early 2023 was a company in genuine crisis. The stock had fallen roughly 50% from its November 2021 high. Revenue growth had decelerated from 25% to the mid-teens. The company had hired aggressively during the pandemic — Benioff would later admit publicly that productivity had declined among newer hires — and operating margins lagged those of peers like ServiceNow and Adobe. Two co-CEOs — first Keith Block, then Bret Taylor — had been elevated and departed in rapid succession, neither lasting more than eighteen months, leaving observers to wonder whether Salesforce could function as anything other than a one-man show.
Then the activists arrived. Starboard Value, Elliott Management, ValueAct Capital, Third Point, and Inclusive Capital Partners all took positions. Five activist investors circling a single company was nearly unprecedented. Their critique was blunt: Salesforce had prioritized revenue growth and top-line vanity metrics over margins, cash flow, and capital discipline. The $60 billion-plus spent on acquisitions had not produced commensurate returns. Operating expenses were bloated. And Benioff, for all his gifts as a visionary and a salesman, had shown limited appetite for the unglamorous work of operational optimization.
In January 2023, Benioff announced Salesforce would lay off approximately 10% of its workforce — roughly 7,000 employees — acknowledging that the company had "hired too many people leading into this economic downturn." It was a stunning admission from a CEO who had spent two decades cultivating an image of corporate benevolence and "ohana" family values. The layoffs were followed by a series of operational moves that the activists had demanded: the M&A committee was disbanded, the pace of deal-making slowed dramatically, stock buybacks were initiated, and operating margins expanded sharply — from approximately 22% in FY2023 to over 30% by FY2025.
The margin expansion was real and impressive. But it also raised a deeper question: had Salesforce been a poorly run company generating exceptional revenue, or an exceptionally run company that had prioritized a different set of metrics? The answer, characteristically, was both. Benioff had built a revenue machine of extraordinary power — growing from zero to nearly $38 billion in twenty-five years, a feat matched by only a handful of enterprise software companies in history. But the machine had been running hot, burning capital on acquisitions of uncertain return, and carrying a cost structure that assumed perpetual high growth. When growth decelerated, the machine's inefficiencies became visible in a way they had not been during the hyper-growth years.
We hired too many people leading into this economic downturn.
The Co-CEO Revolving Door
The leadership question at Salesforce has always been the Marc Benioff question. He is, by any reasonable measure, one of the most successful enterprise software CEOs in history — a founder who has survived for twenty-five years in a role that, in technology, tends to destroy people within a decade. He is also, by the testimony of many who have worked closely with him, an overwhelming presence: charismatic, demanding, prone to late-night emails and spontaneous strategic pivots, equally capable of inspiring devotion and exhausting his lieutenants.
The co-CEO experiment — tried twice, failed twice — reveals the structural limitation. Keith Block, a veteran enterprise sales executive who had been Salesforce's vice chairman and co-CEO, lasted eighteen months before departing in February 2020. Bret Taylor, a genuinely brilliant product executive who had co-created Google Maps and served as CTO of Facebook, was elevated to co-CEO in November 2021 and resigned just over a year later, in January 2023, to start his own AI company (Sierra Technologies). Neither departure was publicly acrimonious, but the pattern was unmistakable: Salesforce operates as an extension of Benioff's personality and vision, and the co-CEO structure — which in theory was supposed to institutionalize succession planning — in practice created an untenable dynamic where a second CEO was redundant when things went well and insufficiently empowered when things went badly.
Parker Harris, the co-founder who had been there since the apartment on Telegraph Hill, remained the constant. He never held the CEO title, never sought it. Instead, he moved through a series of senior technical roles — CTO, then the technology lead for Slack — doing the architectural work that kept the platform coherent while the corporate superstructure above him churned. When generative AI exploded into public consciousness with ChatGPT in late 2022, it was Harris who noticed that Salesforce's V2MOM — the planning document Benioff calls the company's strategic Bible — "had nothing about generative AI." It was Harris who supervised the rapid insertion of AI capabilities into the product suite, who studied retrieval-augmented generation, who made the architectural calls about whether Salesforce should build its own large language model (it decided not to, opting instead to support multiple LLMs including models from Anthropic and OpenAI). The company that Benioff sold to the world was, under the hood, substantially the company that Harris built.
The Agentforce Gambit
In September 2024, at Dreamforce, Benioff declared a "hard pivot" to Agentforce — a platform that allows Salesforce customers to build and deploy autonomous AI agents capable of making decisions and performing tasks across sales, service, marketing, and commerce. This was not a feature release. It was, in Benioff's framing, a category-defining moment comparable to the original "No Software" revelation. AI agents, in this vision, would not merely assist human workers but replace entire categories of routine work — qualifying sales leads, resolving customer service inquiries, generating marketing campaigns, processing orders.
The early results, at least as reported by Salesforce, were striking. By mid-2025, Benioff claimed that AI agents were resolving 85% of Salesforce's own customer service queries and qualifying sales leads 40% faster than before. AI-generated code accounted for 25% of net new code in Salesforce's R&D organization. AI, Benioff said, was doing "30% to 50% of all work within Salesforce itself." Hiring for engineering, customer service, and legal roles had been paused. Fifty-one percent of Salesforce's hiring in Q1 FY2026 was internal transfers. The company was simultaneously cutting approximately 1,000 roles and hiring 1,000 to 2,000 salespeople to sell Agentforce to customers.
We have so many leads that we can't follow up on them all. Sales people basically cherry pick what leads they want to call back. Thousands of leads, tens of thousands of leads, hundreds of thousands of leads have never been called back. But in the agentic world, there's no excuse for that.
The financial markets reacted with enthusiasm — shares climbed 11% after the Q3 FY2025 earnings call that mentioned Agentforce eighty times — but also with the kind of knowing skepticism that comes from watching enterprise software companies rename existing capabilities to ride hype cycles. Benioff himself admitted that Agentforce was "not a material contributor" to current-quarter cRPO (contracted remaining performance obligation), the key leading indicator of future revenue. The pipeline was "incredible," the deals were "200" in the weeks after general availability, but the revenue was still overwhelmingly coming from the existing $37 billion portfolio of CRM, Service Cloud, Marketing Cloud, and platform subscriptions.
The strategic bet is enormous. Every major competitor — Microsoft with Copilot, Google with Gemini, SAP with Joule, ServiceNow with Now Assist — is racing to embed AI agents into enterprise workflows. The question is not whether AI agents will transform enterprise software (they will) but whether Salesforce's position as the system of record for customer data gives it a structural advantage in the age of agents, or whether the agents themselves become the new system of record, rendering the underlying CRM less important.
The Microsoft Shadow
The competitive dynamic between Salesforce and Microsoft is, in many ways, the defining strategic question of Salesforce's next decade. It has been building for years — Microsoft Dynamics 365 has competed with Salesforce's CRM since 2016, Power BI has competed with Tableau, Teams has competed with Slack — but the AI era has intensified the rivalry to an existential degree.
Microsoft's advantage is structural and terrifying. It owns the productivity layer (Office 365), the developer platform (Azure, GitHub), the identity layer (Active Directory), the communications layer (Teams), and, through its partnership with OpenAI, arguably the most advanced AI models in the world. Its ability to bundle AI capabilities into existing enterprise subscriptions — at marginal cost, since the customer is already paying for Microsoft 365 — gives it a pricing weapon that Salesforce cannot match. When Salesforce charges $2 per Agentforce conversation, Microsoft can embed equivalent capabilities into a suite the customer already owns.
Salesforce's counter-argument is data. The CRM is where the customer data lives — the accounts, the contacts, the opportunities, the support cases, the purchase histories. AI agents, Benioff argues, are only as good as the data they can access, and Salesforce's Data Cloud (itself a relatively recent addition to the product suite) can unify customer data from across the enterprise to give agents the context they need to act accurately. "Without our data set, these models are maybe 50% or 60% accurate," Benioff told Fortune. "When you add in our data set, we're getting 90% accuracy."
This is a plausible argument, but it has a vulnerability. Data is portable. APIs exist. And Microsoft, with its Dataverse platform and its Azure data estate, has its own story about unifying enterprise data. The structural question is whether the CRM as system of record retains its privileged position in an agentic world, or whether agents — capable of accessing data from multiple systems simultaneously — erode the moat that Salesforce has spent two decades building.
The Paradox of Ohana
There is an irony that Benioff, the CEO who built a corporate brand around family, compassion, and stakeholder capitalism, is now leading what amounts to the most aggressive workforce restructuring argument in enterprise software. "Jobs will change, and as with every major technological shift, some will go away — and new ones will emerge," he wrote in a Financial Times op-ed in July 2025. "At Salesforce, we've experienced this first-hand: Our organization is being radically reshaped."
The reshaping is real. Thousands of employees have been redeployed. Engineering hiring is on pause. Customer support headcount is shrinking as AI agents handle an increasing share of inquiries. The company paid Matthew McConaughey reportedly more than $10 million annually for its Super Bowl advertising partnership — a sum that drew unflattering comparisons during rounds of layoffs. Benioff told the Wall Street Journal he had no hand in the McConaughey deal, which was approved by the compensation committee. The optics were, to put it gently, suboptimal.
But the deeper tension is not about optics. It is about the fundamental promise of the platform. Salesforce's customers are being sold AI agents to automate their workforces. If Agentforce succeeds — if autonomous agents truly can resolve 85% of customer service queries, qualify sales leads, and generate marketing campaigns — then the logical consequence is that Salesforce's customers will need fewer employees. This is the product working as designed. The question is what happens to per-seat licensing when the seats are occupied by software. Benioff has hinted at outcome-based pricing — charging per AI conversation rather than per human user — but the transition from seat-based to consumption-based revenue is one of the most treacherous passages in SaaS economics, as it decouples revenue growth from the expanding workforce of the customer.
AI is not destiny. We must choose wisely. We must design intentionally.
The Tower on Mission Street
Salesforce Tower, at 1,070 feet and sixty-one stories, was completed in 2018 at a cost of approximately $1.1 billion. Benioff secured naming rights for the top floors and the building's crown, making it the literal and symbolic apex of San Francisco's skyline. On clear days, you can see it from across the Bay, from the Oakland hills, from approaching flights into SFO. It is — and this is not metaphor — the first thing many visitors see when they arrive in San Francisco.
When the building was planned in the mid-2010s, it was an expression of confident expansion: Salesforce was growing 25% annually, hiring thousands, and its founder was buying Time magazine for $190 million in cash, hosting world leaders at Dreamforce, and positioning himself as the conscience of Silicon Valley. By 2023, the tower had become a more ambiguous symbol. San Francisco was emptying. Downtown office vacancy rates approached 35%. The tech workforce that had filled the tower's floors was working remotely or had been laid off. Benioff himself acknowledged the city's struggles while simultaneously defending his commitment to it — investing in local initiatives, urging other CEOs to return to the office, insisting that San Francisco's best days were ahead.
The tower is a fitting emblem for the company it represents. It is massive, visible, impossible to ignore, built on the conviction that growth would continue indefinitely. It houses the headquarters of a company that trades under the ticker CRM — the category made artifact — and whose annual conference takes over the streets surrounding it like a secular pilgrimage. Whether the tower represents the permanence of Salesforce's position or the hubris of a peak-era investment depends on which version of the next decade you believe.
On a clear evening in San Francisco, the top of Salesforce Tower cycles through a display of programmed LED lights — blues, greens, the occasional message. It is the last thing you see before the fog rolls in.
