From requirement text to a go / wait decision
Three steps, in the order the planner asks them.
- 1. Read the requirement literally. Open the panel for the action you want and read its current text. Requirements change between updates — the game record shows content landing on 2026-10-02, the day before this page's check — so a number you memorized last week is already a rumor.
- 2. Test affordability against income, not balance. A requirement in reach is one your sales loop can refill quickly. If paying it would empty you to zero during a slow traffic spell, the honest answer is “wait”, and the planner says so.
- 3. Test the trade-off before acting. Affordable is not the same as useful. Read what the purchase actually changes and whether that outcome serves your current goal — an expansion you can pay for still loses to a sales fix when the real constraint is what customers buy. Run the progress assistant if the bottleneck itself is unclear.