HubSpot for RealGreen franchise networks: portals, brands, and rollups

How should a franchise network where every location runs RealGreen set up HubSpot? Answer one architectural question before anyone buys anything: one shared portal for the network, or a separate portal per franchisee. Everything else, cost, brand control, lead routing, corporate reporting, and who owns the customer data, falls out of that choice. We have wired both architectures, so we can tell you there is no universally right answer, but there is usually a clearly right answer for a specific network, and it depends on who does the marketing and who signs the checks. Here is how we would walk a franchisor through the decision.

What is the one question to answer first?

Ask it concretely: when a homeowner in a franchisee's territory fills out the national website's form, whose system should that lead land in, under whose branding, counted in whose report? If the honest answer is "corporate runs marketing and franchisees run trucks," you are a single-portal network. If franchisees genuinely run their own marketing with their own budgets and corporate mostly licenses the brand, portal-per-franchisee matches reality. Networks get into trouble when the software architecture contradicts the operating model; the marketing-ops side of that alignment is the subject of our RealGreen franchise marketing post, and the general strategy lives in the franchise marketing playbook.

When does one shared portal win?

A single portal, with HubSpot's business-units add-on (an Enterprise-level feature as of this writing) giving each franchisee its own branding, sending domains, and filtered views. The advantages compound with size. Templates, workflows, and lifecycle definitions get built once and distributed everywhere, so the network's best marketing becomes every location's marketing. Rollup reporting is native: corporate sees leads, sold programs, and cost per acquisition across all territories in one place, on one definition of each metric. And each franchisee's RealGreen database can feed the same portal through per-location syncs, keyed by territory.

The honest costs: Enterprise is a serious commitment, permissioning takes genuine admin skill to keep franchisee A out of franchisee B's contacts, and every shared system has a blast radius, since a bad workflow shipped from corporate misfires in fourteen territories at once. Somebody competent has to own the portal full time, and that somebody works for corporate.

Adoption is the underrated risk. A shared portal only pays if franchisees actually work their leads and log their activity in it, and franchisees are owners, not employees; they adopt what visibly helps them sell. Ship the portal with working plays already loaded, prove one location's results, and let the network copy success rather than comply with a memo.

When does portal-per-franchisee win?

Each location buys its own Starter or Professional portal, owns its data outright, and runs marketing its way. Autonomy is clean, local billing is clean, and a franchisee who leaves the network walks out with their portal intact, no data-custody fight required. Smaller networks, and networks where franchisees predate the brand, often start here by default.

The costs mirror the benefits. There is no native rollup: corporate reporting means exporting from N portals into a spreadsheet or BI tool, with N slightly different definitions of "lead." Templates drift within months as each location edits its copy. Admin effort multiplies, because someone sets up lifecycle stages, sync, and suppression correctly N times, or more realistically, doesn't. And the subscription math multiplies the same way: every location carries its own tier, its own onboarding, and its own admin burden, so past a handful of locations the shared portal usually wins on total cost of ownership as well as control. Run both architectures against current HubSpot pricing at your real location count before assuming either way; we deliberately don't quote figures here because they change.

How does lead routing work across territories?

The national site takes a lead; ZIP-code logic assigns it to a territory; the lead lands with the right franchisee's team, under SLA, with source attribution intact. In a single portal that is one workflow with a territory lookup table, and corporate can see whether each location actually worked its leads, which becomes the compliance metric that matters most: speed to first contact. In per-portal architecture, routing means webhooks or middleware pushing leads across portals. That is buildable, and it is the kind of wiring we do routinely (we can connect RealGreen and HubSpot to pretty much anything with an API, a Zapier connection, or a native connection), but brittle is brittle, and boundary disputes get settled by whoever configured the integration. Either way, publish the territory table and the tiebreaker rule (adjacent-territory overflow, corporate house accounts) before spring, not during it. The multi-location mechanics inside a single company, which rhyme with all of this, are in the multi-branch marketing post.

What should the corporate rollup show?

Resist the forty-widget dashboard. A useful franchise rollup fits on one page and answers five questions, monthly, per territory:

• Leads by source, on one shared definition of a lead.
• Cost per sold program, with revenue synced back from each location's RealGreen.
• Speed to first contact, the discipline metric that predicts everything else.
• Program penetration of the base, which shows where upsell campaigns should aim.
• Marketing spend versus the closed-loop revenue it produced.

Who owns the data when a franchisee leaves?

The ugliest franchise disputes are data-custody disputes, and they are all preventable by paragraph. Before any portal is purchased, write down: who owns the contact records in each territory, what corporate may do with network-wide data (benchmarking yes, poaching territories no), and exactly what a departing franchisee takes with them, in what format, within how many days. In a single portal this defaults to corporate ownership with contractual franchisee rights; per-portal defaults the other way. Neither default is wrong, but discovering which one you implied during a franchisee exit is expensive. If you are building this stack across a network, our franchise practice has wired both architectures and will tell you honestly which fits.

The takeaway: portals are just the software expression of your franchise agreement. Decide who runs marketing, who sees what, and who keeps the data when someone leaves, and the one-portal-or-many question mostly answers itself.

Decide the portal question first

1. Write one sentence describing who actually runs marketing in your network: corporate, franchisees, or genuinely both.
2. Price both architectures at your real location count against current HubSpot tier pricing, including admin time, not just subscriptions.
3. Draft the data-ownership and franchisee-exit terms before purchasing anything.
4. Pilot the chosen architecture with two or three locations, including RealGreen sync and lead routing, before network rollout.
5. Stand up the five-question rollup on day one, so every location launches onto the same definitions.