About

I’ve been around Fitzroy Doncaster Cricket Club for most of my life — as a player, a committee member, and just another volunteer roped into whatever needed doing that week. Cricket clubs like FDCC run almost entirely on people giving up their own time, and there’s always more to do than hands to do it.

The thing that finally pushed me to build Morrie was match-day content. Every weekend, someone had to pull together the team sheet, the result, the milestone posts — find the photos, get the sponsor logos right, post it all before everyone lost interest and moved on. It’s a small task on paper, and yet it quietly ate hours every single week, on top of everything else volunteers were already carrying.

I have a background in software, so I did what came naturally: I built a tool to fix it for FDCC. Morrie started as exactly that — a way to turn match data into ready-to-post cards without the Saturday-night scramble. It grew from there, the same way club admin does: sponsor tracking needed a home, so did memberships, renewals, rosters, the annual report. Morrie is still the same idea underneath — take the repetitive parts of running a club off the small group of people who keep it running, so more of their time goes to the club itself.

FDCC is still where it gets used first and tested hardest. Every feature exists because a real committee needed it, not because it looked good on a roadmap.