We built a multiplayer game, launched it quietly, and barely anyone came. Now we're learning distribution from scratch.

The "where people are discussing the problem, not the category" reframe connects to something another commenter pushed earlier in this post — that I should position Vizzy as "multiplayer word game with friends" instead of "daily puzzle," because the first is an unowned slot and the second is fighting Wordle for its ritual. Your framing is the practical consequence of that positioning decision: if the anchor is "fun thing to do with friends online," then Discord friend groups and subs like r/gamingsuggestions are the venues, not word-game-specific spaces.

Honest problem with friend-group Discord servers: they're mostly private. Breaking into them without feeling intrusive is the harder half. Probably means the real play isn't "find where they hang out" but "make content that surfaces in their group chats naturally" — which circles back to the share-moment thing someone else on this post kept pointing at.

Will definitely report back on the tournament. And thanks for the read on IH itself being surprisingly good — we're seeing the same. It's shifted from "a place to post" to "the most useful strategy conversation I've had all month," which I didn't expect.

Accountability/commitment space is close enough in shape — product that's technically solid, no distribution muscle. I keep running into founders with this exact combination. Almost starting to think it's a category of person, not a coincidence.

The "pick ONE channel and go deep" pushback is the correction I needed. I was nodding at the 60-90 day advice earlier in this thread without registering that I'd been unconsciously reading it as "try four things in parallel and see what sticks," which is basically a different (worse) strategy. Depth > breadth in the learning phase, otherwise I'm just bad at four things instead of getting better at one.

And the Discord tournament call is now the third different person on this thread pointing at that specific move. When three independent people converge on the same play, it stops being a suggestion — it's just the next thing to do. We're pitching 2-3 servers this week on hosting one over the weekend.

Curious what "showing up in conversations" looks like in practice for the accountability space. Is there a single community/platform where the conversations are happening consistently, or is it scattered and you're stitching it together? Trying to work out whether Discord, Reddit, or somewhere else is actually the locus for us — the "one channel" question is the harder version of the advice.

Honest answer: you're probably right, and I've been leaning toward "distribution problem" because it's the easier thing to reason about.

We do have the loop surfaces — referral with milestone rewards, a social feed where players create and share emoji puzzles, multiplayer modes that functionally require you to bring a friend or accept a random. But having the surfaces and having them actually trigger are different things. I don't have data that says our referrals convert at any meaningful rate, that social-feed posts get shared outside the app, or that multiplayer modes pull in new players instead of recycling existing ones. The real answer is: we built the hooks but didn't instrument or optimize them, which in practice means they're closer to decoration than loop.

The framing you're offering — "growth embedded in the core experience vs growth as a separate layer" — is the useful distinction. I've been bucketing referral and social as "product" and the channels (Reddit, TikTok, PH) as "growth," when actually most of our real growth should be happening inside the app if those loops worked. The fact that it isn't is the data point I've been refusing to sit with.

Curious which specific loop sounds weakest to you looking in from outside. "Shareable gameplay moments" in particular — is that a feature we're missing, or a framing problem we're failing to build around the modes we already have?

Expert-positioning through blog placement is a different lever than the rest of this thread — most advice so far has been about distribution channels, this is about earned legitimacy. Those compound very differently.

Honest constraint for us: consumer games don't have the same expert-surface area that a scoring framework does. Our equivalents would be the engineering story (Socket.IO namespacing for 6 game modes, offline-first multiplayer sync, atomic guest-to-account migration) pitched to dev-focused publications, or the genre-framing angle (emoji-based word games as an underexplored format) pitched to mobile gaming press. Neither has the same immediate "proprietary thing" credibility that a framework piece carries, which makes the pitch harder.

Curious how you made first contact with Krispitech — cold pitch, warm intro, or did they find you? The outreach mechanics for niche blogs feel opaque to me compared to Reddit or Twitter, and I'd guess more founders underinvest here than overinvest.

Also — what's FPIS? Dropped in curious.

