Define each HubSpot lifecycle stage twice, once for producers and once for policyholders, and give producer status and lead status their own fields. When a record's stage disagrees with what happened, find who wrote it and fix that writer before you fix the record.
What does each stage mean for a producer and a policyholder?
Each stage needs two definitions, because a producer and a policyholder reach it by different events. These are HubSpot's default stages with the definitions we recommend; rewrite the wording to match how your contracting works. Lifecycle stages come with every HubSpot plan. Use contact and company lifecycle stages.
| Stage | For a producer | For a policyholder | What proves it |
|---|---|---|---|
| Subscriber | Signed up for appetite updates or the newsletter | Signed up for content (rare for an MGA) | Newsletter form |
| Lead | Asked for something: an agent guide, a program question, a call | Asked for a quote or coverage information | A producer or insured form |
| Marketing qualified lead | Licensed for the line, in a state you write, agency type fits | In appetite: a business class and state you write | License, state and agency type filled and in range |
| Sales qualified lead | The channel manager talked to them and wants to appoint | Routed to a servicing agent who accepted it | A logged call or meeting, lead status Connected |
| Opportunity | Appointment deal at Application received or later | Quote issued | An open appointment deal, or the quote |
| Customer | Appointed for at least one program | Policy bound | Approval date and appointment record ID, or a bound policy |
| Evangelist | A producing agent who referred another agency, or a top-tier agency | Renewed at least once and referred someone | A logged referral, or agency tier Top producer |
One decision changes everything downstream: is an appointed agent a Customer, or only one who has bound a policy? Whichever you pick becomes the top of the producer funnel and, most likely, a Google Ads conversion. We count an agent appointed for at least one program, and let producer status track whether they've written business since.
Why do producer status and lead status need their own fields?
Give the producer journey its own field so the policyholder journey can't overwrite it. An appointed agent can also buy a policy for their own restaurant, and lifecycle stage can only hold one of those facts. Producer status is copied by a workflow from the appointment deal and the synced submission counts, and nobody edits it by hand.
| Producer status | Means | What proves it |
|---|---|---|
| Prospect | Known to us, has not applied | A contact with audience type Producer |
| Applied | Started an appointment for at least one program | An appointment deal exists |
| Contracting | Paperwork in, waiting on the carrier or the state | Deal at Application received or Submitted to carrier |
| Appointed | Can write at least one program | Deal at Appointed, with approval date and record ID |
| Producing | Bound at least one policy in the last 12 months | Synced bound policy count above zero |
| Inactive | Appointed, but no submission in your limit (180 days, for example) | Last submission date older than the limit |
| Terminated | Appointment ended | Termination recorded in the appointment system |
Lead status is the rep's field. It says what they're doing right now, and its Not a fit values record why a producer stopped: unlicensed for your lines, out of territory, or a book outside your appetite. The unlicensed value also keeps those producers out of your ad audiences.
HubSpot's Lead object is a separate tool. It needs Sales Hub Professional or Enterprise, and this setup doesn't require it. Set up lead pipeline automation.
Who is allowed to change each field?
Each field gets exactly one writer. Yes means allowed.
| Field | Forms | Workflows | Policy admin sync | People |
|---|---|---|---|---|
| Lifecycle stage | No | Yes | No | One named admin |
| Audience type | Adds a value | No | No | Ops |
| Producer status | No | Yes | No | No |
| Lead status | No | Sets New only | No | The contact owner |
| License fields | No | No | If you have a license feed | Contracting |
| Policy fields on renewal deals | No | No | Yes | No |
Turn off the form setting that writes lifecycle stage, so one set of workflows owns it. A license a producer types into a form goes in a separate note field, never in the license fields contracting checks.
Then open Settings > Objects > Contacts > Lifecycle Stage > Automate. Company sync applies a primary company's stage to its contacts, and the deal rules set stages when a deal is created or won, so check what yours are set to before you trust any stage. Automatically set and sync lifecycle stages.
How do you find the records whose stage is wrong?
A producer marked Customer who was never appointed. An appointed agent still getting recruiting emails. A policyholder sitting in a producer list. Each is a stage that stopped matching what happened, and each sends the wrong email, builds the wrong ad audience or reports the wrong conversion.
Start with one of those records before you touch a segment. Say a producer shows as Customer, but there's no appointment deal at Appointed and no record ID from contracting.
- Write down what's there. Record ID, lifecycle stage, producer status, owner, agency and any appointment deals.
- Read the history. Open the Lifecycle stage property history. Note the value, the time and the source of the change. View property history.
- Check what happened. Look for an approval date and an appointment record ID. An application or a booked call doesn't make an appointment.
- Check the association. Producers at an appointed agency each need their own evidence. Confirm this person is on the appointment.
- Write the decision. Keep the stage, correct it, repair the association, or hold it for review, and say why.
At Functional Finance, contacts could belong to a company without being linked to its deal, so we checked who took part before changing a stage, and we left valid Leads alone when the evidence didn't justify moving them.
Export a baseline before you change anything in bulk. The property history export keeps up to 45 revisions for each contact property, uses UTC for change dates, and needs CRM Export plus Contacts Edit All permissions. Export property history.
How do you fix a stage without sending the wrong email or ad?
List every writer first: lifecycle automation settings, forms, workflows, imports, integrations and people. A correct manual fix gets overwritten by the next sync if the integration still sends the wrong value.
Then check what reacts to the change. A stage correction can enroll a producer in a workflow, change a segment, and send a fresh conversion to Google Ads, because HubSpot counts only lifecycle stage changes made after the conversion event was created. So a repair to an old record can send Google a new, false conversion. Ad conversion events.
Know how backward moves work. Imports, forms and workflows only move a stage forward unless the value is cleared first; a manual edit can move it back in one step. A manual backward move clears the legacy "Became a" date for the higher stage, so record the dates your reports use before you change anything. The newer latest-time and cumulative-time properties keep their values, and they need Professional or Enterprise. Use lifecycle stages.
Fix one record, check it again after the next sync, then do the batch. Keep the list of approved record IDs apart from the saved view, because the view's members change as you edit.
Who owns the stages after the cleanup?
Name one person who owns lifecycle and property changes, and one backup. After any change to a form, workflow, import or integration, they rerun the checks above on one record before the change reaches the rest.
FAQs
Is an appointed agent a Customer?
It's your call, and it's the first decision to make. We count an agent appointed for at least one program as a Customer, and producer status tracks whether they've written business. The alternative is to wait for the first bound policy. Whichever you choose becomes the top of your producer funnel.
Can a lifecycle stage move backward?
Not on its own. Automatic updates only move forward. A person can move a stage back with a manual edit; imports, forms and workflows need the value cleared first.
Do we need the Lead object?
No. It needs Sales Hub Professional or Enterprise. Lifecycle stage, producer status and lead status cover an MGA's producer journey without it.
