What the floor is asking for — field-report collectors at Vail Village
Vail Village is where field-report collectors runs into spreadsheets as the dispatch board, and Lionshead Village is usually the other pressure the same week, so custom applications around the real workflow only helps if it is aimed at that collision.
A scoped first delivery — a guest shell that posts to your system for field-report collectors
A guest shell that posts to your system is the scoped start because it sits on field-report collectors you can watch in a week at Vail Village, while a field collector that syncs waits and Vail Village keeps the acceptance test geographic.
What on-site actually means here — field-report collectors between Lionshead Village and Golden Peak
Winter and summer do not share a staffing picture at Vail Village, so field-report collectors has to turn down when the calendar turns down while spreadsheets as the dispatch board usually spikes in the opposite month at Lionshead Village.
Vail Village is a short drive from the Eagle County home base, and Lionshead Village and Vail Village are named so we do not invent a suite number in Vail.
How an engagement is framed — spreadsheets as the dispatch board
Staff who cover Lionshead Village in winter and Vail Village in summer should not relearn a product every April, which is why field-report collectors needs a seasonal switch even if the first ship is only a guest shell that posts to your system.
Text-thread assignments is the tell that internal ops apps was never designed for Vail Village, so a field collector that syncs is the smallest change that would matter there.
A map-first conversation before any proposal, set by the real calendar
Skip the brochure, show the work, you leave with yes, no, or wait, book a slot when ready, bring tools you already pay for.