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
A founder who knew venues, brands and what a night out should feel like.
James knew the venues, the brand partners and the moment that matters: paying at the bar without friction.
What the business needed was a product that could carry that into every venue.
02The limitWhere it stopped scaling
An earlier build had cost $400K and stalled.
The first product offered a venue directory and a gift feature. Without integrated payments, onboarding venues and attracting investors was close to impossible.
Maintenance costs kept rising, years went into development, and competitors moved ahead.
- $400Kspent on the earlier build before it stalled
03Find the leverageIdentify · Validate
Start fresh, and test the one flow that matters on a real night.
The legacy codebase was scrapped. User-story workshops focused the product on instant rewards, friction-free checkout and social sharing.
Live service testing confirmed the near-zero-fee payment flow worked on a busy night, and high-fidelity prototypes let James pitch pilot venues and brand partners before production code shipped.
04Build itDesign · Build · Launch
Loyalty, fee-free payments and discovery in one app.
A custom payment gateway integrates with leading POS systems and removes middle-man fees, so transactions cost customers and venues nothing.
Thumb-reach navigation, one-tap tab sharing and QR checkout were shaped by bartender and patron feedback.