Campaign Brief: Insurance Broker Lead Intake Automation (100M Segment)

Service line: Insurance workflow automation (Brainforge + Contextual) — automate new lead intakes for commercial brokerages (full day → minutes)
Target segment: 100M revenue brokerages with complex risks (surety, construction, captives)
Gate date: [Set 2 weeks from launch] YYYY-MM-DD
Brief owner: [TBD]
Last updated: 2026-02-04

Use this brief to run the campaign and to score it against the Campaign Launch Checklist at the gate. Keep the checklist section updated so go/no-go is obvious.


To complete (from intake)

  • Gate date — Set 2-week gate date.
  • Brief owner — Who owns this brief and gate decision?
  • Target list — ✅ POPULATED — 15 accounts from research report (see §4: Target account list). Criteria: commercial insurance brokerages, 100M revenue, complex risks (surety, construction, captives), documented operational pain.
  • Named account research — ✅ COMPLETE — Top 5 targets (Shepherd, Scott, Starkweather, Houchens, BMB) have custom outreach angles documented in §4.
  • CC content system for postsRobert GPT (specified).
  • Notion link — When content calendar exists, add link here.

1. Launch checklist progress (gate at 2 weeks)

Beta Test (must all be ✅ to advance)

  • v1.0 delivery plan created (link: ________)
  • 3 SOWs created and sent
  • 1 signed contract secured
  • Delivery started
  • 1 milestone reached

Market Ready (commit when we go)

  • Service posted on website
  • Lead gen underway (this campaign)
  • Supporting content calendar in execution (§5 below)
  • Partners updated (Contextual, etc.)
  • 5 customers attracted to a meeting

SOW & meeting tracking

#Company / contactSOW sentSignedMeeting bookedNotes
1
2
3

Target: 3 SOWs sent, 1 signed, 5 total prospects to a meeting.

Note: 100M firms have longer sales cycles than smaller agencies. They have failed automation attempts (cautious), procurement processes, and complex stakeholder alignment. Expect 4–6 week sales cycles vs 2-week for smaller firms. Gate criteria remain but acknowledge velocity will be slower.

Gate decision (at gate date): No-go until all Beta Test boxes above are ✅. Then: Go if Market Ready is achievable; Conditional go if Beta met but Market Ready actions need a follow-up date. See §7 for final call.


2. Positioning & hypothesis

Value Proposition:
“Best in the world at solving [manual lead intake that takes a full day] for [mid-market commercial brokerages (100M)] using [task-specific, cited automation trained only on your data ingestion workflow — not generic LLMs that hallucinate].”

  • Problem: New lead intakes take a full day for a commercial agent (document extraction, risk profiles, submission drafts). Messy, partial documentation; manual work is slow and error-prone. Generic LLMs and OCR have failed because they’re non-deterministic — brokerages tested them and rejected them due to hallucinations and reliability issues.
  • Customer (title / segment):
    • Decision-makers: Head of Operations, COO, CFO, Managing Partner, Head of Surety, Enterprise Architect, SVP Operations
    • Hiring managers: Those hiring for Underwriting Assistants, Intake Coordinators, Processing Specialists, Placement Specialists (signal of operational bloat)
    • Segment: 100M revenue brokerages handling complex risks (surety, construction, captives). “Too large for main-street workflows, too small for enterprise platforms.”
  • Solution (service name / approach): Brainforge + Contextual — cited, auditable, task-specific automation. Not a general LLM. Trained only on your data ingestion workflow. Every extraction has explicit source citations (page, section, timestamp). Zero-to-one lead qualification: cited risk profiles, submission-ready drafts, gap identification. Works with partial docs; integrates with existing CMS.

One-line test hypothesis:
Ops leaders and hiring managers at 100M brokerages will take a meeting when they see that: (1) we know generic LLMs failed them, and (2) our cited, task-specific solution solves the intake bottleneck without the reliability issues.

Competitive differentiation (vs failed LLM pilots):

  • Not general AI trained on everything → Task-specific, trained only on your workflow
  • Not non-deterministic → Cited, auditable outputs with source verification
  • Not a black box → Every data point traced to page/section/timestamp
  • Not a replacement → Sits upstream of your CMS/AMS; augments your team

One-pager / narrative: Design-ready 2-pager copy (ready for design; required for Market Test).
Pricing: 50K/month for 100M segment. Pilot pricing available for first 3 customers who help us build out the service. ROI math: At 75/hr fully-loaded cost = $15K/month wasted on manual work. Solution pays for itself in time savings alone, before accounting for faster close rates and competitive advantage.


