Lecture 12 - Building for the Enterprise (Aaron Levie)

Aaron Levie, CEO of Box, argues that cloud computing and mobile have created the best moment in history to build enterprise software.

Core Opportunity

• Raw-material shifts in storage, browsers, and networks opened file sharing in 2005 (0:01-10:02).
• Enterprise IT spend reaches $3.7T yearly versus $170B for consumer apps and ads combined (9:59-20:01).

Market Transformation

• Cloud replaces on-premise installs; Salesforce and AWS prove standardized platforms win (19:57-29:59).
• Mobile moves buying power to end users, letting startups land then expand inside large accounts.

Winning Playbook

• Spot widest gaps between current practice and new possibility.
• Start intentionally small with a wedge such as PlanGrid blueprints or Zen Payroll (29:56-39:57).
• Exploit asymmetries: platform-agnostic code and new monetization models that incumbents cannot adopt.

Execution Rules

• Serve bleeding-edge customers already living in the future.
• Distill requests into simplest solutions and expose APIs for platform growth (39:55-46:11).

00:00:01 Major Topic: Introduction and Course Framing

Speaker: Aaron Levie

• Aaron Levie, CEO and co-founder of Box, introduces the session as part of a course on how to build an enterprise software company. He frames his goal as persuading the audience that building an enterprise software company is a super cool, valuable path, countering common perceptions that favor consumer software.
• He outlines that the talk will cover three things: (1) quick background on Box and the path to enterprise, (2) major factors that have changed in enterprise software making it feasible for startups today, and (3) practical patterns and patterns you can exploit to build an enterprise software company.
• He warns his voice may be a bit off due to recent speaking, and teases that he will be sipping water throughout.

00:09:59 Major Topic: Box Background and Early Journey

• Box has grown to roughly 240,000 businesses using the product and over 27 million users, with a footprint in about 99% of the Fortune 500. He jokes that the last 1% is Microsoft and hints at their ongoing challenge to win that segment.
• He lists example customers across varied industries (manufacturing, consumer products, General Electric, Stanford healthcare, etc.) to illustrate broad enterprise adoption and use cases (collaboration, research, hospital workflows, etc.).
• The origin story: Box launched as Box.net in 2005, with the idea stemming from experiences in college in 2004 when file sharing across corporate networks was hard and storage in schools was minimal (e.g., USC offering 50 MB of online storage—limited even then).
• The initial market insight: storing/sharing files easily from anywhere was a compelling need; that insight was catalyzed by improvements in storage costs, browser/network capabilities, and the desire to access data from multiple locations.
• Early funding and pivot: Box received angel funding from Mark Cuban and decided to relocate to the Bay Area, planning to offer a free version initially (one gigabyte of storage for Box.net users), which drew hundreds of thousands of signups monthly.
• The core tension faced by founders: their product was robust for consumers but insufficiently secure for enterprises, while the enterprise market demanded more security and capability than the consumer product offered. This highlighted a gap between the two market needs—more vs. less functionality depending on the audience.
• The consumer-vs-enterprise crossroad: Levie compares the two paths—consumer startups (fun, hype, easier monetization via apps or ads) versus enterprise (slower sales cycles, complex procurement, often negative sentiment toward enterprise software, and heavy incumbent competition).
• The economics and business-model differences: consumer apps typically address short-term, lower-dollar purchases (mobile apps, advertising, or subscriptions), whereas enterprise IT involves trillions in annual IT spending and a different value equation focused on productivity and performance.
• The fear vs. opportunity dynamic: investors warned that early-stage teams with limited enterprise experience would struggle against incumbents like Microsoft/Oracle/IBM. Yet Box opted to leverage core consumer DNA (speed, usability, and disruptive cloud-based approaches) and pursue enterprise with a new playbook.
• The decision to pursue enterprise: Box resolved to apply the consumer-side vigor and UX-led design to the enterprise, while rethinking the sales model and product architecture to fit large organizations—recognizing that changing technology factors could unlock a new kind of enterprise software company.

00:19:57 Major Topic: What Has Changed in the Enterprise to Enable Startups

• Levie argues this is an incredible era to build enterprise software because the landscape has shifted in fundamental and actionable ways.
• Cloud adoption and distributed computing: Most application categories are moving to the cloud. The shift from on-premise (data center-based) to cloud-based infrastructure (on-demand computing) reduces the barrier to trying and adopting new software.

