Case study · Multi-day walking tours · The Alps

Proposals in under an hour, and a new route before dinner when a pass closes

A family-run operator of inn-to-inn walking holidays in the Alps wanted its planners back from the spreadsheet. A 12-week pilot of Itinerary Studio, Route Engine and Concierge cut proposal time and moved in-trip re-planning out of late-night phone calls.

An alpine route drawn as a necklace of huts, with a hand re-threading one bead around a snowfield.
Field noteRe-threading one bead kept the whole week intact.

Measured, not promised

Pilot results

Measured by our team and the operator's planners during the 12-week pilot, against a four-week baseline taken before anything changed.

Median time to a send-ready proposal
3.4 h → 52 min
Pilot median, weeks 5–12, 214 proposals
Median time from a stage closure to walkers holding an approved new plan
38 min
Baseline about 2 h 50 min by phone; 14 closures affecting 31 groups, weeks 9–12
Proposals accepted with no more than one revision
63%
Up from 41% in the baseline sample
After-hours calls to the duty planner
−46%
Pilot weeks 9–12 vs. the same weeks a year earlier

Pilot measurements from one operator in one season, not a forecast for your business. We report medians, not best days.

The situation at a glance

What we found in the Discovery Sprint that came before the pilot.

  • Who: a family-run operator of guided and self-guided inn-to-inn walks in the Alps, with one planning office
  • What they sell: six- to twelve-day walking holidays, most of them tailored to the walkers
  • Suppliers: small inns, mountain huts, luggage-transfer drivers and local guides, many confirming by email or phone
  • What hurt: proposals took most of a morning, and mid-trip closures were handled by phone, often after dark
  • Pilot scope: 12 weeks, one season, one planning team, a person approving every change

Timeline

What we built, week by week

Planners kept their old process running in parallel until week 6, so every comparison had a control.

  1. Weeks 1–2

    Stage library and supplier truth

    We mapped about 180 stages and reconciled inn closing days, luggage-transfer cut-offs and last-bus times from three sources into one table the planners could correct.

  2. Weeks 3–5

    Constraints and first drafts

    Route Engine learned the operator's rules: daily effort budgets, rest-day placement, transfer cut-offs. Itinerary Studio drafted in shadow mode; we compared its drafts with the planners' every Friday.

  3. Weeks 6–8

    Drafts in daily use

    Planners began sending edited drafts to real travelers. Concierge ran in shadow mode on in-trip messages, drafting re-plans that a planner reviewed but did not send.

  4. Weeks 9–12

    Re-planning with approval

    Closure-triggered re-plans went live: draft route, inn holds requested by email, luggage instructions updated, and one approval from the duty planner before walkers heard anything.

The situation

The operator sells walking holidays the old-fashioned way: a conversation first, then a proposal built by hand. A typical request reads like a letter. Two friends in their sixties, one with a knee that dislikes long descents, nine days in early September, “somewhere with lakes, nothing scrambly, and at least one rest day with a good view.”

Answering it meant opening the stage spreadsheet, checking which inns were open that week, adding up ascent and descent per day, confirming luggage transfer between the chosen villages, and finding the last bus in case a stage needed shortening. Then writing it up. It took most of a morning, and in spring the team handled dozens of requests a week.

The second problem arrived in season. When early snow closed a high pass or rockfall shut a path, the duty planner phoned inns, re-routed luggage and called walkers, often between 8 and 10 PM, after the guides’ reports came in. Nobody was doing it badly. There was simply no way to see the whole chain at once.

What we tried first

Our first prototype generated complete proposals straight from the brochure and a few hundred past itineraries. The prose was lovely. The routes were not: two of the first ten drafts sent walkers into a village on the inn’s closing day, and one placed a 1,100-meter descent on the morning after the longest day of the trip.

That told us the order was wrong. Language comes last. A route has to be feasible before anyone writes a sentence about it.

We also dry-ran sending re-plan suggestions straight to walkers. It was fast, and it was a mistake: in the test inbox, alternatives arrived before the inns had confirmed rooms. We switched to drafts that a planner approves, and that is how it has stayed.

What we built

A stage graph, not a stage spreadsheet. Roughly 180 stages became a routable network: distance, ascent and descent, surface, exposure, shade, inn and hut options, luggage-transfer cut-offs, and public-transport bail-outs for shortening a day.

Energy budgets per walker. Route Engine holds each traveler to a daily effort budget built from distance and climb, and places rest days where the cumulative load says they belong. The knee that dislikes descents becomes a constraint, not a note in the margin.

Drafts with reasons. Itinerary Studio turns the request into a draft proposal with a line of reasoning for every choice (“Rest day in the lake village: day four is the trip’s biggest climb”). Planners edit, reorder and rewrite; the engine re-checks feasibility after every edit.

Re-planning that waits for a person. Concierge watches the operator’s own closure reports, guide notes and weather data. When a stage closes, it drafts a revised route for each affected group, requests holds from inns by email, and puts the whole package in front of the duty planner. One approval sends walkers the new plan by WhatsApp or SMS, with luggage instructions changed to match.

What changed

The numbers are above. What the planners noticed first was different: a morning of arithmetic became twenty minutes of reading a draft and a longer, better conversation with the traveler. Proposals went out the same day more often than not.

Re-planning moved from the phone to a queue. On the evening that snow closed the season’s highest pass, four groups had revised routes approved and delivered before 7 PM, and the duty planner made two phone calls instead of eleven.

What we’d do differently

Clean supplier data before anything else. Inn closing days lived in three places, and they disagreed. We lost most of week three reconciling them. We now open every pilot with supplier truth.

Let guides define exposure. Our first exposure ratings came from map data. The guides corrected about a fifth of them in a single afternoon. That afternoon belonged in week one.

Measure per planner, not only per team. The median hid a spread: two planners sent drafts nearly as written, one rewrote almost everything. All three were right for their travelers; looking sooner would have helped us tune the drafting.

The drafts don't decide anything for us, and that's exactly why the team trusts them. They do the arithmetic, show their working, and leave the judgment where it always was.

Operations director, family-run walking-tour operator in the AlpsAt the end-of-pilot review

Have a season like this one coming?

Tell us where your planners' mornings go. We start with a Discovery Sprint and measure your baseline before we build anything.