Why we're building ManageFC

The idea for ManageFC is older than the website. For months it lived as a list of things we wanted from a football management game and could not find together in one place: real depth in the simulation, a world big enough to get lost in, and a game that does not punish you for having a life.

In March 2026 we registered the domain and put the first version online. It was rough. It was also the moment the project stopped being an idea and started being something people could open in a browser.

What we wanted

We wrote down three things before we wrote any code, and they are still pinned to the top of our notes.

Depth you can feel. Tactics should change what happens on the pitch in ways you can measure, not just in ways the interface claims. If a setting does nothing, it should not be in the game — or the game should say so.

A world, not a league table. Every club in your world should have a name, a crest, a stadium and a history that keeps going whether or not you play against them. Football is not one division; it is a pyramid, and the climb is the story.

Respect for the player's time. No countdown timers, no daily chores, no penalties for going on holiday. A management game should fit around your week, not the other way round.

What we got wrong at first

The first version did not live up to that third point. It was an always-online world: every club shared one universe, matches kicked off at fixed times, and the world kept moving whether you logged in or not. It looked impressive on a diagram. In practice it meant players had to show up when the game was ready, not when they were.

It took us until May to admit that the shape of the game was fighting the idea behind it. The pivot to a private world per save is the single biggest change in ManageFC's history, and most of this diary is the story of getting there and living with the consequences.

The rule that survived

If we had to reduce the project to one sentence, it would be the one we wrote down in May, after cutting a battle pass we had already built:

We want a game people love, not one they can't put down.

Every feature since has been checked against it. Would a player feel respected by this? Does it still work for someone who plays twice a week? Can they stop for a month without being punished? When the answer is no, the feature changes or goes.

What this diary is

Each entry in this series covers a month or a moment, written from our own records: the dates, the measurements, the bugs, the decisions. We will be honest about the parts that went badly — there are several — because a development diary that only reports successes is an advert.

Next in the series: the first version, and a world that ran on a clock.