Yes, I mean, that's a good question, Ashwin. Obviously, the Commerce deal was something that we were battling for as well, and we did not end up getting selected. The difference between that kind of a transaction or the Ally transaction, where, in many of the smaller institutions -- and I don't mean that negatively, but the smaller institutions will tend to buy on a bundled basis. In the larger clients, that's not the case. So Commerce bought -- may have bought a core engine, but we actually provide them many of their digital and payment solutions. And so as you move up that food chain, winning the core processing capability is certainly important and something we'd like to do, but we still have many relationships with these institutions. And in this case, the core provider doesn't have the capabilities to displace us, and so it is a little bit different than you see in other parts of the landscape. The other thing I would say is those larger clients, as much as we'd like to win them, they tend to be multiyear, 2-, 3-, 4-, 5-year kinds of implementations. And frankly, it's a lot of services revenue, and for us, we don't think that's necessarily our sweet spot. We really are building our company to be in the -- call it, in the $25 billion and less space on the bundled value proposition. Now we'll move up and we have clients that are larger than that. And for clients who want the modern technologies that we provide and they want an integration advantage, then that's great. But if they're really looking for very heavy, professional services and license-type transaction, we have to evaluate each one of those and make a determination. Is it somewhere where we want to play, and are we best suited to deliver that given the opportunity costs associated with those kinds of transactions?