Connect It, Keep Everything: What Turning On STR Squad Looks Like for a PMC

Here is the whole sequence, in the order it happens, for a company running somewhere between eleven and a hundred doors: what you keep, what day one looks like, how it widens at your pace, and everything that stays portable.

If you have read The Fragmented-Stack Tax, you already know what the seams between six systems are worth in staff hours. This is the sequel property managers ask for next: what it actually takes to close them.

What you keep on day one

Start with the part that surprises people, because it is the part that makes everything else easy. On day one, you keep all of it.

That list is the reason this is a short post. Almost everything a new system usually asks of you comes from moving your record of truth from one place to another. STR Squad is built to sit on top of your PMS, so the record stays exactly where it is, and everything pointed at it keeps pointing at the same place.

The full version of that idea is the pinned post, Why Your PMS & Tech Stack Vendors Matter More With STR Squad — Not Less. The short version: the more of your stack you keep, the more a layer is worth, because what it is worth is the connections between the pieces.

Why it stays this light

One design choice does most of the work here, and it is worth seeing plainly: every system in your operation keeps ownership of what it owns.

Your PMS owns the reservation and the ledger. Your pricing tool owns the rate recommendation. Your channel manager owns distribution. Housekeeping owns the turnover board. A layer adds a tier above all of them and leaves each of those ownerships completely intact — it reads what every system knows, acts across them, and writes each result home to the system that owns it, in your account, under your name.

Ownership staying put is what keeps the whole thing light. The work that usually fills an implementation calendar is the work of moving ownership around, and here that calendar simply stays free for the part you actually wanted: turning on the first workflow.

Day one, step by step

Here is the actual sequence. It is shorter than people expect, which is rather the point.

1. You connect the systems you already own. Connection uses credentials for your own accounts, so the layer works inside your stack as your agent. Every action it takes lands in your account, under your name, the same way it would if a coordinator had done it.
2. The layer maps your portfolio. Properties, units, channels, owners, which system is authoritative for what, and where a person is currently the bridge between two systems. On Operator and above, that mapping is a white-glove engagement we run with you.
3. You choose the control mode. Every account starts in Approve-first: the layer does the work and brings it to a person to approve, with its reasoning shown and every action written to an audit log. Auto-pilot is there per workflow, ready for whenever you decide a given workflow has earned it.
4. You turn on one workflow. Pick the seam you would name first if someone asked which handoff eats the most time, and let the layer own that one. Everything else keeps running exactly as it does today.
5. You add systems at your pace. Connected systems are counted per account rather than per property, so widening what the layer can see stays a decision about value rather than a function of your door count.

Through all five steps, every system you run today keeps running today. Your PMS is the book of record in the morning and the book of record in the evening. Your pricing tool keeps pricing, your channel manager keeps distributing, and the turnover board is still the turnover board.

Under the hood, what you are connecting to is 42 specialist AI agents on 12 teams — guest experience, revenue, field ops, finance, reviews, risk — cross-functional by design, so a maintenance signal that changes revenue reaches both. What you experience on day one is deliberately narrower: one workflow, approve-first, inside systems you already run. The full ladder from a single door to a multi-brand group is in One Door or Ten Thousand.

The two front doors

How you start depends on size, and both paths are published on the plans page.

Through ten units, it is self-serve. Solo, Portfolio, and Host Pro each start with a 14-day free trial, with no credit card required up front. Connect, look around, decide.

Eleven units and up, it starts with a guided demo. Operator, Agency, and Fleet are demo-led by design — at that size there is a real portfolio and a real set of channels to map, and that mapping is the most useful half hour of the whole process. It is followed by a one-time white-glove setup engagement, priced per level on the plans page and waived on annual prepay.

Past a hundred units, and for multi-brand groups, your level is quoted around your operation. That tier is the Enterprise Operational Layer: one command center with consolidated CFO, COO, and Strategist views while every brand keeps its own stack and identity — the same design as the rest of this post, applied to a group where “your PMS” is four different PMSs.

Across every level the structure holds: one flat monthly price per account, never per unit. Add a door inside your band and the invoice holds steady. Cross a band and you step to the next published number, with your term price intact until it renews.

Your team keeps its speed, and gains time

Your coordinators keep every screen they are fast in, because those tools are still the tools. What they gain is the connective work: the layer watches the connected systems, routes what it sees to the team that handles it, runs the play, and closes the loop — then brings the calls that need judgment to a person.

Which makes for a pleasant payback curve. It starts on the single workflow you pointed the layer at, on day one, and grows every time you widen. You are compounding from the first week rather than waiting on a go-live date.

And the hours the layer takes on go back where they earn the management fee: to owners and to guests.

Everything stays portable

One more thing worth knowing before you start, because it is true from the first day: everything is exportable and everything is swappable.

Your data comes out any day you want it — CSV, JSON, and an open integration API, spelled out in the openness table — at no charge, whenever you ask. And every integration underneath the layer is swappable: change your pricing tool, change your channel manager, change your PMS, and the layer connects to the new one.

That includes us, by design. We would rather earn the month — it is the arrangement we would want if we were the ones buying.

If you change your PMS later, the layer comes with you

Plenty of management companies are mid-thought about their PMS when they read something like this. Good news on that front: the two decisions are independent, and they are much easier apart than together.

Connect now and your PMS choice stays wide open. Move to a different system next year and the layer connects to the new one, while the workflows you have built on top keep running — your operating habits live in the layer, so they travel with you rather than staying behind.

And when you do move, the playbook is one we have already written: How to Switch Property Management Software Without Losing Reviews, Calendars, or Bookings. It is written to be useful whether or not we are anywhere in the picture.

Frequently asked questions