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
- 05EvolveAfter launch
01The expertiseWhat the company had
Brokers who knew the rules of a market worth billions a year.
Australian water brokers trade entitlements worth billions of dollars every year, across overlapping state and federal rules.
Nick Johnston brought that on-the-ground knowledge: which rule applies to which trade, what each registry needs, where the fees come from.
02The limitWhere it stopped scaling
Every trade meant manual checks and manual records.
Sprawling documentation, shifting rules and siloed data meant each trade was verified and recorded by hand.
That time came straight out of time with clients, and the knowledge that made it work stayed with the people who had it.
03Find the leverageIdentify · Validate
Test with pilot brokers before building.
Discovery workshops with pilot brokers, and click-throughs tested within a fortnight, showed where the real friction was: duplicate data entry and opaque fee calculations.
The product strategy was built around the trade lifecycle, with compliance as the product rather than the obstacle.
04Build itDesign · Build · Launch
One structured, auditable workflow.
Automated form generation, real-time rule validation and a dynamic ledger, in a broker-facing front end that iterated quickly on feedback.
A security-first back end protects sensitive entitlement data. The architecture is API-first, so the platform can connect to government registries and ag-tech dashboards as standards change.
05EvolveAfter launch
Victoria first, then the Murray-Darling Basin.
Aquifa launched to Victorian brokers first and is now live across three states.
The first-season beta ran clean, and the roadmap follows the standards as they evolve across the Basin.