ReadySetLaunch

ReadySetLaunch case study · Failure database

Wriggle

Failure Technology & Software Primary gap · Problem Clarity

Wriggle launched to solve a genuine problem: diners struggled to discover local restaurants offering deals, while restaurants faced empty tables during off-peak hours. The pain was most acute for budget-conscious consumers in mid-sized UK cities and independent restaurants competing against chains.

Problem Clarity
Wriggle launched to solve a genuine problem: diners struggled to discover local restaurants offering deals, while restaurants faced empty tables during off-peak hours. The pain was most acute for budget-conscious consumers in mid-sized UK cities and independent restaurants competing against chains. The problem was measurable—restaurants tracked no-shows and unused capacity, while consumers could quantify money spent on dining. Alternatives existed but were fragmented: individual restaurant loyalty apps, generic deal sites like Groupon, and social media discovery. Wriggle's warning signs emerged early. Despite 400K downloads across seven cities, the platform never demonstrated strong unit economics or retention metrics. The pandemic initially seemed beneficial—restaurants desperately needed customers—yet Wriggle still failed to convert this urgency into sustainable revenue. Management likely underestimated how deal-driven diners differ from regular customers, and how restaurants' desperation during lockdowns wouldn't translate to long-term commission willingness once recovery began. The fundamental mistake was pursuing growth across multiple cities before proving the core business model worked in Bristol.
Demand Signal
Wriggle accumulated 400,000 downloads across seven UK cities, suggesting strong user acquisition. However, the behavioral signals told a different story. While downloads appeared impressive, retention rates remained critically low—users downloaded the app but rarely returned. The company measured interest through download metrics and restaurant partner sign-ups, yet these vanity metrics masked the core problem: users weren't actually booking through the platform. Early traction looked promising with expansion from Bristol to multiple cities, but this growth masked stagnating engagement. The warning signs were everywhere. Wriggle confused distribution with demand; restaurants partnered out of curiosity rather than genuine customer traffic. The company failed to track actual transaction volume or repeat usage patterns. By the time management realized users wanted deal discovery but not the specific execution Wriggle offered, the pandemic accelerated their decline. They'd validated interest in the problem, not demand for their solution. The $2M funding masked fundamental product-market fit issues until it was too late.

Source: https://www.cbinsights.com/research/startup-failure-post-mortem/

Don't repeat the pattern

ReadySetLaunch's Launch Control walks you through thirteen structured questions across the same pillars this case study failed on. You earn your readiness. You don't get told you're ready.

Pressure-test your idea