- The cloud enables scale and on-demand resources; it also changes the cost structure for customers considering new tech.

• Standardization over customization: Enterprises increasingly want open platforms and above-the-stack customization rather than bespoke, bottom-layer customization. This enables startups to deliver value without being locked into heavy, bespoke integrations at the core.
• Global reach and ubiquity: The platforms are becoming global, with customers worldwide able to adopt software more quickly than in the past.
• User-led IT and mobile influence: The rise of mobile devices (iPhone, iPad, Android) has shifted IT from a purely IT-led model (CIO-driven) to a more user-led model. End users within departments (sales, marketing, finance) bring in tools, while IT scales governance and security as needed. This makes it possible for startups to enter via the end user rather than solely through the CIO.
• The magnitude of opportunity: There are billions of people online and hundreds of millions of smartphones globally. This creates a broad, global pool of potential users and a new set of expectations for the technology stack powering modern work.
• Two moments of opportunity for technology revolutions in the enterprise:

1) The raw materials change (cost of computing drops, storage expands, and on-demand provisioning becomes feasible). 2) The customer experience shift (new ways for customers to interact with products, services, and data—e.g., Uber transforming transportation; healthcare’s shift to personalized, predictive care and telemedicine; retail’s omni-channel needs; media shifting from linear to on-demand content).

• Plan Grid example as a concrete illustration of disruption: A construction-focused mobile app that leverages tablets to replace expensive blueprint printing and distribution, highlighting how a new form factor in a specific industry can unlock a new software category.

Quote: > "everything about the enterprise and then by definition the software that an enterprise uses has changed just in the past 5 years. This is probably the most magical time if there could have ever been a magical time to build an enterprise software company." (timestamp 00:19:57, Speaker: Aaron Levie)

00:29:56 Major Topic: Practical Patterns and Early Wins for Enterprise Software

• Patterns to find product-market fit in the enterprise, with a focus on the modern, cloud-enabled, user-led world:

- Spot technology disruptions: Look for enabling technologies or major trends that widen the gap between what’s possible and what is currently done. Example: Plan Grid’s mobile-first solution for construction that addresses the $4B/year blueprint printing problem by leveraging tablets and on-demand content distribution. - Start intentionally small: Find a wedge—the smallest viable use case that solves a meaningful pain and can be delivered with exceptional user experience. The goal is to slip into the enterprise architecture and expand over time, not to attempt the full-stack solution from day one. - Find asymmetries: Build platform-agnostic technology that can work across many ecosystems (instead of forcing deep vertical integration that incumbents favor). Also, seek economically infeasible moves for incumbents (e.g., Zenefits’ model of monetizing via insurance company commissions rather than charging the small business directly). - Lean toward crazy-outlier customers: Seek bleeding-edge users whose needs reveal gaps in the current market and who can evangelize early adoption; use them to shape the platform and identify future use cases (e.g., Skyatch’s enterprise drones for data capture in construction, agriculture, oil & gas). - Listen to customers but don’t build exactly what they say: Distill customer requests into the simplest, most valuable product that addresses core problems. This requires product leadership to translate user feedback into a cohesive, scalable solution. - Modularize, not customize: Build a flexible platform with APIs and openness to allow verticals and integrations without hard-coding every vertical use case. The goal is a durable platform that enables customization at the integration layer rather than inside the core product. - Keep consumer DNA at the center: Maintain high usability and adoption characteristics from consumer products to improve enterprise uptake. A product with strong UX can accelerate deployment and scale within large organizations. - Sales as a complement, not a substitute: Even with strong product-led growth, enterprise sales and consultative selling remain important for deployment, governance, and navigating complex ecosystems.

• Concrete examples and recommended readings:

- Zen Payroll (now Gusto) demonstrates starting with a specific pain point for small businesses (payroll) and expanding into broader HR needs; illustrates a wedge strategy and the potential for up-market evolution. - Zenefits exemplifies exploiting an asymmetric business model (insurance commission funding the software) to disrupt a bundled HR/benefits space. - Plan Grid illustrates identifying a large waste (billions spent on printed blueprints) and enabling a mobile-first solution to capture the data and workflow digitally. - Mixpanel’s approach shows how consumer-friendly analytics tools can be leveraged to propel adoption with a developer-first mindset and then scale via enterprise sales.

