CONCORD

How CONCORD Reached Launch

Firewalk launched CONCORD on August 23, 2024, as a $39.99 PlayStation 5 and PC game. It had 16 characters, 12 maps, six modes, weekly story scenes, and plans for more. Sales stopped eleven days later; buyers were offered refunds, and the servers closed on September 6. That gap between the years spent building it and the time it spent live is what makes the beta worth examining.

The July open beta peaked at 2,388 concurrent Steam players; the paid release peaked at 697. These figures miss PlayStation 5 and count simultaneous players, not everyone who tried the game. Even with those limits, few PC players turned up when entry was free.

I do not know what Firewalk saw in its own data or how it decided to launch. A match needed ten players, and a dependable service needed many more across regions, skill levels, and times of day. The public beta gave little evidence that enough people wanted to fill those matches.

The Cost of Asking Players to Move

Overwatch 2, Valorant, and Apex Legends already had players’ friends, progress, and habits. Trying CONCORD meant learning a new game and persuading others to do the same. I could see its features, but I never found a reason in the pitch for a whole group to switch.

If the population is thin, queues grow and skill matching suffers. The first session gets worse, which gives the next player less reason to join. Audience size changes the match someone actually plays.

The $39.99 price made that group move harder. One curious player now had to persuade several friends to buy in too, while established rivals were free to try. The price could be fair for the amount of content and still get in the way of discovery.

What the Beta Needed to Prove

Firewalk did respond to beta feedback, adding a practice range, join-in-progress, backfilling, and leaver penalties. Those helped people already interested in playing. They did not answer the bigger question raised by the low turnout: how many would come back with friends?

The public pitch listed crew building, role perks, weekly cinematics, and polished shooting. I could tell what was in CONCORD. I could not tell who would say, “This is the shooter my group has been missing.” That feels like a product question, not a line of marketing copy someone forgot to write.

Before a beta, I would write down the numbers that would change the release plan: sign-ups, return rate, groups playing together, regional queues, match quality, and willingness to pay. Then I would name who gets to call for a delay or a change in positioning. If the only acceptable outcome is launch, the beta is a rehearsal, not a test.

The Lesson for Future Launches

By July, Firewalk had years of work behind it and a release date ahead. I can understand the pressure to keep going. But the beta was testing an assumption the game needed to survive: enough people would arrive together and keep playing. The public numbers gave little comfort.

For a future multiplayer launch, I would make the beta a real go/no-go decision. Set a minimum active population and retention level for each region; if the game misses them, change the plan while there is still time. Delaying is painful, but it gives a team a chance to learn. Launching into empty matches leaves very little room to recover.