---
type: "article"
title: "The problem with building a flagship community"
summary: "A single massive audience is not the goal. Here is what I am doing instead to make Commune actually grow."
newsletter: "The Weekly Shift"
newsletter_handle: "franmendez"
newsletter_url: "https://usecommune.com/n/franmendez"
author: "Fran Mendez (@fmvilas)"
published: "2026-03-13T12:01:00.000Z"
canonical_url: "https://usecommune.com/n/franmendez/a/the-problem-with-building-a-flagship-community"
markdown_url: "https://usecommune.com/n/franmendez/a/the-problem-with-building-a-flagship-community.md"
chat_url: "https://usecommune.com/n/franmendez/a/the-problem-with-building-a-flagship-community/chat"
source_url: "https://newsletter.fmvilas.me/posts/the-problem-with-building-a-flagship-community"
body_source: "imported"
likes: 3
replies: 2
body_words: 441
---

# The problem with building a flagship community

![The Weekly Shift](https://embed.filekitcdn.com/e/tppsnKSSV6RtcQVLeDZHT8/5nEuhXaXN7FANZ4f1qdrrM?auto=)

This week I have been super focused on strategy for Commune. For a while, I thought having a flagship community on the platform to use as a rock-solid case study would be a really great idea.

I played around with creating a paid community and newsletter to help people become unrejectable. It would be a space with periodic webinars from different folks teaching you how to improve your skills, share your work, and make jobs find you instead of the other way around. Building this would also give me a great excuse to test new Commune features like private groups and monetization.

After a bit, I completely discarded the unrejectable idea. I have my book, Shift, about to launch, so it made more sense to focus on that. Building a community around Event-Driven Architectures (EDA) and Shift seemed absolutely perfect. Plus, most of you already know me from my work on AsyncAPI, so it felt like a totally natural fit.

The problem is that neither of these ideas actually aligns with what Commune needs right now. Let me explain. For Commune to really work, we need a high density of communities. We need more newsletters and more people so cross-pollination naturally happens. We do not need a ton of people crammed into one single group. The goal is not a single massive audience, but rather a network of many different communities related to the same topics of interest.

Do not get me wrong here. I am not saying those communities are bad ideas. I only considered them because I genuinely believe they are useful. But running them does not push my main goal forward, which is making Commune grow.

So I decided to step back from all those side projects for now. I am fully focused on Commune. I am rolling up my sleeves and doing the not-so-glamorous job of reaching out to people one by one to get them on board. That is what will actually push this whole thing forward.

I am starting with my own network, as you have probably noticed. My network is mostly heavily into APIs, EDA, AsyncAPI, and that kind of stuff — and lately AI as well, but who is not on AI lately! Because of this, you should definitely expect more newsletters around these topics.

I know I'm not alone so I'm going to ask you for help here. **What are some good newsletters around these topics that you think should be on Commune?**

[![](https://embed.filekitcdn.com/e/tppsnKSSV6RtcQVLeDZHT8/wS6akGKJ7qvSAPuMdS3vE7/email)](https://usecommune.com/n/franmendez?article_timestamp=1773403464)

*​*

Pst! I see you're not on Commune yet. [Click here to join us!](https://usecommune.com/join/09b50fa9-9457-4827-849d-3fb2c851659d)​

[![linkedin](https://functions-js.kit.com/icons?icon=linkedin&foreground=ffffff&background=153461&shape=square&v=3)​](https://linkedin.com/in/fmvilas)[![youtube](https://functions-js.kit.com/icons?icon=youtube&foreground=ffffff&background=153461&shape=square&v=3)​](https://youtube.com/@fmvilas)[![github](https://functions-js.kit.com/icons?icon=github&foreground=ffffff&background=153461&shape=square&v=3)​](https://github.com/fmvilas)

Av. Joaquín Costa, 16, Badajoz, Badajoz 06001
​[Unsubscribe](https://preview.kit-mail3.com/unsubscribe) · [Preferences](https://preview.kit-mail3.com/preferences)​

***

## Discussion (2 replies)

Numbering shows the reply tree: `2.1` is a reply to `2`. Message text is reproduced verbatim as posted.

### 1. Fran Mendez (@fmvilas) - 2026-03-13T12:07:28.566Z

Can you suggest any newsletters about APIs, EDA, AsyncAPI and adjacent topics? Let's have them all here! Please note it's ok if they're on Substack.

### 2. Steven Willmott (@njyx) - 2026-03-14T10:40:58.582Z

Don't have any suggestions there but a couple of thoughts: 1) as the number of newsletters on a topic increases, it would be cool to have "topic" tags that one can follow as well - so that way when a new newsletter on a topic (or even a post) comes in it gets visible to a user, 2) perhaps the topics can come from tags people add to post or (in the future): an LLM analysing a post and also sharing it. it seems to me that the power of commune is in the conversation that happens between various authors and their readers on similar topics - which I think is part of the root point of your post.