How it happened.
The same path every Mayfly project follows: the expertise a company already has, where it stopped scaling, and what was found and built.
- 01The expertiseWhat the company had
- 02The limitWhere it stopped scaling
- 03Find the leverageIdentify · Validate
- 04Build itDesign · Build · Launch
01The expertiseWhat the company had
Two founders, a dietitian’s expertise and an audience in the tens of thousands.
Alicia and Bree had built a newsletter audience in the tens of thousands around one idea: food as support, not restriction.
They knew what their readers struggled with, because the readers told them, every week.
02The limitWhere it stopped scaling
An audience asking for a product the founders could not build alone.
Diet culture leaves many women anxious at mealtimes. The audience wanted practical guidance they could use daily.
Non-technical and bootstrapped, the founders had no way to turn that expertise into a product that could scale.
03Find the leverageIdentify · Validate
Turn the inbox into the product.
The struggles in Wirl’s inbox were mapped into user stories. Rapid prototypes went to real subscribers, whose feedback shaped the palette and the copy.
The launch plan was built on the community that already existed.
04Build itDesign · Build · Launch
Log feelings, not calories.
The interface is built around logging feelings rather than counting calories, with recipes, guidance, meditations and check-ins around it.
A modular content engine lets the team add new challenges, such as burnout recovery, without a developer. A low-code build with performance tuning keeps it fast as membership grows.