Your Vote Shipped a Feature in 24 Hours
Last Friday at 4 PM, Noor posted an idea: add a melee finisher when you knock someone down in DOMINION. By Saturday at 4 PM, that move was live, and Noor got a ping in Discord saying shipped. That's not a marketing stunt. It's how the roadmap works now. We don't hide features behind a calendar. We don't wait for a quarterly update. The idea board is the backlog, and the top-voted idea ships before the next Friday.
We built this because we got tired of our own planning. We'd spend weeks on a feature nobody asked for, then watch players ignore it. The board was supposed to fix that. But we didn't expect the speed. The first weekly vote we thought would take a month. It was a small change to the revolver reload animation. Shipped in three days. Then we tried a bigger one: a new enemy type in RUSH. That took ten days. The week after, a new loadout slot in five.
What changed is we stopped polishing. A community-voted feature doesn't get a spec sheet or a beta. It gets a rough build, a known list of bugs, and a note: this is fresh, tell us what breaks. Players don't mind. They're part of the process, and they'd rather play a rough version today than a clean one next month. We fail fast in public, and the players help us fix it.
This week the vote was for a co-op mode in Classic, the 2020 Unity build. We thought two weeks. Took four days because we reused the netcode from the main game. The lesson: community-driven development isn't just listening. It's shipping so fast the community sees the direct line from their vote to the build. That keeps them coming back. And it's why we'll never go back to a closed roadmap.
Try it yourself. The board is open. Post an idea, everyone gets one vote, the top pick becomes next week's feature. The last three winners were all player suggestions. The speed is real, and it's the whole point.
Why Community-Driven Development Fails Most Studios
Ask any developer about community-driven development and they'll say it's a nice idea but it can't scale. Players don't know what they want. It takes too long to implement someone else's half-baked concept. You need a large team to react that fast. We've seen all three excuses fail in real life. The truth is it fails when studios treat it as a suggestion box instead of a production pipeline.
We had our own failure. In 2021, before The Agency launched, we put up a forum thread asking for ideas. Got 200 replies in a week. We read them all, picked five that looked cool, put them on a roadmap. Never shipped any because we had to fix bugs and add features the publisher wanted. Players noticed. They stopped posting. The forum died. That's how to fail: ask for input, then ignore it.
The fix isn't more input. It's making input binding. Every week, the top-voted idea is the next feature. No exceptions. That forces us to design the pipeline around speed. We keep the codebase modular so features plug in without breaking the main game. We use a quick playtest build that bypasses normal QA for the first 24 hours. We accept some features will be rough on day one. And we've learned to say no to ideas that take longer than a week. That's not censorship. It's a constraint that keeps the promise honest.
There are downsides. Some weeks the winner is boring, like changing the crosshair color. Other weeks it's technically risky, like a new game mode. But we ship the boring ones too because the community voted for them. That consistency builds trust. Players know their vote matters even when they don't agree. In a small studio, that trust is worth more than any roadmap.
Most studios can't do this because they're not structured for it. Separate teams for design, code, art, with approval layers in between. Our team is four people. We all wear every hat. When a vote ships, the person who posted the idea gets a credit in the changelog. Small thing, but it turns a feature request into a personal contribution. That keeps the board active.
What This Means for You as a Player
Every time you play The Agency, you're testing a feature a real player asked for, often within the last 48 hours. The game changes constantly. Log in Sunday, find a new weapon that wasn't there Friday. That's a feature we shipped because the community voted for it, not because we thought it was cool.
We see it in the data. When we ship a community-voted feature, retention goes up. No marketing campaign needed. Players tell their friends, I voted for this and it's in the game now. Stronger than any trailer. It's also why we keep everything free. No publisher or investors to please. The only currency that matters is the votes on the board, and those are earned by playing, not buying.
People ask if indie development is worth it, or how profitable it can be. We're not rolling in cash. The Agency covers server costs and a little extra. The real payoff is watching a player's idea become reality in a day. That feedback loop you can't buy. It's also why we'll never sell the game or add pay-to-win. Indie development is the best career we've had, precisely because we can ship this fast.
For you, the takeaway is your voice has a direct impact. You don't need to be a developer or have years of experience. The best idea last month came from a player who'd been playing two days. They wanted a jump pad in the training map. Took us an afternoon. Not a huge feature, but it made that player feel like they owned the game. That's what community-driven development is about: ownership.
So come try the next vote. The board resets every Friday. Pitch something, you get one vote to use on it or another idea. The top pick goes live within seven days. We've done it 34 times without missing a week. That's a track record we're proud of, and it's all because players like you keep bringing ideas. See you on the board.
