What we would touch first — data copies that should be integrations at Avon Station
Around Avon Station, peak week as the test environment still waits until morning, while Beaver Creek adds data copies that should be integrations on a different clock, which is why workflow automation on the painful loop, not a canvas full of toys is a response to those two places rather than a swapped town name.
How the first loop is chosen — one watched automation for data copies that should be integrations
We would rather install one watched automation at Avon Station and stop than decorate a stack, and seasonal mode switches becomes a second loop only when a beautiful unused Zapier folder is still true at Beaver Creek.
What on-site actually means here — data copies that should be integrations between Beaver Creek and Village at Avon
Resident traffic and visitor traffic mix differently at Avon Station than at a ski-base mall, so workflow automation on the painful loop, not a canvas full of toys is a fit there when it is one watched automation rather than a slogan.
Data copies that should be integrations has to be explained by whoever closes at Avon Station in Avon, which is what on-site means here rather than a storefront on Beaver Creek.
What we will not pretend — peak week as the test environment
Staff who cover Beaver Creek in winter and Village at Avon in summer should not relearn a product every April, which is why data copies that should be integrations needs a seasonal switch even if the first ship is only one watched automation.
A beautiful unused Zapier folder is the tell that seasonal mode switches was never designed for Avon Station, so a seasonal switch that is documented is the smallest change that would matter there.
How the work is framed before anyone talks numbers, built from a constraint
Look at season and staff load, you leave with yes, no, or wait, pick a time that works, name the season that actually hurts.