OnPlane

Why I built it

Caddie programs run on paper, group texts and whatever the caddie master remembers. Rosters, onboarding paperwork, training, today's loop assignments, course knowledge. New caddies learn the course by walking it, and nothing that happens out there gets written down. We started OnPlane to fix that.

What it does

• Admin dashboard: roster and applications (with guardian consent for minors), documents, versioned video training, today's loop assignments, announcements, events and scholarships.
• Caddie PWA with an offline-capable AI twin of the caddie master, grounded in the club's course, training and the Rules of Golf.
• Live hole-by-hole round tracking that saves to the phone first and syncs when there's signal.
• Golfer app: snap a scorecard and Claude reads it; track your bag and distances; get a personal game plan and an AI coach.
• No-login guest course guides with hole maps and flyovers, a printable yardage book, and QR tee signs.
• Club insights for pros and committee, shown only once enough golfers contribute that no one can be singled out.

How it works

One Next.js app holds the landing page, the admin, caddie and golfer apps, the public pages and the API. Clerk Organizations make each club its own tenant, and every query is scoped to the club.

Courses import from OpenStreetMap with USGS aerial imagery under each hole.

Every Claude call is metered per club per day, with spend caps for the club and the platform, and rate limits on public and AI endpoints.

Calls I made