I made a BOLD move last week in my Skool community, and here's what happened: 02 Feb: 280 members 08 Feb: 383 members Growth: +103 members (+36.8%) Period: 6 days Watch this 28-min video about the little cool experiment and 'switch' I did — and see behind the scenes what happened (and learn the 3 implementation tips) I also cover these few topics: - Why I switched my community from 'paid' to 'free' - How do I grow my free community organically - What's the best lead magnet for free community - How to use the 'membership questions' to filter member request - How to maintain high standard/quality of a free community - How to optimize the About page for expectation/quality - The key to getting traction via organic content creation - And much more Let me know your thoughts - let's discuss and collaborate. btw I'll repost this in The Skool Game community too - Check out the post here

Hi guys, I hope he doesn't mind me doing this lol ....but quietly he got a bit of a promotion so to speak, and a title change without telling us. Drop a GIF and a kind word for our Sid, man of the hour ✊. Sid is now the man, "Community Lead @ Skool" ... in case you didn't notice it 🙉. You have to keep your wits about you to find the little gems to encourage people you love. ...so thanks my man, for all the help and for taking the leap from being a data analysis guy into a community management guy. 👍 ...that must have been shift work-wise, but I am sure as an ENTJ you like hanging out with us, we like hanging out with you bro! ✅ And good to see you take your weekends off not like us crazy Skooler. Cheers

I'm seeing the same request/pattern/problem emerge over and over again (it comes in various forms but many point back to the same root cause) — the ability for existing members in a free Skool community to upgrade to paid (one-time purchase to unlock course, or start a monthly subscription) ✅ this allows free + paid in one group ✅ seamless monetization ✅ without asking members to leave (or remove them) and rejoin Having multiple groups is not ideal (especially for beginners/new small community) for many reasons - unnecessary complexity - too few members to make sense - distraction to manage 2 groups - destroy the dynamic of existing community - double expenses ($99 x 2) or more - bigger resistance/analysis paralysis for newbies to start => slower adoption If this feature is available: - so many people would have migrated their community here (flexi payment/monetization) - so many newbies would actually start (and not be in analysis paralysis) This might already be on the product roadmap, but man people are screaming out loud for this one lol personally, I'm hoping for the drop of this feature asap (fingers crossed 🤞) Thoughts?

Oh man, I've been so excited about moving to Skool. I LOVE SO MANY THINGS HERE. But I'm an artist, and I teach people how to paint. I am about to move 1500 people here, but... When you share an image in your post, it looks TINY!!! This really sucks for ANYTHING art-related like what we do. I can't express how much I need this. We are an image-based community - Is there anything that can be done??? I know if you click, and then click again, it shows it big. But for ENGAGEMENT, it stinks for us. Will you please make the images bigger on a post? I may have to rethink our being here if not... Thank you!

I understand that this has been requested multiple times, and it's in the backlog pipeline. But I just wanna +1 here so the team can grasp the demand of this request. And some context of why some user wants this. Context: For our community with higher-level clients (with some sort of DFY elements), I'd wish to have the group chat function in Skool so my team, myself, and the client can discuss the DFY stuff in that group chat, it's semi-personal which that particular client might not want to disclose publicly in the group community, but only want to disclose with our team. But still, for everything else, that client still can post and interact in the group community. To me, it's not one way or another - there are more nuances and use cases. It doesn't mean if we want to encourage group interaction in the community, then we cannot do group chat. -Community (public, overall group) -Group chat (semi-private/exclusive to smaller subgroups for certain objectives) -1on1 DM (private) It's just my take, as I'd like everything on Skool (that's why we're here in the first place), or else now I have to figure out where else should I conduct this client-team 'semi-private' group interaction, I might need another tool like Whatsapp group, slack, discord, or something. And that in turn breaks the initial intention of Skool to have all engagement in one place. Can you see how that's going? Just my take. Love the platform, @Sam Ovens, and the team anyways.