Case studies

How Pimsa Seguros stopped going portal by portal and gets its carrier comparison in under 10 minutes

Company
Pimsa, Insurance & Surety Broker
Lines
Auto and major medical
Location
Mexico
Handle product
Personal Lines Quoting agent
Carriers
10 connected by portal
Period measured
August 2 to October 1, 2026
  • 9.6 min

    from request to comparison

    median over the period

  • 94.5%

    of quotes got a response

    at least one carrier quoted

  • 1,447

    carrier portal sessions

    run by the agent in 60 days

Quotes handled by the agent in 60 days

272 quotes

From request to comparison

  • Quotes requested272

    242 distinct clients

  • Quotes with a response from at least one carrier257

    94.5% of the total

  • Compared across 3 or more carriers64%

    median of 7 attempted and 3 quoted

  • Portal sessions that returned a quote66%

    949 of 1,447 sessions

Quotes per week since the end of the pilot

17
Aug 17
62
Aug 24
31
Aug 31
34
Sep 7
28
Sep 14
64
Sep 21
33
Sep 28*

During the pilot (July 14 to August 10) Pimsa quoted with the agent 1 to 8 times a week. Since August 17 the agent has been part of daily operations: ~4.5 quotes per business day. *Partial week.

First carrier quoted in 6.9 minutes and the comparison in 9.6, while the client is still on the call

Aug 2 to Oct 1, 2026

The challenge: ten portals, the same data and a client waiting for the comparison

Pimsa is an insurance and surety broker that quotes auto and major medical with ten carriers, including Inbursa, MetLife, HDI, Chubb and MAPFRE.

In these lines, quoting doesn't happen by email: it happens on each carrier's portal. For every client, someone on the team has to log into a portal, enter the data, wait for the premium, download the result and do it all again on the next one, each portal with its own form, its own rules and its own outages.

And the client doesn't want a single option. They want to see several carriers side by side, and they want it soon. The more portals the team works through, the better the comparison, and the longer the client waits to get it.

Pimsa needed to compare more carriers per client without every quote costing the team a full round of ten portals.

The solution: an agent that works the portals in parallel and builds the comparison on its own

Pimsa rolled out Handle's Personal Lines Quoting agent, connected to the portals of its ten carriers. The broker sends the request; the agent logs into each portal, quotes and returns a comparison ready for the client.

  1. 1

    Receives the broker's request

    auto or major medical

  2. 2

    Logs into the portals in parallel

    median of 7 carriers per request

  3. 3

    Enters the data and quotes on each portal

    0.8 to 3 min per portal

  4. 4

    Builds the comparison

    median of 9.6 min

  5. 5

    Escalates if a portal blocks it

    outages, permissions or login

First response

6.9 min to the first carrier

  1. 01

    Every portal at the same time

    What a person does portal by portal, the agent does in parallel. Each session takes between 0.8 and 3 minutes, but they run together: in 60 days the agent ran 1,447 carrier portal sessions and got a quote in 949 of them.

  2. 02

    The first premium in minutes

    The median from request to the first carrier quoted was 6.9 minutes, and 9 out of 10 requests had their first premium in under 26 minutes. The broker can answer the client almost within the same conversation.

  3. 03

    A comparison that completes itself

    The agent doesn't wait for every portal to finish: it builds the comparison with the first carriers that respond, in a median of 9.6 minutes, and keeps updating it as the rest come in.

  4. 04

    A real comparison

    For each request the agent tries a median of 7 carriers and gets 3 quotes. 64% of the period's quotes were compared across three or more carriers, a comparison there is rarely time to build by hand.

  5. 05

    The broker only steps in when the portal asks for it

    When a portal is down, asks for permissions or requires a login step only the broker can complete, the agent hands it over with the case context. Everything else (entering data, quoting, comparing) the agent handles.

The results: 272 quotes in 60 days, 94.5% with a response and the comparison in under 10 minutes

Over the last 60 days the agent handled 272 quotes for 242 clients in auto and major medical, at a pace of ~4.5 per business day.

257 of those quotes, 94.5%, got a response from at least one carrier. The first arrived in a median of 6.9 minutes and the comparison in 9.6.

A real quote, October 1, 2026

  • 8:39

    The broker's request comes in

  • 8:44

    The first carrier quotes

  • 8:47

    First comparison, with 2 carriers

  • 7 of 9

    carriers quoted by close, from $1,750 to $21,273 MXN

Carriers with the best response rate

CarrierSessions with a quote
Inbursa86%
MetLife84%
HDI82%
Chubb74%
MAPFRE72%

Agent operating volume

ActivityVolume
Quotes handled272
Clients quoted242
Carrier portal sessions1,447
Sessions that returned a quote949
Quotes with a response257 (94.5%)

Production data as of October 1, 2026, covering the last 60 days. "With a response" means at least one carrier returned a quote; it does not measure how many became policies. Duplicate and test quotes were excluded. The premiums in the example are the ones returned by the carriers' portals.

Other key numbers from the period

  • 10

    carriers connected by portal

  • ~4.5

    quotes per business day

  • 7

    carriers attempted per request (median)

  • 3

    carriers quoted per request (median)

  • 64%

    compared across 3 or more carriers

  • 96%

    of sessions quoted in the best week

What's next

With eleven weeks of history, the next step is to measure what happens after the comparison: how many quotes become policies, how many hours of portal work the agent absorbs and how quickly Pimsa delivered a comparison before it had the agent.

Pimsa's bet is clear: every client gets several options in minutes, and the team spends its time advising and closing, not entering the same data on ten portals.

Pimsa × Handle

Is your team still going portal by portal to build every comparison?