K Golf
Web Development + Booking System
Description
K Golf is an eleven-bay indoor-golf venue in Wairau Valley, Auckland. We built them a booking system a customer can drive from their phone in half a minute — pick a session, day and time, choose pay-at-venue or a deposit, and it's done — with the pricing, bay assignment and reminders all handled underneath.
Numbers
Session, day, time, details, done — the whole customer flow fits on one screen, phone-native, no account.
The real venue’s bays, with left-handed stations kept separate and assigned automatically at booking time.
Every slot checks live bay capacity before it’s offered — a full venue simply can’t be booked twice.
Automatic nudges at 24 hours, 3 hours and 30 minutes before — the fix for no-shows, with zero staff effort.
The problem
An indoor-golf venue lives and dies by its bays being full — but bookings by phone and message mean double-bookings, no-shows, and staff pulled off the floor to manage a calendar. Peak nights and quiet mornings need different prices. Left-handers need a specific bay.
A booking page isn't enough. It has to know the venue's rules, and enforce them, so nobody has to.
What we did
THE 30-SECOND FLOW
Practice or a game, how long, which day, what time, three details — done. Phone-native, no account, with the price shown live as the choices are made. Booking confirmed on screen.
NEVER OVERBOOKS
Each time slot checks real bay capacity for the whole session before it's offered, then assigns a free bay automatically — including routing left-handed players to the left-handed station. A full venue can't be booked twice.
PRICING THAT PAYS
Happy-hour rates fill the quiet mornings; peak slots take a deposit to hold the bay so a no-show doesn't cost the night. Off-peak, the customer can just reserve and pay at the venue.
A GRID TO RUN THE DAY
Behind the customer app, an admin grid of bays against time, plus customers, settings, reporting and an audit trail — so the owner runs the venue from one screen, and reminder texts chase the no-shows for them.
Figures describe how the system behaves, shown here in the demo build: pricing, capacity checks, bay assignment and the reminder schedule are real logic, run against seeded bookings. The clip is a real end-to-end run of the customer flow. Live rollout at the venue is on hold pending the owner's go — so there's no public booking link, by design.
More work
