When Founders Fall in Love with Their Feature: A fintech startup's stalled pivot
A real-world example of Endowment effect in action
Context
Ledgerly, a 30-person fintech startup, built a manual reconciliation feature early to differentiate from competitors. Over time the feature became more of an identity marker for the founding team than a high-value product component.
Situation
Customer research and usage metrics showed the manual reconciliation tool was used by fewer than 8% of customers and generated no meaningful upsell. Meanwhile, an automated reconciliation engine—promised to several key prospects—required reallocating two engineers and sunset of parts of the legacy tool.
The bias in action
Founders and the original engineers resisted sunsetting the legacy feature because they had designed it and 'owned' it from day one; they repeatedly argued it represented Ledgerly's craftsmanship. Decision meetings focused on emotional attachment (the story behind the feature) rather than objective metrics, and suggestions to run an A/B test or pilot were deprioritized. As a result, engineering and product roadmaps retained the legacy feature, consuming developer cycles and blocking the automated solution.
Outcome
The automated engine was delayed by six months, during which a competitor shipped an automated reconciliation product and won two of Ledgerly's pipeline deals. Internal morale dipped as engineers worked around the legacy code, and sales churned two prospects who needed automation immediately.