SCaLE 17x There is [Still] NO Open Source Business Model
0 likes594 views
The document discusses the economics of open source software, emphasizing that it is a collaborative effort and lacks a definitive business model, highlighting historical milestones and community dynamics. It contrasts projects with products, noting that projects foster community engagement while products focus on customer transactions, leading to different expectations and success metrics. The narrative includes examples from notable companies like Red Hat to illustrate the evolution and disruption within the open source ecosystem.
![SCaLE 17x There is [Still] NO Open Source Business Model](https://image.slidesharecdn.com/noopensourcebusmodels-scale17x-190329041107/85/SCaLE-17x-There-is-Still-NO-Open-Source-Business-Model-9-320.jpg)
![SCaLE 17x There is [Still] NO Open Source Business Model](https://image.slidesharecdn.com/noopensourcebusmodels-scale17x-190329041107/85/SCaLE-17x-There-is-Still-NO-Open-Source-Business-Model-21-320.jpg)
![SCaLE 17x There is [Still] NO Open Source Business Model](https://image.slidesharecdn.com/noopensourcebusmodels-scale17x-190329041107/85/SCaLE-17x-There-is-Still-NO-Open-Source-Business-Model-22-320.jpg)
![SCaLE 17x There is [Still] NO Open Source Business Model](https://image.slidesharecdn.com/noopensourcebusmodels-scale17x-190329041107/85/SCaLE-17x-There-is-Still-NO-Open-Source-Business-Model-24-320.jpg)
SCaLE 17x There is [Still] NO Open Source Business Model
- 2. Open Source Software is about Engineering Economics
- 3. There is NO Open Source Software Business Model
- 4. Freeloaders means you’re doing it right!
- 5. Open Source Software is about Engineering Economics
- 6. Collaboratively-Developed Liberally-Licensed Software is about Engineering Economics
- 7. 1950 1960 1970 200019901980 2010 Code sharing At Princeton IAS in late 1940s IBM “SHARE” Conf & Library Begins 1953 DECUS Conf & Library Begins 1962 MIT Project Athena Begins 1983 1BSD Released 1977 AT&T Shares First UNIX tapes early-70s Free Software Foundation Launches 1985 2nd DoJ vs IBM begins “Software Bundling is Anti-competitive” 1969 IBM response is to unbundle HW, SW, & services pricing 1st DoJ vs IBM Consent Decree “Hardware Bundling is Anti-competitive” 1956 Open Source Definition 1998 USENIX Begins 1975 Linus Releases Linux 1991 Apache httpd Released 1995 Apache Software Foundation 1999 OSDL Forms 2000 OSDL Re-forms as Linux Foundation 2007 U.S. Congress Adds Computer Software to Copyright Law 1980 GCC 1987 emacs 1975 We’ve collaborated on software since we’ve written software Writing good software is hard work
- 8. 1950 1960 1970 200019901980 2010 Code sharing At Princeton IAS in late 1940s IBM “SHARE” Conf & Library Begins 1953 DECUS Conf & Library Begins 1962 MIT Project Athena Begins 1983 1BSD Released 1977 AT&T Shares First UNIX tapes early-70s Free Software Foundation Launches 1985 2nd DoJ vs IBM begins “Software Bundling is Anti-competitive” 1969 IBM response is to unbundle HW, SW, & services pricing 1st DoJ vs IBM Consent Decree “Hardware Bundling is Anti-competitive” 1956 Open Source Definition 1998 USENIX Begins 1975 Linus Releases Linux 1991 Apache httpd Released 1995 Apache Software Foundation 1999 OSDL Forms 2000 OSDL Re-forms as Linux Foundation 2007 U.S. Congress Adds Computer Software to Copyright Law 1980 GCC 1987 emacs 1975 Copyright Law forced almost 20 years of license experiments to allow us to keep sharing DEC Ultrix 1984 SunOS 1983 OSF/1 1992 Red Hat 1993
- 10. Choosing a License is a Social Contract License reciprocity is not about software freedom; it’s a community decision.
- 11. Collaboratively-Developed Liberally-Licensed Software The Open Source Definition Engineering Economics
- 12. Collaboratively-Developed Liberally-Licensed Software is about Engineering Economics
- 17. Build vs. Buy
- 18. Build vs. Buy vs. (Borrow & Share)
- 19. Open Source Software is about Engineering Economics
- 23. If your core competency is delivering software, then the software is: • Core value proposition to customers • Complement value add to the core value proposition • Context (i.e. non-core competency)
- 25. New market Disruption • Is there a large group of people who historically have not had the money, equipment or skill to do this thing for themselves? – OR – • To use the product or service, do customers need to go to an inconvenient, centralized location? Low-end market Disruption • Are there customers who would be happy to purchase a product with less (but good enough) performance? – AND – • Can we create a business model that enables us to earn attractive profits at the discounted prices? • Is the innovation disruptive to ALL of the significant incumbent firms in the industry? • If it appears to be a sustaining innovation to one or more significant players in an industry, then the odds are stacked in that firm's favour, and the new entrant unlikely to win. Then The Innovator’s Solution, Clayton Christensen
- 26. If your core competency is delivering software, then the software is: • Core value proposition to customers • Complement value add to the core value proposition • Context (i.e. non-core competency)
- 27. Building a project community in context spaces: • Validates the approach to a problem • Demonstrates expertise that can be used in recruitment • Demonstrates committed values to collaboration amongst developers that further recruitment goals
- 28. Building a project community in complement value-add spaces: • Creates stickiness/inertia for the core value. • Creates experts, advocates, and evangelists around the technology • Hardens the complements with new configurations and contributions • Captures direct value to the complements (indirectly to the core) • Is possibly disruptive to competitors
- 29. But – publishing your core value proposition under an open source license: • Makes potential partners into competitors • Allows savvy IT consumers to avoid becoming customers • Creates confusion for the sales and marketing team
- 30. If you invest in building community around the project that sits on your core value proposition: • You create tension when competitors and partners and advanced IT users contribute value they want in your core value proposition. • The power of innovation capture in community around a complement becomes the problem of innovation dilution in your core value proposition. • You accelerate the creation of a community of early adopting users that aren’t interested in paying for your software, instead of creating early adopting customers that understood your product solution sufficiently to give you money.
- 31. Projects are not Products
- 32. Community is not a Customer
- 33. Projects are interesting buckets of technology developed collaboratively by like-minded engineers
- 34. Projects are interesting buckets of technology developed collaboratively by like-minded engineers Products solve customer problems and money is exchanged for perceived value
- 35. Projects have communities Communities have time and no money
- 36. Projects have communities Communities have time and no money Products have customers Customers have money and no time
- 37. • Will contribute time to solve their problems • Look to community and project for solutions • Community wants transparency, meritocracy, and agency • Need guidance and tool support • Become technology advocates • Become knowledgeable experts • Make your solution sticky • They want to buy something • Look to the product to solve their problems • Customers have expectations based on a cost • Community/project is a test for product • May participate in community Community Customer vs
- 38. Community vs Partner • Will contribute time to solve their problems • Look to community and project for solutions • Need guidance and tool support • Become technology evangelists • Become knowledgeable experts • Make your solution sticky • They want to co-market products • Look to the product to cross-sell • Partners have contracts defining business relationships around products/services • Community/project is a test for product • May participate in community
- 39. Freeloaders means you’re doing it right!
- 40. In the World of Atoms: You choose your neighborhood for very personal reasons
- 41. Three Sorts of Neighbours in Your Community The people that simply want to live there ….
- 42. Three Sorts of Neighbours in Your Community The people that simply want to live there …. The people that report potholes and trash, etc. ….
- 43. Three Sorts of Neighbours in Your Community The people that simply want to live there …. The people that report potholes and trash, etc. …. The people that organize the block party, pick up trash, etc. ….
- 44. Three Sorts of People in Your Project Community The people that simply want to use the software The people that report bugs, offer ideas for features, etc. The people that contribute code, documentation, use cases, etc.
- 45. Rules of Thumb and Orders of Magnitude For every 1000 users, … … a 100 will file a bug, … … out of which 10 give you a patch, …
- 46. Rules of Thumb and Orders of Magnitude For every 1000 users, … … a 100 will file a bug, … … out of which 10 give you a patch, … … out of which 1 actually read your contribution guidelines.
- 47. Three On Ramps for Community Building • How do you encourage people to use your project? (Because that’s where you’ll find your developers) • How do you encourage developers to experiment? (Because these are your future contributors) • How do you encourage developers to share their work? (This is the growth & success of your software)
- 48. “The customer didn’t want a quarter inch drill. What they wanted was a quarter inch hole.” Theodore Levitt
- 49. Parking your identity brand on any open source project you own, instead of the product/solution your customers buy, creates confusion for your messaging to customers.
- 50. Open Source Software is about Engineering Economics There is NO Open Source Software Business Model
- 51. Customers versus Community (Money vs. Time; Expectations are different; Conversations are different)
- 52. Customers versus Community (Money vs. Time; Expectations are different; Conversations are different) Partners versus Community (Don’t mix business with community)
- 53. Customers versus Community (Money vs. Time; Expectations are different; Conversations are different) Partners versus Community (Don’t mix business with community) Products versus Projects (Success metrics are different; OKRs and KPIs are different)
- 54. A Story of Red Hat in Three CEOs
- 55. 1994 1999 2008 A Story of Red Hat in Three CEOs
- 56. Last Quick Examples … Kubernetes is a project; AKS and GKE are products OpenStack is a collection of projects; Helion and RDO are products Linux is a project; Fedora is a distro project; RHEL is a product
- 58. Conversion Rates
- 60. Conversion Rate Myths 1:1000 (MySQL Inc.) ~1:100 (JBoss) 1:10 (Red Hat)
- 61. What Business Ratio Changes 2 Orders of Magnitude between Companies in a Market?