PlanUltra builds a shareable crew sheet your team can open on their phone, print as backup, and navigate from at every aid station — no app, no account, works without cell signal.
One URL. Open it on any phone. Print it as backup. Navigate directly from it — even without signal.
Built by the runner. Everything the crew needs.
Each crew-accessible station includes a Google Maps link and a QR code for offline directions. Remote trailheads, forest roads, unmarked pull-offs — your crew can find them at 3am.
The sheet tells your crew exactly how long it takes to drive to the next station, so they know whether to leave immediately or whether they have time to rest. No more guessing.
Drop bag items, gear, food, and what to do if you're talking yourself out of the race at mile 70. It's all in the plan. They read it before the race and execute it on the day.
Your crew knows when to expect you to need a headlamp, what temperature to dress for, and when the sun comes up. PlanUltra pulls conditions for your race date so your crew can prepare, not react.
Built by the runner. Used by the crew.
Enter your race, aid stations, and cutoff times. PlanUltra maps out the course and pulls weather and light conditions for race day.
“Takes about 20 minutes”
Drop a pin for each crew-accessible station. Add parking notes, what you'll need at each stop, and anything else your crew should know — including what to do if you want to bail at mile 70.
Your crew gets a single URL. It works on any phone, prints cleanly, and has everything — directions, drive times, gear lists, conditions — no app, no account needed.
“As a bonus, you've also built yourself a solid race plan”
I'm a product manager who runs ultras on weekends. PlanUltra exists because I wanted a tool like this and couldn't find one — so I built it. It's a hobby project, not a startup. There's no VC money, no growth target, no free trial leading to a paywall.
Running the server costs me almost nothing — AWS and Mapbox both have generous free tiers that easily cover a tool at this scale. An account is required so your plan has somewhere to live between sessions; that's the only reason it exists. The code is open source on GitHub — if you want to fork it, run your own copy, or just look under the hood, go ahead.
“It's also a live example of my product work. If you're curious about that side of things, find me on LinkedIn.”
Give them everything they need so they can focus on being there for you.
Build your crew plan