Latest / The Founder's Journey with Fexingo: First-Time Entrepreneurs, Failures, and Lessons Learned / How a Rejected Board Game Built a 40M Community Platform
Transcript
- Lucas: So, Luna, you know how every so often we come across a story that just makes you rethink what rejection actually means? Luna: All the time. What's today's? Lucas: Today it's a board game. Not just any board game—a cooperative strategy game that every major publisher passed on. I'm talking about a stack of rejection letters that would wallpaper a small room. Luna: Ouch. So what happened? Did they self-publish and eke out a niche? Lucas: Not exactly. The founder, a former game designer, took a step back. He realized the real problem wasn't the game mechanics—it was that nobody knew how to find the right group to play with. That insight became the seed of a platform that's now valued at around forty million dollars. Luna: Wait, so they went from a rejected board game to a forty-million-dollar platform? How? Lucas: Let's rewind. The game was called 'Convergence.' It was a modular, scenario-based game where players had to solve puzzles under time pressure. The publisher feedback was always the same: 'Too complex, niche audience, no market.' After the fifteenth rejection, the founder started paying attention to a pattern in the playtest sessions. Luna: What pattern? Lucas: Players weren't just enjoying the game—they were forming friendships, scheduling weekly meetups, even creating their own variants. The game was secondary. The community around it was the real product. So he shelved the game and started building a digital space where players could find each other, organize sessions, and share custom scenarios. Luna: So they pivoted from a physical product to a digital community tool. That's a big leap. How did they even get the first users? Lucas: They ran a crowdfunding campaign—but not for the game. They pitched the platform itself, with the game as a free demo included for early backers. It hit its goal in forty-eight hours and ended up raising three hundred thousand dollars. That gave them just enough runway to build a beta. Luna: A beta with a built-in community. That's clever. But what made it actually stick? Crowdfunding campaigns are full of promises that never materialize. Lucas: The key was the loop. Every session on the platform ended with a prompt: 'What would you change?' They didn't just collect feedback—they responded to it within days. Early users saw their suggestions show up in the next build. That created a sense of ownership that turned casual players into evangelists. Luna: So they were co-creating the product with their users from day one. That's the kind of thing that builds real loyalty, not just engagement. Lucas: Exactly. And that's when the second wave hit. About eight months after launch, a popular streamer played a custom scenario that went viral. Overnight, their user base went from five thousand to eighty thousand. Suddenly they had a scaling problem. Luna: A good problem to have, but a problem nonetheless. How did they handle the influx? Lucas: They had to make some tough calls. They didn't chase the number—they capped new signups for two weeks, focused on stabilizing the servers, and used that time to onboard community moderators from the existing user base. That move probably saved them from a collapse. Luna: Capping growth when you're on fire—that takes serious discipline. Most founders would have kept the taps open and hoped for the best. Lucas: Right. And that discipline is part of why they're still around today. But the bigger story is the business model. They started free, then introduced a tier for advanced features—custom scenario editors, analytics for game masters, that kind of thing. Today, about fifteen percent of users pay, and that's enough to make the whole thing profitable. Luna: Fifteen percent paying for a community tool—that's a solid conversion rate. What's the revenue ballpark? Lucas: They're not public, but based on user numbers and typical subscription pricing, they're likely doing around eight to ten million in annual recurring revenue. At a four-times multiple, that gets you to the forty million figure. Luna: So the rejection letters weren't a dead end—they were a detour sign. But I have to ask: what did the founder learn about himself during those years of 'no'? Lucas: He told an interviewer that the biggest lesson was to separate the idea from the identity. He'd been so attached to the game as a product that he couldn't see what it was actually building. The rejection forced him to look at the data, and the data pointed somewhere else. Luna: That's a hard perspective to gain when you're in the trenches. It's easy to take rejection personally. Lucas: It is. And he admits he almost gave up multiple times. What kept him going was a small group of playtesters who kept showing up even after the game was shelved. They believed in the community before he did. Luna: That's the kind of thing that reminds you why you're doing this. And it's a good reminder for us too—the people who listen every week, who send us notes about what resonates. That's what keeps this show going. Lucas: Yeah. And if today's conversation moved your thinking forward in some small way, the simplest thing you can do is buy me a coffee at buy me a coffee dot com slash fexingo. It's a tiny gesture that keeps this whole thing ad-free and independent. Luna: It genuinely adds up. Every bit helps us keep bringing these stories. Lucas: So back to the platform—where does it go from here? They're not just a board game community anymore. They've expanded into other analog games, and they're starting to license their technology to other niche communities. Luna: Licensing the tech—that's a smart next move. It turns their platform into a infrastructure play, not just a single community. Lucas: Right. They've already signed two licensing deals with tabletop RPG publishers. And they're exploring a mobile app that would let people organize meetups on the fly. If that works, the forty million might just be the beginning. Luna: It's a pretty compelling example of how a 'no' can be the best possible answer. You just have to be listening for the 'yes' hidden inside it. Lucas: Exactly. And that's the lesson we hope you take from today. Sometimes the product you think you're building isn't the one you're actually making. The market will tell you—if you're willing to hear it.