What this one was

Small room. The plan was pipelines and basic setup, and about a minute in it was clear that a prepared talk was the wrong shape for four people, so we scrapped it and just worked.

That is going to happen sometimes. It is not a bad outcome, it is just a different one, and it produced a couple of things worth writing down.

Testing a rater in public

One agency has been running the same personal lines rater for years and is close to dropping it. They spent most of the session quoting a live risk through a newer rater side by side against the old one.

The comparison came out close enough to matter. Same risk, one quote at $726 without a full motor vehicle report pulled and $733 through the carrier after the full pull. Close enough that the deciding factor stopped being price accuracy and became how many questions the thing asks.

That turned out to be the real point. The older rater walks you through carrier-specific questions one carrier at a time. The newer one lets you set deductibles once and apply them across the board. When the outputs are comparable, the tool that respects your time wins.

Still unsolved for them: the newer rater only handles single family residences today. No condo, no renters. They have been told roughly thirty days for a fix, and that is the only thing blocking a full migration.

Restraint, which was the actual theme

Three things got said that are worth more than any build described.

Less is more on automations. More sequences is not more sophistication. It is more surface area for something to fire at the wrong time.

Just because AI can do it does not mean it is the best way. This came up specifically about AI phone agents. Two agencies in the room had looked at them and passed, for the same reason: they sound robotic, and their customer base would notice and dislike it. Nobody in the room is against the technology. They are against using it in the one place where the relationship actually lives.

Do not let automation make you forget you are a sales organization. The point being that it is possible to get so far into building the machine that you stop doing the thing the machine was supposed to free you up for.

There was also a genuine disagreement worth noting, because nobody resolved it and nobody needed to. One person framed this business as a sales industry, another as a service industry. Both were describing the same book of business.

Qualifying in, not out

One useful distinction. When a lead comes in, the question is not whether you are going to quote it. It is whether it qualifies in.

That sounds like semantics until you build a pipeline around it. Qualifying out means your first automated step is looking for reasons to stop. Qualifying in means your first step is looking for what is missing so you can keep going.

Race conditions are real

A lead filled out the long quote form, and then got an automated text that had nothing to do with what they had just done. Their reply was, more or less, I already filled the form out, I do not know why you are texting me.

That was not a bad automation. It was two automations firing at the same time with no knowledge of each other, and with current tooling there is no clean way to prevent it.

Small practical notes

  • The CRM’s API recently added file upload links on personal lead cards. Not on business leads yet.
  • Commercial leads still cannot cleanly separate a contact record from a company record, which makes imports messy.
  • Bulk record updates work well as a single job rather than one at a time. Twenty records in one pass rather than twenty passes.
  • One agency is reconciling bank deposits against carrier statements to build payout sheets and track chargebacks, which is the same pattern two other agencies described a week earlier from different starting points.

What is next

Thursday at 11:00 Central, same link.

The pipelines and automations walkthrough that got skipped is what we are doing, properly this time. Static rules, where AI belongs, and how they hand off to each other.