3. Campaign overview

What we’re testing:
Whether ops leaders and hiring managers at 100M brokerages respond to positioning around: (1) “We know generic LLMs failed you” (acknowledge Shepherd’s public rejection of RAG/LLMs), (2) Cited, task-specific automation (not general AI), (3) Quantified pain (Scott’s 20-hour WIP reports, Starkweather’s “spreadsheets and PDFs” quote), and (4) Pilot pricing for early adopters.

Target audience:

  • Primary: Head of Operations, COO, CFO, Managing Partner, Head of Surety/Construction, Enterprise Architect, SVP Operations
  • Secondary: Hiring managers actively recruiting for “Underwriting Assistant,” “Intake Coordinator,” “Processing Specialist,” “Placement Specialist” (hiring = operational bloat signal)
  • Segment: 100M revenue, complex risks (surety, construction, captives), documented operational pain (failed automation, manual processes, “spreadsheet fatigue”)

Strategy:
Hybrid approach — Top 5 named accounts (Shepherd, Scott, Starkweather, Houchens, BMB) get custom 1:1 outreach referencing their specific documented pain. Remaining 10 accounts get templated HeyReach sequence informed by research (connection → follow-up 5–7 days → qualification → demo). Multi-thread where possible: reach out to both decision-makers AND hiring managers at the same firm.


4. Execution: Outreach & leadgen

Execution stack

LayerToolRole
EnrichmentClay + HeyReachList building, account + contact data (LinkedIn URL, company, headcount, revenue).
LinkedInHeyReachConnection requests, DMs, sequences. Import list (CSV); run sequence from Message Library.
CRMHubSpotLog outcomes, pipeline.
Email(optional)Instantly or other if adding email steps.

This brief is the source of truth for the sequence. GTM lead uploads the list and creates the campaign in HeyReach. Top 5 accounts (Shepherd, Scott, Starkweather, Houchens, BMB) receive custom 1:1 outreach (see Named Account Outreach Angles below). Remaining accounts use templated sequence.

Target account list (15 accounts from research)

Populated from research report. These are 100M revenue brokerages with documented operational pain (failed automation, manual workflows, hiring for assistants). Ranked by strategic priority.

PriorityCompanyRevenue (Est.)HeadquartersPrimary Pain SignalCustom Angle?
1Shepherd Insurance~$74MCarmel, INFailed LLM/RAG pilot; “non-deterministic,” “unreliable”; manual underwriting “laborious and painful”✅ Custom
2Scott Insurance~99MLynchburg, VA20-hour WIP reports; manual file shuffling; hiring Intake Coordinators✅ Custom
3Starkweather & Shepley~91MEast Providence, RISVP quote: “not having to deal with all these spreadsheets and PDFs”; hiring armies of Assistants✅ Custom
4Houchens Insurance Group~$72MBowling Green, KYFailed direct bill automation; COBRA Processor hiring (rules-based task done manually)✅ Custom
5Bowen, Miclette & Britt~86MHouston, TXManual “assembly line” (Processor → Specialist → online quote gen); construction/energy/surety✅ Custom
6Marshall & Sterling~$87MPoughkeepsie, NYPublic entity / manufacturing; mid-market scaleTemplate
7Sterling Seacrest Pritchard~$86MAtlanta, GAConstruction / healthcare; regional powerhouseTemplate
8Premier Group Insurance~$85MGreenwood Village, COCommercial / personal lines mixTemplate
9Oakbridge Insurance~$78MLaGrange, GAAgribusiness / municipal (complex, non-standard risks)Template
10Lawley Insurance~$74MBuffalo, NYConstruction / benefits; multi-officeTemplate
11Robertson Ryan Insurance~$71MMilwaukee, WITransportation / manufacturingTemplate
12Towne Insurance~$90MNorfolk, VABank-owned / general commercialTemplate
13Christensen Group~100MEden Prairie, MNController quote: “crippling cycle of manual data entry”; ePayPolicy partner (proven tech buyer)Template
14The Mahoney Group~70MMesa, AZBrokerTech Ventures member (actively shopping for tech); “connectivity” pain pointTemplate
15Turner Surety & Brokerage~$51MSaddle Brook, NJSurety specialist (like Scott — WIP bottleneck likely)Template

