Why We Built Ascents
The problem we kept seeing in the mountain industry — and why a spreadsheet was never going to fix it.
Ascents Team
January 15, 2026
Every mountain guide we’ve ever spoken to has had a version of the same story.
A client shows up for a technical alpine course. On their application form, they described themselves as “very experienced” with “multiple alpine routes.” The guide meets them on day one. Within an hour, it’s clear the application was aspirational. The group’s safety is now a management challenge that shouldn’t have existed.
Or this version: an aspiring guide spends three years putting in serious days — real alpine terrain, technical rock, winter conditions — working toward their first professional certification. When the application window opens, they sit down to compile their logbook and discover that half of what they remember is documented in a notebook at home, a quarter is on a phone they lost, and the rest exists only in their memory.
Or this one: a guide company has been operating for fifteen years with an excellent safety record. A client is injured on a trip. The investigation asks for documentation of the pre-trip risk assessment, the client’s stated experience level, the weather decision process, and the guide’s certification at the time. The company’s admin team spends three weeks reconstructing records from email threads and paper files.
These are not edge cases. They’re the ordinary friction of an industry that hasn’t had the right infrastructure.
What already existed
When we started researching the space, we found two categories of existing tool.
The first was generic activity tracking apps — Strava, Garmin Connect, AllTrails. Excellent for consumers. Not designed for professional documentation, verification, certification tracking, or risk governance.
The second was enterprise risk management software — built for construction, oil and gas, healthcare. Powerful, but requiring six-figure implementation budgets, dedicated IT teams, and months of configuration. Completely inaccessible to a one-person guide operation or a small guide company.
Nothing existed in the middle: purpose-built for the mountain industry, affordable for independent guides, and scalable to company-level operations.
What we decided to build
Ascents is built around three core beliefs.
First: experience should be verifiable. A logbook entry that can be countersigned by the guide who was with you is worth far more than one that can’t. We built verification into the core of the product — not as an add-on.
Second: certification pathways should be transparent. Aspiring guides shouldn’t have to guess whether they’re on track. We built tracking against the actual requirements of ACMG, AMGA, IFMGA, and CAA certifications directly into the product.
Third: risk governance should be a natural part of how guide companies work — not a separate compliance exercise. We’re building the Safe System of Guiding framework into Ascents Pro so that documentation happens as a byproduct of running trips, not as an overhead on top of running them.
Where we are now
Ascents is live and in active use. The consumer and aspiring guide product is fully operational. The professional guide and company tools are in active development, with early access available now.
We’re building this with the mountain community. If you’re a guide, an aspiring guide, or run a guide operation — we’d love to hear from you.