Hello Hospitable Team,
I’m a physician and a condo owner in a 26‑unit building where each owner independently manages their own Airbnb and Vrbo listings. When our HOA needed a PMS, I took it upon myself, despite a demanding clinical schedule, to research, evaluate, and implement a solution. After extensive comparison, I chose Hospitable Mogul because it offered the best combination of Airbnb API connectivity, Vrbo automation, owner dashboards, revenue splits, and operational tools.
I want to emphasize that we want to stay with Hospitable. Mogul is close to being the perfect solution for multi‑owner buildings like ours.
However, in the process of onboarding our building, which required more than 100 hours of my own time, I discovered several scoping, privacy, and governance issues that make Mogul difficult for multi‑owner buildings. These are not missing features. They are structural issues that arise because multi‑owner buildings were not part of the original Mogul design assumptions.
The good news is that the changes needed to support this segment are small, incremental, and aligned with your existing architecture.
Global visibility of message templates and customized messages Automated messages are correctly scoped to individual properties, but the template library and customized templates are global. Every owner can see and edit every other owner’s customized messages. This is both a privacy issue and an opportunity for accidental errors. This occurs specifically under Guest Experience, which is currently scoped to “all properties.”
Global visibility of rental contracts Contracts are also global. Owners should not see or edit each other’s agreements.
Notification routing inconsistencies and no unified dashboard Some notifications go to the HOA admin, some to individual owners, and some to both. There is no unified dashboard to manage or audit notification flow. We need a single place to see what was sent, to whom, for which property, and whether it succeeded or failed.
Direct booking listing order is not randomized Platforms like OwnerRez randomize listing order so no owner is unfairly prioritized. For a multi‑owner building, this is essential for fairness and owner satisfaction.
Role and portal complexity The current structure of primary users, secondary users, owners, teammates, the owner portal, and the secondary user portal is confusing. Each of our 26 owners really needs one clear dashboard. I understand this is not a small tweak, but it is a real barrier to adoption for buildings like ours and worth mentioning.
There is a large and underserved market of condo‑hotel buildings, HOA‑run STR buildings, multi‑owner complexes, and boutique buildings with ten to one hundred units. These buildings are not well served by traditional PMS platforms. Mogul is already close to being the ideal solution for this segment. It simply needs a few scoping and visibility enhancements.
Our building alone represents 26 units, but more importantly, we represent a repeatable model. There are thousands of buildings like ours. If Mogul supports this use case cleanly, you unlock an entirely new category of customers.
I have submitted these items through your improvement and ideas page. However, because it is a voting‑based system and multi‑owner buildings are a small percentage of your user base, I have no confidence these issues will ever rise to the top. That is why I am reaching out directly.
We would appreciate a brief meeting with someone on the product or customer success leadership team to discuss:
• Scoping message templates by property or owner • Scoping rental contracts by property or owner • Adding a unified notification dashboard • Adding notification routing rules by role • Randomizing direct‑booking listing order • Ensuring onboarding specialists understand the multi‑owner building model • And, as a longer‑term consideration, simplifying the role and portal structure so each owner has one clear dashboard
These are small design changes with major market consequences.
Thank you for your time. I look forward to speaking with the appropriate product owner or Mogul program lead.
Warm regards
Please authenticate to join the conversation.
Backlog
💡 Feature requests
Mogul
About 13 hours ago
Get notified by email when there are changes.
Backlog
💡 Feature requests
Mogul
About 13 hours ago
Get notified by email when there are changes.