Case Study · Shipped Product

TurfMate — booking manager for a sports turf

A 0→1 product, taken from problem discovery to a live app a real client uses daily.

Role: Product (discovery → scoping → build → ship)Type: 0→1 web appStack: PWA + Supabase on Vercel

Problem

A Pune turf owner ran every booking over WhatsApp from memory. The result: double bookings, and staff or the watchman couldn't see the schedule without calling him. Roughly 7–8 bookings a week, often last-minute and overnight.

Users

V1 is for the people who run the turf (owner + staff), not customers — because the pain was tracking, not booking.

What I shipped (V1)

  • Shared live day-view — owner and staff see the same schedule in real time
  • Add a booking in under 15 seconds, with clashes blocked before saving
  • 24-hour support including overnight slots
  • Auto pricing from the rate card, with manual discount override
  • Calendar month view for planning ahead
  • Repeat bookings for regulars
  • Advance-vs-pending payment tracking
  • Earnings reports
  • One-tap WhatsApp confirmations to customers
  • No-login access — pick your name, and every booking shows who added it
  • Installable to the home screen (PWA)

Key product decisions

Web app, not native

A shareable link went live in days and cost nothing — no app-store friction for a small turf team.

No login in V1

If it's slower than WhatsApp, staff won't use it. Pick-your-name keeps accountability without the friction.

Staff-side first, customers later

The real bottleneck was tracking bookings, not taking them — so V1 solves the owner's problem first.

Outcome

A live shared source of truth that removes double bookings and the "call the owner" dependency. Currently in a real pilot at the turf.

Try the live demo

Sample data — the owner's real instance is kept private.