A single owner running several units usually has no real head office. Each property reports in its own way, on its own rhythm, and the blind spots open in the gaps between the properties rather than inside any one of them. The Portfolio Control Gap Review is the faster wedge into group work than committing to a full control layer on day one: it names, in one place, what the owner cannot currently see across the group, sizes what the blind spots plausibly cost in aggregate, and hands back a fix order that doubles as a deployment map. Built outside-in from public data across every property, plus any reporting samples the owner chooses to share, with no system access needed to start.
A five-property group under one owner, no head office, run through a mix of property managers and channels. It is deliberately built to look like the groups this review is for: two boutique hotels of different sizes, two villa collections, and a room-and-restaurant site, so the comparable pairs (hotel against hotel, villa collection against villa collection) are the ones an owner would expect to be watched side by side, and are not.
The five properties are each run competently in isolation, but the owner has no single, independent line of sight across them: five units report in four different formats, on different rhythms, to different accounts, so no consolidated monthly picture exists and comparable properties are never compared. That gap is where the money hides: a season-long OTA promotion on one villa collection is quietly undercutting its sister collection in the same competitive set, one hotel is carrying materially more channel commission than its comparable twin, and cash clears to separate accounts on separate rhythms with no group-level reconciliation. Most of the highest-severity gaps exist only because this is a group, several of the first fixes are a decision rather than a spend, and the register below ranks them by severity, money and fixability.
The review is a public-data outside view across every property, plus a read of any reporting samples the owner supplies: no credentials, no system access, no internal figures unless the owner hands them over. Per property we run a reduced-scope outside view (channel and rate position, reputation and listing control, AI-assistant visibility once per distinct market the group trades in), capped at the top handful of findings each, because the product is the portfolio view, not five full Reads. The judgement-heavy layer, and the actual product, is what only appears when the properties are laid side by side. Where a claim needs private data to size, the register says so and names the exact data that would prove it.
The core of the deliverable. Every row is a gap that exists only because this is a group: it would not appear in a single-property Read, because it is about what falls between the properties, or about what an owner cannot see when nobody compares them. Ranked by severity, money and fixability. In a real review each row is a full finding object (claim, evidence, severity, confidence, estimated exposure, what would prove it properly, recommended action, owner decision required); here the evidence and exact figures are redacted.
| # | The gap (group-level) | Properties | Cost to the owner | Severity | Fixability |
|---|---|---|---|---|---|
| 1 | Five properties report in four different formats, on different rhythms, with no consolidated monthly picture; the owner cannot see the group in one place, so decisions lag and comparisons never happen | P1P2P3P4P5 | Decisions delayed; $X | High | Control layer |
| 2 | Channel-margin variance between comparable properties that nobody compares: one boutique hotel runs a far higher OTA share than its twin of similar size, and the gap has never been surfaced side by side | P1P3 | $X–$Xk / yr | High | Read-only data |
| 3 | One property's season-long OTA promotion is cannibalising a sister property in the same competitive set: a discount on one villa collection undercuts the other on overlapping dates, and no one owns the trade-off | P2P4 | $X / stay | High | Decision now |
| 4 | Rate-parity drift the owner would only spot with two properties side by side: the same OTA undercuts direct on two of the five, on different dates, so each looks fine alone and the pattern is invisible | P1P4 | $X / booking | High | 2 weeks |
| 5 | No group sign-off rule for OTA promotions: any property or its manager can launch a discount the owner never sees, so promotions like row 3 run unauthorised across the portfolio | P2P4P5 | Enables rows 3–4 | High | Rule, free |
| 6 | Cash clears to different accounts on different rhythms with no group-level reconciliation: payouts land across several accounts, reconciled property by property or not at all, so no one holds the consolidated cash position | P1P2P3P4P5 | Needs read-only data | High | Control layer |
| 7 | Review-reply standards vary property to property: one hotel replies within a day, one villa collection never replies, and there is no group standard, so guest-facing reputation is managed unevenly | P3P5 | Reputation drag | Med | Standard, free |
| 8 | Listing control is inconsistent across the group: some properties are claimed and correct on maps and review sites, others are unclaimed or mis-filed, with no group standard for who owns the public surfaces | P2P4P5 | Free fixes | Med | Free |
| 9 | No single competitive rate position across the group: each property is priced in isolation with no shared view of season, event or compset, so pricing discipline varies by whoever set it | P1P3P5 | $X | Med | Read-only data |
| 10 | Reporting cadence is set by the properties, not the owner: the owner receives what each manager chooses to send, when they choose to send it, with no exception-first view of what needs a decision this week | P1P2P3P4P5 | Owner time; risk | High | Control layer |
Read the fixability column as: a decision or a free change the owner can make this week; a change that needs read-only operating data to size and act on properly; and a standing control layer that only a recurring engagement can hold across the group over time. Every group-level claim here is evidenced in at least two properties' findings.
The gap in row 1 is abstract until you see what closing it produces: the same handful of lines an owner actually needs, for every property, in one place, on one rhythm. Below is that view for the illustrative group, with every figure shown as a band or a redacted placeholder. The value is not any one cell, it is that the row can be read across: the villa-collection promotion (row 3), the hotel channel gap (row 2) and the uneven reputation habit (row 7) all become visible the moment the properties sit on one page.
| The line an owner needs | P1 hotel | P2 villas | P3 hotel | P4 villas | P5 rooms+F&B |
|---|---|---|---|---|---|
| Reports to owner as | Spreadsheet | Spreadsheet | Chat message | Nothing set | |
| Occupancy (illustrative) | ~XX% | ~XX% | ~XX% | ~XX% | ~XX% |
| OTA share of gross | ~75–85% | ~55–65% | ~55–65% | ~60–70% | ~40–50% |
| Est. commission / mo | $X | $X | $X | $X | $X |
| Cash reconciled to owner | Partial | No | Partial | No | No |
| Review reply habit | Same day | Ad hoc | Same day | None | Ad hoc |
| Rate parity vs OTAs | Undercut | Holds | Holds | Undercut | Untracked |
| Listing control | Claimed | Unclaimed | Claimed | Mis-filed | Partial |
This is the shape a group needs, not any client's accounts. In a paid review the bands are replaced by the group's own figures, and the OTA-share and parity rows are confirmed against reservation data where the owner shares it. The point of the page is the comparison: no property is failing on its own, but read across, the pattern the owner is paying for is plain.
The register ends in a fix order, sequenced group-first. Decisions and free changes cluster at the top; the standing control layer comes last because it is the part only a recurring engagement can hold. This order doubles as the deployment map for the control layer it credits into.
First two weeks, decisions and free changes
First quarter, with read-only data
The first-quarter items are not a one-off project; they are a standing control layer. That is the Group Control Tower: the head office a small group does not have, one relationship across many units, read-only and draft-only by default. The same stack already runs in production across our boutique hotel group in Lombok, disclosed to clients and ring-fenced by a written no-operate rule.
Group Control Tower $1,500 base + $750 / property / mo
The smallest group engagement, two properties, lands at $3,000 / mo. Setup is scoped per group before the recurring rhythm begins. Market-protected: limited to one ownership group per agreed competitive set. Terms are bound before any private data access.
Credited once, non-transferable. Public data only, so this review carries no exclusivity; market protection begins only if the group continues into the Control Tower.
A Portfolio Control Gap Review is a public-data outside view plus a read of any reporting samples the owner chooses to share. Its honesty is part of the product, so what it can and cannot see is stated rather than blurred.
| What the review can see without credentials | What needs read-only data to size or confirm |
|---|---|
| Each property's public channel and rate position, and how the comparable properties differ side by side | The real channel mix and commission per property, from reservation sources and commission invoices |
| OTA promotions running across the group, and where one property undercuts another in the same compset | The actual revenue given up to a promotion, from the properties' own booking data |
| Public reputation and review-reply behaviour, and where the group standard is uneven | Guest-contact and enquiry logs behind the reputation picture |
| Listing control and public-surface ownership across every property | Whether cash reconciles across the accounts, from bank feeds and the ledger |
| Which reports the owner receives today, and whether they answer what an owner needs | The consolidated monthly picture itself, which is built once the owner shares read-only data |
Where a claim needs private data, the register names the exact data that would prove it and carries the finding into the fix order and the control layer, rather than inventing a number. Estimates are ranges with the arithmetic shown, marked as estimates, never presented as fact. Public prices are point-in-time, recorded as shown to an anonymous shopper on a stated date. This is a management review for the owner's own decision-making, not an audit opinion, and not accounting, tax or legal advice.
| Window | Focus | Owner involvement |
|---|---|---|
| Days 1–14 | Decisions and free changes: the OTA-promotion sign-off rule, the review-reply standard, listing claims, and the group parity direction | Two decisions: the promotion sign-off rule and the parity policy |
| Days 15–45 | Stand up one consolidated monthly picture and one reconciliation view, once the owner shares read-only data for each property | Grant read-only access per property; approve the consolidated format |
| Days 46–90 | One competitive rate position and an exception-first owner briefing across the group; review realised channel margin and parity | Choose which gaps move into a standing control layer |
Every delivered review ends with the one question that is the bridge to what comes next:
The standard behind it, stated as a plain commitment and not a claim of results: if the readout does not leave the owner with at least three specific, costed gaps they did not already have a line of sight on, we do one further round or refund the fee.
| Product | What it is | Price (USD) |
|---|---|---|
| Free AI Visibility Check | The public-data outside view, no system access | Free |
| Owner's Read: Leakage & Control Review | The single-property ranked leak register and fix order | Standard $1,750 · Pro $3,500 |
| Portfolio Control Gap Review | This deliverable: the group-level control-gap register, for 2–10 properties | $3,500 |
| Group Control Tower | The standing owner-side control layer across the group | $1,500 base + $750 / property / mo |
The $3,500 fee is credited in full against a Group Control Tower setup started within 30 days of the readout. Credited once, non-transferable.