HubSpot for insurance: the MGA guide

HubSpot can run an MGA's producer recruiting, appointments, renewals and marketing, as long as every fact has one home and one writer. Most of it works on Professional, where deals in separate pipelines, association labels and calculation properties do the job a custom object does on Enterprise.

We ran Rainbow's go-to-market, and in under a year it appointed 4,000+ agents across 20+ states at $88 per agent. Read the case study.

Why does a standard HubSpot setup break for an MGA?

A standard setup is contacts, companies and deals, a couple of lead nurtures, and sales stages borrowed from software. That works for a direct-to-consumer brand. An MGA has three problems it was never built for.

• The source of truth lives somewhere else. Policy terms, binding status and premium sit in the policy admin and billing systems. If that data never reaches HubSpot, reports and dashboards drift.
• Commissions need a formula. An agency's commission on a term is premium times the rate in its commission schedule, so HubSpot should calculate it from those two fields.
• The relationship keeps going after the sale. A policy renews, changes coverage or gets cancelled. A producer gets appointed, writes business, then goes quiet. Each of those needs its own follow-up.

Here is how the two setups compare, record by record:

What should an MGA model in HubSpot?

Start with the records the business runs on: producers, the agencies they work for, the programs each agency is appointed for, and the policy terms they write. HubSpot has three tools for that, and your subscription decides which ones you get.

1. Custom objects (Enterprise). A Policies or Appointments object holds those records natively. HubSpot built custom objects to "track business specific data that fits outside of HubSpot's fully-defined objects." Create and edit custom objects.
2. Deals in separate pipelines. An Agency appointments pipeline with one deal per agency and program, and a Policy renewals pipeline with one deal per policy term. Professional allows 100 custom pipelines on seat-based accounts, so both fit. Set up and manage object pipelines.
3. Association labels and calculation properties (Professional or Enterprise). A label says how two records relate: Servicing agent between an insured and their producer, Issuing carrier between an appointment and the carrier whose paper it sits on. A calculation property fills itself from a formula, which is how commission estimates work. Association labels, calculation properties.

On Professional, policy terms live as deals and the renewal pipeline does the job a Policies object would. On Enterprise, a custom object is cleaner. Settle one question before anyone builds: do policy terms live in HubSpot, or stay in policy admin with HubSpot holding a count and a link? Renewal tasks and commission estimates need the terms in HubSpot, and copying them means owning a sync.

The property map in this guide is built for Professional: about 45 fields, each with its source of truth and its one writer. Chapter 1 walks through the model.

Which fields should never share a job?

Give each fact its own field, because one field doing two jobs breaks reporting. An appointed agent can also buy a policy for their own restaurant; if one field holds both facts, one of them gets overwritten. These are the five fields and their jobs:

Record an application and an approval as two separate events. If the same form marks both, follow-up and reporting can't tell them apart.

One rule holds the model together: each field has one writer. If a form, a workflow and an integration can all change the same field, it will be wrong within a month. Chapter 2 defines every stage for producers and policyholders.

Which workflows should you build first?

Build the renewal and producer workflows first, because they act on dates your team already misses. Workflows need a Professional or Enterprise subscription. Create workflows.

1. Renewal review. The renewal spec's timeline starts with a data check 120 days before expiration and opens the review for the servicing rep at 90. Quoted renewals reach the agent at 60.
2. Pending cancellation. When billing marks a term pending cancellation, move it to At risk and give the channel manager a call task for today.
3. Producer onboarding. When an appointment deal reaches Appointed, start onboarding emails and the first-submission campaign, and stop every recruiting email.
4. License and E&O expiring. 30 days out, a task for contracting and an email asking the producer for the renewed license or certificate.
5. Producer inactivity. No submission in 180 days, and producer status moves to Inactive with a reactivation call for the channel manager.

The day counts are examples to set for your programs. Each workflow checks the last successful sync before it runs, so stale data stops the run before it creates a wrong task.

How do you keep producers and policyholders apart?

Give agency principals, producers, policyholders and carrier contacts each their own segment and their own owner. Mixed together, the team works the wrong list and the wrong person gets the wrong email.

Two decisions matter more than the segments. First, many agency agreements say the agent owns the client, so decide whether you ever email a policyholder directly before you build a policyholder list. The renewal spec's default sends renewal messages to the servicing agent, who owns the client conversation. Second, who sees insured data is a compliance question. If one team shouldn't see another team's insureds or agency relationships, set that in user permissions and test it as that user. HubSpot user permissions guide.

What should Google Ads count?

Send Google Ads one milestone you can prove in HubSpot. An appointment request, an approved appointment and a bound policy are different events, and if Google gets the same signal for all three you can't tell which part of the process is working.

The lifecycle definitions in this guide recommend the Producer MQL (licensed for your lines, in a state you write, at an agency type that fits) as the primary conversion, and the approved appointment as a secondary one to observe. Chapter 5 covers the setup.

What does the Enterprise path look like?

On the Enterprise path, we built this for an insurtech we don't name here: a custom object for Policies, calculated commission properties and a workflow alerting reps 60 days before renewal. The team saved 15+ hours a week and increased upsell success by 28% in one quarter. We wrote it up in October 2025: why insurtech companies need a specialized HubSpot implementation.

FAQs

Do we need HubSpot Enterprise?

Only for custom objects, such as a Policies object. Workflows, calculation properties, association labels and the custom report builder need Professional or Enterprise. The property map in this guide is built for Professional.

Can HubSpot replace our policy admin system?

No. HubSpot coordinates producer relationships, follow-up, campaigns and sales activity. The policy admin system stays authoritative for policy terms and binding status, and billing stays the ledger for commissions.

Where do we start if we're not ready for a full build?

Three moves: a review task for each policy term before it expires (90 days out in the renewal spec), producers separated from policyholders in lifecycle stages, and a written map of where your policy data lives. Add a Policies object if you move to Enterprise.

How long does a build take?

We typically reach full rollout in 30 to 45 days, then keep iterating. See what a HubSpot build costs.