Product · piloted in production a religious congregation's volunteer team (pilot)
Help arrives in under two seconds.
At a crowded community event, the volunteer who notices something wrong has no reliable way to tell everyone at once. HaaMee makes it one tap — and tells you loudly when to reach for the radio.
The challenge. Medical emergencies, suspicious behavior, a lost child: the volunteer who sees it first needs the whole team to hear, in words they’ll act on. The fallback is radios and shouting.
Why the usual answers failed. Institutional panic-button systems are priced and trained for school districts — quote-only sales and training line items in the thousands. Group chats bury emergencies between announcements. Volunteers rotate weekly; anything that needs training fails.
The stakes. Life-safety latency. Zero training time. Volunteer-owned phones. A community that is — rightly — wary of surveillance.
What we built. A zero-training alert and coordination app. Pick your zone, tap one button (emergencies require a deliberate 1.5-second hold); every teammate’s phone sounds; leads triage on a live board; directed voice messages replace radio chatter where phones are all you have. Each organization runs an isolated instance — its data shares nothing with anyone.
The workflow. An organization claims its instance from a phone in about fifteen minutes. Volunteers join by QR invite in two. From then on: notice → tap → everyone hears. If the network fails, the app says so, loudly: use the radio.
Decisions that mattered.
- Honesty as a safety feature. Delivery is observed, never assumed — “Sent to 11 of 14.”
- A release gate that blocks any build that can’t prove under-two-second delivery.
- Silent versus loud alerts, so “send help quietly” never alarms the public.
- Researched compliance posture (state alert laws, federal security-grant funding) with the gaps stated plainly.
Timeline. Empty repository to a production-deployed pilot in days; the full commercial layer — landing page, pricing, tutorials, automated provisioning — in five weeks.
Outcomes. Ran in production during a congregation’s busiest religious season. The team reports the parking operation used it and liked it; formal adoption follows the organization’s management cycle. Priced, packaged, and ready for the next venue.
Timeline
- Day 1 Sender app, server, live incident board
- Day 3 First two-phone field test
- Week 2 Landing page, pricing, provisioning
- Week 3 Production pilot through a major religious season
Outcomes
- Ran in production during a congregation's busiest season
- Parking operation used it and liked it; formal adoption follows the management cycle
- Priced, packaged, provisioning automated
✓ = repository-measured. Unmarked figures are client-reported.
Reusable capability: Safety-grade real-time engineering · container-per-organization deployment engine