I've learned the hard way that having a hard cap on change orders isn't just smart, it's survival.

The structure of the refinance can sometimes change how that plays out.

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.

Im in the process of changing the properties from my name to llc. 

I guess it just sucks to know you are in arms reach of what could change your life but you can't get it right now because you are waiting on someone else. 

That classification can actually change the depreciation timeline quite a bit. 

A lot of what you’ve learned absolutely translates, but the “game board” changes a bit with apartments.​At a high level, you’ll want to get comfortable with three big shifts:Lenders and buyers will underwrite more heavily on NOI, cap rate, and DSCR than on simple “can I rent this for X?”

That changes what timeline is actually achievable right now.

Have you changed your LTV caps or structures compared to last year?

Guys don't talk about return on capital deployed, just gross profit dollars.What's your holding cost estimate running per month in Middle TN, and does that change your math if a project stretches 30 days?