You're seeing the preview. Pro unlocks the full Loom teardown, the rebuild plan, every technical spec in the database, and 5 fresh report requests each month.
This report was generated by our Deep Research agent and may contain mistakes.
Did we get something wrong? DM @oscrhong and we'll fix it ASAP!
Loom was a San Francisco-based cloud storage startup that operated from 2012 to 2014, built by a team of German and European founders who entered Y Combinator's Winter 2012 batch under a different name entirely. The company that became Loom started as Popset, a group photo-sharing app, before pivoting into a more technically ambitious product: a cloud-native photo and video library that stored full-resolution files on its servers and served device-optimized versions to each screen, letting users access 150 GB of media while consuming only 500 MB of local storage.[1]
Loom failed not because it built the wrong product, but because it built the right product in a category that incumbents could absorb as a free feature. Dropbox, Apple, and Google each had structural advantages β existing user bases, platform-level OS integration, and infrastructure at scale β that made a standalone freemium photo storage business nearly impossible to sustain before reaching the scale needed to compete.
Dropbox acquired Loom in April 2014, approximately ten months after its public beta launch, for undisclosed terms.[2] The entire team joined Dropbox to work on Carousel, a dedicated photo app that Dropbox itself shut down less than two years later β confirming that even a well-resourced incumbent could not make standalone photo management a viable business.
Jan Senderek began building what would become Loom while completing his master's degree in technology entrepreneurship at University College London.[3] He assembled a founding team of four β Senderek, Philipp Wein, Nicolas Boes, and Daniel Wagner β and spent six months refining prototypes and early betas before the group applied to Y Combinator.[4]
The team entered YC's Winter 2012 batch as Popset, a mobile app for private group photo sharing that also allowed users to export entire albums to Facebook.[5] The milestone carried a footnote: Popset was described at the time as the first German startup funded by Y Combinator.[6] YC provided its standard $20,000 investment plus $150,000 from StartFund, the then-standard package for all YC companies.[7]
Popset did not survive the year. After Demo Day, Senderek concluded the product was solving the wrong problem. The insight was blunt: users did not lack tools for group photo sharing. What they lacked was a way to manage the growing chaos of their personal photo libraries. Senderek later articulated the core lesson from Popset's failure in a single sentence: "You can't have a community and a utilitarian product."[8] A social network and a practical tool, he concluded, were fundamentally incompatible goals for a small team.
The pivot methodology was rigorous. Senderek and a largely rebuilt team β Wein and Wagner remained as co-founders; Boes's status through the transition is not documented β spent approximately a month conducting hundreds of user interviews.[9] What they found was a specific, painful workflow: iPhone users were backing up photos to external hard drives through iTunes, losing precious SSD space on MacBooks, and still living in fear of losing everything. The problem was concrete and universal.
Senderek's diagnosis was equally direct: "There are so many things that are wrong, and it's kind of obvious how to solve that β by simply putting everything in the cloud and making it accessible to you on all your devices."[10]
The team announced Loom publicly in May 2013, framing it explicitly as a "better iCloud" β a cloud-native photo library that would eventually expand to documents, music, and video, with a developer API that could make it a general-purpose storage layer.[11] The ambition was large. The team was eight people. The runway, based on the YC/StartFund capital, was thin. The clock was already running.
Read the complete post-mortem, the rebuild playbook, and the exact reasons Loom is still worth studying now.