Godforge Couples Podcast – Working With Your Wife

You know a Godforge podcast is going to be a little unhinged when the opening vibe is “Valentine’s stream” meets “couples therapy on Discord.”

In this special episode, we get Simon and Rachel, plus Sham and Mairead, sitting down to talk about the side of game development players rarely see: what it’s like when your partner isn’t just supporting your dream… they’re living it with you. From community management and social media learning curves to juggling travel, kids, and remote work setups, this chat is equal parts wholesome, chaotic, and surprisingly insightful.

Let’s break down the biggest moments and what they tell us about where Godforge (and Fateless) is heading.

The episode kicks off with a simple premise: bring the spouses on and talk honestly about the journey. That immediately sets a different tone than your usual dev update. This isn’t “here’s a roadmap.” This is “what does it actually feel like behind the scenes?”

And the dynamic is instantly clear:

• Simon is the hype engine. The “I’ve seen cool stuff, I’m excited, let me show the world!” guy.
• Rachel is the limiter. The one quietly making sure the hype doesn’t turn into accidental leaks.
• Sham is relentlessly optimistic. Excited, forward-focused, and not built for anxiety spirals.
• Mairead is structured chaos control. Process-minded, people-focused, and very honest about how hard the grind can be.

That balance is important, because it mirrors what players say they want from a modern live-service RPG: excitement and stability.

One of the most interesting threads is how none of this was apparently “the plan.”

Simon talks about his career path like a series of doors he didn’t expect to open: starting a YouTube channel without thinking it would become a career, then stepping into bigger projects, then eventually building a game studio. Each time, it’s “let’s see how it goes,” followed by “okay… what’s the next step?”

Rachel’s involvement followed the same pattern. She wasn’t eager to be on camera. She wasn’t trying to be “part of the brand.” But over time, as the work grew, her role became a natural extension of what the company needed, especially on the community and social side.

On Sham and Mairead’s side, it’s similar but with a different trigger: Mairead’s career shift (including being laid off) opened the door to joining Fateless full-time. And once she stepped in, she leaned into what she already knew. Building processes, helping teams function smoothly, and making sure people feel welcomed and supported.

That’s a huge theme in this episode: Fateless didn’t just hire a bunch of people and magically become a studio. It grew into one.

If you’ve spent any time in the Godforge Discord, you already know this: community management is not “posting memes.” It’s constant emotional weather control.

Rachel explains her day-to-day is largely community-focused, discord presence, support, and helping manage socials. She also talks about the learning curve: picking up tools like Canva, figuring out how to build posts, and developing that “brand voice” without prior experience.

And there’s a really relatable moment where she describes spending ages on a graphic… only for Suzi to tweak it in about 90 seconds and make it look incredible. If you’ve ever worked on anything creative, you felt that in your soul.

The big takeaway here is that the community-facing side of Godforge isn’t an afterthought. It’s treated like a pillar, because Fateless believes trust and transparency are an actual competitive advantage.

Sham even calls it out directly: community management is “literally our edge against anyone else in the market.”

That’s a bold statement. But it’s also why the community is as invested as it is.

There’s also a genuinely fascinating bit where Simon reflects on how the company structure changed.

Early on, Fateless thought they’d lean heavily on outsourcing: an external team handles most of the production, while the core group holds the vision. They still work with Magic Media “to some capacity,” but the studio has evolved into roughly 50 in-house employees instead.

That shift matters because it changes how fast you can iterate, how consistent the quality is, and how much the team can “own” the final product.

Mairead then explains where she fits into that growth: she quickly spotted the need to translate task-management systems (like Jira) into something creatives can actually work with comfortably. The goal isn’t to turn artists into spreadsheet robots, it’s to free them up to focus on making great art, while production structure handles the chaos around it.

That’s one of those behind-the-scenes realities players don’t always think about: the better the internal process, the smoother the player experience tends to be.

This episode does a good job balancing the fun with the real.

Travel comes up a lot: events, networking, industry relationships. Simon frames it as consistently valuable, even when they initially questioned whether a trip would be “worth it,” they came back feeling like it pushed the company forward.

But for Mairead especially, the impact is very real. She talks about juggling three young kids while Sham travels, and how that forced her to build more independence. Like finally getting her driver’s license after a brutal winter day trying to push a frozen stroller through Chicago.

That story is hilarious, but it’s also telling: the “supportive partner” role isn’t passive. It’s active problem-solving, adapting, and sometimes sheer stubborn determination.

Rachel echoes a different version of that challenge: when everyone’s working at home (especially early on), it can actually be harder than when someone’s away, because kids are right there, noise is right there, and you’re constantly trying to keep life from crashing into work.

This is the side of game development that doesn’t show up on trailers, but absolutely shapes the project.

One of the most memorable parts is the analogy that the community has its own built-in immune system.

They describe having a “crew” in the community that pushes back against toxicity, like white blood cells showing up when negativity flares. It’s a funny image, but it’s also an important concept: communities don’t stay healthy just because moderators exist. They stay healthy when players buy into the culture and reinforce it.

Simon adds a broader point that’s honestly just true about gaming in general: players feel things intensely. Love turns into passion, and frustration turns into fire. The swing between positivity and negativity can be extreme, and managing that is going to be one of the big challenges as the game grows toward release and beyond.

If you’ve been through launches in this genre before, you already know what that means.

When the talk turns to launch and live ops, the mood becomes a blend of hype and realism.

Rachel says she’s looking forward to the next stages, but she’s also aware that being “the community person” means being on the front line when player volume spikes. Sham jokes they’re only expecting “one or two more people” than Alpha… while also referencing that Alpha was around 35–40k players.

So yeah. No pressure.

Mairead’s answer is the most grounded: she enjoys the work, especially now that she has enough experience to know what’s actually an emergency and what isn’t. But she’s also open about the difficulty of balancing a full-time job, three kids, and travel. Her approach is to keep reframing anxious energy into excitement, and to lean on the team’s experience in an industry that’s still new to her.

Sham’s take is pure momentum: he doesn’t really do anxiety, just progress. If something goes wrong, it’s “okay, new day, next step.” But he also emphasizes being proactive, identify what could go wrong and get ahead of it.

And Simon lands in a familiar place: excited, proud of what they’re building, but constantly chasing the next quality improvement.

That’s the real vibe of Godforge right now: a studio trying to ship something big, without compromising on polish.

This podcast episode is a reminder that Godforge isn’t just built by designers, artists, and engineers. It’s also built by family units, people keeping the studio stable, the community supported, and the day-to-day chaos organized.

Rachel’s community work and social presence help keep the bridge between devs and players strong. Mairead’s production mindset helps the internal machine run smoother as the team scales. And together with Simon and Sham, you get a genuinely interesting look at what it takes to build a hero collector RPG from scratch.