How I built and shipped the NAMYO Volunteer Network app

Before the app, volunteer coordination lived in group chats. Sign-ups were manual, attendance was guessed at, and nobody could answer basic questions: how many volunteers do we actually have, where are they, and which ones showed up last time.

That made growth impossible to plan for. My first job was not writing code — it was mapping the real workflow the coordinators already used, so the product would match how people behaved instead of asking them to change overnight.

I kept the first version deliberately narrow: volunteer profiles, event listings, sign-up, and attendance. Everything else — messaging, badges, reporting dashboards — was written down and postponed. A launch that works beats a launch that impresses.

Mobile came first because almost every volunteer joins from a phone on a slow connection. Screens are light, actions are few, and the sign-up flow is short enough to finish in one sitting.

I also insisted on a single source of truth for volunteer records. Once coordinators trusted the numbers in the app, the spreadsheets died on their own.

I ran the IT function alongside the build: assigning work, reviewing what shipped, and keeping the launch-event technology — registration, devices, connectivity, screens — from becoming a surprise on the day.

Weekly checkpoints with the leadership team kept scope honest. Anything that could not be demonstrated in a working build was not counted as done.

The app went live for the December 2025 launch event, with onboarding handled in person so volunteers left the room already registered. I also secured funding for the initiative, which paid for infrastructure and the launch itself.

What I would repeat: freeze scope early, test on the cheapest phone you can find, and rehearse launch-day operations end to end before the audience arrives.