The wildfire-risk AI gap isn't the models. It's the motion.

Wildfire-risk firms have world-class AI. What they don't have is a way to sell the same intelligence to agencies, utilities, and insurers at once.

Eli Wood headshot

Eli Wood

July 1, 2026 3 min read
A wildfire-risk signal from a terrain map routed to three different buyers: an agency, a utility, and an insurer.

The problem isn't the models. It's the motion.

Right now, somewhere in the Mountain West, a team of fire scientists is running half a billion wildfire simulations a day. Their models are genuinely good — trained on decades of burn data, calibrated to local terrain, validated against real incidents. They can tell a utility which transmission corridor is most likely to spark the next catastrophic fire. They can show an insurer which zip code will be uninsurable in three years.

They cannot tell you who should sign the check.

That is the real wildfire-risk AI problem. The technology gap closed faster than anyone expected. The distribution gap is widening. Risk firms — from satellite operators to university spinouts chasing their first utility contract — are stuck at a three-stakeholder impasse. Government agencies want peer review and 18-month procurement cycles. Utilities need legal sign-off on any data-sharing before they'll even test a demo. Insurers run their own models and don't want to admit they need yours. Nobody has figured out how to package “credible risk intelligence” so all three buyers can say yes at the same time.

Why this is happening now

Two things converged that cracked this open. First, the liability moment hit utilities hard: after a major utility's market-cap collapse following catastrophic wildfire litigation, every utility executive quietly started taking risk calls they wouldn't have taken in 2022. Adoption of predictive wildfire modeling accelerated — not because the technology changed, but because the risk of not adopting it suddenly looked existential. Second, active fire seasons put regulators, insurers, and utilities on the same news feed at the same time. The window is open.

But being technically capable and being commercially deployable are two different problems. A firm can build the best detection system on the market and still land its first regional client fourteen months after opening the door. The bottleneck is never the science.

The insight: separate the judgment engine from the buyer

Applied AI in a domain where being wrong is expensive follows a few disciplines. Keep a human in the loop where a false negative costs lives or a false positive costs credibility. Separate the deterministic rules from the judgment layer, so the model's probabilistic call is legible and defensible to a skeptical emergency manager. Start where the judgment is both expensive and repetitive. And earn trust with explainability — a risk score nobody can interrogate is a risk score nobody will buy.

None of that is a distribution strategy on its own. The firms that break through stop building a product for “the market” and start answering one question per buyer: what do they need to say yes, and who controls that decision? For utilities, it's often a Director of Wildfire Mitigation — a title that didn't exist five years ago — justifying a line item to a liability-scared CFO. For agencies, an emergency manager who needs something defensible, not just accurate. For insurers, a head of analytics who wants a proprietary edge without building it in-house.

What to do in two days

The foundational work for all three paths is the same: get clarity on what you have, what problem it actually solves, and how to explain it to a room that didn't go to fire-science school. That takes about two days. It produces a clear offer, a distribution channel, and a first conversation that doesn't require a 47-page RFP.

If this is your situation — you have real AI capabilities in wildfire or climate risk, you serve a multi-stakeholder buyer mix, and you're feeling the pull of an active season — spend two days with us. We call it a Foundation Sprint.

About the author

Eli Wood headshot
Eli Wood

CEO, Black Flag Design

Eli Wood leads Black Flag Design, a creative technology company focused on shipping ambitious digital products, AI systems, and design-forward software with a direct point of view on how technology changes work.

Related stories

More from the journal

Pen-and-ink sketch of a small clockwork robot working at a tool-covered workbench late at night while a human sleeps peacefully on a couch in the background, a wall clock reading 2:00 above
ai April 24, 2026 13 min read

The Agent Stays Up Late, Not Me

Every senior engineer knows the right way to set up a codebase. None of them do it. Here’s the four-stage framework we use — The Ratchet — to take a vibe-coded project all the way to a thing you’d trust in production, and the punchline about why this only just became worth doing.

Most teams have always known they should be running tests, type-checking, security audits, accessibility checks, dead-code analysis, prose linting, and a coverage floor. Most teams run two of those. Here’s why that math has finally inverted, and the four-stage framework we use to ratchet a vibe-coded project to a hardened one.

Keith Pattison

Keith Pattison

Founder, Black Flag Design

Read
Black Flag Journal
claude code April 20, 2026 5 min read

What a Year of Claude Code Trails Tells You About Your Team

Claude Code leaves evidence — sessions, commits, PRs, review notes. Read it like a logbook and you'll find what devs actually need to know before they go deeper.

After a year of shipping with Claude Code across real client work, the signal isn't in any single session — it's in the trails. Here's what those trails told us about where Claude Code shines, where it drifts, and the habits devs should build before they lean in harder.

Eli Wood headshot

Eli Wood

CEO, Black Flag Design

Read
Black Flag Journal
playbook April 20, 2026 6 min read

The Black Flag Playbook: Six Principles for Shipping with AI

Battle-tested principles for teams building real software with AI-generated code. Human judgment, tight scope, and weekly evidence — the disciplines that keep AI-built systems reliable.

The six rules we use to ship production software with AI. Small scope, weekly demos, human-led oversight, and continuous improvement — drawn from six months of real client engagements.

Keith Pattison

Keith Pattison

Founder, Black Flag Design

Read