Our Story

We're two software engineers who also happen to be ultra runners. Between us, we've toed the line at some of the most grueling races out there — 50Ks, 100-milers, multi-day sufferfests. We've obsessed over our splits, our nutrition windows, our drop bags.

But somewhere deep in a race — when the wheels start to come off and the only thing keeping you moving is the voice of someone who drove four hours to stand in the dark at an aid station — you stop thinking about yourself. You start thinking about them.

Our crews. The ones running on no sleep, navigating unmarked forest roads, tracking us on their phones while managing a cooler full of food we may or may not want at 3 AM. They do it out of pure love for the sport and for us. And we kept putting all our tools, all our tech, all our planning energy into the runner — and almost nothing into the people making the finish line possible.

The conversation that started UltraCrew happened the way most good ideas do — exhausted, post-race, rehashing everything that went wrong. We kept coming back to the same thing: our crews had no real tools. And the one crewing was drowning — juggling a hand-scrawled pace chart, a group text thread, and three different apps that none of them could get to talk to each other.

We looked at each other and said: we build software for a living. Why is this so hard?

So we built the tool we wish we'd had — not for the runner alone, but designed from the ground up around the crew experience. Real-time coordination, race planning, pacing, and logistics all in one place. Because when your crew is dialed in, you run better. It's that simple.

UltraCrew is now in beta, and we're looking for experienced ultra runners and crew members to help shape it. If you've ever stood at an aid station at midnight willing your runner home, this was built for you.