Guidewire's Qusar Puts Agents Inside Core Underwriting and Claims Data

Guidewire's August 3 Qusar release wires a governed Agentic Framework directly into the core system that already prices, bills and pays claims for more than 570 insurers, giving prebuilt agents live access to policy, claims and billing data (Guidewire, August 2026).

Automobile Club of Southern California is the only customer Guidewire named running it, and that thin verification, not the demo, is what actuaries evaluating the release should scrutinize first.

Key Takeaways

Agents read and write into PolicyCenter, ClaimCenter and BillingCenter, not a sandbox, so every agent action becomes part of the system of record an examiner can later request.
22% of insurers expect an agentic AI solution in production by year-end 2026 on Celent's survey, which is the denominator a one-customer launch should be read against.
Twenty-four states and the District of Columbia have adopted the NAIC Model Bulletin as of March 2026, largely without modification, covering most of the premium volume running on this install base.
The NAIC's AI Systems Evaluation Tool is in a 12-state pilot running March through September 2026, with four exhibits quantifying AI usage and assessing governance risk.

What the Agentic Framework Actually Ships

Qusar bundles three prebuilt agents with a separate developer toolkit, all running inside Guidewire Cloud Platform rather than as a bolt-on product. Claim Summarization generates adjuster-facing summaries pulled from claim files. Policy Change assists underwriters and customer service reps through endorsement processing. Agentic First Notice of Loss walks claimants through reporting a loss using conversational voice AI instead of a web form, writing structured data back into the claim record as the conversation unfolds.

Guidewire also shipped Developer and Builder Assistants tuned to its own Gosu, Integrations, Jutro and Functions environments, which the company says help engineering teams ship configuration changes more than 40% faster than generic coding assistants manage inside a Guidewire tenant, plus a Data Curation Assistant that converts plain-language requests into SQL and a Product Design Assistant that automates parts of product configuration.

The separating word is "framework," not the agent list. Earlier core-system AI features shipped as fixed products: a chatbot bolted onto policy administration, doing one job. This release exposes the connective tissue, the same live read and write pathways into PolicyCenter, ClaimCenter and BillingCenter that Guidewire's own engineers use, so carriers can build custom agents rather than only consume the three Guidewire shipped. Every carrier that builds on the framework inherits responsibility for what its own agents do with that access.

Verification is thin against that surface. Auto Club has run InsuranceSuite since 2007 and moved it to Guidewire Cloud in 2023, and CIO Garrett Anderson's quote attaches no cycle-time figure, no leakage reduction, and no count of how many agents are live in production versus still in pilot. Celent's Karlyn Carnahan is quoted inside the press release rather than in a published report; Celent's separately published survey work puts 22% of insurers expecting an agentic AI solution in production by year-end 2026.

What Agent Write-Access Does to a Triangle

None of the Qusar materials attach a dollar figure to claims cycle time or expense reduction, which is notable given how central "days instead of months" language has been to prior releases. If agentic FNOL and claim summarization do compress cycle time at scale, the effect surfaces first in paid-to-incurred development patterns.

A genuine acceleration in early-stage reporting and payment compresses the early development factors in a paid loss triangle. A reserving actuary who does not footnote the process change risks reading a structural break as favorable development rather than a shift in claim-handling mechanics. That is not academic. Carriers that adopted straight-through-processing claims automation in prior cycles have had to explain to auditors, more than once, why a triangle suddenly looked better than history would predict.

Agent	Core data touched	Governance question it raises
Claim Summarization	Claim notes, adjuster files	Does the summary omit facts material to a coverage or reserve decision, and is that omission auditable after the fact?
Policy Change	Policy, billing, endorsement data	Who is accountable when an agent-assisted endorsement produces an underwriting outcome a human reviewer would not have reached alone?
Agentic FNOL (voice)	First-party loss narrative	Does a voice agent's structured extraction of an unstructured loss story create an adverse-action-style record if it misclassifies severity?

The expense side carries a comparable ambiguity. If agent-assisted claim summarization genuinely reduces adjuster hours per claim, it shows up as a favorable shift in the loss adjustment expense component of the combined ratio. But the governance layer is not optional overhead sitting on top of that saving; it is the precondition for trusting the saving is real rather than an artifact of an agent reclassifying claims into a lower-touch bucket without a human catching the error.

An agent with live write access to billing and claims data that is wrong in a systematic, undetected way does not only create a compliance exposure. It can move the loss triangle before anyone notices, which is a different and arguably larger risk than the one most carriers are evaluating when they assess an agentic vendor on speed alone.

The Documentation Layer That Does Not Come for Free

The NAIC Model Bulletin on the Use of Artificial Intelligence Systems by Insurers, adopted in December 2023, requires each insurer to maintain a written AI Systems Program, build a governance accountability structure spanning compliance, legal and data science functions, and extend vendor diligence, including contractual audit rights, over any third-party AI system it relies on for a regulated decision. Twenty-four states and the District of Columbia had adopted it, largely without modification, as of March 2026 (Quarles & Brady).

An actuary who signs off on a rating algorithm inherits a documented paper trail almost automatically: filed rate pages, an actuarial memorandum, a standards-compliant selection process. An agent that autonomously drafts a policy change or triages an FNOL claim generates none of that by default, unless the carrier builds logging into the framework as a deliberate design choice rather than an afterthought. Because the agents write into the system of record rather than a sandbox, every agent action is available to a market conduct examiner, or to a plaintiff's attorney in an adverse-action dispute.

Regulators are building the instrument to check it. The AI Systems Evaluation Tool is running a 12-state pilot from March through September 2026, with four exhibits that quantify AI usage, assess governance risk, flag high-risk systems and detail underlying data. Feedback is due back in September and October 2026, ahead of expected adoption at the November fall meeting (the 12-state pilot).

The gap the framework cannot close sits on the actuarial side of the same records. A policy-change agent operating inside PolicyCenter can see the filed rate that already landed there, but it cannot see the actuarial assumptions, credibility weighting or GLM structure that produced that rate if the model was built and version-controlled in an external platform. Akur8's Deploy product exists to solve the inverse problem, getting external rating logic into the core system, and it does not make the assumptions behind the rate visible to an agent acting on it.

Guidewire's Qusar Puts Agents Inside Core Underwriting and Claims Data

Key Takeaways

What the Agentic Framework Actually Ships

What Agent Write-Access Does to a Triangle

The Documentation Layer That Does Not Come for Free

Further Reading

Sources