Guidewire work that survives the next cloud release.
We configure, integrate and upgrade PolicyCenter, ClaimCenter and BillingCenter. Carriers moving self-managed InsuranceSuite to Guidewire Cloud get help from us, and when a team runs short we bring in certified Gosu and integration developers.
Cohash works on Guidewire InsuranceSuite, meaning PolicyCenter, ClaimCenter and BillingCenter.
We move self-managed installs to Guidewire Cloud, clean up Gosu customizations, build integrations on Cloud API, App Events and Integration Gateway, and supply certified developers. Guidewire Cloud ships named releases, the latest being Qusar in August 2026, so we plan work to keep you within Guidewire's N-3 window.
you probably need this if
The Guidewire Cloud move is approved, but nobody has counted the Gosu customizations yet.
Each release takes months because custom PCF and Gosu break in regression.
Some integrations still hit the database directly or call custom SOAP services, and neither will be there in the cloud.
16 Apr 2026ProNavigator in Palisades Embedded expert AI insights in insurance workflows, launched with the Palisades release after the October 2025 acquisition agreement. source ↗
Aug 2026Qusar release This release touches InsuranceSuite, PricingCenter, InsuranceNow, Jutro, Analytics, Data Platform and Cloud Platform. PolicyCenter, ClaimCenter and BillingCenter move to Cloud API 1.16.0. source ↗
today · Oct 22, 2026
no date yetRelease cadenceJasper shipped in March 2024 and Qusar in August 2026. In between came Kufri, Las Leñas, Mammoth, Niseko, Olos and Palisades.source ↗
no date yetCertification N-3 policyGuidewire won't let anyone work on a Guidewire Cloud implementation without certification. And it doesn't last forever. Fall more than three releases behind and you sit the proctored exams again.source ↗
the story · guidewire estate
From the first call to a setup your own team can run.
Here's what usually prompts a call about your Guidewire estate, what we do about it and in which order, and where you end up.
01 · where it hurts02 · what we change03 · how it runs04 · where you end up
incident board · guidewire estate3 open
openThe Guidewire Cloud move is approved, but nobody has counted the Gosu customizations yet.
recurringEach release takes months because custom PCF and Gosu break in regression.
blockedSome integrations still hit the database directly or call custom SOAP services, and neither will be there in the cloud.
exposure
Self-managed to Guidewire Cloud…PolicyCenter, ClaimCenter and…Cloud API and event integrationsRelease readinessAI agent scoping on GuidewireCertified developer staffing
startrehearsehandover
Customization inventory
Integration redesign
Conversion and rehearsal
Release rhythm and handover
we are here
ready to hand over
The cut-over date rests on a counted list of changes and a timed rehearsal.
We move releases on a published schedule, and the team stays eligible to work on the…
Gosu, PCF and integration inventory scored keep, rework or drop
Interface map with Cloud API, App Events or Integration Gateway chosen per feed
chapter 01 · where it hurts
Why teams reach out
The Guidewire Cloud move is approved, but nobody has counted the Gosu customizations yet.
Each release takes months because custom PCF and Gosu break in regression.
Some integrations still hit the database directly or call custom SOAP services, and neither will be there in the cloud.
chapter 02 · what we change
How we solve it
Self-managed to Guidewire Cloud migration
PolicyCenter, ClaimCenter and BillingCenter configuration
Cloud API and event integrations
Release readiness
AI agent scoping on Guidewire
Certified developer staffing
chapter 03 · how it runs
Our approach
Customization inventory
Integration redesign
Conversion and rehearsal
Release rhythm and handover
chapter 04 · where you end up
What changes
The cut-over date rests on a counted list of changes and a timed rehearsal.
We move releases on a published schedule, and the team stays eligible to work on the tenant.
Gosu, PCF and integration inventory scored keep, rework or drop
Interface map with Cloud API, App Events or Integration Gateway chosen per feed
what we do
Our Guidewire work
6 kinds of Guidewire work, each run by engineers who have done it on live tenants.
An inventory of Gosu, PCF and integration customizations scored against Guidewire Cloud standards, a decision per item to keep, rework or drop, and a data conversion plan rehearsed before cut-over.
Product model, rating, claim and billing configuration in Gosu, written so the next cloud release doesn't break it.
Integrations built on the versioned Cloud API, App Events and Integration Gateway (Apache Camel) instead of the point-to-point code that blocked your last upgrade.
A regression pack and a review of the release notes for each Guidewire Cloud release, so you move releases on a schedule you set.
Scoping for the Agentic Framework that arrived in Qusar, covering which data each agent may read, evaluation cases and human review before anything binds or pays.
Contract, contract-to-hire and permanent Gosu, integration and Jutro developers, onsite in the US or from nearshore and offshore teams across time zones.
capability 01 / 06in production
Self-managed to Guidewire Cloud migration
An inventory of Gosu, PCF and integration customizations scored against Guidewire Cloud standards, a decision per item to keep, rework or drop, and a data conversion plan rehearsed before cut-over.
Integrations built on the versioned Cloud API, App Events and Integration Gateway (Apache Camel) instead of the point-to-point code that blocked your last upgrade.
Scoping for the Agentic Framework that arrived in Qusar, covering which data each agent may read, evaluation cases and human review before anything binds or pays.
Contract, contract-to-hire and permanent Gosu, integration and Jutro developers, onsite in the US or from nearshore and offshore teams across time zones.
We pieced these together from Guidewire situations that come up a lot. They're patterns. You won't find a specific client in them.
case file 01
Self-managed ClaimCenter with years of Gosu and a cloud deadline
composite · not a client story
Beforethe situation
ClaimCenter runs self-managed with heavy Gosu rule customization and custom SOAP services that other systems call directly. The carrier has signed for Guidewire Cloud and has a date, but no count of what has to change.
What we dothe work
We start by inventorying every customization and scoring it against Guidewire Cloud standards. Then the callers of those custom SOAP services move to Cloud API or App Events, one at a time. Claim conversion is rehearsed at full volume before anyone puts the date in writing.
Afterwhere you end up
The cut-over date rests on a counted list of changes and a timed rehearsal. Once the move is done, other systems reach ClaimCenter through supported interfaces only.
case file 02
A cloud tenant two releases behind with lapsing certifications
composite · not a client story
Beforethe situation
PolicyCenter is already on Guidewire Cloud but two releases behind. Several contract developers' certifications are close to falling outside N-3, and regression testing is manual.
What we dothe work
We build a regression pack out of the carrier's own products and rating. Then we check each developer's certification against the target release and book the New Features courses alongside the upgrade plan.
Afterwhere you end up
We move releases on a published schedule, and the team stays eligible to work on the tenant.
We don't start a step until the last one has produced something you can check.
step 01
Customization inventory
Every Gosu class goes on the list, and so does every PCF, rule set and integration. We score each against Guidewire Cloud standards and mark it keep, rework or drop.
step 02
Integration redesign
Each interface gets mapped to Cloud API, App Events or Integration Gateway. No code moves until we've agreed the owner and test data for it.
step 03
Conversion and rehearsal
Policy, claim and billing conversion is rehearsed at full production volume. The timings from those runs set the cut-over window.
step 04
Release rhythm and handover
When we go, a regression pack stays behind. So does a release-notes review routine, and a skills plan that keeps your developers certified inside N-3.
ai on guidewire
Where AI fits on Guidewire, and where it needs guardrails.
Guidewire's Agentic Framework became generally available in the Qusar release of August 2026, with Agent Studio for building agents and MCP for reaching outside tools. Developer Assistants for Gosu, Integrations and Jutro are GA too, and ProNavigator assistants sit in PolicyCenter and ClaimCenter. Teams need to decide which agents get which data.
AI agentasks for data or an action
Scoped identityonly the access it needs
MCP serverthe one door into the platform
Logged, approveda person signs off on writes
Guidewiredoes the work
Guidewire's Agentic Framework connects agents to external tools and data through MCP. Guidewire doesn't currently publish a separate MCP server for outside agents, so those should call InsuranceSuite APIs. For us that means a dedicated service account, narrow permissions, logged calls and human approval for policy or claim changes.
Agentic Framework and Agent Studio
A model-agnostic framework for building and running AI agents with native access to the core system, and for governing them. Agent Studio is its low-code builder. For us the work is per agent. We scope what data it can reach, write its evaluation cases and set human review.
Developer Assistants
In Qusar, the Guidewire-aware assistants for Gosu, Integrations and Jutro went GA. The Functions assistant is still in early access. Our part is setting coding rules for using them. Code review and regression tests don't change from what human-written changes get.
ProNavigator and claims features
Palisades (April 2026) brought ProNavigator to PolicyCenter, ClaimCenter and InsuranceNow. Agentic FNOL, a voice-driven first notice of loss into ClaimCenter, is still in restricted access. Claim Summarization is in early or restricted access, so for us it depends on the product.
AI for cloud migration work
If you're a carrier moving to Guidewire Cloud, AI helps you inventory Gosu customizations, explain old rules and draft test cases. For us, each keep, replace or drop call is still made by people.
How Guidewire Cloud connects to the rest of a carrier
Agents, brokers and customers use Jutro front ends and Cloud API to reach PolicyCenter, ClaimCenter and BillingCenter. Outbound changes go out as App Events through Integration Gateway, to CRM, payments and the data platform.
01 · Channels
Jutro portalsagent · policyholder → Guidewire Cloud · Cloud API
Salesforceagent and service desk → Guidewire Cloud · Cloud API
Oktaworkforce and portal sign-in → Jutro portals · OIDC sign-in
These are working documents, written against your configuration, so your team can run them without us.
inventory01
Gosu, PCF and integration inventory scored keep, rework or drop
yours to keep
code02
Interface map with Cloud API, App Events or Integration Gateway chosen per feed
yours to keep
runbook03
Data conversion runbook with rehearsal timings
yours to keep
tests04
Regression pack for PolicyCenter, ClaimCenter and BillingCenter releases
yours to keep
document05
Certification matrix per developer against your current release
yours to keep
design06
Agent access and review design for the Agentic Framework
yours to keep
talent and delivery · guidewire
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Put these to anyone bidding on your Guidewire work. The ones who've done it answer differently from the ones who've read about it.
Q1
Which of our Gosu customizations violate Guidewire Cloud standards, and who decides what to drop?
The customizations decide what a cloud move costs and how long it takes. Score the list item by item, and have a business owner decide each drop. That keeps the plan honest.
Q2
Is everyone on the team certified within N-3 of the release we're on?
Guidewire requires certification for everyone on a Guidewire Cloud implementation. Fall outside N-3 and you're asked to retake the proctored exams.
Q3
Which integrations will use Cloud API, App Events or Integration Gateway, and why?
Each one fits a different pattern. Choosing interface by interface keeps you from rebuilding point-to-point code in the cloud.
Q4
How will you rehearse data conversion, and on what volume?
Conversion timing sets the outage window. A rehearsal on partial data gives a number you can't trust.
Q5
What will an AI agent in ClaimCenter be allowed to read and change?
Qusar brought the Agentic Framework. Agents need a scoped identity, evaluation cases and human approval before they touch a claim payment.
01How long does a move from self-managed InsuranceSuite to Guidewire Cloud take?
It depends on how many lines of business and products you run, how much Gosu and PCF customization sits on top of the base product, and how many integrations need rework for Cloud API or App Events. We size it after the customization inventory, not before.
02Do your developers hold current Guidewire certifications?
Yes. Guidewire wants everyone on a Guidewire Cloud implementation certified, under an N-3 policy. So we check each developer's certification covers a release within three of yours before they start.
03Which Guidewire release are you working on?
Guidewire Cloud releases have names. Palisades shipped in April 2026, and Qusar was available from August 2026. We work on whichever release your tenant runs, and plan the next move from the release notes.
04Can you build integrations without custom Gosu web services?
In most cases, yes. Guidewire's cloud integration framework offers the versioned Cloud API, App Events delivered by webhooks or Integration Gateway, and Integration Gateway itself, built on Apache Camel. We pick per integration based on volume, latency and who owns the other end.
05Do you also work on Duck Creek?
Yes. Some carriers end up running both after an acquisition. We have a separate Duck Creek page, and we staff each platform with its own specialists.
06Can you staff Guidewire developers offshore?
Yes, alongside onsite US and nearshore people, in whatever time zone suits. The part to settle first is which environments and data offshore staff can reach under your policies and your Guidewire agreement. We sort that with you before anyone gets a login.
services
Related services
Projects on Guidewire usually end up touching one of these, so they're worth a look.
