Skip to main content

CASE STUDY

Building a nationwide
movement with AI.BROS.

A grassroots men's health organisation running circles across New Zealand — coordinated by AI, not enterprise software. Events platform, knowledge brain, meeting notes pipeline, and community tools built in hours for $0.

20+

local groups nationwide

7

MCP tools

$0

enterprise software costs

Hours

to build, not months

THE PROBLEM

A growing movement with no infrastructure.

BROS (Brotherhood of Real Ones / Stand) is a men's health organisation running circles across New Zealand. Not a corporate wellness programme — a grassroots movement. Local coordinators in cities and towns around the country hosting regular men's circles for connection, vulnerability, and mutual support.

The organisation was growing, and the coordination was falling apart. Events were scattered across Facebook pages and WhatsApp groups. Meeting notes lived in personal notebooks or nowhere at all. Decisions made in one meeting were forgotten by the next. New coordinators had no way to find what had been discussed, decided, or tried before. There was no shared knowledge base, no event visibility, and no communication infrastructure beyond personal messaging.

BROS had no budget for enterprise software. No Salesforce CRM, no Monday.com project management, no Eventbrite fees. The organisation runs on volunteer energy and small-scale funding. Whatever was built had to be free to run, simple to use, and powerful enough to coordinate a nationwide network of independent groups.

The challenge wasn't technical ambition. It was the gap between what a grassroots organisation needs and what it can afford. BROS needed the coordination capability of a well-resourced national organisation — event management, institutional memory, meeting notes, communication tools — built from scratch, for free.

WHAT WAS BUILT

National coordination. Zero enterprise software.

Four connected systems that give BROS the coordination capability of a well-funded national organisation — without the cost.

bros-events — nationwide event platform

A dedicated events platform showing every men's circle happening across New Zealand. Coordinators can list their events with location, time, frequency, and description. Anyone can browse by region or find the nearest circle. One URL replaces dozens of Facebook events pages and scattered WhatsApp messages. Built on Next.js, deployed on Vercel.

Local Fires map

A visual map showing active BROS circles across the country — each one a "local fire." The map makes the movement visible at a national scale. New members can see that this isn't one group in one city — it's a network spanning the country. Coordinators can see where there are gaps and where new circles might take root.

Dedicated MCP brain — organisational memory

A BROS-specific MCP server with its own knowledge brain. Every decision, discussion, and insight is captured and searchable. "What did we decide about the membership model?" — answered in seconds. "What was discussed at the March meeting?" — found and summarised. The brain grows with every interaction, building institutional memory that survives coordinator turnover.

Meeting notes pipeline

Meeting transcripts (from voice notes or calls) are processed into structured meeting notes — TLDR summary, topic sections with key points, and checkbox action items. Notes are automatically saved as Google Docs in the BROS Drive folder, organised by topic subfolder. No more lost minutes. No more "what did we agree on?" The meeting notes system routes content to the right folder, reuses topic categories, and makes everything searchable.

Google Drive integration

All BROS documents — meeting notes, planning docs, resources — are automatically routed to the correct subfolder in BROS's shared Google Drive. The MCP server handles folder routing, naming conventions, and deduplication. Coordinators across the country can access everything through Drive without needing to learn a new platform.

Community coordination tools

Airtable-backed task and project management for the BROS leadership team. Track what's being worked on, who's responsible, and what's blocked. Lightweight enough for a volunteer team, structured enough to keep a national movement organised. Connected to the brain so decisions and context flow between tasks and knowledge.

TECH STACK

Tools a volunteer team can maintain.

Everything chosen for simplicity, free tiers, and long-term sustainability. No vendor lock-in. No subscriptions the organisation can't afford if funding changes.

Events Platform

Next.js, Vercel (free tier)

Knowledge Brain

Custom MCP server, 7 dedicated tools

Meeting Notes

MLX Whisper transcription, Google Docs

Document Management

Google Drive (shared, auto-routed)

Task & Project Tracking

Airtable (free tier)

AI Orchestration

Claude Code, MCP protocol

RESULTS

Coordinators coordinate. The system remembers.

Nationwide events visible on one platform. Anyone in New Zealand can find their nearest men's circle without joining a Facebook group or knowing someone in the network.

Meeting notes auto-routed to Google Drive. Every discussion is captured, structured, and searchable. New coordinators can onboard by reading what came before.

Organisational brain captures every decision and context. "What did we try for recruitment in Auckland?" — answered from the brain in seconds, not from someone's memory.

Local Fires map shows the movement's national footprint. Useful for fundraising, partnerships, and helping new members understand the scale.

Zero enterprise software costs. The entire coordination stack runs on free tiers. BROS's limited budget goes to the work, not to SaaS subscriptions.

Coordinators across the country self-serve. They don't need to ask a central administrator to find a document, check a decision, or list an event.

TIMELINE

Built in hours, not months.

The entire BROS coordination stack was built in focused sessions using Claude Code. The events platform, MCP brain, meeting notes pipeline, and Drive integration — all built and deployed rapidly because the patterns had already been proven on other projects.

This is what happens when you solve infrastructure problems once and apply them across organisations. The voice-to-meeting-notes pipeline was built for Mangaroa Farms. The MCP brain architecture was proven across multiple projects. The Google Drive routing was already working. Adapting these systems for BROS was a matter of configuration, not invention.

That's the compounding advantage of building AI infrastructure — each new project benefits from everything built before. What would take a traditional development agency months to scope, build, and deploy was operational in hours.

Running a community
without the infrastructure?

Events, knowledge management, coordination tools, and communication — built for your organisation, running on free-tier infrastructure. One discovery call to see what's possible.

Building a Nationwide Movement with AI — BROS Case Study | Build With Billy