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 network of 90,000 contractors already in place.
Clipboard had spent years building a community of 90,000 hospitality contractors.
That network was the asset. The question was how to turn it into a marketplace that worked for workers and venues on the same day.
- 90,000contractors in the existing community
02The limitWhere it stopped scaling
Staffing marketplaces fail when one side turns up before the other.
Most staffing marketplaces stall at launch because they cannot attract workers and venues at the same time.
Hospitality staffing also has a payment problem: workers wait to be paid, and venues wait to fill shifts.
03Find the leverageIdentify · Validate
Build on the network, and lead with pay.
Choosey was built on top of the existing community, so supply and demand were both present at launch.
The offer was centred on instant pay for workers and quick shift filling for venues.
04Build itDesign · Build · Launch
Fast queries, essential workflows, load-tested for a busy Friday.
Database schemas were rebuilt for faster queries and workflows cut to their essentials.
The platform was load-tested beyond several thousand concurrent sessions before launch. Compliance is handled in the background.