Sources: Research report triangulated from financial data, hiring patterns (LinkedIn), and leadership commentary (public statements, case studies, employee reviews).

ICP titles

Primary decision-makers:

  • Head of Operations / SVP Operations
  • COO
  • CFO (for ROI-driven, surety/financial workflows)
  • Managing Partner
  • Head of Surety / Head of Construction
  • Enterprise Architect / CTO (for firms attempting digital transformation)
  • Underwriting leads / Director of Underwriting

Secondary (hiring managers = operational bloat signal):

  • Anyone actively hiring for: “Underwriting Assistant,” “Intake Coordinator,” “Processing Specialist,” “Placement Specialist,” “COBRA Processor,” “Production Underwriting Assistant”
  • Strategy: Multi-thread — reach out to both the decision-maker AND the hiring manager at the same firm. Hiring manager confirms the pain; decision-maker has budget authority.

Named account outreach angles (Top 5 — Custom 1:1)

These 5 accounts have documented, specific pain points from the research report. Use custom outreach that references their exact situation. Do NOT use generic templates.


1. SHEPHERD INSURANCE (~$74M, Carmel, IN)

Pain: Publicly documented failed LLM/RAG pilot. They tested AI and rejected it because outputs were “non-deterministic” and “unreliable.” Manual underwriting is “laborious and painful.” 4-day submission-to-proposal lag.

Target personas:

  • Head of Operations / COO
  • Hiring manager for “Personal Lines Account Manager” roles (multiple listings)

Custom angle:

  • Hook: “I saw your team tested LLMs for underwriting intake and hit the reliability wall. We built what you were looking for.”
  • Differentiation: “Not a general LLM. Task-specific, trained only on your intake workflow. Every extraction is cited (page, section) — no hallucinations, no guessing.”
  • ROI: “Your 4-day lag on 50+ leads/month = 200 hours/month of manual work. We turn that into 20 hours.”
  • Proof: Reference their own documentation of the failure; offer to show the deterministic IDP approach that solves it.

Message framework:

  • Opening: Acknowledge the failed pilot (show you did research)
  • Problem: “You rejected LLMs for the right reason — reliability”
  • Solution: “We’re the cited, task-specific alternative”
  • Ask: “15-minute demo — show you how we solve the exact problem your pilot couldn’t”

2. SCOTT INSURANCE (~99M, Lynchburg, VA)

Pain: 20-hour WIP reports for surety clients. “Highly manual process.” Manual file shuffling in benefits (“losing documents”).

Target personas:

  • VP of Surety / Head of Surety
  • CFO (financial data spreading is their domain)
  • Hiring manager for “Intake Coordinator” and “Production Underwriting Assistant”

Custom angle:

  • Hook: “Your VP mentioned WIP reports take 20 hours. That’s half an FTE per month on one task.”
  • ROI: “50 contractors × 20 hours each = 1,000 hours/year = $75K/year in labor. We turn 20 hours into 20 minutes.”
  • Solution: “Automated financial data spreading. Ingest QuickBooks export or Excel WIP schedule → auto-map to surety format → cited output.”
  • Proof: “Show you the workflow with a sample contractor WIP.”

Message framework:

  • Opening: “Saw your team is hiring Intake Coordinators — and I understand why. Your surety WIP workflow is eating 20 hours per report.”
  • Problem: “At 50 clients, that’s 1,000 hours/year just on report generation.”
  • Solution: “We automate the financial data spreading — 20 hours → 20 minutes.”
  • Ask: “Can I show you the WIP workflow with a sample contractor? 15 minutes.”

3. STARKWEATHER & SHEPLEY (~91M, East Providence, RI)

Pain: SVP quote: “If I could change one thing, it would be not having to deal with all these spreadsheets and PDFs.” Hiring armies of Assistants. Hiring an Enterprise Architect (trying to build data foundation while drowning in manual work).

Target personas:

  • SVP Operations (the person who gave the quote)
  • Enterprise Architect (they need tools, not just strategy)
  • Hiring manager for “Commercial Underwriting Assistant,” “Personal Lines Assistant Account Manager”

Custom angle:

  • Hook: “Your SVP said they want to stop ‘dealing with all these spreadsheets and PDFs.’ We turn those spreadsheets into the data foundation your Enterprise Architect needs.”
  • Problem: “You’re hiring an Architect to build a modern data layer, but your team is still buried in static files. The Architect needs structured inputs, not more Excel.”
  • Solution: “We sit upstream. Ingest the spreadsheets/PDFs → structure them into your data warehouse → cited, auditable.”
  • Proof: “Show you how we turn a messy schedule of locations (Excel) into structured risk data.”

