LogoUse the Commons

Make the Move:
Transitioning Your SME

Moving from a closed, proprietary system to the digital commons requires a shift in behaviour. However, it is easier than you think. On this page you find a actionable steps that you can take to make the move.

01

The Baseline: Why Change What Works?

The digital economy is dominated by a small number of corporations. For most SMEs, relying on closed, proprietary tech giants feels like the safe, and only, option. This dependency creates a structural asymmetry that leaves your business vulnerable to price increases and policy changes.

The status quo
Closed & Proprietary
Vendor lock-in: pricing, roadmaps, and APIs change with no notice
Escalating costs: subscription fees compound with every user and every feature tier
Infrastructure asymmetry: a handful of corporations control the tools everyone else depends on
Black-box systems: no ability to audit, modify, or migrate without permission
VS
The alternative
The Digital Commons
Community ownership: shared infrastructure maintained by thousands of contributors worldwide
Already in your stack: Python, Wikipedia, Git. you use the commons every day without realising it
Shared maintenance burden: bugs get fixed collectively, not just by whoever you can afford to hire
Collaborative value creation: your contributions improve the infrastructure everyone, including you, depends on
96%
of the world's servers run on Linux, a commons-built operating system
0
lines of code needed; most SMEs are already reliant on the commons right now
02

Talking to Leadership

Organizational change starts with one employee going to their manager. If you are a developer or team lead, you need to communicate the importance of the digital commons in language that resonates with leadership.

1. Lead with ROI

Managers speak numbers. Explain that switching from proprietary software to open-source solutions can save the company thousands in development and licensing costs. Show them the concrete savings and strategic advantages of moving to the commons.

2. Frame it as Risk Mitigation

Proprietary software carries vendor lock-in. Adopting shared infrastructure distributes the maintenance burden to the community, reducing technical debt and providing more control over your technology stack.

3. Highlight Talent Attraction

Top-tier engineering talent wants to work for companies that respect the commons. Open-sourcing tools is powerful marketing for your engineering culture and can help you attract top talent.

Your Elevator Pitch

"Our business already depends on open-source software, and the next step is to move away from proprietary systems into the digital commons. We should begin shifting select projects into shared commons infrastructure, help contribute to the open-source tools we already use, and keep critical work out of vendor lock-in. I propose a 5-step, low-risk pilot to begin that transition and measure the operational and strategic benefits."

03

Your 5-Step Migration System

Change only happens through intentions and perceived control. We have broken down the transition into five risk-free steps based on proven innovation adoption frameworks.

1

Find Advantage

Discover Your Advantage Calculate the ROI and find the bottom-line benefits.
People will only act when they have the available information and can see the positive outcomes. Transitioning is about working smarter. The first step is to uncover the massive cost-savings and relative advantage of the open-source tools you already use.
Use our Dependency Assessment Tool to calculate the exact monetary value your codebase extracts from the commons. dependency.html Assess Dependency
2

Compatibility

Recognize Compatibility You are already highly compatible with the commons.
Transitioning doesn't mean starting from scratch. Your business is likely already using open-source infrastructure (like Python, Linux, or Git). By officially aligning your practices with open-source communities, you signal powerful core values like transparency and collaboration to the market.
See how other successful SMEs and organizations are already thriving in this space. cases.html View Case Studies
3

Start a Trial

Start a Trial Test safely without committing everything at once.
You do not have to flip a switch and open-source your entire company. Innovation requires "divisibility": the ability to test a new practice safely. Start testing open source alternatives for proprietary tools. Or choose a single, non-critical internal tool or script and share your work in a trial environment with a select group of external partners, before fully transitioning it to the public commons.
Not sure which proprietary tool to replace? Find open-source alternatives to get started. https://opensourcealternative.to/ Find Open-Source Alternatives
4

Manage Complexity

Manage Complexity Use licenses to set automated governance.
Licenses act as the critical bridge between your materials (the code) and your meanings (your values). Choosing the right license manages the complexity of the transition. It tells the community exactly how they can interact with your shared infrastructure without requiring constant manual oversight.
If you want maximum adoption, choose Permissive. If you want reciprocity, choose Copyleft. #licenses View Licenses
5

Communicate

