Hey Luis. I took a careful look at your agency. I think you're sitting on something bigger than it looks.
A handful of observations about your agency and the market around it, plus four directions you could try and one list of things I wouldn't touch. No pitch, no pricing. I want to see which of these you think is real, which you're already on top of, and which I got wrong.
You're the review leader on Sunrise Highway. By signal quality.
233 Google reviews. A perfect 5.0 average. The biggest-volume insurance office on your corridor — Silvia Romanita Allstate at 236 Sunrise Hwy — has 273 reviews at 4.71 stars. More reviews, lower signal. You have the highest-quality review signal on the street. Most five-year-old agencies never get close to that number at that rating.
"I truly appreciate Luis' transparency and professionalism. From the start, he was incredibly attentive, genuinely kind. He took the time to answer my questions and made the process feel smooth and stress free." Michaella Jimenez, Google review
Everything in this note starts from that fact. You've earned the trust. What's below is about the distribution around it — and about what the market is doing around you that makes distribution worth thinking about right now, not next year.
Three numbers that would make me look at my book differently if I were you.
None of these are about you specifically. They're the gravity field your agency is operating in. I think they quietly change the math on a couple of things you might have parked.
- NY auto rate shock. Q1 2024, State Farm secured a +24.9% auto rate increase in New York — the largest of any carrier that quarter — affecting 1.75 million NY policyholders. Every single one had a reason to re-shop the next twelve months. (S&P Global Market Intelligence.)
- Hispanic life gap widening. LIMRA's 2025 Insurance Barometer: Hispanic life insurance ownership dropped from 51% in 2021 to 40% in 2025 — the lowest of any US ethnicity. 53% say they need more coverage. (LIMRA 2025 Barometer, primary source.)
- Where Spanish speakers actually live online. 2024 Pew data (via DDIA): 54% of US Latinos use WhatsApp — the highest of any US demographic. Referrals travel on WhatsApp and inside family networks, not on an English /es mirror. (Pew via DDIA Q4 2024 Snapshot.)
- In-market rate. J.D. Power 2024 Insurance Shopping Study (n=10,003): 49% of US auto customers actively shopped in the past year; 29% switched carriers. Roughly 1 in 7 in any zip is shopping at any given moment.
Your review trust is already there. Retention, Spanish reach, and who gets to the shopper first — that's where the weight is right now.
You have the best reviews in town, and you're not on page one.
If someone in Lindenhurst searches "car insurance Lindenhurst NY" today, you don't appear in the top results. Ten buildings down from your office, Young Insurance NY (196 S 1st Street) does. An independent shop with a thin web footprint and a handful of Google reviews, still Google surfaces them before you.
Allstate agents, two independent brokers, and your own-street neighbor are all above you at the exact moment a local shopper has their wallet out. This is a distribution problem, not a product problem. Part of it isn't your fault at all: it's the structure State Farm puts every captive agent into. Your template is fixed; the leverage lies in the channels around it — Google Business Profile, review signal, external profiles, and direct conversations.
The Spanish version of your site exists. It reads like State Farm, not like your agency.
State Farm auto-generates a Spanish mirror the moment an agent flags Spanish as an office language. Open luissfinsurance.com/es →: every product page, team bio, office detail is translated. The scaffolding is there. What's on it, and what's missing, is the problem.
Half your reviewers are Hispanic: Rosario Aponte, Jiménez, Pauta, on and on. You, Brenda, and Jordy are bilingual. Brenda's bio on /es even tells the story of her Salvadoran roots and her Queens upbringing. All the raw material is there. Yet the Spanish version reads as a corporate-voice translation that could belong to any of the 4,000+ Spanish-speaking State Farm agencies nationwide. Nothing on it signals your Lindenhurst, your Hispanic community, your 233 reviews.
Worth saying plainly: a lot of the Spanish audience you could serve doesn't arrive through /es at all. With 54% of US Latinos on WhatsApp and most journeys starting with a referral or a Google Maps search, the Spanish layer worth investing in is probably on the bilingual-phone-number and WhatsApp-referral side, not a separately hosted page (I'll come back to why a separately hosted page is a bad idea in Observation 11).
Your reviews are trapped on one platform.
To be plain: you don't have a review-count problem. 233 is more than most of your peers will ever see. The observation is about distribution. When a shopper compares agents on Yelp or Facebook, they don't see you. That's not because customers don't love you, they do, it's because no one has routed them to those platforms.
Tom Falletta at Allstate uses an automated review tool (Birdeye) to spread his across every platform — that's part of why he shows up where you don't. The fix is a small, one-time setup: each happy customer gets gently steered to the platform that needs the signal most. Nothing here is trying to generate more reviews than you already get — just spreading the ones you get across two more shelves.
601 Instagram posts. 223 followers. The content isn't the problem.
You've put in the work. The issue is what's going out: mostly reposted corporate State Farm copy, English only, no local story behind any of it. Your "Quotes for Good" donation program is a gift of a content angle, and it's almost invisible outside the website footer.
Reminder on why the bilingual side of this specifically matters today: LIMRA 2025 shows Hispanic life insurance ownership at 40%, down from 51% in 2021 — the lowest of any US ethnicity, with 53% saying they need more coverage. Your reviewer mix is half Hispanic, your office is bilingual, your IG feed is English. There's a gap between who trusts you and who sees you on social.
The realistic shape of what could move this.
Four directions follow. Before they do, a quick honesty note so we're on the same page about what I'm not claiming:
None of what's below is new technology. Bilingual SMS text-back, review distribution to Yelp/FB, bilingual social drafts, renewal cadence — these have existed as SaaS for years (Birdeye, Podium, AgencyZoom, BrightFire, HighLevel). The reason I'm sending you this note isn't "nobody does this" — it's that the small-agency bilingual captive segment is one almost nobody targets specifically, and most of the tools are generic.
What I could plausibly bring: (a) fitting tools to your bilingual Lindenhurst/Copiague mix rather than a generic US-agent profile, (b) a setup you own rather than rent — so if we stop working together, you keep the system instead of losing access, (c) one point of contact for the whole stack instead of four SaaS dashboards.
Some of the directions below might already be handled by a tool you use, or something you've tried and dropped. That's fine — tell me. The point of this note is to map where you are, not to sell you a stack.
Bilingual SMS text-back, so weekend leads don't sit until Tuesday.
Inbound-only. Missed calls get a bilingual text back. Forms trigger an instant bilingual auto-reply. No chat widget on your State Farm site (your template wouldn't accept one, and that's fine).
Today
A Spanish-speaking family lands on your site at 9 PM Saturday. They fill out the quote form. The message goes to Brenda's inbox. She reads it Monday at 9:15. By then they've also submitted to Young Insurance, Tom Falletta's Allstate, and GEICO. Whoever replied first tends to win. Weekend is also when insurance shopping peaks.
What would change
Inbound SMS on a dedicated agency number (Twilio or similar) with two behaviors:
- If someone calls the office after hours or during a busy slot and no one picks up → they get an automatic text-back within 90 seconds, in whatever language the inbound voicemail suggests, asking if they want a callback Monday or an SMS reply now.
- If someone fills the web form → they get an immediate bilingual SMS confirmation ("Got your request for an auto quote. Luis or Brenda will follow up Monday 9 AM. If you need anything sooner, reply here.") instead of waiting in Brenda's inbox.
- Whoever is on — Luis, Brenda, Jordy — sees the conversation threaded in one place rather than across voicemail + email + SMS.
One thing to say plainly
GoHighLevel (a general marketing platform, ~$97/mo Starter) already has native bilingual missed-call-text-back as a feature, and there's a whole cottage industry of GHL agencies that configure it for small businesses for $500–$1,500 one-time. If you've looked into this and it's configured — great, this direction is already solved and we move on.
Where I might add value if this isn't configured: picking bilingual templates tuned for insurance-specific inquiries (auto quote vs. claims question vs. policy change — different flows), writing the handoff into your Monday morning triage, and confirming the SMS routing doesn't step on whatever SMS you already send from the office line. That last piece is where most generic setups get sloppy.
On the compliance question, honestly
Inbound transactional SMS — customer called you or submitted your form — is the safest TCPA category. After the 11th Circuit vacated the FCC's one-to-one consent rule in January 2025, this is the federally-safest form of outbound SMS today. The question that's not federally settled is carrier approval: State Farm's agent-marketing guidelines are member-gated, and I don't have them. Some SF agents run third-party SMS stacks; some get pushback from their field consultant. Worth a five-minute ask with yours before anything goes live.
What your agency would get
Weekend/after-hours leads stop sitting in Brenda's Monday inbox. Spanish-speaking families hear back in Spanish, in under two minutes, in a medium where SMS open rates run in the high 90s and response rates materially outrun email (CTIA industry data). Monday mornings start with a short list of already-warm conversations instead of an unsorted form queue.
What's known vs. what's theory
Known: The speed-to-lead mechanism is real. MIT 2007 (Dr. James Oldroyd, 15K+ leads across 6 companies, tested on insurance): responding within 5 min = 100× connect rate vs. 30 min. Velocify 2014 insurance mystery shop across 25 carriers: 39% of quote forms never got a callback, average call response was 2.3 days. Both studies are old; directionally consistent with more recent cross-industry data. Not known: whether your specific weekend pipeline has enough volume for this to meaningfully move your book. That's a measurement question for after setup, not a sales claim.
233 Google reviews; zero on Yelp. Point the firehose at the empty platforms.
Not about generating more reviews. About spreading the ones you already earn to the two platforms that need them.
Today
Every time you bind a new policy, a happy customer walks out. Sometimes Brenda remembers to ask for a Google review; they leave one. Your Yelp page has been empty for years. Your Facebook has three. Tom Falletta at Allstate uses Birdeye to distribute his reviews across every platform; that's part of why he shows up where you don't.
What would change
Same cadence you're already running, just routed to the empty shelves:
- When you mark a new policy as bound, a short workflow fires
- The customer gets a bilingual thank-you note referencing their policy type "Gracias Maria por confiar en nosotros con tu auto y tu casa", not a template
- The review link routes to whichever platform is thinnest right now (Yelp first, then Facebook, Google as fallback for your longest-tenure customers)
- One gentle reminder after five days, then stop
- Tracks who left a review so the same ask never fires twice
vs. Birdeye or Podium
These tools do exactly this. Birdeye runs $299–$599/mo per location, forever. The value of a custom build is (a) the routing logic is bilingual and tuned to your policy mix instead of generic, (b) the data on who-asked-who-responded lives on your side, not in a vendor's database, (c) the monthly cost stops after the initial build — you pay only for the actual SMS, which is pennies per month at your volume.
If you already use Birdeye or a similar tool and it's working — we drop this direction. The only reason to rebuild it is if you're not using one yet.
What your agency would get
Your Yelp page fills in over 6–8 months. Facebook follows. Customers who trust Yelp or Facebook can finally find you at the top of their preferred platform. Your review signal stops being a single point of failure.
Caveat on the "before/after" numbers
Birdeye's public insurance case studies (GAINSCO: 1→2,561 reviews; TrueCoverage: 1→1,365) are generation cases — businesses going from zero to thousands. Your case isn't that. You have 233, they just live on one platform. The comparable before/after looks more like "Yelp 0 → 40 over 8 months, Facebook 3 → 35", not four-digit numbers. Small, useful, one-time setup, no recurring SaaS bill.
Bilingual social built from the things you already do.
You've posted 601 times for 223 followers. The fix isn't more posts; it's posts that actually speak to half your audience in their language and tell stories that are only yours.
Today
The IG feed is mostly reposted State Farm graphics, generic PSAs, English only. Your "Quotes for Good" charity program is a gift of a content angle, and it's buried in the website footer. The posts-per-new-follower ratio (~3) is well outside healthy local-business range, and the 12-month follower growth barely moves.
What would change
A bilingual content drafting loop that uses the things your agency already produces as raw material:
- Trained on your 233 reviews, your Chamber events, your Quotes for Good donations, and the Lindenhurst/Copiague community calendar
- 2–3 bilingual drafts per week in formats that work on IG: short carousels, reel scripts, text-on-image quote cards
- Example draft: "Meet Ricardo — full coverage for less than his last agent. This week, his quote helped us donate to @LindenhurstFoodPantry. Quotes for Good, because being a good neighbor should literally mean something." Spanish version auto-generated alongside.
- Drafts land in a shared inbox; you click approve; it publishes
- Your time: 20–30 minutes a week reviewing drafts
vs. the alternatives
BrightFire, AgentMethods, and similar templated-content vendors do exist. They run $200–$400/mo and post generic, English-only State-Farm-flavored content across your feed. The difference is bilingual + your actual voice + your Lindenhurst specifics — the stuff a generic vendor can't do because they don't know your book.
If you've already contracted BrightFire or similar and the content is landing, this direction is moot.
What reasonable success would look like
Three to six months: IG posts in Spanish actually reach Hispanic Lindenhurst/Copiague accounts (you'll see it in follower demographics). Quotes for Good becomes a monthly beat your local paper could pick up. The posts-per-follower ratio moves from 0.37 toward the ~2–3 range a healthy local service business sees. Not viral. Just not wasted.
Your reviews are full of "home AND auto." Let's stop the rest from slipping.
With one honest limitation upfront: I don't have real-time access to your State Farm back-end. No outside consultant does. This runs on monthly CSV exports, not live data.
Today
You sold Maria an auto policy 10 months ago. She insures her house with Liberty Mutual. Her son turns 17 in six months. Her auto renews in 60 days. She hasn't heard from your office since January.
Reviews are full of "got home and auto with Luis, great rates!" — customers who found the cross-sell on their own. How many Marias didn't, and are sitting in your book right now?
What would change
Monthly cadence built on a CSV you pull from your agent portal (a familiar operation, not a new data connection):
- Your monthly CSV export — who has auto only, who has home only, renewal dates, recent quotes, last contact — drops into a shared workspace once a month (you or Brenda do the pull)
- An AI layer reviews the list, flags cross-sell opportunities (home at another carrier + auto with you → bundle candidate) and upcoming renewals
- It drafts bilingual outreach in your voice, using the customer's actual name and policy situation: "Hey Maria, Brenda here. Your auto renews Aug 12. I noticed you insure your house with Liberty — quick check, you'd save around $X/year bundling with us. Want me to pull a quote?"
- Brenda reviews, approves, sends — the outreach goes out from your office, you stay on the carrier-approved side of every compliance line
What it can't do, plainly
It cannot detect a renewal in real-time or a life event the moment it happens. Those live inside State Farm's system and nobody outside SF touches them. What it can do: work off a once-a-month snapshot. That's good enough for a cross-sell cadence; it's not good enough for real-time renewal alerts.
Anyone pitching "AI watches your State Farm policy data in real time" is either confused or wrong. That's worth stating plainly before we go further.
Before any of this happens — the same compliance step as Direction one
This direction assumes two things I can't verify from the outside: (a) that your agent portal actually lets you pull a policyholder CSV in the shape described, and (b) that sharing that export with an outside consultant or AI service is permissible under your State Farm agent agreement. On top of that, once policyholder data leaves the carrier system, NY's SHIELD Act and similar state privacy rules around PII kick in. None of this is fatal — small agencies run CSV-based outreach cadences regularly — but it's the kind of thing to clear with your field consultant and agency ops before we build anything, not after. If any of the three checks comes back "no," this direction drops off the list.
What your agency would get
Cross-sell opportunities stop quietly slipping. Renewals stop being last-minute scrambles. Revenue per customer grows without spending more on lead generation. Your book deepens instead of just widening. The monthly CSV upload becomes a 10-minute ritual, not a new job.
The things that sound good and would quietly fail in week four.
A short list of plays I've seen pitched to State Farm captive agents that either can't be done cleanly inside State Farm's structure, or can't be done at all. I'm putting them up front so you know where I drew the line.
-
A second, "personal" content website on your own domainAn earlier version of this note included this. I took it out. Every State Farm agent-branded domain I checked (including
luissfinsurance.com,anthonyalbanoagency.com, and one I flagged as a potential counter-example,clarkalvarado.com) resolves to State Farm's own infrastructure. They're template reskins, not independent sites. Running a genuinely off-template content site conflicts with captive brand guidelines and, in NY specifically, puts you in DFS §2122 territory the moment a quote CTA touches it. -
A custom chat widget on luissfinsurance.comYour site is the State Farm corporate template. Third-party JavaScript doesn't go on it — State Farm corporate controls the DOM. Any "chat on your site" pitch is really chat on a separate domain, which sends us back to the first bullet.
-
"AI reads your State Farm policy data and writes renewal messages in real time"Requires State Farm back-end access. No outside tool has it, you can't grant it. Anyone selling this is either hand-waving or wrong. If the cadence has real value, it lives on a monthly CSV (Direction 4 above), not on live data.
-
Weekly Google Business Profile posts as a growth channelLaw-wise probably fine. Carrier-wise, I couldn't confirm. State Farm banned agents from Google+ in 2013 (precedent), and I didn't find a documented SF captive agent running weekly GBP Posts in the wild. Worth asking your field consultant before anyone touches this — not worth building until you have.
-
Full-funnel SEO on your State Farm templateYou don't control metadata, URL structure, or schema on the template — State Farm does. City landing pages, rich snippets, structured data all live outside your reach. Real SEO moves for a captive agent are: Google Business Profile optimization, external profile sites (Yelp/FB/BBB), and the kind of small informational landing page that (per the first bullet) brings carrier-agreement questions with it.
This list will probably get longer as I keep reading, not shorter. If any of these sound wrong — if you know a State Farm agent running one of them cleanly — I want to hear it. It would change what I'd suggest next.
Honest about my side of this.
I'm not pitching a menu of subscriptions. I'm not selling an "agency on retainer" package. The shape that makes sense to me:
-
• Start with a 20–30 minute callYou tell me what resonates, what's already running, what I got wrong, what's just not where the pain is. I'd rather start with your actual picture than a polished one.
-
• If it's worth a second round — pick one directionNot four at once. The one with the shortest path to something measurable for your specific mix — auto/home book, bilingual customer share, Lindenhurst/Copiague geography.
-
• Build and hand it overCustom builds using modern AI APIs (Claude, GPT-4), n8n or Make for workflow, Twilio for SMS, Airtable or similar for data. Everything lives on infrastructure you own or have full credentials for — so if we stop working together, you keep the entire system.
-
• Measure what actually movesMonthly: what came in, what converted, what didn't. When one direction is earning, we look at the second. When one direction isn't, we kill it — not prolong it.
How to tell me this landed. For any observation or direction above that struck you — right or wrong — one of four words is enough: resonates / already doing / not my pain / didn't get it. One-word answers are entirely fine. I'd rather have your honest read than a polite one. The things I got wrong are more useful to me than the ones I got right.
Drop me a line whenever.
No deck to sit through, no slide count. 20–30 minutes when you have them, neighbor to neighbor.
dslabakov@me.com