About ChoirPower

Built for modern choir collaboration

ChoirPower helps choirs plan, rehearse, communicate, and share music in one connected workspace.

The Product

ChoirPower combines member management, repertoire, event planning, chat, and media workflows so choirs can reduce admin overhead and focus on musical progress.

The platform is designed for both leadership and members, with role-based capabilities that keep day-to-day collaboration clear and structured.

The Company

ChoirPower is built by a product and engineering team focused on practical digital tools for ensemble and community organizations.

We work closely with real choirs and iteratively improve the platform based on operational needs and feedback.

The Team

Our cross-functional team includes product design, frontend/backend engineering, operations, and support. We prioritize reliability, usability, and transparent communication.

Jonas Lehtinen portrait

Jonas Lehtinen

Founder, CEO/CTO

Jonas leads product direction and architecture, working closely with choirs to keep planning, rehearsal, and communication workflows aligned in one platform.

Amalia Strauss portrait

Amalia Strauss

CFO

Amalia leads financial planning, pricing strategy, and operational forecasting, ensuring ChoirPower grows sustainably while staying accessible for choirs of different sizes.

Sofia Bergman portrait

Sofia Bergman

Customer Success Manager

Sofia supports onboarding and day-to-day adoption with conductors and admins, helping teams configure ChoirPower quickly and build practical routines.

Primary role

Choir operations workspace Combines public marketing pages with authenticated choir coordination and collaboration views.

Shared stewardship

Prosper Foundation

ChoirPower is one of the mounted SaaS solutions in the SaaSpawn ecosystem. Its About surface therefore needs to connect product-specific narrative with the broader Prosper-aligned stewardship model.

Declaration

Declaration and commitments

The product-specific About story remains intact above this block. This supplementary section adds the consistent licences and standards disclosure now expected across the ecosystem.

Licences & standards

External dependencies, derived assets, and open standards

Every item should link to the relevant licence file, project page or repository, and contribution path so provenance and participation stay visible.

Application stack 5 items

Core open-source frontend stack used across ChoirPower web surfaces.

Feature libraries 8 items

Open-source libraries used by the ChoirPower public and member-facing frontend.

Open standards 3 items

Standards and de-facto browser norms that ChoirPower depends on directly.