Circle.so
Purpose of this section
Document the rationale for Circle as CSI’s community infrastructure.
Platform Requirements for CSI
Define needs before naming the tool.
Requirements CSI must meet:
Host free and paid education
Support professional moderation and safety
Enable structured learning alongside discussion
Scale nationally without fragmenting experience
Support future specialization tracks
Why Circle.so Fits CSI
Position Circle as infrastructure, not software.
Core justifications:
Combines community, courses, events, and content in one system
Supports both free access and paid specializations
Enables emotional safety through moderation, guidelines, and space design
Designed for member transformation, not algorithmic engagement
Strategic Benefits to CSI
Frame benefits at the initiative level, not feature level.
Suggested benefit categories:
Educational coherence: one home for all CSI learning
Operational simplicity: fewer systems, clearer governance
Trust and legitimacy: professional container vs social platforms
Scalability: national reach without losing human structure
Long-Term Fit
Explain why this choice supports CSI’s future, not just launch.
Points to cover:
Ability to layer specializations over time
Support for in-person event integration
Capacity to evolve without replatforming
Alignment with CSI’s mission-centered, non-extractive design
Last updated