Dead on arrival for a straight wholesale.

I personally believe the PM lied about what he told the plumber about not doing the work - since the plumber arrived AFTER the "stop work" texting conversation took place.

I said "disruption" not crash. 

They arrived after the leasing office closed, and couldn't get a permit.

We still send cleaner over to the house, she arrives, no smell, no food & house is spotless.We ended up submitting the cancellation through Airbnb so we didn't get penalized & didn't issue a refund.

I talked with my attorney who really hasn't done any short sales since the crash.

We tested Monday and ended up building our ops around ClickUp as the system of record, with our PMS and automations feeding it.How we run STR ops (high level)PMS drives the truth (reservations, changes, cancellations).Automation pushes events into ClickUp so humans work from tasks, not inboxes.For example: Guesty → webhook → database layer → create/update ClickUp tasks for inquiries + reservations, with custom fields like check-in/out, guest, listing, status, conversation links, etcWe also automate “edge-case ops” like pool heat, early check-in, late checkout, pets, extra guests by generating subtasks/checklists off a request.Where Monday tends to feel greatFast to set up boards, very visual.Good for simple pipelines: turns, maintenance queues, onboarding checklists.Dashboards and “who owns what” is easy for teams that hate complexity.The biggest hurdles / limitations people hit with Monday in STR (in my experience)When the PMS needs to be the source of truthSTR is event-driven: reservation updates, cancellations, date changes, channel messages.If Monday is the “truth”, you end up reconciling drift constantly.Automation ceilingMonday automations are solid for basic triggers, but once you want “if X then create Y tasks, keep them in sync, dedupe, move between pipelines, update 15 fields, attach links”, you start wanting a real workflow engine + database.Data model constraintsSTR ops has “objects”: Reservation, Property, Guest, Work Order, Vendor, Owner, Conversation.Monday is board/item-first, so relationships can get awkward at scale unless you build a lot of glue.High-volume operational noiseHundreds of small updates (date changes, guest count changes, messaging, payments, add-ons) can turn boards into a scroll-fest unless you are very strict about what becomes an item vs a log.If someone is committed to Monday, this is the way I would set it upBoards by function, not by property:Reservations pipeline (pre-arrival, in-house, checkout, post-stay)Turns and housekeepingMaintenance and inspectionsOwner requests and approvalsOne unique ID field per reservation and treat it like a primary key.Use an integration layer (Zapier, Make, n8n, custom) so the PMS updates Monday automatically, not manually.Bottom lineMonday is awesome if your ops are mostly human-driven and you want speed + visibility.

I was working at a bank right before the last crash when I started.

Hiring is slow, not frozen.This environment typically supports gradual rate adjustments rather than aggressive moves.What This Means for Mortgage RatesInflation is cooling.Labor data is softening beneath the surface.The Fed remains cautious.Housing affordability is improving.That’s not a crash setup.It’s a stabilization setup.And stabilization is often what allows spring markets to gain traction.What to Watch This WeekFed meeting minutes (Wednesday)Q4 GDP (Friday)December PCE inflation (Friday)Builder confidence + new home sales + pending salesMarkets will be watching closely for confirmation that inflation continues easing.Technical SnapshotMortgage Bonds are testing resistance near 100.38.

I arrived today.