I m the founder of http://Trends.vc. A newsletter and community helping founders discover new ideas and markets. Ask me anything about nomading, masterminds, habits or community building. I'll be answering all questions on Wednesday, the 3rd of August
Art = the expression or application of human creative skill and imagination, producing works to be appreciated primarily for their beauty or emotional power.
I m Rosie Sherry and I ve been building communities for quite some time! I m here to answer anything and everything I can about community building. Here are some of the things I ve done: - I started back in 2006 with a local Girl Geek Dinner Meetup
- I founded Ministry of Testing, an indie, 7 figure revenue and profitable community of practice for software testers. I handed this community over for someone else to run (I did not sell it).
- I led the community at Indie Hackers for a couple of years
- I started Indiependent, a small community for indie founders where people get kicked for inactivity
- I ve been writing about community at Rosieland (covering community growth, flywheels, Minimum Viable Communities, Community Discovery, and much more!)
- I breathe, eat, sleep community Ask me anything about community, I can cover things like:
- Tools to use, or not
- Community on a budget
- Community as a business
- Minimum Viable Communities
- Community Discovery
- Community Growth & Flywheels
- Building a sustainable community
- Community trends
- Why so many people are getting community wrong! I'll be answering questions on the 7th of September!
The users who email you angry or leave detailed feedback are actually doing you a favor even if it hurts. You can learn from them.
The real ghosts are the ones who quietly downgrade, cancel via the billing portal, and ignore every single automated exit survey you send. You're left staring at a dashboard with zero qualitative context on why they left.
for SaaS builders: what creative strategies or prompts actually get silent churners to tell you what went wrong?
early on whenever a paying user asked for a specific feature, my immediate reaction was to build it to keep them happy. Our roadmap became a messy patchwork quilt of random requests.
Eventually, I realized those feature requests were often band-aids covering up a confusing core UX or a deeper workflow mismatch. Building what they asked for didn't even stop them from churning later.
for founders managing small teams: how do you filter out the noise of individual feature requests and stick to your core product vision?
I love @Cursor. It's enabled me to build (vibe code) so many web apps, sites, extensions, and little things quickly that 1. bring me joy and 2. help me with work or realize personal projects. However... I'm seeing a TON of movement around @Claude by Anthropic's Claude Code. I haven't personally tried it but it's apparently insane (and can also be expensive?) I'm curious. Should I switch? What are you currently using? Or do they both have their own use case. I right now like cursor because I can build directly in a GitHub repo or locally and it helps me learn my way around an IDE. Looking forward to hearing everyone's thoughts!
For the longest time my weekly dopamine hit was watching the signups counter tick up. I thought traction meant volume.
Then we started tracking 7-day and 30-day active usage, and the reality check was brutal. We were pouring water into a leaky bucket, celebrating every new registration while users slipped away silently within 48 hours.
For founders who survived this transition: what specific metrics or milestones forced you to stop celebrating signups and actually fix your activation loop?
