We read your Guidewire or Duck Creek configuration and hand back a complete map — what’s custom, what’s dead, what breaks on cloud. Read-only. Non-production. No SI engagement required.
The team that built your system rotated off years ago. The documentation describes what was intended in 2017, not what’s running now.
Rules fire for products you stopped writing. Integrations point at systems you decommissioned. All of it is in scope until someone proves it isn’t.
Cloud migration isn’t a lift-and-shift. Custom code has to be assessed, rewritten, or retired — and you can’t plan any of it until you know what you have.
Every deviation from Guidewire or Duck Creek’s shipped base configuration — entity extensions, business rules, product model changes, custom code, integrations — counted, classified, and traced to the file and commit that created it.
Which of your customizations collide with the vendor’s current release, ranked by blast radius. The list your migration plan should start from.
Rules that haven’t fired in 18 months. Coverages never attached to a bound policy. Integrations with no traffic since 2023. Scope you can delete instead of migrate.
Your underwriting and validation logic written so an underwriter can read it — not just a developer. Confirm the rules still match the policy you actually want to write.
if (submission.Priority == 3
and driver.Age < 25
and vehicle.Symbol >= 20) {
addUWIssue("REFER_SENIOR",
Blocking)
}
On tier-3 submissions, any driver under 25 on a high-symbol vehicle is referred to a senior underwriter and cannot bind without sign-off.
Four steps, no change to anything that’s running.
Read-only access to your configuration repository in a development environment. Guidewire Cloud customers already have this provisioned; on-premise carriers point us at existing source control or a Studio project.
We parse the actual artifacts and build a dependency graph of how they connect.
We join that map to your runtime data to separate what exists from what is used.
A living map you can query, not a PDF.
We don’t ask a language model what’s in your system. Configuration is parsed deterministically, so the inventory is exact — every finding carries a file path, a line number, and the commit that introduced it. AI is used where it earns its place: naming what a rule does, reconstructing why it was built, and rendering logic in plain English. If we tell you a coverage exists, it exists.
Point us at PolicyCenter in a development environment. We’ll come back with your customization inventory and cloud-readiness map. If it isn’t useful, you’ve spent an afternoon of a developer’s time.