Dual Property and Casualty and Benefits Pipeline
How an agency ran two Blueprints in one Zoho CRM, separating B2B Property and Casualty from B2C Employer Benefits with distinct stages, required fields, and renewal logic.
Client details generalized to protect confidentiality.
Agencies writing two lines of business with genuinely different sales processes, currently forcing both through one pipeline.
The Challenge
One pipeline served both sides of the agency. Property and Casualty ran a B2B process with quotes, carrier submissions, and a bind decision. Employer Benefits ran a B2C enrollment process with entirely different stages and timelines. Sharing stages meant both sides worked around names that did not fit, mandatory fields were set to whatever both could satisfy, and pipeline reporting mixed two unrelated processes into one number.
The Solution
Separate Blueprints per Line
Each line of business gets its own Blueprint with stages named for how that business actually works.
- Two Blueprints on the same module
- Layout rules by record type
- Stage names specific to each line
- Transition permissions per team
Line-Specific Mandatory Fields
Required information is enforced per line, so neither side is asked for fields that do not apply to it.
- Mandatory fields set per transition
- Conditional layouts by line
- Validation at the transition, not on save
- Different document requirements per line
Quote to Enrolled Stage Logic
The benefits side runs quote through enrollment, and the P and C side runs quote through bind, each with its own downstream automation.
- Distinct stage sets per Blueprint
- Automated tasks per stage entry
- Stage-based notification rules
- Aging alerts tuned per line
Renewal Logic per Line
Renewals behave differently for each line, so renewal tasks and outreach follow the timeline that applies.
- Renewal date fields per policy type
- Scheduled function creating renewal records
- Outreach cadence by line
- Renewal pipeline separate from new business
Apps in This Solution
Zoho CRM
Under the Hood Technical detail
- Blueprint Architecture
- Two Blueprints run on the same module using record type to determine which applies, rather than splitting into two modules. Keeping one module preserved cross-sell visibility, which was the reason both lines were in one CRM to begin with.
- Layout Strategy
- Conditional layouts hide fields that do not apply to the active line. The alternative, one layout with every field from both processes, was what made the original single pipeline unusable.
- Renewal Handling
- Renewals create their own records rather than reopening the original policy record, so new business and renewal volume can be reported separately. Agencies that reopen the original lose the ability to say how much new business they actually wrote.
- Reporting Impact
- Pipeline reports now filter by line, which means conversion rate is meaningful. A blended conversion rate across a B2B bind process and a B2C enrollment process describes nothing.
- Notable Constraint
- Some clients buy both lines. The account relationship stays single while the deal records stay separate, so cross-sell is visible without merging two processes that should not share stages.
The Results
- Each line of business runs stages that match how it actually sells.
- Conversion reporting is meaningful because the two lines report separately.
- Renewal volume is distinguishable from new business.
One Pipeline Serving Two Businesses?
We have built multi-line Blueprint structures for agencies and brokers. Tell us how your lines of business differ.