Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Behind the Cloud

Behind the Cloud

The Untold Story of How Salesforce.com Went from Idea to Billion-Dollar Company-and Revolutionized an Industry
A $1.8 million software bill set the stage for a radically different way to sell business tools.
by Marc Benioff 2009 304 pages
3.78
4k+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Replace costly software installations with a service customers can start online

Remove the old burden. In 1999, enterprise software could cost more than $1.8 million in its first year for 200 users, including licenses, hardware, customization, support, and training. Benioff proposed delivering customer relationship management software through the Internet for a monthly fee, without customers installing or maintaining it themselves. The model, now commonly called Software-as-a-Service, made business software more accessible and gave customers a quicker way to try it.

Bet on one model. Salesforce.com built a shared service rather than offering customers a choice between hosted software and traditional installed software. That commitment let the company update one system for everyone and made its delivery model part of its identity. The idea sounded risky when customers worried about placing business data on someone else's servers.

Analysis

The innovation was not simply moving software online. It shifted who carried the cost, complexity, and operational responsibility. That is a business-model change as much as a technical one. The comparison with utilities helps explain the appeal: customers buy access to a maintained capability rather than assembling the machinery themselves. The tradeoff is dependence on the provider. For cloud services, convenience only earns trust when security, reliability, and clear communication are treated as core features, not back-office details.

Let customer behavior, not executive hunches, steer product development

Watch real use. Salesforce.com's first prototype appeared about a month after the team began building it. The founders invited prospective users to test it, asked salespeople what frustrated them about existing systems, and hired a usability firm to record people navigating the site. A test revealed that a button for creating an account disappeared on some monitors. Moving it to the left made it easier to find.

Turn feedback into changes. The team tracked bugs and requests, contacted early users, and added features in response to repeated needs. A health care customer objected that generic labels such as accounts and contacts did not match the language of hospitals. That request led to customizable tabs and, over time, broader ways for customers to tailor the application without writing code.

Analysis

This is product discovery as a disciplined learning loop: observe behavior, identify friction, make a change, and check whether it helps. It resembles methods used in experimental design, where direct observation can expose problems that interviews miss. The caution is that the loudest customers are not always representative. Requests need to be tested for frequency, importance, and fit with the product's broader direction. Listening works best when customer input informs judgment rather than replacing it.

Make the industry's old model your antagonist, not just another competitor

Sell the change. Salesforce.com framed its offer as an alternative to expensive, slow-to-install enterprise software, not merely as a different CRM product. Its launch event dramatized that contrast, drew more than 1,500 attendees, and attracted press attention. The company also used bold branding and public challenges to the market leader Siebel, casting itself as a smaller company pushing a broader industry shift.

Attention is not revenue. The book also describes a marketing review that found only fourteen leads from six months of direct-mail campaigns, despite monthly spending of $2 million to $3 million across advertising and mail. The company concluded that dramatic campaigns could create recognition without producing customers, and redirected effort toward channels that generated stronger sales results.

Analysis

A clear antagonist gives customers a useful contrast: the familiar way of doing things becomes visible as a choice, not a natural law. This is a powerful form of category positioning. But the story also shows why attention metrics can mislead. A stunt may generate coverage, yet coverage is only valuable if it builds credibility or moves buyers toward action. The strongest narrative is not simply that incumbents are wrong. It explains a real customer problem and demonstrates a better alternative.

Give customers a room to persuade one another

Let users testify. Salesforce.com invited customers, prospects, journalists, and partners to events together. At early City Tour gatherings, customers often answered prospects' questions before company employees could. The company learned that attendees valued meeting other users, so it made space for open discussion, demonstrations, and informal gatherings. At some events, about 80 percent of attending prospects became customers, while the events cost roughly $250 per attendee.

Start with the end user. Traditional enterprise vendors tended to sell to budget-holding executives. Salesforce.com focused on sales, marketing, and support employees who actually used the software. It celebrated these users as customer heroes and made their accounts of implementation and results central to its marketing. The strategy worked because customers were already using the service and could describe its value from experience.

Analysis

Peer testimony reduces the distance between a vendor's promise and a buyer's imagined experience. It also creates a learning environment: users exchange practical knowledge that a polished sales presentation rarely supplies. This resembles network effects, where a product becomes more valuable as useful connections form around it. The limitation is selection bias. Events tend to attract engaged customers, so their praise cannot stand in for systematic measures of satisfaction across the whole customer base.

Change the revenue model when customer-friendly terms endanger survival

