how cooper makes insurance submissions 15x faster with KERNEL
cooper uses KERNEL to help process more than a billion dollars in insurance premiums, sending each application to up to 10 carriers at once without building a browser team of its own.
15x
faster applications
160-200
engineering hours a week not spent on browser infrastructure
“insurance carriers offer portals, not apis. KERNEL lets our agents work through those portals on their own, saving brokers up to five hours per quote request.”
shashank mj, head of engineering, cooper
cooper is an ai coworker for insurance professionals in the commercial insurance industry. it has processed nearly $1 billion in premiums and grown more than 10x this year, all with an engineering team of less than 10 people.
cooper submits insurance applications to multiple carriers in parallel and loops in human brokers for help when needed. because so many of cooper’s tasks involve accessing insurance portals, reliable and efficient browser infrastructure is critical. cooper chose KERNEL to help streamline this process by giving agents access to browsers that their engineering doesn’t need to personally manage. the impact of this work is that they’ve saved over $1.25 million in premiums, while processing 6,000 documents per week for their customers.
problem: browser infrastructure is critical to insurance workflows, but not a competitive differentiator
when a business needs insurance, its broker asks several carriers for quotes to find the best price and terms. every carrier has its own portal. the forms are long, and a trucking company might have hundreds of vehicles to enter, so a single application can easily take a broker four to five hours, which is why most brokers only apply to the two or three carriers most likely to quote. cooper’s agents apply to seven to ten carriers at once in under 20 minutes. clients see more options, and brokers place more business.
“a mid-sized business often pays $100,000 or more a year in premium, and the brokerage earns 10 to 15 percent of that as commission. when a broker can go to more carriers, winning even a couple of extra policies a month makes a real difference to their business.”
shashank mj, head of engineering, cooper
however, insurance portals are also difficult for agents to navigate. they are often built using legacy technologies or involve complexities like iframes, which can confuse agents, and the forms often have dynamic fields, which prevents agents from knowing all of the information required in advance.
cooper first tried running headless chromium in the same sandbox as its agent, and quickly saw that it would not hold up in production.
“starting a headless chromium browser is easy, but running hundreds of them reliably in production takes much more. you need sessions that pause and resume, and profiles that keep people signed in. you also need a live view for the moments when a person has to step in. we estimated it would take four or five engineers several months to build what KERNEL gives us out of the box.”
shashank mj, head of engineering, cooper
cooper’s engineering team is small with around 10 engineers. to build and maintain their own browser infrastructure, they would have to expand the engineering team by 50%.
“it would take a team of at least four or five engineers to do what KERNEL does for us.”
shashank mj, head of engineering, cooper
solution: choosing a remote browser infrastructure service
because cooper has such a small and focused team, paying for remote browser infrastructure was a no-brainer for them. they evaluated headless chromium and other browser providers on the market and ultimately chose KERNEL because it performed the best on the different insurance portals that they care the most about.
cooper counts on KERNEL’s reliability and scalability, which allows their browser infrastructure to adapt to ebbs and flows in quote requests.
“our tasks can run for multiple hours. what matters most is that a browser stays up once it starts. we also need to launch hundreds of browsers at the start of each month, when our volume peaks. KERNEL has handled both, even as we’ve grown 5x in the last three months.”
shashank mj, head of engineering, cooper
in particular, cooper has leveraged KERNEL’s ability to auto-pause and auto-resume browser sessions in their agent-broker interactions. when an agent is filling out a form on an online portal, it frequently encounters requests for information it does not have. cooper can ask a human to provide this information or hand off control of the browser, allowing the human-in-the-loop to interact directly with a portal. however, this handoff means there may be a period during which the agent waits for a response from a human. to save money and time, KERNEL can auto-pause the browser until the human is ready, then auto-resume so that the agent can pick up where it left off.
because different online portals frequently ask for the same information, cooper goes a step further by batching its requests so that the human broker isn’t interrupted more than necessary. cooper’s goal is zero interruptions per human, and this batching behavior, paired with KERNEL’s ability to auto-pause and auto-resume browser sessions, is getting them closer to that goal.
results: cooper saved money for its clients by reducing the time to complete insurance applications
“browser infrastructure isn’t where we add value for our customers, so building it ourselves never made sense. KERNEL has kept up with us through 10x growth, and their team is quick to help whenever we need them. that frees our engineers to spend their time on the agent and on the insurance problems we’re excited to solve.”
shashank mj, head of engineering, cooper
with KERNEL, cooper cuts the time to complete an insurance application by over 90%, from four to five hours to under 20 minutes, without adding anyone to its engineering team. brokers use that time to reach more carriers and win more business, and cooper has now processed more than $1 billion in premiums.
if you’re a startup with an agentic product at its core, but don’t want an entire team focused on browser infrastructure, we can help.