Share Your Success Observability drives widespread adoption.
Public pressure and the expectations of others play a massive role in behavioural change. Once you have successfully adopted commons practices, making your migration observable to others is key. Showcasing your success helps normalize the practice for other SMEs (which can in turn benefit you) and attracts talent that values collaborative environments.
Assess how contributions can shift the entire ecosystem toward cooperation. assessment.html Run the Simulation
Discover Your Advantage
Calculate the ROI and find the bottom-line benefits.
People will only act when they have the available information and can see the positive outcomes. Transitioning is about working smarter. The first step is to uncover the massive cost-savings and relative advantage of the open-source tools you already use.
Use our Dependency Assessment Tool to calculate the exact monetary value your codebase extracts from the commons.
Assess Dependency →
04

Choose Your License

A license is the legal framework that defines how your open-source project can be used, modified, and distributed. Instead of sorting through legal jargon, select your primary business priority below to find the right framework for your infrastructure.

What is your primary goal?

Need guidance? Try the License Selection Wizard

Permissive Licenses

MIT, Apache 2.0

Permissive frameworks grant maximum freedom. They allow external developers, commercial entities, and competitors to copy, modify, and distribute your codebase freely without requiring their derived works to remain open-source.

Strategic Pros

Frictionless adoption; massive velocity; easy integration into commercial stacks; trusted heavily by modern engineering teams.

Strategic Risks

Allows rival firms to proprietary-ize your work, capture modifications, and benefit commercially without contributing back.

ℹ️ License definitions adapted from the open-source guide at choosealicense.com
05

The Commons Survival Guide

Opening your infrastructure is just the beginning. The market is tough, but real-world case studies show exactly how to overcome the four biggest threats to the digital commons.

Scaling Quality

The Problem

An influx of new contributors creates messy, inconsistent code and fragmented documentation.

The Fix

Enforce strict automated governance, mandate pull-request testing, and assign dedicated internal maintainers.

Real-World Proof: Ingres Database

When Ingres transitioned to open-source, they only survived the massive user growth by creating a dedicated organizational body to enforce documentation coherence.

Sustainable Funding

The Problem

Projects that rely purely on volunteer goodwill frequently face burnout and collapse due to lack of capital.

The Fix

Adopt a hybrid model. SMEs can pool capital to support shared tools, or redistribute commercial revenues to fund the core infrastructure.

Real-World Proof: Enspiral & Decidim

Enspiral redirects commercial profits to fund shared tools, while Decidim thrives by mixing community code with institutional city funding.

The Free-Rider

The Problem

Competitors will extract value from your open-source tools for free while you bear the maintenance costs.

The Fix

Offer "selective incentives" like premium sponsor support, exclusive access, and public reputational boosts to convert lurkers into contributors.

Real-World Proof: Simulation Data

Our Contribution Simulator data proves that leveraging public recognition tips the scale, making it mathematically rational for competitors to start contributing.

Facing Big Tech

The Problem

Highly funded commercial giants can easily drown out your project's visibility, stopping new contributor growth.

The Fix

Don't try to out-spend them; out-commit them. Focus heavily on retaining your core community members who will passionately defend the open model.

Real-World Proof: OpenStreetMap

When Google Maps aggressively pushed its commercial product, existing OSM contributors actually doubled down and increased participation to protect the project.

06

Rethinking Practices

Transitioning to the commons isn't a one-time event, it requires a shift in mindset. To move sustainably away from the competitive, closed model, three pillars must shift together. Changing only one is not enough.

Pillar 01

Meanings
Values & Norms

Shift your team's mental model away from proprietary ownership as the default. The commons runs on norms of transparency, peer-review, and collective stewardship. These values must be internalized and practiced, not just stated in a policy doc.

In practice: Hold an internal retrospective asking "what code are we using that the community would maintain for free?" Often the answer surprises teams.
Pillar 02

Materials
Tools & Infrastructure

Openness requires the right physical infrastructure. You need collaborative platforms, public version control, and appropriate licenses that legally enable sharing without creating risk for your core business.

Start here: Create a public GitHub repository for your first open project. Use it to share a non-critical internal tool or script with the community. This simple act of sharing in public is the first step toward building a collaborative infrastructure.
Pillar 03

Competences
Skills & Confidence

Managing a public project is a distinct skill set. Your team needs to develop the confidence to engage with external contributors, triage community issues, and communicate decisions transparently in public spaces.

Build it gradually: Assign one team member as "community manager" for your first open project. One person taking ownership of the transition process makes it less overwhelming and more likely to succeed.

Ready to see where you stand?

Use our free Assessment tool to measure your current dependency on the commons and get a personalised transition plan in minutes.