WH

Finance and operations, across the portfolio.

I work in hospitality finance and operations with a background across revenue management, hotel operations, labor analytics, and portfolio-level reporting. My day-to-day involves working across a range of properties — from select-service to full-service — helping ownership groups and operators make sense of their numbers.

This site is where I write about what actually helps hotels run better. Not textbook theory. Not vendor talking points. The practical, unglamorous work of reading a P&L at 10pm before a Monday call, figuring out why labor is off by $40K, or building a bridge that tells a clean story to an ownership group without hiding the bad news.

Everything here comes from real portfolio work. Examples are anonymized. The thinking is my own.


  • GOP and House Profit — how to read it, how to present it, what it's actually telling you
  • Labor productivity — CPOR, MPOR, PTEB, and what the ratios miss
  • ProfitSword, Unifocus, and the systems hotel teams actually live inside
  • Acquisitions and transitions — the financial risk in the first 90 days
  • Reporting discipline — how to build reports people actually use
  • AI and automation tools in a finance workflow
  • Leadership at the intersection of finance and operations

A résumé. A consulting pitch. A place to name specific properties or share confidential financials. When I write "in a multi-property portfolio..." that's intentional — the lesson is the point, not the property.

Read the writing Get in touch

Finance exists to help operations decide, not to report after the fact.

The report is never the problem.

If a report isn't being used, it's usually because it arrived too late, answered the wrong question, or nobody trusted the numbers. Fix the process before you fix the format.

Labor is local.

Portfolio-level labor benchmarks tell you almost nothing useful at the property level. What matters is what that specific hotel, with that specific mix, should cost to run this week.

Flow-through is a story, not a score.

A 200% flow-through number means something went wrong. The question is whether operations caused it or absorbed it — and those require very different responses.

Ownership groups deserve plain language.

A bridge that buries bad news under jargon doesn't protect the relationship — it erodes it. Tell the story clearly, with context, and then focus on what's being done about it.

The month-end isn't the close.

By the time you're reviewing finals, you've already lost the chance to fix most of what you're discussing. The useful work happens in the last week of the live month.

Systems don't fix process problems.

Every hotel technology implementation that goes sideways goes sideways for the same reason: the team expected the software to create discipline that didn't exist before. It doesn't work that way.

Get the occasional note

No weekly pressure. When something useful is ready, it goes out. That's it.