How to shape Fintech Products inside a European €5.9B+ eCommerce Platform


How to shape Fintech Products inside a European €5.9B+ eCommerce Platform

READ ON

​HERBIG.CO​

PUBLISHED

May 23, 2025

READING TIME

4 min & 48 sec

​Dear Reader,​

Better product management practices can emerge anywhere. While Silicon Valley companies have long been considered the Standard for product practices, there is immense value in understanding how companies adapt and evolve these practices in different contexts, especially in Europe.

This is why I'm starting a mini-series that explores how European companies "do product," highlighting practices that will be familiar, yet inspirational to many teams. These aren't necessarily revolutionary approaches, but rather thoughtful adaptations that showcase how product management evolves in different environments.

In this first piece, we'll look at how bol.com, the Netherlands' largest online retail platform, shapes its Fintech products. Through my conversation with Damien Folkerts, Head of Product Fintech, we'll explore how they navigate the complexity of serving multiple customer groups while maintaining high product ambitions.

Building financial products within a major e-commerce platform presents unique challenges. The complexity comes from serving three core customer segments: For consumers, the team develops seamless payment experiences and buy-now-pay-later options. Business partners require reliable financial infrastructure – from invoicing systems to VAT handling and customizable payout schedules. At the same time, internal teams depend on financial steering information for strategic decision-making.

While you cannot solve prioritization challenges through arbitrary scoring, Damien’s team tries to bring each decision back to value. As fluffy as the term sounds, it’s a helpful anchor. Because value might not always mean value for end customers. Sometimes, the most significant value comes from serving a strategic pillar of the company or enabling another team in the background.

Or when value is all about meeting regulatory requirements. Instead of treating compliance as a constraint, the team proactively identifies opportunities to turn these requirements into value-adding features from a customer perspective. "We look at the regulation and think about what problem it's trying to solve for the customer," Folkerts explains. This mindset helps them maintain customer focus even within strict regulatory frameworks.

This balancing act becomes even more important because Damien and his team operate at the intersection of e-commerce and banking. Unlike pure fintech companies focusing solely on financial services or traditional e-commerce platforms that outsource financial complexity, bol.com's team must navigate both worlds. "We need to ensure our financial products not only comply with financial and fiscal regulations but also enhance rather than hinder our marketplace dynamics," Folkerts explains. This dual responsibility shapes how they approach product development, forcing them to think beyond traditional fintech or e-commerce paradigms.

From my perspective, Bol.com's approach to fintech products is noteworthy because it has expanded its definition of a product. From consumer-facing payment solutions to partner financial tools and internal steering capabilities, each is treated as a product with its strategic attributes: Who are we serving? How can we serve them as best as possible? Who are we competing against? How are we supporting the company strategy?

This mindset shift has allowed them to apply product thinking more broadly, leading to better outcomes across their financial ecosystem.

How to Apply This:

  • Map your products' value streams - which capabilities enable others vs serve customers directly?
  • Review your current product segmentation - is it based on technical boundaries or customer needs?
  • Document where compliance requirements could create customer value vs just meeting regulations

Next week, we'll explore how bol.com's fintech team approaches discovery, including a story about attempting to interview non-paying partners and partners that misuse the platform, and what this taught them about knowing when to kill ideas.

Did you enjoy the newsletter? Please forward it. It only takes two clicks. Creating this one took two hours.

Thank you for Practicing Product,

​Tim​

PS: The most meditative part of my mid-morning coffee routine

How to Dive Deeper into Product Strategy

Learn how I helped companies like Chrono24 and ausbildung.de hone their Product Strategy practices. I closely work with product organizations through workshops and coaching to introduce and adapt Product Strategy.

Content I found Practical This Week

Why you should care about internal product management

video preview​

Demystifying Platform Product Management

The Platform PM is arguably one of the most valuable yet least understood roles in tech today. At the risk of sounding hyperbolic, this is a sentiment we’ve both felt at various stages of our careers leading platform products ourselves, working with organizations that are developing the platform muscle as they scale. Whether a company is expanding its portfolio or extending its product into a broader ecosystem, platform PMs are a key part of executing successfully.

Do’s and Don’ts in Product Team Topology

The worst example is splitting product responsibilities by engineering layers (i.e., backend, frontend, integrations, research, web, mobile, etc.). A slightly better one, but still not the one you want to go with, is splitting by functional modules or areas (i.e., notifications, analytics, detection (for cybersecurity products, for example), primary logic (like the route and ETA calculation in Waze), etc.). These types of splits score low both on substance (how can one build a good roadmap and vision for notifications or the front end of the product?) and on independence, although not necessarily the way you think.

Who is Tim Herbig?

As a Product Management Coach, I guide Product Teams to measure the real progress of their evidence-informed decisions.

I focus on better practices to connect the dots of Product Strategy, Product OKRs, and Product Discovery.

Product Practice Newsletter

1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes. Explore my new book on realprogressbook.com

Read more from Product Practice Newsletter

Product Practice #430 How to Think About Product Strategy in the Age of AI PUBLISHED Oct 16, 2026 READ ON HERBIG.CO Dear Reader, Two weeks ago, I had the incredible opportunity to be on Akash's Product Growth Podcast. Now that the episode is out, I can finally share it with you as well. I typically don't put podcast episodes front and center in this newsletter, but since this is more of a 1-hour AI Product Strategy Masterclass than an audio-only podcast, I think it's one of the best pieces of...

Product Practice #429 Linked Better Practices over Stacked Best Practices PUBLISHED Oct 11, 2026 READ ON HERBIG.CO Meet Me Next Week at Just Product 2026 Get your Ticket Dear Reader, When a leadership team wants to introduce OKRs, it can be tempting to start by turning every bullet point of your strategy into an OKR. But a long list of priorities will still compete for the same time and attention, even when it gets repackaged. Before moving into OKR drafting, I like to work through this...

Product Practice #428 Linked Better Practices over Stacked Best Practices PUBLISHED Oct 5, 2026 READ ON HERBIG.CO Dear Reader, Sorry for the slip in sending this one out on Friday. To make up for it, there will be (for the first time ever) two newsletters going out this week. Recently, a CPO told me about an engineer who had used AI to develop a proposal. But when the decisions in it were questioned, the engineer kept referring him back to the output. The CPO wondered how that conversation...