Message framework:

  • Opening: “Saw you’re hiring an Enterprise Architect and multiple Underwriting Assistants at the same time. Classic scaling paradox.”
  • Problem: “Your SVP wants to stop dealing with spreadsheets. Your Architect needs structured data. Your assistants are the human middleware in between.”
  • Solution: “We automate the spreadsheet-to-structure step — so your Architect has the inputs they need and your assistants can focus on exceptions.”
  • Ask: “15-minute demo — show you the ingestion layer that feeds your data transformation.”

4. HOUCHENS INSURANCE GROUP (~$72M, Bowling Green, KY)

Pain: Failed direct bill automation (“falls short” due to “complexity of direct bill statements”). Hiring COBRA Processors (rules-based task done manually). 12 offices in 5 states (integration nightmare).

Target personas:

  • Head of Operations / COO
  • Sarah Walden, Senior Application Technician (manages software across 12 offices)
  • Hiring manager for “COBRA Processor” and “Personal Lines Client Associate”

Custom angle:

  • Hook: “I saw your first automation attempt (direct bill reconciliation) failed due to statement complexity. We specialize in parsing complex, non-standard carrier docs.”
  • Problem: “Commission reconciliation across 12 offices, 5 states, multiple carrier formats = integration hell. Manual processing doesn’t scale.”
  • Solution: “AI-powered commission reconciliation. Parses the ‘complex statements’ your last vendor couldn’t handle. Cited outputs.”
  • Secondary: “Also saw you’re hiring COBRA Processors. COBRA is rules-based — perfect for automation. We can handle that too.”

Message framework:

  • Opening: “Saw your direct bill automation failed due to statement complexity — and now you’re back to manual processing across 12 offices.”
  • Problem: “Post-placement reconciliation (commission, COBRA) is eating resources. Manual doesn’t scale when you’re managing 5 states.”
  • Solution: “We handle the ‘complex statements’ problem with cited extraction. Plus COBRA automation (rules-based, perfect fit).”
  • Ask: “Show you how we parse a messy carrier statement. 15 minutes.”

5. BOWEN, MICLETTE & BRITT (~86M, Houston, TX)

Pain: Manual “assembly line” workflow: Processor opens email → hands to Placement Specialist → Specialist types data into carrier websites (“generate quotes online”) → forwards for review. Heavy construction/energy/surety (paper-heavy industries).

Target personas:

  • Head of Operations / COO
  • Hiring manager for “Commercial Insurance Placement Specialist”

Custom angle:

  • Hook: “Your Placement Specialists are manually typing data into carrier websites to generate quotes. That’s a $75K/year human doing a bot’s job.”
  • Problem: “Processor → Specialist → online quote gen = two manual handoffs, double the labor cost, double the error risk.”
  • Solution: “API-first submission automation. Data from intake → pushed to carriers automatically. Your Specialists focus on negotiation, not data entry.”
  • Proof: “Show you the API workflow: one click to push a submission to 5 carriers simultaneously.”

Message framework:

  • Opening: “Saw you’re hiring Placement Specialists. I understand why — your workflow has two manual handoffs before a quote even gets generated.”
  • Problem: “Processor distributes → Specialist types into carrier websites → forwards for review. That’s an assembly line built on human middleware.”
  • Solution: “We eliminate the manual ‘online quote generation’ step. API push to multiple carriers simultaneously.”
  • Ask: “15-minute demo — show you the submission workflow with a sample construction risk.”

Automated vs human-in-the-loop

WhatWhoNotes
First message + follow-upsAutomatedOnce list and sequence are in HeyReach, connection request and follow-up (5–7 days) send per Sequence definition. Human selects which option per step when building the sequence.
ROI/qualification, demo pitch, thank youHuman or sequencedOptionally add as later steps in HeyReach; or handle in reply when they respond.
Intro ask (mutuals)HumanIf using mutual path, Slack approval before asking for intro.

Order of operations & rules

