Liveops Manager

Built with: Next.js, TypeScript

Teams running a live game plan their offers, events and mini-games on two different clocks at once. There is the calendar date, and there is the day of the current season. Every plan has to be readable in both, and in a spreadsheet that reconciliation happens by hand, every time.

This is a planning calendar built around that problem. One seasonality rule propagates across the whole board in both directions, so “day 17 of season 12” and “October 5” are the same glance, with no mental arithmetic and no second spreadsheet tab.

What it does differently

• Recurrence belongs to the slot its rule iterates, not the date it happens to land on. Move a season boundary and season-anchored series follow it. Skip one occurrence and the skip survives regeneration.
• One lane per thing you run, rather than a task list, so the board answers what live operations actually asks: when did we last run this, when is it next, and how long was the gap?
• Reading never costs a seat. A board is shared by link and needs no account, so producers, marketing and partners can just read it. A reader who wants in asks for edit access in one click.
• Every change saves as it is made and reaches colleagues within seconds, with undo across the whole board and archiving that keeps the history.

Why I built it

I have spent my career in product management on live mobile games, where a large part of the job is designing and managing the economy: the sinks and taps that keep it in balance, and the offers and rewarded ads that sit on top of it. Almost all of it runs on a schedule, and the schedule is where the decisions actually live.

There was no tool built for that job. Planning ends up in whatever general-purpose grid is at hand, and the people who need to read the plan sit elsewhere: design, marketing, community support. They need to work on it together, both at the same time and at different times, without waiting for someone to send a newer version.

So I built the calendar I wanted to use.