The "small specific experiments" framing is the thing I've been missing. I've been thinking in "posts" and "launches" when the unit should be "today I tested X, here's what happened." Smaller content unit, content writes itself from the work, and the reader gets something useful regardless of whether they care about the product.

What's funny is this is the third version of this idea someone's landed on me this week — different angles, same core. Someone else put it as "show people using the product on content they already cared about," another as "the share moment matters more than the channel." When three people arrive at the same conclusion from different directions, I'm taking it as the signal.

Curious what "running real timestamps through the API and showing the output" looks like for RedLINE in practice — mostly Twitter/X, or are you finding other venues? The format clicks for me but I can't picture the placement yet.

And thanks for the read on offline-first + cross-platform being the right angle. That's the part we keep second-guessing.

This is oddly comforting — the specifics of my space feel different (consumer game, mobile-first) but the shape of the problem is identical. Developer who built quietly and expected launch day to do work it was never going to do.

The promo-paradox you named is something I've been trying to articulate and couldn't. Every community I've tried is either "no self-promo, ever" or "everyone's yelling at nobody," and neither one is useful. The small servers and subs where people actually read each other's posts seem to be the only middle ground — and those are the ones you can't scale into anything meaningful.

Appreciate the note, really. If you're ever posting your own journey, drop the link — I'd want to follow your side of this too. And no pressure on trying the game tomorrow — honest feedback whenever is worth more than a courtesy install.

The empty-lobby death spiral is the thing we've been most scared of — a multiplayer game that feels dead kills faster than a solo game that just isn't great. That's a useful forcing function: stop thinking about "ship more features," start thinking about "make the lobby full at 8pm Saturday."

The fixed-session idea matches what another founder on this post suggested a few hours ago — show up with a tournament or event, not a link. That's three separate pieces of advice this week all pointing at the same move, which I'm taking as the signal. We're actually pitching a couple of gaming Discords this week on hosting a Vizzy tournament over the weekend — first attempt at exactly this play.

One question: the "daily manual outreach" you mentioned — was that mostly 1:1 DMs to individuals, or public posts in communities, or some mix? The mental image of what actually got you those first 200 could mean very different tactical playbooks. Curious what the ratio was.

Taking these in order because all three land.

The tournament idea is the one I hadn't framed right. We've been thinking "post in subreddits / show up on Discord" when the real play is "arrive with an offer only your product can provide." Hosting something the community can't get without you is a different pitch entirely. That's going on this week's list.

Format over channel — uncomfortable because we've been doing the opposite. Writing about what Vizzy is instead of showing someone play it and react. "Real usage on content people already care about" is the reframe. I don't have a good excuse for why we started with the harder version.

On not hiring yet — my instinct was to push back, but the more I sit with it the more right it feels. Briefing someone to fix a problem I don't yet understand the shape of is how expensive mediocre work gets produced. 60-90 days of doing it badly myself is cheaper than hiring badly.

On the retention question — honest answer: our data here is directional, not rigorous. We see that people who find the core loop come back, but we don't have clean cohort analysis yet. You've exposed the real gap in my thinking — we're optimizing for distribution before we've confirmed the retention numbers justify it. If retention is weak, distribution just accelerates churn.

If you had to pick one loop to instrument properly this week — daily-puzzle retention or multiplayer session retention — where would you start? Those two behave so differently that I'm not sure how to sequence them.

Fair point, and honestly not one I'd given enough weight. On a scroll feed, "Vizzy" doesn't do its own work — someone seeing the word cold has no way to know if it's a puzzle, a fitness tracker, or a chat app.

Renaming is off the table at this stage (App Store identity, SEO, existing players), but what you're really pointing at — the hook doing the work the name can't — is something I'd been treating as instinct rather than a testable variable. We've been thinking channel-first: where to post, what subs, what cadence. The actual first three words of each post have been improvised.

Haven't run structured naming/hook tests alongside channel tests. Mostly because I didn't know how to — outside of landing page A/B tools, the short-form-hook version of that feels harder to instrument.

Curious how you approach it when you do. Is it mostly ship-30-variants-and-see-what-survives, or do you start with a framework before the variants?