Case Study · Hospitality / outdoor recreation
Google thought they were a completely different business.
The situation
Six repair attempts on a broken form. The schema said someone else.
The park had opened recently: 23 sites across a short-term RV and camping operation and 31 long-term residential rental units. The location had real demand drivers: strong seasonal swings, with peak-event weekends commanding several times the base nightly rate. But the digital foundation was actively suppressing that demand.
The prior vendor's site contained JSON-LD schema markup that identified the business as an entirely different company: wrong name, wrong location, wrong phone number. Google's index reflected that identity. The contact form had been broken for an extended period; six repair attempts had been made. Booking ran through a third-party marketplace platform at $100/mo plus a 10% commission on every reservation. The owner had no conversion tracking: "I have no idea what my actual conversion rate is."
The peak-event pricing premium, several times the base rate, existed in the owner's head and nowhere else. The 31 long-term rental units required approximately 70 manual texts per renewal season, sent individually by the owner. After-hours inquiries received no response. The operation ran on the owner's attention, not on systems.
What we architected
Correct the identity. Build the booking layer. Automate the journey.
Foundation first. The wrong identity and broken form meant every other system was building on sand. Phase 2 deploys the booking layer, SMS automation, inquiry handling, and manager dashboard onto the clean foundation Phase 1 created. It brings together the booking system we built, guest-journey automation, and the after-hours inquiry agent.
Phase 1: Foundation
Replace the broken vendor site with a correct, professional presence. Live now.
Identity correction
Working contact infrastructure
Owner-editable admin panel
Forward-compatible architecture
Phase 2: Autonomous Guest Journey
Native booking, dynamic pricing, pre-arrival SMS, and 24/7 inquiry handling. Pending third-party contract end.
Native 4-step booking modal
Owned reservation data layer
Pre-arrival SMS automation
After-hours inquiry agent
Manager dashboard
Outcomes
Baseline figures from the engagement. Phase 2 projection labeled.
Phase 1, the website, is live. Phase 2 is designed and waits on the third-party booking contract ending, so its figures are labeled as planned. Baselines are as reported by the client.
Continue
Other case studies.
Engagement starts here
Start with the assessment.
A few questions about how work moves through your business. Your score and the one gap to fix first are emailed to you.
Not limited to what's listed. Every engagement starts by assessing what your business actually needs, and we build whatever it requires.