How We Built Baseline Maps from a Frustrated Fishing Weekend

Baseline Maps was not pitched. It was not roadmapped on a whiteboard or scoped in a deck. It started with one of us standing on a gravel bar in February, refreshing a government website on a cold phone, trying to figure out whether the river was fishable. The answer was no. The frustration was yes. That weekend turned into a notebook, then a prototype, then an app that now spans fishing, hunting, and foraging. This is how that happened, in order, with the people who pushed each step.

The frustrated weekend

The first version of this story has no code in it. It is a steelhead guide standing in waders, screenshotting flow charts from a USGS site, cross-referencing a state agency PDF, opening a weather app, opening a tide app, then closing all of them because the river was already too high. We were checking five apps and a stack of agency documents to answer one question: should we fish tomorrow? That stack was the product brief. Nothing existed that put the answer in one place. The decision to build started in that gap.

Three rivers, one user

The first build covered three rivers. That was it. One of us could open the app and see flow, trend, and a rough fishability read in under ten seconds. There was no account system, no map, no notifications. There was no logo. The single user was a steelhead guide who already had the agency bookmarks memorized — the app just made the bookmarks faster. Within a month he was using it more than the websites. That was the signal we needed.

We almost killed it twice in the first ninety days. Once because a friend with a real product job told us nobody pays for fishing apps. Once because we shipped a flow-trend chart that was wrong by a factor of ten and the guide caught it before we did. The second moment was the one that taught us the rule we still follow: the people using the app catch things faster than we will, so the feedback loop has to be the shortest part of the build.

From a fishing tool to Driftline

We named it Driftline once it had a real user beyond the original one. A second guide, then a third. Then a Kenai dipnetter who needed sockeye return numbers and tide stage in the same glance and could not find anywhere that put them together. He sent a list of every data source he was checking manually. We added them one at a time. Driftline became the calm, data-forward fishing app we wished existed — the opposite of a hype feed. Quiet, dense, fast.

The dipnetter changed how we thought about coverage. He was not on a river — he was on a tidal flat. The model in our heads up to that point had been “river plus flow.” His use case forced us to expand it to “any water body that decides whether someone goes today.” That meant tides, marine conditions, lake levels, ice-off windows, hatch timing. Each one shipped quietly as users asked. Six months in, we had moved from three rivers to eleven hundred.

When the first Founder asked about hunting

The pivot happened in a single message. A Founder who used Driftline for summer trout asked, in October, whether the same approach would work for his blacktail hunt. Could we show GMU boundaries, public versus private land, harvest stats, and the regulation that applied to the exact tag in his pocket? We could. We did. Ridgeline started as a single weekend prototype for one blacktail hunter in southwest Washington and grew into a hunting mode that now covers nine Western states (WA, OR, ID, MT, CO, WY, UT, AZ, NM), with new states added as users in those states ask.

The build pattern was identical to the fishing one. One user with a specific season, a specific tag, a specific frustration. We watched him plan a hunt across a kitchen table and rebuilt the planning screen three times until the flow matched how he actually moved through the decision. Then we shipped it to the rest of the community and waited to hear what we got wrong. We got plenty wrong. Each thing got smaller and more specific over time, which is how we knew the foundation was holding.

Becoming Baseline Maps

By the time Ridgeline shipped, we were running two apps inside one app and the naming was confusing everyone. A user emailed asking why his hunting buddy could not find “the fishing one” in the App Store — they were the same app, with a mode toggle. We sat with that confusion for a week and then renamed the umbrella. Baseline Maps became the platform. Driftline became fishing mode. Ridgeline became hunting mode. A forager in the Cascades asked next, and that became foraging mode. Same map, different lens.

What we won’t change

Some things are non-negotiable, and they were decided early enough that they feel like ground rules now. The app does not sell user location data. It does not run an activity feed. It does not gamify trips. It does not push notifications that are not earned. It does not ship features we cannot personally use on a Saturday — every release goes through one of us on a real trip before it touches users. The interface stays calm because outdoor decisions are already loud enough.

We also do not build the app in public for marketing reasons. We build it in public because the people using it have sharper opinions than we do. A blacktail hunter watching a draft regulation overlay will tell you what is wrong with it in ninety seconds. A guide will tell you the exact threshold at which a flow trend stops being useful and starts being noise. We listen to that, and the build gets better. That is the whole loop.

The team is small on purpose. There is no marketing department. There is an in-app feedback box, a Discord, and an email address one of us reads every morning over coffee. When a user reports a problem, the same person who reads the report often fixes it the same day. The cost of that closeness is that we move slower than a venture-backed competitor. The benefit is that nothing ships that we would not personally rely on in a canyon with no signal.

We also write our own tooling for the data work, because the public datasets are messy and the agency feeds break in interesting ways. Our infrastructure is built to keep working when the upstream sources do not. When a state fish and wildlife site went down for three days last fall, the app kept showing the last good regulation snapshot with a small timestamp so users knew exactly how fresh the data was. That is the kind of detail we obsess over and rarely talk about.

What’s next (and who decides)

The roadmap is not on a website. It is in the app, under a tab called the Development Queue, and the order is partly ours and partly yours. Every Founder can see what is being worked on, what is queued behind it, and what just shipped. Items move up the queue when users in our community ask for them more than once. They move down when no one mentions them for a month. There is no public quarterly roadmap because we genuinely do not know what the next quarter looks like until the people using the app tell us.

What we do know: more states for hunting, more provinces for fishing, deeper marine data for the coastal users who have been patient, and a continued refusal to add a single feature that would make the app louder. If you are reading this and there is a layer, a dataset, or a workflow you wish existed, open the app, find the Development Queue, and tell us. That is genuinely how the next version gets built. The frustrated weekend that started this is happening to someone right now. The next mode of Baseline Maps is probably already in their head.