StepWhenOptionsSelection logic
I. ConnectionFirst touchOption 1 (mutual + industry), 2 (pain point), 3 (growth)Mutual + title → 1. No mutual + pain → 2. Growth signals → 3.
II. Follow-up5–7 biz days after connectionOption 1 (time/volume), 2 (competitive/quality), 3 (ROI)Standard → 1. Competitive/quality → 2. Larger, ROI-focused → 3.
III. ROI & qualificationWhen they respond interestedOption 1 (qualification questions), 2 (address objection)Interested → 1. Objection → 2.
IV. Case study & demoAfter qualificationOption 1 (problem–solution), 2 (ROI pitch), 3 (pilot)Standard → 1. ROI-driven → 2. Hesitant → 3.
V. Thank youWhen conversation endsOption 1 (door open), 2 (resource), 3 (referral)Decline → 1. Not ready → 2. Good rapport → 3.

Full options, placeholders, and ROI math: Message template.

Sequence definition (for upload to HeyReach)

Build this sequence in HeyReach. Human selects which message option per step when creating the campaign.

StepChannelActionMessage templateDelay
1LinkedInSend connection requestI. Connection (Option 1, 2, or 3 by profile)
2LinkedInIf connected → send messageII. Follow-up (Option 1, 2, or 3)5–7 business days
3+(optional)If they reply → sendIII. ROI/Qualification or IV. DemoOn reply

Add more steps if you add III/IV/V as sequenced steps.

Message library

Source: insurance-broker-lead-intake.md

All connection, follow-up, ROI/qualification, case study/demo, and thank-you options with placeholders and selection logic live in that file. Reference it when building the HeyReach campaign; paste the chosen option per step into the tool.

Outreach checklist (per prospect)

  • Confirm ICP fit (role, brokerage, size, volume)
  • Check mutual count
  • Identify top mutuals / Slack approval if needed (human)
  • List uploaded; sequence live (first message + follow-up automated)
  • Outcome logged (HubSpot)

5. Execution: Content (supporting calendar)

Content supports credibility (demos, proof). Post drafts, if used, go through the CC content system (user specifies Robert GPT or Uttam GPT).

Goal: Support outreach with proof: zero-to-one intake and gap analysis demos. Use demo summaries and links in conversations; optional content calendar (problem → solution → service) for LinkedIn/Notion.

Pillars & sequence:

  • Core content (6 posts): Problem (2) → Solution (2) → Service (2) — foundational positioning
  • Niche pain-point content (4 posts): Target specific documented pain from research (LLM failure, WIP bottleneck, spreadsheet chaos, hiring bloat)
  • Total: 10 posts over 3–4 weeks

Content lives in: [Add link to Notion content calendar when created.]

CC content system for drafting: Robert GPT — use content/cc-content-system/robert-gpt/memory/examples/linkedin/FORMAT_INDEX.md and memory/patterns/linkedin-patterns.md when turning these outlines into full Post + Carousel.


Content sequence outlines (Robert GPT formats)

Each outline is ready for full draft via Robert GPT. Structure pattern names refer to memory/patterns/linkedin-patterns.md.


POST 1 — Why intake takes a full day (and it’s not your team’s fault)

Pillar: Problem
Robert GPT format: Thought Leadership - Diagnostic (Blame Shift + Reveal). Structure: Diagnostic List Format. Example reference: 2026-01-attribution-invisible-touchpoints.md.

FACTS / EVIDENCE:

  • Cold leads arrive with messy documentation (policies, certificates, agreements, transcripts); no standard format.
  • Manual extraction of risk categories, coverage details, and exposures takes 2–3 hours per lead; then drafting submission emails from scratch.
  • Partial information is the norm — you don’t know what’s missing until you’ve already invested time; manual extraction is error-prone.
  • Competitors moving faster compound the pressure.

IMPLICATIONS:

  • Full day per intake per agent; at 50+ leads/month, hundreds of hours lost.
  • Teams blamed for “being slow” when the real issue is upstream (document chaos, no structure).
  • This isn’t a people problem. It’s a data-and-process problem.

CTA: If this sounds familiar, you’re not alone. Want to see how brokerages are cutting intake from hours to minutes? DM us.


POST 2 — Adding headcount doesn’t fix lead intake

Pillar: Problem
Robert GPT format: Thought Leadership - Problem → Common Fix → Better Fix. Structure: Problem → Common Fix → Better Fix. Example reference: 2026-01-edge-layer-does-doesnt.md.

FACTS / EVIDENCE:

  • Common fixes: hire more underwriters, buy another tool, “better intake forms,” outsource to offshore.
  • None address the root cause: turning messy, partial docs into structured risk profiles and submission-ready drafts at the source.
  • More people = same manual process at larger scale; tools that don’t read and cite the actual documents add another layer, not a fix.
  • The bottleneck is zero-to-one: from cold lead to first credible, cited output.

