Your first week as an operator

Open the operator dashboard. Make sure the numbers match what your predecessor (or the spreadsheet you inherited) says. Specifically: occupancy, MRR, and the count of in-flight invoices. If any of these don't line up, stop here and talk to support — every later decision in this week depends on these three numbers.

The three numbers that matter on day one

1. Active members— the dashboard's “Members” count should match your CRM. If it doesn't, that's a data wire issue and is worth a 30-min support call before you do anything else.
2. This-month occupancy — for the day-by-day grid in the calendar. You want to know what a normal Tuesday looks like before Tuesday hits.
3. Open invoices— both pending-payment and overdue. Anything >30 days overdue gets flagged for Friday's call list.

I started with the numbers and I was wrong about three of them. Better to find that out on Monday than at the Friday review.

Walk in through the front door at 09:00. Hold a coffee. Look at what a member sees when they badge in. The lighting at the entry, the temperature in the meeting rooms, the sound bleed from the standing bench. Make a list. Don't fix anything yet — the list is the artefact.

Five things I look for

• Wi-Fi at the worst desk.The desk in the back corner that no-one chooses. If Wi-Fi is bad there, the AP coverage isn't enough — and you won't hear about it from the corner-desk member, you'll hear about it from the visitor.
• The kitchen at 10:30. Not 08:00 (empty) or 12:30 (chaotic). 10:30 is when the morning coffee rush is done and you can see if the dishwasher is still running, if the milk is half-empty, if the bins are full.
• The boardroom temperature at 14:00. Sun-side rooms get hot. Members notice this even if no-one complains.
• The visitor sign-in flow. Walk in as a visitor would. Time it. If it takes more than 90 seconds, the kiosk needs to be friendlier or the host notification needs to be faster.
• The way out. Members remember how they leave more than how they arrive. A messy exit is a bad memory.

Pick your top 10 members by hours-booked-this-quarter. Send them a calendar invite for a 20-minute chat. Subject: “Buying you a coffee — picking your brain.” Do not send the agenda. The point is to listen, not to validate a thesis.

Three questions I always ask

• “What was the last thing here that annoyed you?” Specific. Not “what could be better.” Past tense, concrete event.
• “If we changed one thing, what would you tell your friend at another space?”Surfaces the comparison point you didn't know was the comparison point.
• “Who else here should I talk to?”Network discovery. You'll find the quiet influencers this way.

She asked what annoyed me last week. I said it was the standing desk that wobbled. It was fixed by Thursday. That was the moment I knew this operator was different.

Pull the rate card. Read it as a member would. Is the pricing legible? Does the member tier actually pay off vs guest? Is there a tier no-one buys (and if so, can you delete it)? Pricing changes are slow to make and easy to mis-time, so this week is about diagnosis, not changes.

Three diagnostics I run

1. Member-vs-guest gap.If a guest day-pass is >1.5x what a member pays per day, members feel rewarded. If <1.2x, members feel they're subsidising guests. Anywhere in between is fine.
2. Tier population.Pull the count of active members per tier. If a tier has <3% of your population and you're not selling new ones, it's a candidate for retirement.
3. Bundle leakage.Look at members who consistently use 1 hour over their bundle every week. That's a tier upgrade conversation, not a billing dispute.

-- Members consistently using > 1 hr above bundle, last 8 weeks
SELECT m.id, m.name, m.tier, sum(b.hours_used) - 8 * t.bundle_hours AS overage
FROM members m
JOIN bookings b ON b.member_id = m.id
JOIN tiers t ON t.id = m.tier_id
WHERE b.created_at > now() - interval '8 weeks'
GROUP BY m.id, m.name, m.tier, t.bundle_hours
HAVING sum(b.hours_used) > 8 * (t.bundle_hours + 1)
ORDER BY overage DESC;

Friday at 15:00. Pull the team into the boardroom (or onto a call). Show four metrics, tell two stories. That's it. The week ends with shared facts and a shared narrative.

The four metrics

• Occupancy this week vs last week. The trend matters more than the number.
• MRR delta this week. New signups minus churn — what changed?
• NPS / member sentiment from the 10 one-on-ones. Anecdotal but load-bearing.
• Open issues from Tuesday's floor walk.What got fixed, what didn't, what's next.

The two stories

One internal — “here's the thing we learned this week, and what we're going to do about it.” One external — a member story, named with permission. The stories are what people remember after the meeting; the metrics are what they check on Monday.

The temptation to keep checking is real. Don't. Operators who burn out in month three are the ones who don't take a weekend in week one. The data will be there Monday — and the AI assistant catches anything truly urgent (refund-cliff, payment failures, capacity at 100% on a weekend booking). Trust the safety net.

On Sunday evening, write yourself a short note for Monday: the three things from Friday you're carrying in, and the one thing you're explicitly not going to work on this week. Both lists matter.