• The closing guidance emphasizes: the current era is primed for building enterprise software; read three books to deepen understanding; be aware that competition exists but there’s substantial opportunity for entrants who apply the right patterns.

Notable lines: - "Start intentionally small... slip in between the gaps of other existing products but is something that you think over time expands to become a more important part of the enterprise architecture." (paraphrase of the wedge strategy; timestamp 00:29:56) - "Find asymmetries... platform-agnostic across all platforms... economically infeasible moves for incumbents." (summary of asymmetry points; timestamp 00:29:56) - "Plan Grid is a mobile application that lets you manage construction projects, lets you get access to your blueprints, lets you manage all of the data around a construction process." (Plan Grid description; timestamp 00:29:56) - "The magical thing about building an enterprise software company right now is you can keep consumer DNA at the center of the product... adoption is easier, sale is easier, virality is higher." (summary of consumer DNA advantage; timestamp 00:29:56)

00:39:55 Major Topic: Final Patterns, Books, and Closing Thoughts

• Practical takeaways and caveats for aspiring enterprise software founders:

- Always consider the opportunity to disrupt with technology by identifying a disruption and building a product that leverages new capabilities. - Start small, then expand; don’t try to conquer the entire market in one go. - Look for asymmetries that incumbents won’t or can’t exploit, such as platform openness or alternative monetization models. - Engage with bleeding-edge customers to shape your product, while maintaining a strong core platform capable of broader deployment. - Preserve and leverage consumer DNA in product design to boost adoption even within enterprise contexts. - Use a sales approach that complements product-led growth rather than relying solely on a direct sales force.

• Readings suggested for deeper understanding: Crossing the Chasm, Innovator's Dilemma, and Behind the Cloud.
• Final encouragement: This is an amazing time to start an enterprise software company. If it doesn’t work out, there are opportunities with Box or other ventures. He even jokes about hiring if you fail, and playfully warns not to compete with Box since they have competition already.

00:46:00 Resources and Closing (Embedded Throughout)

• Mentions several companies and concepts as illustrations throughout the talk, including: Box itself, Plan Grid, Zen Payroll, Zenefits, Skyatch, Palantir, public cloud (Amazon Web Services), and major incumbents like Microsoft, Google, Oracle, IBM.
• Specific books recommended for deeper theory: Crossing the Chasm, Innovator's Dilemma, Behind the Cloud.
• The talk closes with a reminder to leverage the Internet, user-driven adoption, and a modern go-to-market approach to enterprise software.

Resources Mentioned

• Plan Grid: Mobile construction project management app.
• Zen Payroll (now Gusto): Payroll software for small businesses.
• Zenefits: HR/benefits software with a novel monetization approach via insurance commissions.
• Skyatch: Enterprise drone platform for data capture in construction, farming, oil & gas.
• Palantir: Data analytics and enterprise software reference.
• Mixpanel: Developer-focused analytics platform referenced as an example of product-driven growth.
• Salesforce, Amazon Web Services (AWS): Cloud and enterprise software ecosystem references.
• Plan Grid, Box.net, Box (Box’s current brand): Evolution from Box.net to Box.
• Books: Crossing the Chasm, Innovator's Dilemma, Behind the Cloud.
• Industry patterns: Omni-channel retail, personalized healthcare, on-demand media distribution, and broader digital transformation in multiple sectors.

Summary of Key Takeaways from the Talk

• The enterprise software market has undergone a fundamental shift due to cloud computing, platform openness, global scalability, and user-led IT adoption.
• The cost of computing and storage has dropped dramatically, enabling scalable, on-demand solutions that were previously impractical.
• Startups should look for a wedge: a small, highly deliverable problem where you can provide an exceptional user experience and then expand.
• Asymmetries (platform-agnostic approaches, novel monetization models) can protect startups from incumbents who favor vertical integration or traditional pricing.
• A consumer DNA in the product helps with adoption and viral growth even in enterprise contexts.
• Always balance customer feedback with a strong product strategy; don’t simply build what customers say, but distill it into the best solution.
• Modularize via APIs and openness rather than heavy customization to stay scalable and adaptable across industries.
• Sales remain important; don’t rely on product alone to win enterprise deals. A consultative, domain-focused sales team is still valuable.
• The three books cited provide strategic frameworks for entering and scaling in enterprise markets.

