Fable

Fable launched with a stripped-down MVP focused on centralizing product specifications and decision logs—essentially a collaborative document hub for product teams. ​​‌‌‌‌‌‌‌​‌‌​​‌​​​​​​‌‌​‌‌‌​​​‌‌The founders shipped quickly within months of YC Winter 2021 acceptance, deliberately omitting integrations with existing tools like Jira and Slack that would have required significant engineering effort. They believed teams would adopt Fable as a standalone source of truth, similar to how Figma disrupted design workflows. However, this execution strategy proved fatal. By avoiding integrations, Fable created friction in established workflows rather than reducing it. Product teams already lived in their existing tools and saw Fable as yet another tab to maintain. The founders missed critical warning signs: low daily active users and adoption plateaus after initial onboarding. They underestimated switching costs in enterprise software and overestimated teams' willingness to consolidate information in a new platform. The lean approach that worked for Figma and Linear backfired because those tools solved novel problems, while Fable competed directly against entrenched alternatives without offering sufficient workflow integration advantages.