Built on the line · Tuned for the field
Run the mobe, not the phone tree.
One shared picture of who's available, who's up next, and who's rolling. Coordination software for wildfire mobilizations, built by the firefighters who want to fight fires, not phone trees.
The first hour of a mobilization
A mob call lands. The churn has already started.
There's a major fire somewhere. Someone calls for help. And somewhere else, a coordinator has about an hour to figure out which rigs are actually available, who's current on their quals, whose turn it is, and who can really roll tonight. He's working it across texts, two group chats, and a phone that won't stop buzzing. Half his statuses went stale days ago, and he doesn't know which ones.
During the wildfire season, that scenario is playing out over and over: every fire, every region, a flurry of activity to get rigs and firefighters deployed, with nothing shared underneath it. Apparatus status lives in one place. The priority queue gets kept by hand somewhere else. Crew rosters live in spreadsheets scattered across every district. Forms are filled out by hand, mailed or faxed or emailed, and information disappears. The record, the thing you'll need when someone asks months later who mobilized and who didn't and why, is scattered across email and chats and memories.
Fighting wildfires is hard enough. Mobilize is built to make it easy to get the firefighters into a position to do it.
Two ways in.
You run a district.
Get your rigs and people on the road faster, get your information to the people who need to have it, and stop re-keying rosters that already live somewhere else.
For fire districts →You run the program.
Give every district one consistent way to mobilize, configured to your chain of command, with an audit-grade record you can stand behind.
For program leadership →We're firefighters. We're also the people you'd want building this.
The two of us who built Mobilize are structure and wildland firefighters at San Juan Island Fire & Rescue, so we know how messy and broken the process of getting resources to the fires is from being in the thick of it, getting that last-minute text message to grab our Red Cards and go. But a lot of fire software gets built by firefighters. What makes us more unusual is the rest of our day jobs: we've spent our careers building software that isn't allowed to go down, government cloud infrastructure on one side, medical devices on the other, the kind of systems where an outage has life-and-death consequences attached. We built Mobilize the same way.