The gap between hotel PMSs and golf tee-sheets, in data

Methodology

We worked with 14 golf-resort hotels on the Costa del Sol, Costa Brava, and Mallorca, plus 22 associated courses. A 6-week audit (February-March 2026) over 1,847 combined hotel + golf bookings. Metrics observed: time between the hotel booking and the last tee-time confirmation, number of emails involved, errors detected.

Findings

Average time to confirm tee times after check-in: 9.2 hours (median 4h, p90 28h).

Emails per combined booking: 5.4 on average. 73% of bookings require at least 4 emails between hotel, guest, and course.

Error rate: 6.1% of bookings had at least one tee time misassigned, sent to the wrong course, or registered with a wrong name. The error is caught at the course on the day of play, causing either a lost tee time (1.8% of total) or an emergency reassignment.

Silent cancellations: 2.4% of combined bookings cancel the tee time without notifying the hotel, leaving the room paid and the course slot lost.

Operator time: the average concierge spends 23 minutes per combined booking coordinating emails, calls, changes, and reconfirmations.

The annual cost

For a 200-room golf-resort hotel with 35% golfer guests, assuming 60% annual occupancy:

• ~15,300 combined bookings/year
• ~5,860 operator hours/year dedicated to coordination
• ~37 bookings lost/year due to errors
• Estimated direct loss: €50,000 - €90,000 in unbilled greenfees, before operator cost

And that's one hotel.

Why no one has fixed it before

Three reasons:

1. Fragmented market: every PMS talks to every tee-sheet differently. Building 8 × 8 ad-hoc integrations is unviable as a business model. 2. Invisible category: golf-resort is a small vertical inside hospitality (estimated 6-8% of European hotels). Major vendors don't prioritise it. 3. Regional stack: TeeOne in Spain, Golfmanager in some European resorts, Club Prophet in US/UK. No global leader justifies cross-vendor investment.

GolfStay exists because the first principle (fragmented market) stops being a problem when you work with agnostic adapters: one TeeOne integration serves every hotel using TeeOne. One Mews adapter serves every Mews. The economics only work from the infrastructure layer, not the customer end.