The Festival Ticketing Stack Held Together by One Retired Teacher: Inside Small-Town Tourism's No-Code Habit

The tourism office for a town of 4,300 people in the Ozarks has a staff of one and a half. The 'half' is Denise, a retired high school biology teacher who volunteers two days a week and, without ceremony, built and maintains the entire digital infrastructure for the town's visitor economy: a Glide app with hiking trail maps, a shop directory, festival ticketing, and a lodging availability board that local innkeepers update through a form she built in twenty minutes on a Tuesday.

Nobody hired her. Nobody reviewed her code, because there isn't any. And if Denise decides next spring that she'd rather spend her Tuesdays at the lake, the town's entire digital visitor experience — the thing that now handles 60% of Pumpkin Festival ticket sales — goes with her.

This scenario is playing out in hundreds of small towns across America, and almost nobody is talking about it.

What Understaffed Bureaus Are Actually Building

Spend a week calling visitor bureaus, chambers of commerce, and main street associations in towns under 10,000 people, and a pattern emerges. The professional-grade tourism platforms — the ones with sales reps and onboarding webinars — are priced for cities with real budgets. A small bureau facing a $10,000-plus annual contract does what small organizations always do: it improvises.

The improvised stacks look remarkably similar from town to town:

• Google Sheets as the town database. Every shop, restaurant, trailhead, and historic marker, lovingly categorized by a volunteer or an overworked director.
• Glide or Softr as the public face. Mobile-friendly visitor apps and web directories, often better maintained than the official site, because they're easier to update.
• Event ticketing cobbled together from forms, payment links, and spreadsheets — occasionally a Tally form wired to a Stripe account, occasionally just Venmo and a prayer.
• Zapier or Make gluing it together, usually set up once, by one person, and never touched again.

The results can be genuinely impressive. We saw a trail conditions app in western North Carolina that hikers check more faithfully than the official Forest Service page. We saw a chamber directory in Kansas that auto-generates a printable map for the annual visitor guide, saving the director what she estimates as 'three solid weeks of InDesign work I do not know how to do.'

The budgets involved would make a SaaS sales rep weep: frequently under $100 a month, all in.

The Single-Point-of-Failure Problem

Here's the uncomfortable part. In most of these towns, exactly one person understands the stack. Ask who maintains the festival ticketing app and you'll hear a name, not a process. Ask what happens when that person moves, burns out, or — this came up more than once — passes away, and you'll get a pause on the phone.

The failure modes are unglamorous but real. A Google account gets locked. A free-tier limit gets hit during the busiest weekend of the year. A platform changes its pricing, and a $0 tool becomes a $59-a-month tool right before ticket sales open. One main street director told us she discovered their entire shop directory was living in the personal Google account of a former board member who'd moved to Arizona. Recovery took two months and one very awkward phone call.

There's also a platform-risk layer: these civic tools are often built on consumer-grade free tiers that were never designed for public infrastructure. When the vendor changes something, there's no IT department to notice before the town's visitors do.

What Actually Works — and What Should Change

To be clear, the case for these stacks remains strong. A $40-a-month Glide app that a town can actually maintain beats a $15,000 custom build it can't. The improvisation isn't a failure of small-town America; it's a rational response to a software market that priced them out.

But a few cheap habits would de-risk the whole model, and every town running a volunteer-built stack should steal them:

1. Own the data. Everything should live in a Sheet or Airtable base owned by an organizational account, not a volunteer's personal Gmail. Export it quarterly.
2. Document the setup. A single Google Doc — 'how our ticketing works, logins in the chamber safe' — turns a person-dependent system into a town-dependent one.
3. Build a bench. At least two people should have access to everything. Denise's Ozark town now has a 'backup Denise.' She is, appropriately, another retired teacher.
4. Watch the free tier. Know your platform's limits before your peak weekend finds them for you.

The Bigger Picture

There's a policy-shaped hole here. Small towns are quietly building public digital infrastructure on consumer tools, unpaid, because no product exists for them and no program funds them. That's a gap — and, depending on your perspective, either a market opportunity or a quiet civic vulnerability.

Denise, when we raised the what-if-you-left question, laughed. 'I made a binder,' she said. 'It's in the drawer with the parade permits.'

The binder exists. The town knows where it is. For now, in the arithmetic of small-town resilience, that counts as an IT department.