Map
An interactive map of tasks, hubs and hazards with address search and drawing tools, so a coordinator can see the whole response at a glance and create work right where it is needed.
Built in Orange, Texas by people who have run a response out of a church parking lot with a clipboard and a dying phone. Free for residents, free for volunteers, free for every agency working beside us.
The problem
Within 48 hours of a major storm there are more willing hands than there are ways to point them at the right door. Requests arrive as Facebook comments, texts to a volunteer's personal number, and handwritten notes that get rained on.
Meanwhile a volunteer with a tractor sits idle because nobody knew he had a tractor. A woman on oxygen goes three days unvisited because her road off the highway didn't make it onto anyone's list. Two crews show up to the same house while the next block waits a week.
This is not a shortage of goodwill. It is a data problem wearing a disaster costume.
The approach
Every request becomes a task on a map with a priority, a time window, and a list of what it actually takes to finish: the skills, the resources, and the companions.
Volunteers list theirs once. Tasks ask for the same vocabulary. The map does the rest.
Working today
An interactive map of tasks, hubs and hazards with address search and drawing tools, so a coordinator can see the whole response at a glance and create work right where it is needed.
Response hubs classified by type — fire department, church, nonprofit, business — and by the services they offer: food, medical, communications, drop-off, charging. Each has a dashboard with weather, roster, storage and deliveries.
A live activity stream over WebSockets. When a volunteer joins a task, a hub opens, or a situation changes, everyone sees it immediately.
Volunteer profiles organized around Skills, Resources and Companions, with equipment quantities and travel availability, so dispatch stops being a guess.
Development timeline
Four phases. Two are done. Here's the rest — and what it costs to finish.
Founder Jordan Davis not only identified the problem but also began sketching out potential solutions.
Frontend design and features needed for the initial version of the app started with AI assistance.
Help INC has teamed up with Nerd Family Technologies to accelerate the development process, ensuring quality, efficiency and fill in the gaps from AI beginnings.
iOS and Android in the stores, English and Spanish, and data exchange with the county and VOAD systems already in use.
Why donors fund software
Software is the least photogenic thing we do and one of the highest-leverage. A crew that is routed well finishes three houses in the time a guessing crew finishes one. A hub that knows its own inventory stops turning people away for water it has in the back.
And because we give it away, every dollar you put into the build also funds the church two counties over that will never be on our payroll or our roster.
We're choosing pilot partners now, starting in Orange County and working outward — churches, fire departments, VOADs and community groups who will use it for real and tell us where it breaks.