IMPLICATIONS:

  • Brokerages spend thousands of hours and dollars every year on a process that could be automated at the point of ingestion.
  • Scaling by adding headcount scales cost and delay, not throughput per dollar.
  • Fix has to happen before the damage — at capture and extraction, not downstream.

CTA: If you’re scaling intake by adding people, DM us. We’ll walk you through the math.


POST 3 — From messy docs to cited risk profiles in minutes

Pillar: Solution
Robert GPT format: Thought Leadership - Silo-to-Signal Structure. Structure: Silo-to-Signal Structure. Example reference: 2026-01-identify-unattributed-revenue.md.

FACTS / EVIDENCE:

  • Each document type (policy, certificate, agreement, transcript) lives in its own “silo”; brokers manually cross-reference and reconcile.
  • AI can run in parallel with your existing workflow: ingest the same messy docs, extract structured risk and coverage profiles with explicit source citations (page, section, timestamp).
  • Output: submission-ready email drafts grounded in actual documentation; clear flagging of gaps and missing information.
  • Works with partial documentation — doesn’t require complete info to surface insights.

IMPLICATIONS:

  • Zero-to-one shifts from hours to minutes; same team can process 2–3x more leads.
  • Citations build trust (carriers, clients) and auditability; no black box.
  • Downstream tools (CMS, CRM) stay; automation sits upstream.

CTA: That’s the problem. Here’s how we solve it. DM us for a 15-minute demo.


POST 4 — You don’t have to choose between speed and quality

Pillar: Solution
Robert GPT format: Thought Leadership - Sequence Flip Narrative. Structure: Sequence Flip Narrative. Example reference: 2026-01-edge-privacy-tradeoff.md.

FACTS / EVIDENCE:

  • Old trade-off: move fast (guess, template) or be thorough (slow, manual). Teams split the difference and still lose.
  • “Who told you it was a law of physics?” — The trade-off was a limitation of how intake was done, not an inevitability.
  • When extraction and drafting are automated with citations, you get both: speed (minutes per lead) and quality (every claim tied to a source).
  • Brokers stay in the loop: review, edit, approve — but the heavy lifting is done.

IMPLICATIONS:

  • Faster time-to-submission and higher close rates; no sacrifice on accuracy or compliance.
  • Relationship-building (trust, advice) becomes the focus instead of data entry.

CTA: The trade-off was real. It just isn’t anymore. DM us to see how.


POST 5 — What we actually do: zero-to-one lead intake

Pillar: Service
Robert GPT format: B2B Services - Framework Teaching. Structure: Clear stages; what we do / don’t do. Example reference: b2b-services-stage-framework.md, 2026-01-edge-layer-does-doesnt.md (what we do and don’t).

FACTS / EVIDENCE:

  • We don’t replace your CMS or your people. We automate the zero-to-one: cold lead + messy docs → cited risk profile + submission-ready draft.
  • Brainforge + Contextual: extract risk categories and coverage details with explicit citations; generate email drafts grounded in the actual documents; identify gaps.
  • Works with partial info (certificate + transcript only, etc.); integrates with Google Drive, Box, SharePoint, your CMS.
  • Demo 1 (zero-to-one) and Demo 2 (gap analysis) show the workflow; transcripts in campaign brief.

IMPLICATIONS:

  • Brokerages save thousands of hours and dollars; focus on relationships and placement, not manual extraction.
  • Pilot-friendly: 5–10 leads to prove value, then scale.

CTA: Want to see it with a sample lead? DM us for a quick demo.


POST 6 — Give value before you ask for business: gap coverage analysis

Pillar: Service
Robert GPT format: Thought Leadership - Organizational Insight. Structure: Direct Claim Hook + insight. Example reference: 2026-01-data-truth-alignment.md.

FACTS / EVIDENCE:

  • Gap coverage analysis = understand current and future operations vs coverage; identify where policy language leaves the client exposed; cite exact policy references and impact.
  • Run as a free, no-obligation risk review as part of intake — shifts the conversation from “selling” to “here’s what we noticed; here’s the value if we work together.”
  • Builds trust and credibility before asking for business; brokers deliver real value with minimal manual work (AI does the heavy lifting, citations keep it credible).
  • Output: recommended actions, executive summary, draft email for client or carrier — actionable artifacts.

