Forward-Deployed · Production Systems · 2024 to 2026
Operations platform for a short-term-rental portfolio
Ran product and engineering, with one other developer, for the platform a 147-property rental operator ran its business on.
Representative UI, abstract, with no client data.
How it works
Guesty · PriceLabs · QuickBooks · Plaid · Stripe · Wise · Monday · others
15-min pipeline, header-adaptive back-off, file locking
materialized views compute metrics server-side
live ops UI plus message-to-task classification
payout matching, anomaly + failure alerts
Architecture
By the numbers
Where the reconciliation engine paid off
Context
A growing short-term-rental portfolio was running on manual spreadsheets and disconnected tools. Revenue leaked through unreconciled payouts, and the team had no single source of truth across listings, reservations, pricing, and cleaning.
What I did
- Built an operations dashboard unifying listings, reservations, calendars and pricing across twelve integrated systems.
- Designed a reconciliation engine that cross-checks payouts against reservations to flag missing and mismatched money.
- Engineered a token-budgeted sync engine (header-adaptive back-off, DB-cached OAuth, file locking) to stay under strict provider rate limits.
- Added an LLM layer that classifies guest messages/reviews into an operational task queue, plus monitoring and alerting so failures surface before they hit operations.
Outcome
- Recovered about $94K in revenue that manual review had missed.
- Replaced spreadsheet operations with a live dashboard the team runs daily.
- Reconciliation and sync run continuously instead of as occasional manual audits.
Under the hood
The sync engine
- Runs every 15 minutes across two Guesty accounts and multiple providers, but must live inside a hard rate-limit budget (one provider caps OAuth at ~5 tokens/day).
- DB-cached OAuth, header-adaptive back-off, and file-based locking prevent overlapping runs and token exhaustion; a four-layer reliability design self-heals from partial failures.
The reconciliation engine
- Cross-checks bookings, payouts and bank/Stripe/QuickBooks transactions across two currencies to find money that manual review missed.
- Recovered ~$94K of missed and mismatched revenue and eliminated a large double-count that had distorted the P&L.
The LLM operations layer
- Every guest, owner and staff message and review runs through an LLM pipeline that routes it into the right maintenance or service task.
- Turnover and inspection automation across the portfolio feeds a downstream payroll pipeline and saves the ops team ~15 hours a week.
Finding the failures that never raise an error
- Monday.com's items(ids:) field paginates with an undocumented default page size of 25. Code asking for 100 ids received the first 25, with no error and no truncation flag, and six call sites had been reading a fraction of the portfolio for an unknown period.
- It was found by measuring requested-versus-returned counts rather than by reading the code, and only after a first fix that was correct in itself failed to move the symptom. That negative result is what located the real cause.
- The same pass caught a cancellation path reporting success without verifying its own writes, and a sync reporting zero changes while reading under a third of its population. All three now fail loudly rather than silently.