For City & Members Clubs

The Relationships
Are the Entire Product.
They Shouldn't Run on Memory.

An operating system for the member experience. So the club runs on systems, not on whoever is working that day.

▾

Member Experience

Every member expects to be known.
Your team turns over every 18 months.

A long-standing member walks in with a guest. The new front-desk associate has no idea who they are or their usual table preference.
A member's spouse has a dietary restriction that the dining room knew about last year. New chef, new staff, knowledge gone.
A board member mentioned at the last social that the wine list needs updating. Did anyone capture that? Where?
The members who feel known stay. The ones who have to re-introduce themselves leave.

Richardson -- preferred table, dietary notes current

Known

New member (Mar) -- no preferences captured yet

Blank

Guest policy complaint -- unresolved 3 weeks

Open

4 members haven't visited in 60+ days

At risk

What changes

Every member's preferences, history, and open requests in one system
New staff inherit institutional knowledge from day one
The personal touch survives turnover

Events

Wine dinners, speaker series, holiday parties,
private bookings -- all at once

The Friday speaker series, the Saturday private party, and the Sunday brunch service all need the main dining room. Who owns the schedule?
A member booked the private room for 30. Catering confirmed. But did the bar manager get the drink pre-order?
Last year's holiday party had 140 RSVPs and 190 showed up. Nobody wrote down what went wrong with the seating.
Event setup, teardown, and staffing coordination happens in a group text that disappears

What changes

Every event, private booking, and recurring series in one calendar with full logistics
Cross-department coordination happens in the system, not in group texts
Post-event notes carry forward so last year's mistakes don't repeat

Discretion

Members expect privacy.
Your tools weren't built for that.

A member's billing dispute. A guest incident. A board conversation about a member's conduct. These need to stay inside the club.
The club management platform stores member data on servers you don't control and can't audit
A member who's a public figure. A member going through a divorce. The staff knows, and discretion matters, but the systems don't enforce it.
When a member asks "who has access to my information?" you should have a better answer than "our software vendor"

What changes

Member data runs on infrastructure you control. No third-party access.
Sensitive matters tracked with explicit access controls
Discretion becomes a system property, not just a cultural expectation

Team

Front desk, dining, bar, events, and maintenance
all run their own show

The dining room is set for 60. Events just confirmed a private party for 25 in the same space. Nobody told the maitre d'.
Maintenance scheduled HVAC work during the board meeting. The GM found out when the noise started.
A member complained about service to the front desk. The dining manager never heard about it.
You're the only person who sees across all departments. When you're off, things fall through.

What changes

Cross-department visibility without another meeting or group text
Scheduling conflicts surface before the day-of scramble
The coordination lives in the system, not in the GM's head

📊

Membership Pulse

Visit frequency, dining spend, event attendance by member
Resignation risk signals before the letter arrives
The data you wish you had before the exit interview

🍽

F&B Intelligence

Revenue by event type, day of week, season
Member dining preferences and frequency
The numbers the board always asks about, always ready

📝

Board & Committee Prep

Board packet drafts from data already being tracked
Committee action items tracked to completion
"What did we decide in January?" answered instantly

👤

New Member Onboarding

Welcome sequence, intro events, mentor matching
First 90 days of engagement tracked
No new member falls through the cracks

🔒

Private infrastructure

Sensitive data runs on hardware you control. Member information, billing, and board materials never touch a third party's servers.

📱

No new software to learn

Text it, email it, Slack it. The system works through the tools your staff already uses. No app rollout. No training sessions.

🛡

Board-ready security

When a board member asks who has access to member data, the answer is clear. Your data. Your hardware. Your control.

1

You pick one problem

Whichever would change your week the most. You know your club.

2

We build it on your real workflow

Not a demo with fake data. 30 days on your actual operation. No long-term contract.

3

If it works, we add the next one

Each capability is modular. Same system. The pace is yours.

Picture Lock Studios

We build AI-powered operational systems for select clients. We started by building one for ourselves, running a creative agency with 50+ AI agents handling the work that used to eat our week.

Why city clubs

City and members clubs sell an experience built on relationships and discretion. The tech needs to modernize, but the tools can't compromise the atmosphere. We build systems that stay invisible to the member while making the operation run.

The Relationships
Are the Entire Product.
They Shouldn't Run on Memory.

Four Things That Eat Your Week

Every member expects to be known.
Your team turns over every 18 months.

Wine dinners, speaker series, holiday parties,
private bookings -- all at once

Members expect privacy.
Your tools weren't built for that.

Front desk, dining, bar, events, and maintenance
all run their own show

Also Built Into the System

Membership Pulse

F&B Intelligence

Board & Committee Prep

New Member Onboarding

Member Data Stays at the Club

Private infrastructure

No new software to learn

Board-ready security

How It Works

You pick one problem

We build it on your real workflow

If it works, we add the next one

Picture Lock Studios

Why city clubs

The RelationshipsAre the Entire Product.They Shouldn't Run on Memory.

Four Things That Eat Your Week

Every member expects to be known.Your team turns over every 18 months.

Wine dinners, speaker series, holiday parties,private bookings -- all at once

Members expect privacy.Your tools weren't built for that.

Front desk, dining, bar, events, and maintenanceall run their own show

Also Built Into the System

Membership Pulse

F&B Intelligence

Board & Committee Prep

New Member Onboarding

Member Data Stays at the Club

Private infrastructure

No new software to learn

Board-ready security

How It Works

You pick one problem

We build it on your real workflow

If it works, we add the next one

Picture Lock Studios

Why city clubs

The Relationships
Are the Entire Product.
They Shouldn't Run on Memory.

Every member expects to be known.
Your team turns over every 18 months.

Wine dinners, speaker series, holiday parties,
private bookings -- all at once

Members expect privacy.
Your tools weren't built for that.

Front desk, dining, bar, events, and maintenance
all run their own show