adds the business model section of the guide

Author: eiso

README.md

@@ -11,6 +11,7 @@ We try to put as much information here as possible, in the rare cases that a top
   * Roadmap
   * [Culture](general/culture.md)
   * [Product](general/product.md)
+  * [Business Model](general/business_model.md)
   * [Organizational & Legal Structure](general/organizational_legal_structure.md)
   * [Investors, Board of Directors and Advisors](general/investors_board_advisors.md)
   * Leadership

general/business_model.md

@@ -0,0 +1,56 @@
+Business model
+---------------
+
+This section of our guide functions as a snapshot of our latest thinking related to the business model of source{d}. This is a live document that will continue to grow as we learn more.
+
+## Context related to our culture
+
+> ‘We want to always remain a company that does everything with the individual developer in mind. Not the developer as an employee of a company, but the developer as an individual in the developer community.’ 
+
+source: [source{d}'s culture document](culture.md#for-developers)
+
+At source{d} we pride ourselves on always choosing to do what is best for the individual developer in the community. This principle is shared by our team members, our management team, the founders, our [advisors](investors_board_advisors.md#advisors), [board of directors](investors_board_advisors.md#board-of-directors) and [shareholders](investors_board_advisors.md#shareholders)).
+
+When thinking about our business model, the most important question for us is: 
+
+**By choosing to monetize in this manner, are we still doing what is best for the individual developer in the community?**
+
+An example of a situation where we wouldn't be, is when for instance as a company we would choose to make a core feature that would benefit the individual developer not under an open-source permissive license. 
+
+An example of a situation where that would be okay is if the feature truly only benefits an enterprise use case.
+
+## Background
+
+Joseph Jacks (one of our advisors) maintains the [Commercial Open Source Software Index](https://docs.google.com/spreadsheets/d/17nKMpi_Dh5slCqzLSFBoWMxNvWiwt2R-t4e_l7LPLhU/edit#gid=0) where he tracks all companies built around open-source software that have >100mm annual revenue. 
+
+Almost every single one of these companies follows what is called the [open-core model](https://en.wikipedia.org/wiki/Open_core). 
+
+> Open core is a business model for the monetization of commercially produced open-source software. ...primarily involves offering a "core" or feature-limited version of a software product as free and open-source software, while offering "commercial" versions or add-ons as proprietary software.
+
+It's important to note that while often proprietary means closed source code, it doesn't have to be. You can have your source code open to the world but with a restrictive license that for instance can only be used for academic research.
+
+**Side-note:** as an organization whatever we do, we should never write/implement our own open source licenses, the community has already done a great job of creating and vetting a selection of licenses that are the status quo.
+
+## source{d} business model
+
+### Who do we want to target as customers?
+
+To make sure we stay true to doing what is right for individual developers in the community, we do not want to charge any individual users.
+
+We don't believe startups and SME's make up a large enough market to build a sustainable company in the long term. The amount you can charge to small organizations pales in comparission to what you can charge enterprises (value add * # of developers). At the same time, selling to SME's is almost always a [SaaS](https://en.wikipedia.org/wiki/Software_as_a_service) business.  While there are success stories of this, such as [Travis CI](https://travis-ci.com/) we don't think it's the right route for source{d}. 
+
+**source{d} focuses on enterprises as its customers**
+
+From the point of view of value we can add to an organization, large scale analysis & ML on top of source code shines when there is a large amount of code and a large number of developers.
+
+### Enterprises as customers
+
+Today every large organization has become/is becoming a software company. The number of software developers in what were once considered traditional businesses, such as banks and airlines, is often already in the 1,000s or 10,000s.
+
+There is a growing number of challenges that enterprises face within their [Software Development Life Cycle (SDLC)](https://en.wikipedia.org/wiki/Systems_development_life_cycle) that can start to be tackled with large scale language-agnostic analysis of their source code, and trained ML models.
+
+### Business model meets our technology
+
+The current model that we are exploring is to have single node versions of our technology stack be fully open-source under a permissive licenses such as [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) but multiple nodes of our stack that allow distributed computing over a large amount of repositories with a large number of concurent users to be under a restrictive license. 
+
+This would allow us to charge enterprises who are in need for a large number of nodes but not disadvantage individual developers or smaller organizations to take advantage of our technology.