Catskills weekender — The guest already paid Airbnb. They haven't paid the town yet.

Hudson Valley tourism runs on strangers who arrive Friday, leave Sunday, and remember the rental — not the bakery. That's not because the bakery is bad. It's because the app layer is rented.

The town / the place

Weekend traffic from New York City into the Catskills — cabins, weddings, leaf-peepers, the whole seasonal swing. The money lands in booking platforms and national brands first.

The problem

Tourist spend leaks the same way payroll leaks — through interfaces you don't own. QR codes on the fridge that go nowhere useful. "Things to do" lists that are SEO spam. A guest book that's a notebook.

The leak: the guest's attention is captured before they cross the county line.

What we built

A guest-facing layer — QR splash, lightweight auth if you need it, local directory, booking hooks to real operators — designed so the town's merchants sit in the path of the spend, not as an afterthought on page six of a PDF house manual.

Source: BMG + Woodstock ecosystem packet — the same diagram language we used to connect studio, hospitality, and directory rails.

The math

Email capture on join isn't a gimmick — it's consent-based re-marketing that doesn't route through a Silicon Valley retargeting tax. Compare $0 marginal cost for a second visit offer from the innkeeper versus 15–30% OTAs on the first booking — different line item, same fight: who owns the relationship.

What it means

Tourism apps should make money for the town — not as a slogan, as routing. If the guest's first tap is yours, the second tap can be the diner, the guide, the venue, the gear rental shop on Main Street.

Start This Week

24 hours: Replace one generic "local tips" printout with three links you control.

7 days: Add a single QR → directory profile for one high-margin partner (food, experience, transport).

90 days: Measure repeat direct bookings against OTA share — if you won't measure it, don't pretend you're fighting extraction.