A roster is a zero-sum allocation problem before it’s anything else. A team only has so many minutes to give out in a game; five players times a 40-minute game is 200 minutes, or 240 in a league that plays 48-minute games like the G League, and every minute you hand one player is a minute you’re not handing someone else. That constraint is easy to state and surprisingly easy to lose track of in practice, especially mid-build, when a squad plan starts to feel like a wishlist instead of an allocation.
The failure mode is familiar: you build a squad that looks great player-by-player, a strong starting five, solid depth, an exciting young signing, and only notice once it’s finished that the minutes don’t actually add up to a coherent rotation. Too many players competing for the same 15 minutes off the bench. A starter pencilled in for 32 minutes a game who’s realistically a 26-minute player. The individual pieces are good. The allocation isn’t.
The useful discipline is to treat minutes as the actual currency of a roster build, not points or rebounds. Before asking “is this a good player,” ask “where do his minutes come from, and who do they come from instead?” Signing a good player without a clear answer to that second question doesn’t upgrade your roster; it just creates a minutes conflict you’ll have to resolve later, usually under worse conditions than you have right now.
This is exactly the discipline MelonIQ’s Squad Builder is built around: every player in a plan carries a minutes figure, the tool tracks the running total against a real budget, and the projected team line reflects what actually happens when those minutes get redistributed, not an optimistic version where everyone plays 30 a night. A squad plan that respects the budget isn’t just more realistic. It’s the only version of the plan that tells you anything useful about what the team will actually look like.