Weather built around every field.

Why I built FieldCast

A simpler way to understand what the weather means for every field.

I’ve spent my career working at the intersection of agronomy, agricultural data, mapping, and practical field decisions. Much of that work has involved taking complicated information—soil maps, weather records, crop development, disease risk, field boundaries, and management considerations—and turning it into tools growers and agronomists can actually use.

That experience taught me that agriculture does not have a shortage of data. The harder problem is making that information clear, timely, and useful when someone is deciding what to do in a particular field.

Weather is often the first thing growers check each morning. Traditional weather applications make that easy, but they generally stop at a city, ZIP code, or location on a map. They can tell you what the weather may be, but not always what those conditions mean for the fields where the work will happen.

I developed FieldCast around the idea that a familiar weather application could become much more useful if the field—not the nearest town—became the center of the experience.

FieldCast can still be used simply to check current conditions, hourly weather, maps, or the extended forecast. When more context is needed, that same forecast becomes connected to individual field boundaries, soil conditions, crop timing, seasonal rainfall, operation windows, and longer-term trends.

My goal is to close the gap between checking the weather and deciding what that weather means for the work ahead—without losing the simplicity that makes a good weather application useful in the first place.

“The forecast should remain simple. The intelligence behind it should understand the field.”