HomeCase StudiesHow Grey Hornbill Solves Post-Hours Booking Gaps for Golf Courses

How Grey Hornbill Solves Post-Hours Booking Gaps for Golf Courses

With an MBA in International Business, I bring marketing and IT operations expertise into building innovative products. I founded Plus Bytes, where I built Grey Hornbill — a golf course booking platform combining a web widget & an AI voice agent.
Puneet B
By Puneet B · Marketing and IT operations professional building innovative products for real-world industries · Pune, India
Published August 13, 2026 · 5 min read
This case study is based on responses submitted directly by the founder or member of the team from Grey Hornbill. They have verified ownership of their domain greyhornbill.com on SaaS Browser.
Grey Hornbill homepage

How Grey Hornbill got started

Golf courses lose 30 to 40% of booking calls to voicemail or missed calls after hours, and that's real revenue walking away simply because no one was there to pick up the phone. Online booking widgets solve part of the problem, but phone is still how most golfers actually book, especially at smaller, independently run courses where staff are juggling the pro shop, the course, and the front desk all at once. The moment that crystallized it was realizing this isn't a staffing problem you can just throw more people at. A golfer calls after hours, gets nothing, and just books somewhere else, and the course never even finds out they lost that booking. That gap, invisible on paper but very real in lost revenue, is what Grey Hornbill was built to close, an AI voice agent that answers every call, checks live availability, and books the tee time on the spot, so the phone stops being the weak link in the booking chain.

Growing Grey Hornbill: what worked and what didn't

Worked, dogfooding. Running Grey Hornbill Golf Club on our own system made every pitch concrete, since showing "here's a live screenshot of our own tee sheet" is far more convincing than any feature list or slide deck could ever be. Prospects trust proof over promises, and having a real course actually running on the platform, with real bookings landing in a real calendar, closed conversations that a demo video never could. Flopped, initially considering the free trial as a stripped-down teaser version instead of the full product. The instinct was to hold something back until a course committed to paying, but that undercuts the entire pitch. Free for 12 months only converts belief when it's genuinely the real thing, not a limited demo people quietly forget about after a week. Once we locked in that the Basic tier would be the complete, un-crippled widget, the offer actually started landing the way it was meant to.

What Grey Hornbill customers really think

The most common friction is confusion between what the AI voice agent, George, actually does versus the self-serve web widget. People initially assume "AI-powered" applies to the whole product, when really it's George specifically who handles the live phone conversation, checks availability, and books the tee time on the spot. The widget, by contrast, is straightforward self-serve booking with no AI layer to it at all, and conflating the two ends up setting the wrong expectations before a call even happens. We fixed this by being deliberate and explicit in our messaging, George handles live phone calls, the widget handles self-serve web booking, and we never blur the two together just because "AI" sounds good attached to everything. Being precise about what's actually AI, rather than letting the term stretch across the whole product to sound more impressive, avoided overclaiming and, more importantly, rebuilt trust with prospects who've grown skeptical of vague AI marketing claims in general.

“The biggest difference is that my staff can actually focus on the golfers in front of them.”

— A Grey Hornbill customer

What most people get wrong about Golf Course Management

People assume the competition is full club-management platforms like foreUP, Lightspeed, and GGGolf, systems built around F&B point of sale, inventory tracking, and member CRM. That's a fundamentally different, much heavier product category, representing years of accounting and inventory integration work that most golf courses never actually asked for in the first place, and building toward that scope would mean solving problems nobody on the actual call is complaining about. Grey Hornbill doesn't compete in that space at all. Instead, it solves one specific, undefended problem, missed phone calls after hours, when a golfer wants to book and simply can't get through. None of those larger platforms actually address that gap because it isn't really their problem to solve. The bigger misconception is that adopting Grey Hornbill means ripping out an existing system. It doesn't. Courses keep whatever they already have and layer this on top, specifically to close the one hole those systems leave open.

What's next for Grey Hornbill

Golfer profiles with booking history so returning callers get recognized, plus SMS and WhatsApp booking confirmations, are next up. A public pricing page is also coming now that tiers are locked in, a free Basic widget, a paid Advanced tier, and custom pricing for George based on call volume. Longer-term, the plan is to expand into Food and Beverage pricing and pro shop shopping, moving Grey Hornbill toward becoming a genuinely comprehensive golf course management platform, not just a booking tool, while still keeping the same phone-and-web booking core that made it useful from day one.

Grey Hornbill traction so far

50+ paying customers, and growing. Twenty thousand bookings so far.

Puneet's background

A background in marketing and IT operations and service management, plus prior experience building AI agents for healthcare appointment booking, not the golf industry specifically. That earlier work gave me a real head start on the core problem, AI-driven scheduling and the messy edge cases around availability and cancellations, while bringing product and operations discipline into how Grey Hornbill got built. The engine was designed as a single source of truth from day one, rather than letting booking logic fork separately across the web widget, the phone agent, and staff-facing tools, which is a mistake that's much harder to unwind once it's already in production.

Biggest lesson building Grey Hornbill

Early on, Google Calendar was treated as a source of truth for availability rather than what it should have been, a display layer. That created real sync fragility across the widget, the phone agent, and staff-facing tools, with edge cases showing up whenever two booking paths tried to read or write availability at slightly different moments. The fix was demoting Calendar to a one-way mirror and making a single engine module the actual source of truth for every booking path instead. It worked, but it ended up being a bigger rebuild than it should have needed to be if the architecture had been right from day one.
Build the single source-of-truth booking engine first, before any calendar integration, it would have avoided a full-stack pattern of sync-fragility bugs that took a dedicated cleanup pass to unwind later.

Grey Hornbill at a glance

MRR
$50-100k
Founded
2026
Target market (B2B/B2C)
Business
Growth model (Product/Sales)
Both
Uses AI
Yes