Insurance & annuity agencies

You’re not short on leads. You’re losing the ones you paid for.

Most agencies think they have a lead problem. They have a plumbing problem. Leads land in four different inboxes, nobody owns the first response, and the text follow-up stopped delivering months ago without anyone being told.

01 / Diagnostic

Read this and tell me it isn’t your agency.

One lead, through a normal week, in an agency where nothing is wired together. Every step below is somebody doing their job correctly. The lead is lost anyway.

  1. Thu 7:40pmLead submits a form. It emails the office inbox.
  2. Thu 7:40pmNobody is in the office.
  3. Fri 10:15amReceptionist sees it, forwards it to a producer.
  4. Fri 2:30pmProducer texts. The text does not deliver. Nobody knows.
  5. Fri 2:31pmProducer calls. No answer. Leaves a voicemail.
  6. MonProducer means to follow up. Doesn’t.
  7. NeverThe lead bought from the agency that called at 7:41pm Thursday.
A typical week, not a worst caseIllustrative · no client data is shown
Intake
Current state

Forms, calls, chats, DMs, and three lead vendors land in four different places. Nobody owns the first response.

Fixed

One pipeline, every source.

Delivery
Current state

A2P registration was rejected or never completed, so carriers silently drop the texts. The agency reads it as leads ignoring them.

Fixed

Registered, verified, delivering.

Follow-up
Current state

Depends on a producer remembering. Two attempts, then it stops.

Fixed

Sequenced, not remembered.

Visibility
Current state

Lead spend in one place, issued policies in another, and the join is a spreadsheet somebody updates on Fridays.

Fixed

Cost per issued policy, by source.

02 / Delivery

Why your texts stopped landing.

Since February 2025, AT&T, T-Mobile, and Verizon block unregistered application-to-person SMS on 10-digit numbers. Not throttled. Not delayed. Dropped. Registration runs through The Campaign Registry, and rejection is common. Three causes account for most of it.

01

EIN mismatch

The agency operates as “Smith Insurance Group” but the EIN is registered to “Smith Insurance Group LLC.” That alone kills the registration and resets the clock.

02

Campaign description too vague

“Customer notifications” and “appointment updates” get rejected. Carriers want the audience, the trigger, and the content named specifically.

03

Opt-in that can’t be verified

Carriers now require a live, publicly reachable URL showing the opt-in flow. Screenshots no longer clear it. A parked domain or a broken form page is an automatic flag.

A2P registration checkcarriers: all

$ strygon a2p --check --carriers all

Brand registration status and vetting score

Campaign use case against carrier acceptance criteria

Legal entity and EIN match against the registered record

Opt-in URL reachable, live, and showing the consent flow

Test message delivery on AT&T, T-Mobile, and Verizon

Carrier requirements, not Strygon policyVerify against current carrier documentation

03 / Scope

One system, eight things it does.

Not eight products. One system with eight jobs, built in the order that stops the bleeding first.

01

One front door

Every lead source wired into a single pipeline. Website forms stop emailing the office. Lead vendors connect by webhook so leads arrive in seconds.

02

A phone number that works

A2P 10DLC brand and campaign registration done correctly, entity records reconciled, and a real opt-in page carriers can verify.

03

First touch in under 60 seconds

A lead arrives and the system texts them, notifies the assigned producer, and books the task. Enforced by the build, not reported after the fact.

04

Routing that isn’t a single list

Annuity inquiries to the producer who writes annuities. Unlicensed states flagged instead of sitting. Reassignment when the first producer doesn’t respond.

05

Follow-up that doesn’t rely on memory

A sequenced cadence across 14 days, then long-term nurture. The next action is always in front of the producer.

06

Renewals and cross-sell

Sequences at 90, 60, and 30 days out. Second-policy and annuity conversations triggered by what the client already owns. This is revenue already sitting in the database.

07

A number the owner reads

Leads by source, time to first touch by producer, appointments, issued policies, cost per issued policy. One dashboard, weekly readout.

08

Consent records that survive a subpoena

Consent captured at every intake point and stored where it can be retrieved. Opt-outs synchronized across every channel. Internal DNC handling. State retention rules flagged where the agency writes business.

04 / Start

Two ways to start. Both priced here.

One proves the delivery problem and fixes it. The other installs the whole system. Most agencies should start with the first.

015 business days

A2P Rescue

$500

Find out why your texts stopped delivering, and fix it.

What the number covers

  • Audit of current brand and campaign registration status
  • Legal entity and EIN reconciliation
  • Campaign use-case descriptions rewritten to carrier-acceptable specificity
  • A live, compliant opt-in page built or repaired
  • Resubmission through The Campaign Registry
  • Delivery tested on all three major carriers before signoff
  • A one-page written summary of what was broken and what changed
0215 business days

Agency Revenue Infrastructure

$5,000

Everything in section 04, installed as one system.

What the number covers

  • All eight components above, built and wired as a single system
  • Integration with the existing agency management system where an API exists (AgencyBloc, HawkSoft, EZLynx and similar)
  • Two weeks of post-launch fixes
Deposit50%To start, balance at launchHalf up front, half when it goes live. There is no third invoice between them.
TimelineDay 0Is the day the deposit clearsCounted in business days from there, not from the first conversation.
OwnershipAgencyHolds every account and recordNumbers, registrations, lists, and consent records are the agency’s from day one, and stay with it if the engagement ends.
ScopeWrittenBefore anything is builtIt does not change without a new number. That protects the timeline as much as the price.
Terms of the engagementCheckable against the scope document

usestandby + done-for-you CRM + attribution

Three parts that only pay off as one loop.

Strygon owns usestandby, a sales-training product built for this market. On its own it makes a producer sharper. Wired into the CRM that routes the lead and the attribution that reports what the lead cost and whether it wrote, it stops being a training tool and becomes a feedback loop.

Each part is useful alone. Joined, the reporting tells the training what to work on, and that is the part an agency cannot assemble out of three separate vendors.

Built and operated by Strygon, not resold

05 / IMOs & FMOs

For IMOs and FMOs.

Your agents ask you for tech help you aren’t set up to give.

Downline agents come to the IMO when their CRM is broken, their texts stop delivering, or their follow-up falls apart. That’s a support cost with no good answer. The same infrastructure below can be built for the IMO’s own operation, or offered to agents as a standing benefit with the delivery handled here.

01

Internal build

The IMO’s own recruiting pipeline, agent onboarding automation, downline visibility, and sub-account provisioning at scale. Scoped per organization.

02

Agent benefit

A fixed-price package the IMO can point agents at. Delivery handled here, no support load on the IMO.

03

A conversation first

No proposal before understanding what agents are actually asking for.

06 / Limits

What this is not.

Being specific about the limits is part of the engagement.

Strygon builds infrastructure. The agency owns the numbers, the registration, the lists, and every consent record.

No consumer insurance leads are bought, sold, or brokered.

Nothing is ever sent from a Strygon-controlled number to an agency’s list.

No advice is given on policy suitability, carrier selection, or anything inside state insurance department advertising review.

Compliance architecture is engineering work, not legal advice. Consent language should be cleared by the agency’s own counsel.

07 / Contact

Start with what’s broken.

Send the situation in a paragraph. What broke, and where it shows up. A read comes back on what’s likely wrong and what fixing it takes.

 

The system, part by part

What gets built here, and why.

Every part of the architecture, aimed at what actually breaks in insurance agencies & agents. The build is scoped from these, not from a package.

The parts that matter most hereThe architecture does not change between them