Fix the cash mismatch. Salesforce.com initially offered monthly billing and free trials, which lowered the barrier to adoption. During the dot-com crash, however, customers disappeared while the company continued paying sales commissions based on longer commitments. It was losing $1 million to $1.5 million each month. The company introduced annual contracts, charging $50 per user monthly when paid for a year in advance, compared with $65 for month-to-month service. Upfront payment helped it move from negative to positive cash flow in under a year.

Adapt how customers buy. Salesforce.com also moved from free trials toward paid proofs of concept for larger organizations, where executive and technical approval mattered. Its land-and-expand approach began with a smaller team or division, then grew after success. Customer success managers helped existing clients use the service and supported renewals.

Analysis

The episode is a reminder that a company's revenue model must match its cost structure and sales cycle. Recurring subscriptions can make income more predictable, but they do not automatically solve cash-flow problems. Upfront payment helped Salesforce.com, while preserving a monthly option for customers who valued flexibility. The broader lesson is to distinguish a customer-friendly promise from a financially viable one. A model that cannot fund reliable service will ultimately fail the customers it was meant to serve.

Turn a useful application into a platform others can extend

Build beyond the core product. Salesforce.com began with a simple sales-tracking application, then added an application programming interface so its service could exchange information with other programs. It later opened its platform to developers, who could build applications using Salesforce.com's infrastructure rather than creating the entire technology stack themselves. The company described this broader model as Platform-as-a-Service.

Create a market around the product. AppExchange gave developers a place to list applications and customers a place to search, review, try, and buy them. By the book's account, customers and partners had created more than 110,000 custom applications on the platform. The marketplace expanded what customers could do while giving developers access to potential users. It also made customers more invested in the surrounding ecosystem.

Analysis

Platforms can multiply innovation because the company no longer has to build every useful application itself. Developers contribute specialized knowledge, while a marketplace helps match that work with customer demand. The arrangement also changes the company's role from product maker to rule setter. That creates obligations: platform owners need dependable infrastructure, fair access, and standards that protect users. An ecosystem is not automatically healthy just because many applications exist. Trust and quality determine whether it compounds value or adds clutter.

Give from company resources before generosity becomes convenient

Design giving into the business. After seeing a charitable program at Oracle struggle because volunteering was simply added to employees' existing duties, Benioff wanted philanthropy built into Salesforce.com from its beginning. The foundation was established when the company incorporated. Its 1-1-1 model committed a portion of company equity, employee time, and product to community benefit. The product contribution gave nonprofits access to Salesforce.com's software, while employees also volunteered and the foundation provided grants.

Make it useful to recipients. The company worked with nonprofit leaders and young people to shape programs rather than assuming what communities needed. One early computer-center effort failed to engage students who already knew basic computer skills. The foundation shifted toward youth media, helping students make films and websites about issues in their lives. Their work reached public audiences and, in some cases, influenced policy and funding.

Analysis

The model treats philanthropy as an operating choice, not a separate act of generosity after the business has finished its work. That can bring useful assets, skills, and relationships into community programs. Its strongest feature is the insistence on listening to recipients, which helps prevent well-meaning organizations from supplying what they happen to have rather than what people need. Still, embedded giving does not guarantee impact. Outcomes, community control, and the opportunity cost of donated resources deserve ongoing scrutiny.

Grow abroad through local proof, leaders, and lasting presence

Adapt the route. Salesforce.com built language and currency flexibility into its product early, then expanded market by market. In Europe it began with a centralized sales team in Dublin. In Japan, local partners and experienced leaders helped the company understand the market, but the company later added direct sales when partnerships alone moved too slowly. Japan Post first bought 5,000 subscriptions, then expanded to more than 70,000, providing a major local reference.

Show commitment. In Asia, Salesforce.com learned that flying in for events and leaving afterward did not build durable demand. It invested in a Singapore hub, local hiring, data-center capacity, and community activity. The company also discovered that a marketing protest that worked in the United States could collide with local rules and expectations elsewhere.

Analysis

International expansion is a problem of institutional distance as much as geography. Language, procurement norms, regulation, and trusted relationships shape how a product is understood. Local leaders can translate both the market and the company's expectations, but they need genuine authority rather than a ceremonial role. The book's cases support a useful balance: preserve the core product promise while adapting the path to adoption. A repeatable playbook is valuable only when local evidence can revise it.

Make strategy a living document everyone can translate into work