IMPLICATIONS:

  • Relationships built on value first; close rates and retention improve when the first touch is helpful, not pitchy.
  • Differentiator for brokerages competing on service, not just price.

CTA: If you want to lead with value, not pitch, DM us. We’ll show you how gap analysis fits into intake.


Niche pain-point content (Target-specific)

These posts target the specific documented pain points from the research. Use these to amplify outreach to Shepherd, Scott, Starkweather, Houchens, and similar firms.


POST 7 — Why your LLM pilot failed (and what actually works)

Pillar: Problem (Niche)
Target audience: Shepherd Insurance, firms that tested and rejected AI
Robert GPT format: Thought Leadership - Problem Diagnosis (Acknowledge Failed Attempt). Structure: Problem → Why It Failed → What Works Instead. Example reference: 2026-01-edge-layer-does-doesnt.md (what works vs what doesn’t).

FACTS / EVIDENCE:

  • Mid-market brokerages tested LLMs and RAG for intake automation; many rejected them due to “non-deterministic” outputs, hallucinations, unreliable table extraction.
  • Example: Shepherd Insurance publicly documented that LLMs “do not produce a reliable output every time” and the “hype has not lived up to expectations.”
  • The failure wasn’t your team’s fault. General LLMs are trained on everything (Wikipedia, Reddit, novels). They’re designed to be creative, not precise.
  • Insurance requires 100% accuracy on structured data (schedules of vehicles, locations, values). A model that “guesses” or “fills in the blank” is a liability risk.

IMPLICATIONS:

  • The AI hype cycle promised automation but delivered unreliable black boxes.
  • Brokerages were right to reject it — “close enough” doesn’t work when you’re liable for errors.
  • The problem isn’t AI itself; it’s general-purpose AI applied to precision tasks.

CTA: If you tested AI and it failed, you rejected it for the right reason. Want to see the task-specific alternative that works? DM us.


POST 8 — The 20-hour report that’s costing you $50,000 a year

Pillar: Problem (Niche)
Target audience: Scott Insurance, surety-focused brokerages
Robert GPT format: Thought Leadership - Cost Quantification. Structure: Quantified Pain Hook + Hidden Cost Reveal. Example reference: Use direct, data-driven hook.

FACTS / EVIDENCE:

  • Work-In-Progress (WIP) reports for surety clients: reconcile % completion, costs incurred, billings for every active project.
  • At some brokerages, generating a single WIP report takes up to 20 hours (documented example: Scott Insurance VP quote).
  • Math: 50 surety clients × 20 hours each = 1,000 hours/year. At 75,000/year on one manual task**.
  • The bottleneck: Financial data arrives in QuickBooks exports, Excel schedules, PDFs; analysts manually map it to the surety’s required format.

IMPLICATIONS:

  • This is half an FTE’s annual capacity spent on report generation — not analysis, not client service, just data entry.
  • Firms hire “Production Underwriting Assistants” to handle the volume, scaling cost instead of solving the problem.
  • In a hard market (rising remarketing volume), this bottleneck compounds.

CTA: If WIP reports are eating your team’s time, DM us. We’ll show you the 20-minute version.


POST 9 — You hired an Enterprise Architect but your team still lives in spreadsheets

Pillar: Problem (Niche)
Target audience: Starkweather & Shepley, firms attempting digital transformation
Robert GPT format: Thought Leadership - Organizational Paradox. Structure: Paradox Hook (hiring Architect + hiring Assistants) + Root Cause. Example reference: Diagnostic structure.

FACTS / EVIDENCE:

  • Mid-market brokerages hire “Enterprise Architects” and “CTOs” to build modern data foundations.
  • At the same time, they’re hiring armies of “Underwriting Assistants” to “deal with all these spreadsheets and PDFs” (documented quote: Starkweather & Shepley SVP).
  • The paradox: The Architect is designing a data warehouse, but the team is drowning in static files. The assistants are human middleware, moving data from Excel to the system.
  • The Architect can’t build the foundation without structured inputs. The assistants can’t structure the inputs fast enough.

IMPLICATIONS:

  • This is the “scaling paradox” of the 100M segment: large enough to need architecture, not large enough to have automated ingestion.
  • Hiring more assistants scales cost; hiring an Architect without solving ingestion scales frustration.
  • The fix isn’t downstream (better AMS, better reporting). The fix is upstream (automate the spreadsheet-to-structure step).