Executive Summary

Aaron Levie argues that the enterprise software space is exceptionally ripe for startups today due to a convergence of cloud computing, platform openness, global reach, and user-led IT. Box’s journey—from a consumer-oriented file-sharing concept to a robust enterprise solution—serves as a practical case study of identifying a technology disruption, starting with a narrow wedge, and expanding within enterprises by leveraging a consumer-friendly UX, a modular platform approach, and a sales strategy that complements product-led growth. The talk emphasizes looking for technology disruptions, starting small, targeting asymmetries, engaging bleeding-edge customers, and maintaining a consumer-centric product philosophy to accelerate adoption and scale across industries. Levie also stresses the importance of planning for the new realities of enterprise IT—where the end user can drive adoption, and cloud-enabled, open platforms can enable rapid expansion beyond the largest incumbents.

Key Takeaways (Punchy)

• Cloud and platform shifts make it feasible for startups to compete in enterprise software.
• Start with a wedge; don’t try to replace the entire enterprise stack upfront.
• Platform openness and cross-platform compatibility create broad opportunities across many customers.
• Look for asymmetries in cost structures or monetization that incumbents can’t easily replicate.
• Keep consumer UX at the core to improve enterprise adoption and reduce sales friction.
• Don’t ignore sales; enterprise buys still require consultative support.
• Focus on bleeding-edge customers to shape the product and identify future markets.
• Modularize through APIs to enable customization without bespoke builds.
• The three books cited provide essential strategic frameworks for enterprise software success.
• Now is an ideal time to embark on building an enterprise software company.

Action Items

• Identify a disruptive enabling technology or trend relevant to the target industry.
• Define a wedge problem with a tight scope that can achieve a compelling ROI for a typical enterprise unit.
• Design a product with platform openness (APIs) to support cross-system integration rather than full vertical customization.
• Validate with a bleeding-edge customer and document how your product improves a core business metric.
• Build a minimal viable product that delivers superior UX relative to incumbents.
• Develop a go-to-market plan that combines product-led adoption with a consultative sales approach.
• Explore alternative monetization models or partnerships that can subsidize customer adoption (e.g., insurance commissions or other channel incentives).
• Read Crossing the Chasm, Innovator's Dilemma, Behind the Cloud to deepen strategic understanding.
• Keep the consumer DNA in UI/UX to improve adoption and feel native within enterprise settings.
• Prepare a scalable architectural plan that supports global deployment and ongoing platform enrichment.

Mental Models

• Spot Technology Disruptions: Seek big delta between current capabilities and what modern enabling technologies make feasible.
• Start Small / Wedge Strategy: Begin with a narrow, high-value use case that can anchor future expansion.
• Asymmetry Framing: Target opportunities where incumbents face structural constraints (cost, scope, platform compatibility).
• Modularize, Don’t Customize: Build a platform that can be extended via APIs rather than bespoke code.
• User-Locused Enterprise: Leverage consumer UX to drive adoption in enterprise contexts; balance with necessary governance in sales.

Glossary

• Enterprise Software: Software used by organizations to manage core business processes (HR, finance, procurement) rather than consumer apps.
• Cloud Computing: On-demand delivery of IT resources (servers, storage, databases) over the internet, typically billed by usage.
• Platform Openness: A design approach that exposes APIs and interfaces so others can build on and integrate with the product.
• Wedge Strategy: Entering a market by solving a small, focused problem exceptionally well, then expanding.
• Asymmetry: A competitive advantage that incumbents cannot easily replicate due to cost, scope, or architecture.
• End-User IT: IT decisions increasingly driven by individuals or departments, not only by the CIO.
• MVP (Minimal Viable Product): A version of a product with just enough features to satisfy early adopters and provide feedback for future development.
• RFP (Request for Proposal): A formal procurement process in which potential vendors propose solutions.

Quotes

Topics

• Enterprise Software
• Startup Strategy
• Cloud Computing
• User-Led IT
• Platform Strategy
• Market Disruption