Pavilion launched on October 5 as a national vacation rental company built from 20 local management companies that together manage more than 5,000 homes and host about 50,000 guests a month across the United States, according to its launch release.
Four of the 20 founding companies have since merged into others, so the group operates as 16 today. Each keeps its local team and leader. Pavilion supplies the shared layer: technology, data, owner reporting, accounting, revenue management, business development, purchasing and insurance. The leaders of the local companies become shareholders and, together with the Pavilion team, own the majority of the business. The release names TZP Group, investment funds managed by HPS Investment Partners and Capital Dynamics as investors, with PGIM as primary lender for the platform.
Why it matters to operators
For anyone who sells software to vacation rental managers, or runs a management company that buys it, the thing to watch is who makes the purchase. The release lists technology, data and revenue management as shared services, which points to 20 separate stack choices being folded into one platform decision. It does not name the systems Pavilion runs or say whether the local companies keep a say in tooling, so the pace and scope of that consolidation are not yet public.
The same trade shows up elsewhere in hospitality. Accor’s choice of Mews as the first partner in its F&B technology program standardizes a stack across a brand portfolio. Pavilion reaches a similar result through ownership instead of a brand standard. Shared revenue management is also the function SiteMinder targeted with its Dynamic Commerce Engine for hotel pricing and distribution.
Our read: a local manager gains lower cost per stack and loses some choice over which stack. Vendors in this segment should ask who signs the contract after a roll-up closes, because the answer decides whether they sell to 16 operators or to one.
