You’re right... it’s absolutely possible to build time-step models in spreadsheets. The distinction I’m trying to make is that in spreadsheets, time is somethin

You’re right... it’s absolutely possible to build time-step models in spreadsheets. The distinction I’m trying to make is that in spreadsheets, time is something the modeler has to impose and maintain. It’s not native to the system. Every dependency and assumption is hard-coded into formulas that only the creator fully understands. That makes the model powerful, but also fragile and hard to scale. In contrast, (and the whole thesis of the software we've built) simulation and event-based approaches treat time as a first-class citizen. The engine itself steps through each day, week, or month, checking which events are active and applying their effects. Instead of hand-building those mechanics each time, you snap together reusable logic blocks. For the modeler, it’s less about “can we do this?” (because spreadsheets can do almost anything) and more about “should we keep reinventing the wheel, or use a framework that makes time and dependencies explicit by design?”