Brendan Rius on Building MEE6 Into a Tool Used by 20 Million Discord Servers
Not every widely used piece of software gets there through a funding announcement or a splashy launch. Some grow the way MEE6 has, quietly, inside the communities that already needed it, built and refined by a small team. Today the product runs across more than 20 million Discord servers, handling the small but constant work of welcoming members, assigning roles, moderating conversations, and keeping things organized for people who were never going to write code to do any of it themselves.
We spoke with Brendan Rius, who co-founded MEE6 and still spends much of his time close to the product. In the conversation below, he walks through how MEE6 came together, how the business has been shaped by the decision to stay bootstrapped, and what nearly a decade of building for community owners has taught him about the gap between a feature that works and a feature that matters.
Overview
Business Name: MEE6
Website URL: https://mee6.xyz/
Founders: Brendan Rius and Anis Belkacem
Business Location: Remote (France and US)
Year Started: 2016
Number of Employees/Contractors/Freelancers: 10
Tell us about yourself and your business.
I’m an engineer and the co-founder of MEE6, which I run with Anis Belkacem. I started programming as a kid and worked as a freelance developer before MEE6. I built the original software, and over time my role expanded into product, hiring, and running the business.
MEE6 helps people run communities on Discord. It handles things like moderation, welcome messages, roles, and activities for members, without requiring the community owner to write code. It has grown to be used across more than 20 million Discord servers, and we’ve built the business without raising outside funding.
How does your business make money?
MEE6 has a free product and a paid Premium offering. Community owners can use the free features and pay for additional functionality and customization when those become useful to them.
That means the business doesn’t depend on everyone becoming a paying customer. We need a useful free product, a clear reason to upgrade, and operating costs that make sense for the mix of free and paid users.
What was your inspiration for starting the business?
The practical problem was that running a Discord community involved a lot of repetitive work. Someone had to welcome members, manage roles, moderate conversations, and keep things organized.
Software could take care of some of that, but the people running the communities weren’t necessarily developers. MEE6 brought those tools together in something they could configure without coding. That combination of a useful problem and an accessible product is what interests me.
How and when did you launch the business?
We started MEE6 in 2016. I built the original software, and my involvement gradually expanded from development into product decisions and running the company with Anis. What we do today is much broader, but it grew out of that hands-on work on the product.
How is the business funded?
MEE6 is bootstrapped. We haven’t raised outside funding; we’ve financed the company through the business itself.
That has shaped how we spend money and decide what to build. A feature or a hire has to make sense given the resources we have. I like the independence that comes with it, although I don’t think bootstrapping is automatically the right choice for every business.
How did you find your first few clients or customers?
Discord itself was our main source of discovery. People would come across MEE6 in a community they belonged to, use it as a member, and then install it when they were setting up or managing a server of their own.
That meant many people had already experienced the product before choosing it. The free offering also made it easy to try. Our paying customers came from that broader user base as community owners found they wanted the additional features.
What was your first year in business like?
The early period was very hands-on. I was writing and improving the software directly. My role was much closer to building the product myself than it is today, when more of my work involves deciding what the company should focus on.
One lesson I’ve taken from building software is that a feature can work exactly as intended and still be confusing or not particularly useful. Understanding that difference has influenced how I approach products.
What strategies did you use to grow the business?
The early period was very hands-on. I was writing and improving the software directly. As the company grew, more of my work involved deciding what we should focus on, but I’ve always kept a clear focus on the product.
More recently, AI has made the team increasingly efficient, which has let me spend more time working directly on the product again.
One lesson I’ve taken from building software is that a feature can work exactly as intended and still be confusing or not particularly useful. Understanding that difference has influenced how I approach products.
What was the biggest challenge you had to overcome?
The biggest challenge was deciding where to spend our limited time and resources. There were always more ideas than we could pursue, and being bootstrapped meant we couldn’t afford to spread ourselves too thin.
We had to be clear about which problems were worth solving and what would actually make a difference for users and the business. A feature could be a good idea and still not be the right priority. Staying focused also meant accepting that some worthwhile things would have to wait.
What have been the most significant keys to your business’s success?
A useful product, a natural way for people to discover it, and a business model that could support continued development. All three mattered. A large number of users alone wouldn’t have been enough.
Being able to build the early product ourselves also helped. We could act on what we were learning without needing a large team first. As the company grew, deciding what deserved our attention became just as important as our ability to build it.
Tell us about your team.
We work with a small, distributed team. Anis and I run the company together, and the work covers developing the product, keeping it running, and supporting the communities that use it.
We’ve tried to make hiring decisions around what the business actually needs to accomplish. Adding people also adds coordination, so I don’t see a bigger team as an achievement by itself.
What is the most important lesson you’ve learned growing the business?
Being able to build something doesn’t tell you whether it’s worth building. As a developer, it’s easy to get interested in how a feature could work and spend too little time on whether people need it.
I now put more weight on the whole decision: who it helps, how much it improves their experience, and what it will take to maintain. Sometimes improving an existing feature is a better use of time than adding a new one.
What separates your business from your competitors?
MEE6 brings a broad set of community tools into one product that people can configure without coding. That is useful for someone who wants to run a server without assembling and maintaining a collection of separate tools.
We’ve also spent years working on the product across a very wide range of communities. That experience helps us understand where people get stuck and what needs to remain simple, even as the product becomes more capable.
What advice do you have for other entrepreneurs?
Think about how people will find your product while you’re deciding what to build. It’s easy to spend months on the product and leave distribution as a problem to solve later. With MEE6, being visible inside Discord was a major part of why the business could work.
I’d also separate the decision to build a company from the decision to raise money. Work out what your particular business needs. Funding and headcount are useful when they help you accomplish something; they aren’t measures of progress on their own.
If you had to start from scratch, where would you begin?
I’d start with a group of people I could reach and a problem I could understand in detail. I’d want to know what they do today, what frustrates them, and whether solving it would matter enough for them to try a new product.
Then I’d build a small version and get it into their hands. Given my background, building is the part I naturally gravitate toward. I’d be deliberate about spending time on the other half: how people discover the product, why they keep using it, and whether it can support a business.
