Where should a bank configure a platform, and where should it build its own software? Recorded live with Dimitry Oosthoek, Head of Strategic Client Solutions at Akkuro, and hosted by Hanna Yadlouskaya, COO of WislaCode.
- The four places a requirement can live: the product, configuration, product evolution or an extension
- Who owns the seam between the platform and the bank's own code
- The exit cost, and the signals that the line needs to move
Chapters20
- 00:00Introduction: why this topic
- 02:30Dimitry Oosthoek: does a unique bank need unique software?
- 06:12Business difference vs software difference
- 07:39Use it, configure it, evolve it, extend around it
- 12:18Client examples: ASN Bank and Semmie
- 14:06Where do you draw the line?
- 15:33Slava Kostin: nobody prices the seam
- 17:36Who owns "around"?
- 20:36Gartner pace layers and Wardley evolution
- 23:29The exit cost
- 24:51I was wrong about the mobile bank
- 26:27Revolut: bought first, then built
- 29:01Q: what signals tell you the line needs to move?
- 31:06Q: what changed your mind on mobile banking?
- 32:44Q: who owns the integration layer?
- 36:31Q: how does a platform decide what belongs in it?
- 40:12Audience: digital currencies and core banking
- 44:28Audience: when does a configured platform become legacy?
- 47:37Audience: why not buy what our competitor bought?
- 50:41Wrap-up