Rutvik Ghughal

← Rutvik Ghughal  /  case studies

Case study 04

Turning tee-time chaos into a fair allocation system

Golf booking looks like a booking problem. It isn’t — it’s capacity-constrained social logistics. An 11-slide concept that replaces “fastest fingers” with a request window, weighted allocation and an admin rules engine.

Context
Product assignment · “Playo for Golf” (Assignment 1a)
Year
2026
Contribution
Solo
Frameworks
Friction funnel · user prioritization 2×2 · MVP scoping · North Star · phased roadmap

What this is: an independent product exercise — an outside-in concept for a hypothetical golf vertical, produced with AI-assisted visuals (NotebookLM). Not affiliated with, commissioned by, or endorsed by Playo. The dashboard numbers shown below are illustrative targets inside a mockup, not measured results — nothing here shipped.

The reframe

“Golf is not just ‘booking’; it is a capacity-constrained, social logistics challenge.”

Slide 2 — the context

Mapped as a funnel: intent to playcoordination chaos (phone calls, “are you free?”, WhatsApp groups) → booking execution (fastest fingers, bots) → a small percentage of successful rounds, with failed bookings and stress leaking out the side.

Who to build for — and who to ignore

Users plotted on strategic importance × operational complexity, with an explicit de-scope list.

Primary — the engine

Club Member / Captain

Solves the coordination problem. High strategic importance, low operational complexity — the flywheel starts here.

Primary — the gatekeeper

Tee-Time Admin

Enables the inventory. High importance, high complexity — but without the admin there is no supply.

Secondary

Public-course golfer · benefits golfer

Lower strategic importance; the benefits golfer only arrives with credit-card and entitlement integrations.

De-scoped for MVP

Coach / instructor · tournament committee

“Lesson marketplaces are a distraction from the core logistics engine.”

Pain, mapped to feature

WhoThe pain pointThe feature opportunity
Member / CaptainRelease-time rush. Seconds matter, creating “herding cats” anxiety over WhatsApp.Smart Request Window & Group Builder
Tee-Time AdminManual exceptions. Substitutions, waitlist calls, and “Min 3” enforcement done by hand.Automated Rules Engine & Dynamic Tee Sheet
Benefits GolferEntitlement opacity. Multi-step request → validate → confirm loops.Integrated eligibility checks

“The friction isn’t just the UI; it’s the lack of transparency in the queuing logic.”

Slide 4 — key insight

The strategy

Shift from “first-click wins” to a reliable, social and fair operating system — a Fairness Engine of configurable allocation logic sitting over three pillars, on an operational admin console.

Pillar 1

Reliability

Remove “exact second” stress. Enforce the rules upfront rather than policing after.

Pillar 2

Playo-ness (group fill)

Facilitate invites, fill empty spots, build the social graph.

Pillar 3

Tournament Lite

Scheduling and draw visibility — the thing that drives daily usage, not just weekend usage.

Fastest fingers (anxiety) → request window (calm) Manual policing → automated constraints Solo booking → flight formation

The mechanism

Request window opens (5–10 min, no FCFS) Pool requests Weighted logic: waitlist history (+), no-show penalty (−) Allocation Confirm, or waitlist with priority
Why this allocation model over the alternatives: it neutralizes bots and scripts, removes exact-second anxiety, and preserves cultural fairness — unlike a “pay-to-win” auction, which a members’ club will not tolerate.

What the two sides actually see

Golfer app

Smart intent & group builder

  • Smart Request — select time bands to raise success probability, not sniper shots at one slot.
  • Group Builder — pre-invite friends before the window even opens; “open to fill” toggle for the rest.
  • Waitlist 2.0 — transparent positioning shown as low / medium / high likelihood when capacity is full.

Admin console

Policy as software

  • Rules engine — configurable windows (7 days out), member-only times, minimum player counts.
  • Tee sheet creator — dynamic sessions, shotgun vs regular tee times, live violation flags.
  • Management — automated waitlist backfilling and auditable overrides.
  • Broadcasts — smart notifications for course closures or frost delays.

How success is defined

North Star: Successful Round Participation Rate — requested, confirmed and checked in.

“We are not optimizing for bookings made, but for successful rounds played.”

Illustrative only. These figures appear inside a mockup dashboard in the deck as target values. They are not measured outcomes — the product was never built.
MetricIllustrative target
Round participation rate84%
Time to confirm a full flight4.2 hrs
Waitlist conversion (cancellations backfilled)35%
Weekly active members620

Three phases

Phase 1 — MVP pilot

Ops & core

Target: 1–2 private clubs. Smart booking request, group builder, admin console (rules engine), Tournament Lite.

Phase 2 — fairness

Allocation & flow

Target: full club rollout. Full request-window logic, starter check-in workflow, advanced substitution flows.

Phase 3 — expansion

Scale & commercial

Target: public courses. Public marketplace, credit-card integrations, coach booking module.

The closing frame: an operating layer for golf that balances golfer experience with admin control — golfers get reliability, social connection and fairness; admins get automation, control and less manual overhead.
← All case studiesNext: From mass to class: can a value brand stretch to premium? →