Give priorities a shared shape. Benioff created V2MOM to make company direction explicit. The framework connects the desired future with the principles that matter, the actions intended to reach it, the barriers in the way, and the results that will show progress. Salesforce.com revisited the document every six months and gathered input from senior leaders, managers, and employees. The first version was handwritten on an American Express envelope and served as a compact business plan.

Connect levels of work. Executives and their teams created related versions so individual responsibilities could connect to company priorities. Employees could comment on the corporate plan through an internal idea-sharing tool. This made strategy a continuing conversation rather than a document produced once and left in a drawer.

Analysis

A strategy framework earns its keep when it improves choices, not when it merely standardizes vocabulary. V2MOM's value lies in connecting aspiration to obstacles and observable results, while inviting feedback from people close to the work. This resembles the logic of management systems that align goals across teams. There is a risk, however, that frequent alignment becomes compliance theater. A living plan must leave room for dissent and revision, or its clarity can harden into an excuse not to notice changing conditions.

Recruit as a growth engine, then keep raising the talent bar

Treat hiring as everyone's work. Salesforce.com hired a human-resources leader early, after its first strategy document identified talent as a major obstacle. The company used employee and board networks to find candidates, looked for attitude and ability as well as experience, and involved multiple colleagues in interviews. In its all-yes approach, one serious no could stop a hire, on the premise that a new colleague needed broad support to succeed.

Retain through development. An employee survey revealed that people wanted clearer career paths, prompting more training and development opportunities. The company also used role changes and new assignments to challenge strong employees. Its onboarding introduced new hires to the product, company practices, and community work, so that organizational culture was taught rather than left to chance.

Analysis

Hiring is a form of capacity planning: each good hire expands what an organization can build, sell, or support. The book's emphasis on referrals and shared evaluation recognizes that colleagues possess information a résumé cannot show. But consensus has a cost. An all-yes rule may reduce avoidable mismatches while also filtering for similarity and discouraging unconventional candidates. Strong hiring systems need both cultural alignment and protection against groupthink, especially when innovation depends on people seeing problems differently.

Fund the company you are building, then professionalize before the IPO

Do not depend on one door. Benioff put $6 million of personal capital into Salesforce.com, then raised money from people in his network after venture firms repeatedly declined. The company ultimately raised $65 million across five rounds from 1999 to 2002. The book argues that founders should assess funding needs carefully, document investments professionally, and consider angels and other private investors rather than treating venture capital as the only path.

Pair innovation with financial discipline. Before its 2004 public listing, Salesforce.com hired experienced finance leaders, formalized accounting and revenue procedures, and built internal controls ahead of regulatory requirements. The company kept its public-facing marketing unconventional while treating financial reporting conservatively. That preparation helped establish credibility for a business model regulators and investors had not encountered before.

Analysis

Capital is not neutral: its source can influence control, time horizons, and which risks a company is encouraged to take. A wider funding search may preserve options, but personal networks can also concentrate risk among people who trust the founder more than the forecast. The book's most durable point is not that venture capital should be avoided. It is that funding choices and financial systems should fit the venture's needs, with rigorous reporting protecting the freedom to experiment elsewhere.

Analysis

Behind the Cloud is a founder's retrospective, a startup manual, and a company history arranged as a sequence of practical plays. Its central argument is that Salesforce.com grew by changing more than software delivery: it linked product design, pricing, marketing, customer advocacy, philanthropy, and management around a new model of access. The narrative makes that interdependence legible. A subscription product needs continuous service; continuous service demands customer trust; trust is reinforced by transparent operations and responsive development; recurring revenue makes retention and customer success financially central.

The book is most useful when its advice emerges from a specific constraint. The dot-com crash forced a pricing and cash-flow change. Enterprise buyers required a shift from informal trials to organizational approval. Outages exposed the cost of silence. These episodes show strategy as adaptation, not a fixed master plan. The company's willingness to change its own public commitments is especially instructive: principles matter, but survival sometimes requires revising tactics while explaining the reasons clearly.

Its evidence is also shaped by hindsight. Salesforce.com survived, so the book naturally highlights choices that appear prescient and gives less attention to comparable companies whose bold bets failed. The founder's account also compresses the contributions of employees, customers, investors, and favorable market timing into a coherent leadership story. Readers should treat the plays as hypotheses to test, not universal laws. For example, provocative attacks on a dominant competitor can earn attention, but their success depends on a credible product and a receptive press environment.

The deeper lesson is architectural: align incentives and capabilities so that the desired behavior is easier to repeat. Customer feedback, annual contracts, partner marketplaces, employee alignment, and giving are presented not as isolated initiatives but as connected operating mechanisms. That makes the book valuable beyond technology. Its strongest advice is to build a business whose model, culture, and customer experience reinforce one another, while remaining willing to change the parts that stop working.

