You mentioned needing to build new capabilities for commercial banking to target banks. What additional developments were necessary for banks compared to credit unions?

The second bucket involves ACH and wire transfers. Just because you can do them doesn't mean you have all the functionality a bank needs. There are numerous permutations regarding payment types, payment limits, and entitlements of who can do certain things. For example, employees of a business need separation between accounts payable and accounts receivable, and there are multiple layers of management in larger businesses regarding who can approve, create, or review transactions and up to what dollar amounts. These permutations can become very complex quickly. In the credit union world, it's all based on the end user.

It seems to be a very different data architecture.

Yes, it is. If you don't start with the proper data architecture and have to retrofit or rewrite it, it can be a lot of work. Not that you're asking, but I'll tell you where Alkami is on that journey. They tried to retrofit many times, and I think they finally hired the right people in the last year to properly diagram the correct structure. This way, they can stop retrofitting and rebuild a new microservice, a new entitlements and limits engine to support larger business needs.