How to Set Up HubSpot for an Insurance Agency or Brokerage
An insurance agency does not close a sale and move on. It binds a policy that renews every year, places it with a carrier whose appetite decides what can be written at all, and carries the claims made against it as the thing that determines whether that carrier keeps writing. A CRM holding four objects can record the pursuit and nothing that follows it. This walkthrough sets out the object model RevOps HQ installs for agencies and brokerages: what each of the four added objects carries, why the deal ends at bind and the policy begins there, and the renewal, coverage gap and carrier concentration reporting that becomes possible once the model holds.
Key takeaways
- Policy, coverage line, carrier and claim are custom objects added to HubSpot’s standard four. Each carries figures the standard objects have nowhere to put.
- A deal ends at bind and a policy begins there. The deal records the pursuit and stops; the policy records what exists afterwards, with a status, an annual premium and the renewal date the service calendar is built from.
- Binding creates the policy and its renewal date in the same action, so the renewal exists from the first day rather than being entered later by someone who remembers.
- A carrier writes many policies, which is what makes premium concentration visible. An agency with most of its premium through one carrier holds a risk no single policy record shows.
- Coverage line is separate from policy because a gap is identified per line. A client insured on property and liability but not on umbrella has a gap that exists between records rather than on any one of them.
- Claims attach to the coverage line, so claim amount and producer follow-up resolve to the line and to the carrier behind it rather than only to an account.
- Loss ratio held on both the account and the carrier is what turns remarketing from a reaction into a schedule: a deteriorating ratio is remarketed early rather than at renewal.
- Reporting follows from the model: premium by line of business and policy status, claim amount by status, carrier concentration, coverage gaps, and household premium by account type.
The Object Model Decides What Can Be Reported
HubSpot ships four objects. Contacts are people, companies are organisations, deals are transaction opportunities, and tickets are service issues arising from them. Those four describe a business that sells something and supports it afterwards.
They do not describe an agency. The policy, the coverage line, the carrier and the claim each carry figures with nowhere to sit in that model, and the questions an agency principal asks are all questions about them. Whether coverage gaps can be listed, whether premium concentration by carrier is visible, whether a renewal calendar exists at all: each is a consequence of the model rather than of the reporting tool above it.
The Deal Ends at Bind; the Policy Begins There
The deal records the pursuit. It moves from lead through the expiry date captured, quoted, presented, and finishes bound or lost. At that point it is history, and its job is done.
The policy records what exists afterwards and keeps existing. It carries a status that moves from bound to active and eventually to lapsed, cancelled or non-renewed. It carries an annual premium. Above all it carries a renewal date, which is the field the entire service calendar is built from.
Agencies holding this on the deal record end up with a closed-won deal carrying a premium figure that was true on the day it bound. The renewal then lives in a spreadsheet or in a producer’s memory, and the ninety-day board that should be driving outreach does not exist. Binding creates the policy and its renewal date in the same action, which is what makes the calendar real from the first day rather than accurate only where somebody remembered to enter it.
A Coverage Gap Exists Between Records
Coverage line is a separate object because the question an agency needs answered is per line rather than per policy. A client insured on property and general liability but carrying no umbrella has a gap, and that gap is not a property of any record they hold. It is the absence of one.
With lines as records, each carrying its own limit and deductible, the gap becomes a query rather than an observation made during a review that may or may not happen. Recording it during the review is what allows outreach to be scheduled against it, ordinarily eight weeks before the renewal it relates to.
Concentration Is Only Visible From the Carrier
A carrier writes many policies, and the relationship is where two numbers live that no policy shows on its own: total premium placed, and the loss ratio the agency runs with that carrier.
Concentration is the risk this makes visible. An agency placing most of its premium through one carrier is exposed to that carrier’s appetite changing, and the exposure is invisible while premium is only ever read per account. Loss ratio held alongside it decides the other direction: a deteriorating ratio is a remarketing trigger, and acting on it early is materially different from discovering it when the carrier declines to renew.
Claims Resolve to the Line, Not the Account
A claim attaches to the coverage line it is made against. That is what allows claim amount by status to be read against the line and the carrier behind it, rather than aggregated to an account where the pattern disappears.
Producer follow-up is recorded on the claim as a defined value rather than left as an assumption. A reported claim with no follow-up recorded is then a list, and the list is what an automation acts on. A claim is the moment a client is most attentive to whether the agency is present, and it is the moment most easily missed.
The Reporting the Model Produces
Each of the following follows from the objects rather than being added on top. None requires an export.
- Sales by quote type, separating renewal shopping from new business, cross-sell and remarketing
- Lines of business by policy status, so quoted business sitting unbound is visible against what is active
- Premium placed by appetite, across personal, commercial, specialty and surplus
- Claim amount by status, and claim status against producer follow-up
- Coverage gaps by line, and limit amounts against whether a gap is recorded
- Household premium by account type, across personal, commercial, benefits and mixed
- Annual premium by line of business, and total annual premium on whatever period the agency reports on
The non-renewed list is the one that changes behaviour soonest. Policies recorded as non-renewed are a defined set, which means they can be enrolled directly into a remarketing campaign rather than reconstructed from memory each quarter.
What Installation Involves
The objects, the properties, the workflows and the reporting described here are built. An installation configures them in the agency’s portal and then adapts the remainder, which is ordinarily a matter of the lines written, the carriers represented, and the stages a quote passes through before it binds.
Agencies differ at the edges and not in the middle. A policy renews, a carrier decides what can be placed, a gap sits between records, and a claim tests whether anyone follows up. The customisation sits at the edges.
Frequently asked questions
Does this replace our agency management system?
Ordinarily not. An AMS carries rating, downloads from carriers, accounting and compliance functions that a CRM does not replace. What this model does is make HubSpot the record of the commercial relationship, with the AMS integrated into it rather than duplicated by it.
Why not keep the premium on the deal record?
A deal closes once and stops changing. A policy renews annually, changes status, and carries the date the service calendar is built from. Holding the premium on a closed deal means it is correct on the bind date and progressively wrong afterwards, and it leaves the renewal with nowhere to live.
How are coverage gaps actually identified?
By recording each coverage line as its own record with its limit and deductible, and marking during a review where a line that ought to exist does not. The gap is then a filterable set rather than a note in a file, which is what allows outreach to be scheduled against it ahead of the renewal.
Can renewals be worked from a board?
Yes. With the renewal date on the policy, a board of policies renewing in the next ninety days is a saved view, and the outreach that should begin around eight weeks out is a workflow rather than a reminder somebody sets.
What does an installation cost relative to building it?
A partner building this specification from an empty portal is ordinarily a five-figure engagement, because the objects, properties, workflows and reporting are all bespoke work. This model is already built, so the engagement configures it and adapts the remainder.
Talk through the Insurance build
Book a timeOpens HubSpot in a new tab. The in-page calendar needs the cookies you declined.
Setting up HubSpot for your agency or brokerage?
The object model, workflows and reporting described here are already built and can be installed in an existing portal, then adapted to the lines written and the carriers represented. A short call establishes whether the model fits before any work is scoped.