The plan marketplace looks like GitHub.
Who This Matters To (And Why)
Critical: Architect,Developer,GC. These parties make or lose money directly based on this thesis.
Important: Engineer,Investor,Banker. These parties execute decisions shaped by this thesis.
Context: City,Inspector,Broker. These parties need to understand it to avoid friction.
Highest typology impact: Multifamily,Office,Industrial,Mixed Use. Lower impact: Hotel,Retail.
The plan marketplace looks like GitHub. Plans are repos. Typologies are forks.
How It Shapes Development
The plan marketplace looks like GitHub because GitHub is a marketplace for reusable code: a place where developers share solutions to common problems, where solutions are versioned and forkable, where quality is signaled by usage count and contributor activity, and where the best solutions propagate rapidly across the ecosystem. A building plan marketplace would be the same thing for building designs: a place where architects share proven floor plan configurations, where configurations are versioned and adaptable, where quality is signaled by construction performance data, and where efficient solutions propagate across the industry instead of being reinvented project by project.
The GitHub model resolves the attribution problem that has prevented plan sharing. Open source software licenses allow reuse with attribution requirements. A building plan marketplace with equivalent licensing would allow an architect in Dallas to adapt a proven multifamily floor plate from an architect in Seattle, with the original designer receiving credit and potentially a licensing fee. The adaptations are tracked as forks. The original design receives credit for every building it influences. This is not a new business model — it is the existing open source software business model applied to building design.
Stars and forks are quality signals in the GitHub model. A repository with 10,000 stars and 500 forks has been vetted by a large community of developers who found it useful. A repository with 3 stars and 0 forks may be unused for good reason. A plan marketplace would use equivalent signals: how many buildings have been built from this plan type? What were the construction costs relative to estimate? What is the occupancy rate? Plans with strong construction and operating performance records propagate. Plans that look good in rendering but perform poorly in construction get fewer builds and accumulate negative signal. The marketplace self-selects toward proven solutions.
The liability barrier is the main obstacle. An architect whose plan is used in another building without their direct supervision has traditionally been exposed to liability for that building's performance. This exposure has suppressed plan sharing throughout the industry's history. The GitHub model addresses this through licensing: the license specifies the conditions of reuse and explicitly limits the original author's liability for adaptations. A building plan marketplace license that specifies the engineer of record for each adaptation bears responsibility for that adaptation would replicate the liability structure of open source software. The original designer contributes the starting point. The local engineer takes responsibility for the implementation.