After the Acquisition: An STR Squad for Every PMC, One Command Center for the Parent

This is the multi-PMC chapter of a story the rest of this blog tells one level at a time. One Door or Ten Thousand — how STR Squad scales at every level covers what changes as an operation grows and what holds the whole way up. Past a certain size the live question stops being how many doors you run and becomes how many PMCs run them.

Every PMC you acquire arrives with its own tech stack

Open the folder on any acquisition and the same seven assets are inside:

1. The property management software the PMC already runs — with years of reservations, owner ledgers, and statements inside it, and an audit history that ties to filed numbers.
2. A pricing tool tuned to that market by somebody who has watched that market through several seasons.
3. A payment processor on terms someone negotiated — and a settlement rhythm the accounting team already reconciles against.
4. A cleaner and trades network with names, rates, and standing — the part of an operation that takes the longest to rebuild anywhere else.
5. Owner relationships that renew because a specific person picks up the phone and answers the question.
6. A brand guests have already booked once and would book again, with the reviews and repeat-stay history that go with it.
7. The team’s muscle memory — which system to check when. It is the least documented asset in the folder and one of the most valuable.

Every one of those sits on the balance sheet of the operation, whether or not it appears on the one the accountants keep. A group that keeps all seven keeps the reason it went after the PMC in the first place.

Where a roll-up’s operating leverage actually lives

Three things create leverage across a multi-PMC group, and only one of them is procurement:

1. One operating picture. When Tuesday at PMC A and Tuesday at PMC B are visible in the same view, in the same shape, the difference between them is something you can act on that same week rather than at the next board meeting.
2. Standards that travel. The response time, the escalation path, and the review-recovery play that the best PMC in the group already runs — held everywhere, in every brand’s own voice.
3. Terms that compound. Processing and vendor terms quoted against the whole portfolio rather than against each PMC’s original size, and tool overlap you can see well enough to consolidate on purpose.

Notice what none of the three ask for: that every PMC run the same software. Visibility is a property of the layer above the systems, not of the systems agreeing to become one system.

There is arithmetic underneath that. A single operation running six systems has fifteen pairs that have to stay in agreement — the two prices of a property management tech stack is the single-company version of that story. A group of four PMCs has four of those sets, plus everything the parent wants to read across all four at once. Each PMC you add multiplies what one shared view is worth, which is exactly why the view is the thing to stand up first.

Day one: every PMC runs its own STR Squad, and the parent gets the command center

Each PMC gets its own STR Squad, built to sit on top of the property management software that PMC already runs. The PMC keeps its PMS as its own system of record; its squad connects into that PMC’s own accounts, works across the systems around the PMS, and writes results back under that PMC’s own brand.

Then it rolls up. Every PMC’s squad feeds the STR Squad Enterprise Operational Layer: one command center with consolidated CFO, COO, and Strategist views for the parent, while every PMC keeps its own stack and identity. Each squad is the same engine that runs a single portfolio — 42 specialist AI agents on 12 teams, cross-functional by design — working for its own PMC, with the parent reading across all of them at once.

That is the whole structural move, and it is worth saying plainly: the group standardizes the operation without standardizing the stack.

Three consolidated views STR Squad gives the parent: CFO, COO, and Strategist

One command center, three seats at it. Each one reads across every connected PMC, and each one keeps every PMC’s own numbers reconciling where they already reconcile.

Underneath all three, every agent action shows its reasoning and lands in an audit log, and each PMC’s control mode is yours to set: Approve-first while trust builds, then Auto-pilot one workflow at a time. A group can hold one PMC at Approve-first and widen another, and the audit log reads the same in both.

Standardize the operation while every PMC keeps its own stack and identity

Standardization usually gets discussed as a software decision. In a group it is an operating decision, and the two come apart cleanly.

What the group holds in common: the response time a guest waits, the escalation path a 2 a.m. lockout takes, the way a soft review gets answered, the owner report that lands on the same day everywhere, and the house rules and knowledge base each PMC’s squad works from. Those are the things a guest and an owner actually experience, and they are what a group is really buying when it says “one standard.”

What each PMC keeps: its PMS, its pricing tool, its processor, its cleaners, its market knowledge, and its name on the door and on the guest’s confirmation email. Guests who booked the local brand keep booking the local brand.

The acquired team hears the second list on their first Monday, and that is the point: the people who know that market keep the tools they are fluent in and spend their first quarter inside the group doing the work that made the PMC worth acquiring. Their hours go to owners and guests, and the group gets its standards at the same time.

STR Squad at group scale: quoted around your operation, portable any day

At group scale STR Squad is quoted around the operation rather than picked off a rate card — the number of PMCs, the systems connected, the shape of the portfolio, and the terms you want. What holds at every level holds here too: one flat monthly price per account, never per unit, so adding doors inside a PMC leaves the arithmetic you approved intact. The published ladder for smaller portfolios is on the plans page.

And the door stays open. Your group’s data is exportable any day you want it — CSV, JSON, open API, spelled out in the openness table — and any PMC can swap any vendor underneath STR Squad without re-platforming. Vendor payouts stay whole, too: you pick your own cleaners and trades, and we take 0% of what you pay them. A layer you can leave is a layer you can trust with four PMCs at once.

STR Squad goes live PMC by PMC, in the order you choose

Groups generally start with one PMC rather than all of them, and which one is a strategy call:

• The newest acquisition — when you want the group’s standards in place while the team is still forming its habits inside the group.
• The largest PMC — when the fastest read on group-wide numbers is what the parent is waiting on, since one PMC can carry most of the consolidated picture on its own.
• The PMC with the widest stack — when you would rather see the most involved connection shape working first, and treat everything after it as the easy version.

Each PMC’s turn is a connection into that PMC’s own accounts, one workflow live at a time, with the audit log filling while everyone watches. The PMCs that have not had their turn yet keep running exactly as they run today, and the consolidated view fills in PMC by PMC as they connect. What a single company’s first day looks like, step by step, is in Connect It, Keep Everything — day one of property management software implementation.

Frequently asked questions about STR Squad across a multi-PMC group