
Uber for Flowers.
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
If you only have a few minutes to spare, here’s what investors, operators, and founders should know about BloomThat (S13).
BloomThat was "Uber for flowers," and that framing was the problem. Founded in 2013 by David Bladow, Matthew Schwab, and Chad Powell, the Y Combinator startup promised beautiful bouquets delivered fast and free, same-day, in the San Francisco Bay Area — a delightful consumer experience built on on-demand courier logistics.[5] It raised about $7.5 million and won fans, but by mid-2015 it was burning over $500,000 a month, because same-day delivery of a bulky, perishable, low-frequency product has punishing unit economics.[4]
To survive, BloomThat did the only thing it could: it removed the very promises that differentiated it — pulling back markets, slowing delivery, and adding the delivery fees it had proudly avoided — and shifted toward a conventional shipped-flowers model.[4] That made it an ordinary online florist competing with giants. In January 2018, flower-delivery incumbent FTD quietly acquired BloomThat for a small amount of cash, paused the on-demand service, and wound it down by that September.[2]
BloomThat launched in 2013 out of Y Combinator, riding the on-demand wave that made "Uber for X" the reflexive pitch of the era.[7] Founders David Bladow, Matthew Schwab, and Chad Powell targeted a genuinely bad experience: buying flowers online was expensive, the selection was overwhelming, and delivery was slow and unreliable. Their answer was radical simplicity and speed — a small, curated set of gorgeous bouquets, delivered the same day, fast and free, ordered in a couple of taps.
The product was legitimately lovable, and that was the seduction. Customers delighted by a bouquet arriving in ninety minutes with no delivery fee tell their friends, and the growth felt like validation.[5] But the promises that made customers love BloomThat — same-day, fast, free — were precisely the ones that made each order lose money. The founders had built a wonderful experience on top of an economic structure that couldn't sustain it, and the more it grew, the faster it burned.
BloomThat's original product was an on-demand flower-delivery app. Instead of the overwhelming catalogs of traditional florists, it offered a tightly curated selection — a handful of beautifully photographed arrangements — that a customer could order in seconds and have hand-delivered the same day, initially with no delivery fee.[5] The experience mimicked the best of on-demand: simplicity, speed, and a polished mobile flow.
Behind the app sat the hard part: sourcing fresh flowers, arranging them, and running a courier operation that could deliver perishable bouquets quickly across a metro area. This logistics layer was expensive and unforgiving — flowers wilt, demand spikes violently around holidays, and same-day courier delivery of a bulky item costs more than the margin on most bouquets.[4] When the economics forced a retreat, BloomThat added fees and moved toward shipping flowers in boxes like everyone else, abandoning the speed-and-simplicity identity that had defined it.
BloomThat served urban consumers buying flowers as gifts or for themselves — a broad audience, but one that buys flowers rarely and unpredictably, mostly around occasions.
The flower-delivery market is large but structurally difficult: low purchase frequency, extreme seasonality, thin margins, and perishability. On-demand only made those constraints harder.
Read the complete post-mortem, the rebuild playbook, and the exact reasons BloomThat is still worth studying now.