CTA: If you’re building a data foundation but your team is still in Excel, DM us. We’ll show you the ingestion layer.


POST 10 — If you’re hiring “Intake Coordinators,” you’re treating a symptom

Pillar: Problem (Niche)
Target audience: Hiring managers, ops leaders at all target firms
Robert GPT format: Thought Leadership - Symptom vs Root Cause. Structure: Symptom (hiring) → Root Cause (process) → Fix (automation). Example reference: Problem → Common Fix → Better Fix pattern.

FACTS / EVIDENCE:

  • Search “Intake Coordinator” or “Processing Specialist” or “Underwriting Assistant” on LinkedIn at mid-market brokerages. Dozens of open roles.
  • These roles exist to move data: monitor email inboxes, download attachments, enter data into systems, “gather information by carrier.”
  • They are human middleware. They exist because the software doesn’t talk to the software.
  • Hiring these roles is a symptom. The root cause: unstructured data (PDFs, spreadsheets, emails) + rigid systems (AMS, carrier portals) + no ingestion layer.

IMPLICATIONS:

  • Every “Intake Coordinator” you hire costs 70K/year. That’s 70K/year confirming that your intake process isn’t automated.
  • In a hard market (higher remarketing volume), you hire more Coordinators. You scale cost, not throughput.
  • Competitors who automate intake will handle 2–3× the volume with the same team size.

CTA: If you’re hiring Coordinators, let’s talk about why. DM us — we’ll show you the automation that eliminates the role.


Content index (UPDATED) (one-line reference; full copy & status in Notion):

#PillarTopic / hookRobert GPT formatTarget audienceNotion / link
1ProblemWhy intake takes a full day (not your team’s fault)Diagnostic (Blame Shift + Reveal)General
2ProblemAdding headcount doesn’t fix intakeProblem → Common Fix → Better FixGeneral
3SolutionMessy docs → cited risk profiles in minutesSilo-to-SignalGeneral
4SolutionYou don’t have to choose speed vs qualitySequence Flip NarrativeGeneral
5ServiceWhat we do: zero-to-one lead intakeB2B Services / Do & Don’tGeneral
6ServiceGive value first: gap coverage analysisOrganizational InsightGeneral
7Problem (Niche)Why your LLM pilot failed (and what works)Problem DiagnosisShepherd, AI skeptics
8Problem (Niche)The 20-hour report costing $50K/yearCost QuantificationScott, surety firms
9Problem (Niche)Hired Architect but team lives in spreadsheetsOrganizational ParadoxStarkweather, transformation firms
10Problem (Niche)Hiring “Intake Coordinators” = treating symptomSymptom vs Root CauseHiring managers, all firms

At gate: “Supporting content calendar in execution” = confirm in Notion that posts are queued/going out; use the link above.


Demo / proof points (for conversations and content):

DemoFocusKey proofTranscript
Demo 1Zero-to-one lead intakeCited risk profiles + submission-ready drafts from messy/partial docs; hours → minutesZero-to-One demo transcript
Demo 2Gap coverage analysisFree risk review; policy-language gaps, impact, recommended actions; trust-building before asking for businessGap Analysis demo transcript

Use these when prospects ask “how it works” or “can I see a demo?” — share demo links or summarize outcomes (cited profiles, email drafts, gap analysis with citations).

Post drafts: Full copy (Post + Carousel) from these outlines: use Robert GPT with the format and example references above, and output in the Campaign Post Template so it’s pastable into Notion.


6. Roles & owner

ActionOwner
Brief owner / gate decision[TBD]
Outreach execution (HeyReach, list)[TBD]
Intro approval (1–9 mutuals)[TBD]
Founder intro send[TBD]
Content publish[TBD]

7. Gate decision (fill at gate date)

Gate date: [Set]

Sales cycle note: 100M firms have longer sales cycles than smaller agencies. They have failed automation attempts (cautious), procurement processes, complex stakeholder alignment, and higher ACV scrutiny. Expect 4–6 week sales cycles vs 2 weeks for smaller firms. Gate criteria remain (3 SOWs, 1 signed, 5 meetings) but acknowledge velocity will be slower. Quality over speed — landing 1 Shepherd or 1 Scott is worth more than 10 small agencies.

  • Go — Beta criteria met; proceeding to full rollout.
  • Conditional go — Beta met; Market Ready actions committed with follow-up date.
  • No-go — Beta not met; iterate or pause. Next test date: _______________.

Notes: