New York Yacht Club
Member operations, food and beverage, and overnight room analytics for a private club.
Hospitality and private clubs
Club operations run on systems that were never designed to agree with each other: point of sale, room bookings, membership, and billing each hold part of a member's activity, and the member-facing view has to reconcile all of them. A member who dined on Tuesday and stayed on Wednesday is two unrelated rows until something joins them.
From operational complexity to shared context.
Point-of-sale, room, and membership data resolved to one member record
Restaurant covers and overnight occupancy read from the same governed tables as the finance close
Member-360 views scoped by row-level policy, so staff see what their role allows and no more
Daily operations reporting run by the people who run the club, not by a data team
The capabilities behind the workflow
One governed store behind operations and finance
Row-level policy on member data
Pipelines supervised by people who are not full-time data engineers