I joined Insurance Navy because of how the brokerage was built from the start, over 20 years serving drivers that a lot of the bigger name carriers simply didn’t want to insure. My role isn’t running the business, but as someone who researches rate factors for a living, I see the difference play out daily in the data I work with. Because we’re independent and not tied to one carrier, a driver with a DUI or a lapse in coverage isn’t stuck with one company’s take on their risk. We can place them with whichever of our carrier partners, Progressive, National General, or Kemper, actually prices that specific history fairly, and that flexibility is what separates a broker from a single-carrier agent.

From where I sit on the content side, a large share of new readers and eventually new clients find us through search when they’re trying to understand why their rate went up or what a specific violation will cost them long term. That intent-driven traffic tends to convert well because they’re already trying to solve a real problem, not just comparing prices. I’d like to see more of that traffic come from people sharing our rate factor breakdowns directly, the way you’d share a genuinely useful reference page with a friend who just got a ticket, because that kind of organic trust-based sharing tends to bring in readers who stick with the content and eventually the brand.

I’ve handed over a lot of the early data aggregation work, pulling and organizing raw rate comparison figures across carriers and states before I start writing, which used to eat hours out of my week. It’s straightforward pattern matching across large data sets, exactly what these tools are built for. Where I went back to doing it myself is interpreting what a rate change actually means for a reader’s specific situation, like explaining why a single at-fault accident might raise one person’s premium by a small amount and another’s by a lot depending on their carrier and state. That requires judgment about context an automated summary tends to flatten out.

Definitely. Readers used to land on my articles asking what a rate factor even was. Now the questions in comments and reader emails are much more pointed, asking how much a specific ticket or accident will move their premium compared to another violation, which tells me they’ve already absorbed some baseline explanation somewhere before finding us. We’ve also started seeing a small but growing slice of traffic tagged as coming from AI assistant platforms in our analytics, and it consistently lands on the pieces with hard numbers in them rather than the general overview content, which fits since those tools are built to extract a specific figure rather than a broad description.

Put real, specific numbers into everything you publish, actual percentage ranges for how a violation affects a premium, actual state-by-state comparisons, because that specificity is exactly what both readers and AI assistants are trying to extract when they land on a page. My data-driven pieces consistently outperform my more general ones for this reason alone. What I’d tell them to ignore is the pressure to hedge every figure into vagueness out of caution, since burying the actual number under disclaimers defeats the purpose of writing a data-driven piece in the first place, and readers trust a real number a lot more than they trust a paragraph that avoids giving one.