Partner with us
LS2 develops, hosts, and maintains the software. You bring it to your network — under a public mandate or as a commercial offering. Capital-light for you, product-focused for us — and your member organizations get tools built for their reality.
The model
A simple division of labor
You have a network that trusts you — member institutions, public bodies, schools, or the education and government clients you already serve. We have a product team that ships and operates SaaS used by 50+ institutions and over 100,000 students. In an LS2 partnership, each side does what it does best: we build, host, secure, and support the software; you bring it to the organizations you serve. You don't hire developers, run infrastructure, or carry maintenance risk. We don't build a distribution channel in your market — you already are one.
Two ways to partner
Distribute what exists, or co-create what's missing
1. Distribute our existing solutions
Bring proven products to your network today: Teameo (class management on Microsoft Teams), Classeo (class management on Moodle), Calendo (schedule sync to Teams, Outlook, and Google Calendar), and Archiveo (Microsoft 365 records archiving for public bodies). All four are in production — you distribute, we deliver. Open to public-sector organizations and to private companies serving education or government, such as resellers, integrators, and Microsoft Partners.
2. Co-create a new SaaS
Your network shares a need no product covers? We scope it with you, build a pilot together, and validate it with a first group of your member organizations. Once the pilot proves itself, you bring the product to your market — with LS2 developing, hosting, and maintaining it behind the scenes. This track is reserved for education and government organizations with a mandate and a network.
Proof the model works
Archiveo: built by LS2, distributed by a partner
Archiveo is the partnership model running in production today. LS2 develops, hosts, and maintains the product; a government archives institution distributes it to the public bodies in its network, which must transfer records to the national archive at the end of their legally mandated retention periods. The institution brings the mandate, the domain authority, and the relationships; LS2 brings the software and operates it. Neither side could deliver this alone — together, public bodies get a compliant archiving workflow without either organization stepping outside its strengths.
What each side brings
A partnership with clear roles
LS2 brings
- The product and its roadmap
- Hosting and operations (99.9% uptime track record)
- Technical support
- Security and compliance experience (Law 25, GDPR)
You bring
- A domain mandate your network recognizes
- A distribution network of organizations
- Market knowledge — the need, the language, the constraints
- The relationship with your network — commercial or mandate-driven
Questions partners ask
Partnership FAQ
Who qualifies as an LS2 partner?
It depends on the track. Distribution is open to education or government organizations — ministries, agencies, archives and library institutions, consortiums, school networks, associations — and to private companies serving those markets, such as resellers, integrators, and Microsoft Partners. Co-creating a new SaaS is reserved for education or government organizations with a mandate and a network of institutions that share the need.
How does a co-creation pilot start?
With a scoping conversation: you describe a need your network shares, we assess whether it fits a SaaS model. If it does, we define a pilot together — a working product deployed with a first group of organizations from your network. The pilot validates the product and the distribution model before a wider rollout.
Who owns what?
LS2 owns, hosts, and maintains the product. You own your client relationships and your distribution channel. The commercial terms of each partnership — branding, pricing to your network, revenue model — are defined in the partnership agreement.
What timeline should we expect?
Distributing an existing solution can start as soon as the agreement is signed — the products are live and in production today. Co-creating a new SaaS takes longer: scoping, then a pilot, then market rollout. The pace depends mostly on how quickly your network can engage.
Tell us about your network
One email is enough to start the conversation. Tell us who you are, who your network serves, and whether you're thinking distribution or co-creation — we'll take it from there.
Write to partners@ls2.io