Head Office vs Site Roles
In a property operator, work splits between centralised head-office functions — marketing, revenue management, finance, and central leasing — and site-specific roles based at each building, such as on-site leasing, operations, and residence life. Where an operator draws the line, especially for the sales function, drives how systems are structured, how leads route, who sees which records, and where operational knowledge sits.
What are head-office and site roles in a property operator?
Head-office teams sit centrally and serve the portfolio as a whole. They include the functions that benefit from centralisation: marketing campaigns and enquiry generation, revenue management and pricing, finance and reporting, and often a central contact centre or leasing team that handles initial enquiries across all buildings from one place.
Site teams are based at individual buildings and handle the things that require physical presence or local knowledge. That means conducting viewings, managing move-ins and move-outs, dealing with maintenance issues, running resident events, and converting the enquiries the central team has qualified.
The boundary between the two layers varies by operator. Smaller operators may carry out all leasing centrally and have sites focus entirely on operations. Larger portfolios may have a mix: a central marketing function, regional leasing managers, and building-level operations coordinators.
Centralised vs devolved sales: the trade-off
The biggest decision is whether the sales function is centralised or pushed out to sites. Both models work, and both have real costs.
Centralised sales. A central team of three or four people owns selling across the whole portfolio. The licensing cost is straightforward and visible: you pay for that number of HubSpot Sales Hub paid seats, and that is roughly where the system cost sits. In return, you get specialists. People who do nothing but sell, all day, handle a much higher volume of enquiries and tend to convert better, because selling is a skill that improves with repetition and focus. The downside is that the central team is one step removed from the physical building and relies on site teams for viewings and local knowledge.
Devolved sales. In many operators the sales function is pushed out to sites instead, and each building effectively runs as its own mini-business, almost like a franchise. The same person who handles leasing is often also doing viewings and covering front-desk enquiries. When someone walks in or the phone rings, the half-finished sales follow-up gets put down. Selling becomes one of five or six jobs rather than the job, and it frequently slips down the priority list. One person doing a general role across several tasks has genuine advantages: local presence, flexibility, and a single point of contact for the resident. It also has a clear drawback: conversion now depends on a generalist who sells occasionally rather than a specialist who sells constantly.
There is no universally right answer. The point is that the choice is a commercial one with direct consequences for conversion, cost, and how the CRM should be built.
Where does the systems knowledge sit?
The sales question leads to a second one that operators often miss until it bites: who runs the systems?
A centralised team usually has, or can justify, a dedicated systems administrator. In a HubSpot operator that is the HubSpot admin: the person who knows which workflows are live, monitors whether they are firing correctly, and adjusts them as the operation changes. That knowledge is concentrated and maintained in one place.
Devolve everything to sites and the question becomes unavoidable: who picks that up? Where does the workflow knowledge live when there is no central owner? Site teams also typically turn over faster than central functions, so the risk of knowledge drain is higher. When the one person at a building who understood the setup leaves, the understanding can leave with them, and the system slowly drifts out of alignment with how the operator actually works.
This is where the priority an operator places on systems over people shows up. A business that depends on individuals to remember how everything works carries a single-point-of-failure risk on every site. A business that invests in well-maintained systems is far more resilient to the people moving on.
Key takeaways
- Head-office functions cover marketing, revenue management, finance, and central leasing; site functions cover on-site operations, viewings, maintenance, and residence life.
- The split is the primary design constraint for CRM setup: lead routing, permissions, and reporting all flow from it.
- Where the sales function sits is the biggest decision. A centralised specialist team costs a known number of HubSpot Sales seats and tends to convert better; a devolved model spreads selling across generalists who are also doing viewings and front desk, so it can take lower priority.
- Centralised teams usually have a systems admin who owns the workflows; devolving to sites raises the question of where that knowledge sits, and higher site turnover makes knowledge drain a real risk.
- A retained HubSpot partner maintains the systems, frees internal resource, avoids extra central headcount, and removes the key-person chain risk of knowledge leaving with one employee.
How Cloudfox Helps With Head Office vs Site Roles
Cloudfox configures HubSpot to mirror the operator's head-office and site structure from the start. That means creating teams and permissions so each group of users sees exactly what they need and nothing they do not. Pipelines are built to reflect the actual leasing journey and the handover point between central and site. Lead-routing workflows assign new enquiries to the correct site team automatically based on the property of interest. Central marketing and revenue management get portfolio-wide dashboards; site teams get building-level views.
Beyond the build, a retained HubSpot partner solves the knowledge problem directly. Rather than relying on a central systems admin you have to hire and retain, or hoping site staff maintain workflows they were never trained to own, the systems are maintained for you. That frees internal resource for revenue-generating work, removes the need to carry additional central headcount just to administer the CRM, and removes the chain risk: the system does not break when one person leaves, because the knowledge does not sit with one person. The operating model is held in well-maintained systems, not in someone's head.
The result is a system that enforces the operating model rather than working against it. Central marketing generates demand. Whoever owns sales converts it. Reporting is accurate at every level because the structure is right to begin with, and it stays right because someone is keeping it that way.
Frequently Asked Questions About Head Office vs Site Roles
Is it better to centralise the sales team or devolve it to sites?
Both work, and the right answer depends on the operator. A centralised team of three or four specialists costs a known number of HubSpot Sales seats and usually converts better, because they sell full-time and handle higher volume. A devolved model puts selling in the hands of site staff who are also running viewings and front-desk enquiries, so sales can slip down the priority list, but it keeps a single local point of contact at each building. The trade-off is specialist focus and conversion versus local presence and flexibility.
Who maintains the HubSpot workflows if sales is devolved to sites?
This is the question devolved models often leave unanswered. A centralised team usually has a HubSpot admin who owns and tweaks the workflows. Push everything to sites and there is frequently no clear owner, and because site teams turn over faster, the knowledge can drain away when staff leave. A retained partner removes the problem by maintaining the systems regardless of who is on site.
How should a CRM handle lead routing between a central contact centre and site teams?
The enquiry comes in centrally and is logged in the CRM against the prospect's preferred site. At the point of handover (typically when a viewing is booked or the lead is qualified), the CRM assigns the contact to the relevant site team automatically. HubSpot can do this via workflow-based assignment rules: the trigger is a property of interest field or a pipeline stage change, and the action is team assignment and task creation for the site leasing contact.
Should site teams have access to the full portfolio in the CRM?
Generally no. Site users should see their building's contacts, deals, and tasks. Portfolio visibility is a head-office and management function. HubSpot's team-based permissions model supports this directly: users are assigned to teams that scope their view, so site staff are not navigating records they have no involvement with.
What pipeline stages should a centralised leasing model use?
The stages should reflect the actual journey and the handover. A typical setup runs: Enquiry received (central) to Qualified (central, after initial outreach) to Viewing scheduled (handover to site) to Offer made to Booking confirmed to Tenancy active. The key is that the handover between central and site has a named stage that triggers the assignment, so it is visible and measurable, not just an informal email.
How does this affect revenue reporting?
Central revenue management and asset managers need pipeline data at portfolio level to make pricing and planning decisions. If pipelines are built for site teams only, roll-up reporting becomes difficult. Designing the pipeline with both audiences in mind from the start avoids rebuilding the reporting structure later.