Liz Avrutov’s Post

3 steps to start a community: 1. Setup a platform 2. Meet core users to onboard them 3. Regularly post conversation starters Another great video from Jono Bacon. https://lnkd.in/eRg3dgQu #communuty #communityengagement #communutybuilding

Know what gets a community founder like me excited? Great questions from new community builders. How long should it take to launch? What do I need in place to throw the switch? How do I pay outside presenters? Questions like these show people are serious about their launch, really thinking it through. My goal: Get some folks launched by Jan-Feb '25! These and many more questions get answered live tomorrow, on the official first Community Growth Academy Q&A for the first initial paid member cohort, tomorrow. I'll be tuning in from the RV, of course. Recent photo of hubby & me near Santa Cruz for interest. 😉 Nothing better than running a digital biz from...wherever. #vanlife P.S. - Are you an expert who could earn through paid community? Check out Community Growth Academy on Skool.

💥 Ready to Build and Monetize Your Community? 💥 I’ve created a FREE step-by-step checklist to help you fast-track your journey to a thriving, profitable community. Whether you're just starting or need a boost, this checklist gives you the exact steps you need to start generating real income from your community. 🎯 Ready to get started? Download it here: https://lnkd.in/gfG7pSWJ Get the Free Checklist

Community management tools every freelancer should try out: Orbit Orbit is a community growth platform that scales the impact of your company's most valuable resource - your community 🚀   They are a Community Management honoree for Contra’s 2024 Creator Tools Awards!

What I learned when my community launch flopped… I was told: “If you build it, they will come.” Spoiler: nobody came 🫠 In July-August, I poured weeks into building my community. I ran a program with a group of 10 multilingual creators. Slides, frameworks, workshops — built it all out. And it was brilliant, don’t get me wrong. The plan was then to open a community in September. But when I went to launch in Q4… crickets. Because I made a mistake. Building first, promoting second. The lesson I learned the hard way ⬇ Creator misconception: It’s not about what you build. It’s about who’s excited to join before you begin. Sell the idea before you create the solution. This is working smarter – and it’s the fastest way to: ✅ save time ✅ validate your offer ✅ avoid unnecessary work I’ll learn from mistakes for my January re-launch by: 1️⃣ Creating a roadmap to show the transformation 2️⃣ Starting promo early to build curiosity and excitement 3️⃣ Incentivising early adopters to join (discounts, bonuses) Building something amazing is important. But getting people to care about it?  That’s what creates energy. Energy = motivation Motivation = action No energy, no action.  Lesson learned 💡 What’s 1 piece of advice you found to be untrue? P.S. I'd rather make a mistake and share than pretend I get everything right always. Often, I get more wrong than right.  But I always learn from my mistakes 😉

🌟 Your voice matters! 🌟 Here's what our amazing users have to say about Society Notebook and how it simplifies maintenance collections, arrears management, and more! 🚀 We’re committed to making community management seamless and efficient for everyone. 💡 Have feedback for us? We’d love to hear from you! ⭐ Rate us, share your thoughts, and help us grow stronger together. hashtag #ClientFeedback #SocietyNotebook #CommunityManagement #CustomerLove #EfficiencyRedefined #YourOpinionMatters

💸 Turn Your Community into a Revenue Stream! Struggling to turn your community into real, consistent income? You don’t have to guess anymore. My FREE checklist gives you the exact steps to build a profitable, engaged community that works for YOU. ✅ It’s simple. It’s actionable. It works! Download Your Free Checklist Here

Building a community in Web3 is just for a select few in your team. Or rather, is it for everyone? It's important to understand that all team members should be involved in the community-building process and it's not for a select few like community managers, or social media managers. The success of building a Web3 project heavily relies on the community base. As a Founder, cultivating a strong community that believes in your project will result in a robust user base. The focus should be on creating an entire ecosystem, not just products, and everyone must be part of this process. If your team doesn't fully embrace community engagement and recognize its power, progress may be limited. Every team member needs to participate in the community-building process, no one should be exempt from contributing. When the community sees everyone dedicated to addressing questions and feedback, it builds long-term trust. POV: How do you think everyone on the team can contribute to community building?

Relaunching your project shouldn't be the reason your users start to lose trust in you. It doesn't matter what the reason is for re-launching, that shouldn't make you silent on them for weeks and then months. And in all of this, the loyal ones still can't believe what's happening because their trust in you is one hundred. A founder I started working with last year as the community manager and who has already gained the trust of the community decided it's time to relaunch this year without even informing the community until I asked in DM and he told me he's going to relaunch. This is a community that has always been thriving even during times when the team is asleep and there has to be a mod on standby during those hours. This is also a project that releases weekly episodes on its YouTube channel which has gotten the interest of the whole community. But as the founder, your bi-weekly AMA sessions started to turn into monthly and then none at all till when the community began asking questions about your inactivity and negligence. There's only so much the community manager can do. If my role is to bridge the gap between the project and its users, then how do I continue to communicate with the community when the founder isn't responsive? As founders, regular communication with your team and community builds trust and that trust can only be broken when you lose out on communication with them. Do you want to relaunch? Then communicate! Do you want to merge with another project? Then communicate! The only way your community can continue to root for you is to communicate with them about your plans. _________ My name is Rachel Edeh and I help founders in web3 build a thriving community or manage one.