What Growing a Hotel 73% in 3 Months Taught Me About Engineering

The line on my site says: ran a hotel, grew revenue 73% in 3 months. People assume it's a flex. It's actually the most useful engineering education I've had.

I took over operations, restructured the sales strategy, and the P&L moved 73% in a single quarter. Here's what actually transferred to building software.

1. Instrument before you optimize

The first thing wrong with the hotel wasn't strategy — it was that nobody could answer basic questions with numbers. Where do bookings come from? What does an empty room on a Tuesday actually cost?

Same disease as an unobserved backend. You cannot fix what you cannot see. In both worlds, step one is the same: get the metrics flowing before touching anything.

2. Revenue problems are usually pipeline problems

"We need more customers" is the hotel version of "we need more servers." Usually false. The demand was there — it was leaking at specific stages. Restructuring the sales strategy meant finding where interested people fell out and fixing those stages, in order of leak size.

That's throughput engineering. Find the bottleneck, fix the bottleneck, re-measure, repeat. Kafka pipeline or booking pipeline — the math doesn't care.

3. Ops is a real-time system with humans as components

A hotel is a distributed system with SLAs measured in guest patience. Staff schedules, housekeeping turnaround, check-in latency — all queues and capacity planning. And like any system, the failure mode isn't average load. It's the spike: the wedding weekend, the festival rush.

Design for the spike. Everything else is easy.

4. Selling is a technical skill

Engineers love pretending sales is someone else's job. Watching revenue respond within weeks to changes in how we positioned and priced the same physical rooms cured me of that. Nothing about the product changed — the interface to the customer did.

Every technical founder eventually learns this. I got to learn it at hotel speed instead of startup speed: feedback in days, not quarters.

The meta-lesson: running a real business with real cash flow builds an intuition no tutorial can — that every system, human or software, is a set of flows with bottlenecks, and your job is to find the one that matters right now. That intuition is why I'm comfortable being CTO of tunyt.com at 20.