PODCAST

The Architecture of Scale: Building Repeatable Fintech Products – Story of Software S05E03

Listen to Sam Sengupta, CEO of Finray Europe, on market segmentation, building repeatable fintech products, and why clean data is the foundation of a good AI strategy.
Story of Software podcast by Zartis

 

 

The Guest: Sam Sengupta, CEO, Finray Europe

Sam Sengupta is the CEO of Finray Europe, a platform designed to automate complex financial operations for some of the world’s largest institutions. His route into fintech leadership was shaped by three forces: an inquisitive, globally curious mindset, a personal decision to relocate to Ireland in 2006, and the influence of private equity investment cycles across the firms he has worked for. He began his career at Morgan Stanley, spanning London, Tokyo, Hong Kong, and New York over a decade, before moving into fund services with Citco in Dublin, then into corporate services with TMF, and eventually into a series of Series A and Series B startups. That range — from global investment bank to early-stage venture — gave him a front-row view of how technology strategy changes at every stage of a company’s growth.

In this episode, we move beyond high-level product-market fit theory and into the actual methodology Sam has used to find surgical entry points into financial services markets, build repeatable product blueprints, and frame ROI in a way that makes technology adoption feel non-negotiable rather than optional. The conversation also tackles the uncomfortable reality that data is still being ignored in most organisations, and why that makes the coming AI disruption far more abrupt than most incumbents expect.

Some of the episode highlights include:

  • Why “spray and pray” is not just acceptable in early-stage startups — it is necessary, and how Finray’s foundational data model makes pivoting between verticals faster than competitors expect
  • Budget-back problem framing: finding the segment where the money already exists to solve the problem, rather than trying to create a new budget line
  • Building a rinse-and-repeat product blueprint: why 80% of the product should be out-of-the-box, and how to protect that core from bespoke client requests
  • The six-to-eight week data integration proof of value, and why the “wow moment” it produces is replacing multi-year consulting engagements
  • Human-agent collaboration in financial services: why 99.9% accuracy is not good enough, and what “agent-ready” data infrastructure actually looks like
  • The Kodak moment coming for fund administration and broader financial services, and why the organisations that wait until the fire is burning may already be too late

 

 

Q: Once you’ve solved a problem for one major institution, how do you make sure the product stays templated rather than getting pulled into bespoke builds by your biggest clients?

“For me, what it really comes down to is product-market fit, and I don’t use that term lightly. It’s not just ‘fit in isolation’; it’s the addressable market, the segmentation of that market, and then the fit into that specific segment. Once you’ve got that right, in my opinion 80% or more of the CX, UX, and UI should already slot into the rinse-and-repeat model.

Finray has been built this way. We have the core data model and sub-ledger architecture, which handles 80% of what clients are looking for out of the box. The remaining 20% shapes it for the target segment. That part is genuinely customisable, institutions can apply rules and internal policies on their own terms, but it sits on top of a foundation that never changes. So when a client comes to us with a bespoke request, it almost always turns out to be something at the top layer, not something that requires reworking the foundation. We’ve not seen a case yet where it goes deeper than that.

The way I think about protecting the core is through product usage data. There are widely available tools that let you monitor how clients actually use your product, and that gives you real signal about where the ARR opportunities are. Not one-off edge cases, but the patterns that tell you something is genuinely repeatable. That distinction – between a pattern and an edge case – is really what separates a scalable product from a professional services business dressed up as software.”

 

 

Listen to the Story of Software on:

Apple Podcasts, Spotify, Deezer, & any other podcast platform of your choice. The Story of Software Podcast is produced by Zartis, a software services company. We hope you enjoy listening to this tech podcast and feel free to share any feedback with us: podcast@zartis.com

More episodes

Zartis Tech Review

Your monthly source for AI and software related news