Project management, survived by your decisions.
Play the project manager of an AI SaaS startup racing toward production. A deterministic rules engine computes late-breaking consequences while an AI Game Master narrates every crisis.
🚨 Standup Crisis: Lead angel demands an AI agent demo by Monday. Lead architect warns: auth pipeline has critical flaws. Shipping now skips security review.
Select your directive:
Hold the line: refactor core auth security, push demo to Friday.
✅ Security debt prevented. Consequence scheduled: Investor discontent flag raised for Day 08.
You're the project manager. The client won't wait. Deliver in 40 days.
You're assigned to an AI SaaS startup with a 7-person team, a $120,000 budget, and a client who wants the product on schedule. Every day something breaks: payment integration is late, QA finds 12 critical bugs before the demo, the client suddenly wants "just a simple dashboard" that takes a week.
Devs, QA, and Sarah awaiting decisions
Every contractor hour & crunch burns cash
Demo on Day 10 · Release on Day 40
How it works
Real management dynamics: quick choices, unscripted text, and delayed consequences.
Type or tap, your call.
Quick choices appear under every situation — or type what you'd actually do. "Ask QA and the tech lead to check whether we can safely demo the unaffected features" works just as well as any button.
Right now, it's fine. In a week, it isn't.
Every decision lands today and echoes later. Ignore a technical-debt warning and the impact isn't on your dashboard today — it detonates 5 to 7 days later, in front of the client.
One run, 40 days.
A full delivery arc — kickoff, the client demo on Day 10, the release on Day 40 — fits in about 10–20 minutes of focused decisions. Then a final report tells you what your management style cost the project.
Try a decision
Real situations, straight from the game.
The payment integration is late.
Sarah, your senior developer, says the integration needs at least 5 extra days. The client demo is in 10 days.
The team agrees reluctantly and stays late. Daily velocity temporarily jumps, but coffee cups pile up.
Dev fatigue peaks around Day 6. Sarah misses a subtle edge-case webhook validation, creating silent regressions.
Accelerates the timeline today at the direct expense of team morale (-18%) and long-term code stability.
Every choice has trade-offs. There's no "correct" answer — only consequences that follow you to Day 40.
Experience the full 40-day delivery arc on Telegram with zero installation.