What separates an embedded finance partnership that changes customer behavior from an integration nobody would miss? In this episode of Tech Talks Daily, I speak with Rory Herriman, Chief Technology Officer and Chief Operations Officer for Zip's US business. Rory works across product, technology, operations, and business strategy, giving him a broad view of what happens after the API connection is complete and real customers begin using the service. Rory challenges a common understanding of embedded finance as placing one financial product inside another company's experience. Customers rarely wake up wanting embedded finance. They want to complete a purchase, manage their money, or solve a practical problem without an unnecessary interruption. The real test is whether the two businesses create something together that neither could provide independently. Rory calls this derived product market fit. Both products may succeed separately, but the combined experience must generate additional value for the customer if the partnership is going to last. Technology integration is only one part of the work. As businesses add customers and partners, they create new customer journeys, compliance obligations, servicing models, governance requirements, and operational processes. Rory argues that this complexity grows exponentially rather than linearly. This changes how technology teams should approach architecture. Instead of creating another custom integration for every opportunity, each partnership should contribute reusable capabilities to a wider platform. APIs, shared services, configuration tools, support processes, and governance models can then serve the growing ecosystem. We also discuss what partnership conversations reveal. Rory sees customer journey discussions during the first meeting as a positive sign. A conversation dominated by revenue division or integration mechanics may indicate that the participants have not established why the customer needs the combined service. His internal test is refreshingly simple. If the company launched the capability and removed it several months later, would the customer notice? If the answer is no, the partnership may have created technical activity without meaningful customer value. AI also enters the discussion. Rory believes AI can move financial services toward adaptive experiences where the product responds to the customer's circumstances. This offers opportunities for personalization and automated servicing, but it also increases the importance of responsible design, governance, customer consent, and clear accountability. For leaders building one-to-many embedded finance models, Rory's advice is to begin with the customer journey, establish alignment on values and service expectations, and build platforms that become stronger with each partnership. Would your customers miss the financial services you are embedding, or are they simply another feature occupying space in the journey? Listen to the episode and share your thoughts with me.

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related