Insurance · Acquisition

Lead buying and acquisition for insurance agencies

Lead vendors report cost per lead because it is the number they control. The agency gets paid on written policy, which lands weeks later and often under a different producer's name. Until those two ends are joined inside one system, vendor selection is being decided by whoever sends the tidiest invoice.

Start a buildIndustry overview
06Paid search & social · Landing pages
Acquisition06
Paid search & socialLanding pagesAttribution
InsuranceIllustrative

Acquisition

Paid, local presence, landing pages, and attribution.

Acquisition · InsuranceOne pairing of the matrix
Service
Acquisition
Industry
Insurance agencies & agents
Covers
Life & final expense · Medicare & health · P&C agencies · Producer teams
Architecture
Unchanged from every other vertical — only the breaks differ
Engagement
A defined build, or run under management

What usually breaks

Before anything gets built.

The same failures recur across insurance agencies & agents. Strygon maps the specific system before proposing anything, but these are the ones worth checking for.

Bought, then aged

A purchased lead is worth most in the first minute and close to nothing the next day. Most sit in a shared inbox until a producer works down to them.

Unready producers

Objection handling gets learned live, on leads the agency already paid for. A rep who is not ready yet costs policies rather than training hours.

Source blindness

Spend goes to three vendors, policies get written, and nothing joins the two. The lag makes guessing feel reasonable.

Recurring in insuranceObserved pattern · the specific system still gets mapped

The approach

What Strygon does about it.

Acquisition, aimed at those failures specifically rather than at a generic checklist.

01Acquisition
Every vendor posts into one pipelineAcquisition
01
Part of the scoped build

Every vendor posts into one pipeline

Vendor feeds, forms, and inbound calls arrive on a single record shape. That is the precondition for comparing them at all, and it is usually missing.

02Acquisition
Judged on written, not on deliveredAcquisition
02
Part of the scoped build

Judged on written, not on delivered

Vendor reporting runs on policies written per hundred leads bought rather than on the vendor's own count of what it delivered.

03Acquisition
Producer performance split from source qualityAcquisition
03
Part of the scoped build

Producer performance split from source quality

One report separates who worked the lead from where it came from, so a weak vendor and an unready producer stop looking like the same problem.

04Acquisition
Budget moves on the joinAcquisition
04
Part of the scoped build

Budget moves on the join

Spend shifts toward sources that produce placed business, which is a decision the agency can only make once the join between cost and outcome exists.

The approach for this pairingScoped in writing before work starts

What gets built

Concrete deliverables.

Everything in acquisition, applied to how insurance agencies & agents actually runs.

All of acquisitionIndustry overview
Paid search and paid social
Local presence and profile management
Landing pages and conversion tracking
Reporting that joins campaign activity to the pages and queries it landed on
Attribution that survives contact with reality
In scopeScoped in writing before work starts

Also for this industry

Other parts of the same system.

CRM & automation
CRM & automation03
Pipeline architectureSpeed-to-lead
Applied hereIllustrative

CRM & automation infrastructure

A purchased lead is an asset with an expiry date. Routing has to treat the clock as the product, and hand the lead to a producer who can actually write it.

Read the crm & automation read
Local & private AI
Local & private AI01
Self-hosted inferenceRetrieval on private data
Applied hereIllustrative

Local & private AI models

Applications carry dates of birth, health answers, and identifiers. That is exactly the material a general-purpose AI API should never be handed.

Read the local & private ai read
Custom software
Custom software02
Internal toolsData pipelines
Applied hereIllustrative

Custom software

Commission, chargebacks, and persistency live in five carrier portals and a spreadsheet. Nobody can say what a producer is actually worth.

Read the custom software read

Start

Start with what’s broken.

Send the situation in a paragraph. Strygon comes back with a read on what’s likely wrong and what it would take to fix, before anyone talks about price.

Most builds start withleads dying in an inbox., three half-finished pipelines., follow-up nobody owns., numbers that never agree., four vendors blaming each other.

Or email hello@strygon.com

What to send
A paragraph. What broke, and where it shows up.
What comes back
A read on what is likely wrong and what fixing it takes.
Price
The last conversation, not the first