Ask a US payments company when it last made a regulated business decision and the answer is often "not recently". Ask what changed in the last two quarters and you get faster settlement, a new payout method, a held float, a marketplace feature, a new customer class.
Each of those can change whether the company holds value, whose permissions it depends on, and which states it touches. None of them were described internally as regulatory decisions.
Held value is the trigger to watch
In our view the single most consequential variable in payments is whether, and for how long, the company controls funds belonging to someone else. Product decisions create that condition routinely without naming it.
A simulation habit catches it at design time: for any change to funds flow, test whether it creates or extends a period of control over customer funds, and what that would change depending on the institutional configuration.
Ship faster by deciding earlier
Product teams assume regulatory analysis slows delivery. What we see slowing delivery is discovering the consequence late — after build, when the option set has narrowed to one and the choice is ship it or write it off.
At that point regulatory uncertainty is a product and capital-allocation problem, not a legal problem. Someone is deciding whether to spend another quarter of engineering on a structure that may not survive a partner-bank review.
Simulating at design time widens the options while changing course is still a whiteboard exercise. That is the part we think can become infrastructure.