Summary in 30 Seconds
In 1999, enterprise software could cost more than $1.8 million in its first year for 200 users. Delivering it online by subscription lowered the barrier to adoption, but monthly billing threatened cash flow during the dot-com crash. Annual prepayment helped reverse losses within a year. Product changes based on observed customer use built trust, while an open platform attracted more than 110,000 custom applications. Local leaders and proof points supported international growth.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.78 out of 5
Average of 4k+ ratings from Goodreads and Amazon.

Behind the Cloud receives mixed reviews, with praise for its insights into Salesforce's history and SaaS industry development. Readers appreciate Benioff's philanthropic initiatives and marketing strategies. However, some criticize the book's arrogant tone and lack of depth in addressing challenges. Many find the advice valuable for entrepreneurs, while others see it as basic or outdated. The book's structure of "plays" is both praised for its clarity and criticized for its disconnected nature. Overall, it's considered informative but potentially self-congratulatory.

Your rating:
4.33
113 ratings
Want to read the full book?

Glossary

Software-as-a-Service (SaaS)

Hosted software subscription

A way of providing software over the Internet as an ongoing service. Customers access the application through a browser and pay a recurring fee rather than buying and installing a software package themselves. The provider hosts, maintains, and updates the service, while customers use it without managing the underlying infrastructure.

multitenancy

Shared service, separate data

A technology architecture in which many customers use the same underlying application and infrastructure. Each customer's information and experience remain separately protected, while common resources such as databases and servers are shared. Salesforce.com used this approach to update and operate one service for many organizations instead of maintaining a separate software installation for each customer.

V2MOM

Organizational alignment framework

Salesforce.com's management framework for clarifying company direction and connecting it to execution. It organizes a plan around the desired future, guiding principles, actions, obstacles, and measures of progress. The company used it as a living document, revising it regularly and creating aligned versions throughout the organization so employees could connect their work to shared priorities.

1-1-1 model

Three-part corporate giving

Salesforce.com's approach to integrating philanthropy into its business. It allocates a portion of company equity, employee time, and company product to community benefit. The model was established alongside the company, with software access, volunteering, and grants supporting nonprofit organizations. The book presents it as a commitment that can grow alongside the business.

seed-and-grow strategy

Start small, expand adoption

Salesforce.com's approach to winning customers by making initial adoption low risk, often through free or limited trials, then improving the service through user feedback and converting successful use into paid subscriptions. It also describes beginning with smaller companies or departments and expanding within organizations as the product proves its value.

land and expand

Win small, grow accounts

A sales approach in which a company begins with a limited deployment inside a larger organization, such as one department or group of users. After demonstrating value and building support, the vendor seeks broader adoption across the organization. Salesforce.com used this route to reduce buyers' initial risk while creating a path to larger contracts.

IdeaExchange

Customer ideas and voting

Salesforce.com's online community tool for collecting, discussing, and ranking customer suggestions. Users could submit ideas and vote or comment on proposals, helping the company see which requests resonated with the community. The platform also allowed outside developers to spot unmet needs and build complementary applications.

intelligent reaction

Iterative product learning

A development approach, attributed in the book to software pioneer Adam Bosworth, in which a company learns from actual usage and adjusts its product through frequent releases. Salesforce.com contrasted its short cycles of updates and customer feedback with traditional software projects that could take years to deliver a major release.

AppExchange

Business app marketplace

Salesforce.com's online marketplace for applications built to work with its service and platform. Developers could publish applications, while customers could search, review, test, and purchase them. The marketplace extended the product through partner contributions and helped create an ecosystem around Salesforce.com's technology.

About the Author

Marc Benioff is the chairman, co-CEO, and founder of Salesforce, a pioneering cloud computing company. Recognized for his innovation and leadership, Benioff has received numerous accolades from publications like Forbes, Fortune, and Harvard Business Review. He's known for his commitment to equality and philanthropy, having created the 1-1-1 model that donates 1% of the company's equity, product, and employees' time to communities worldwide. This model has inspired over 8,500 companies to adopt similar practices through the Pledge 1% movement. Under Benioff's leadership, Salesforce has grown into a Fortune 500 company with over 45,000 employees and has been recognized for its innovation and workplace culture.

Download PDF

To save this Behind the Cloud summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.34 MB     Pages: 19

Download EPUB

To read this Behind the Cloud summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.38 MB     Pages: 21
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...