insurance core

Duck Creek configuration that keeps up with monthly feature releases.

We configure and integrate Duck Creek Policy, Billing and Claims, move on-premises installs to Duck Creek OnDemand, and staff certified configurators when a rating change or a new state filing can't wait.

platform dossierDuck CreekInsurance core
Vendor
Duck Creek Technologies
Owner
Vista Equity Partners, since March 2023
SaaS
Duck Creek OnDemand, built on Microsoft Azure
Current release
Feature Release 26.09, in production from 10 Sep 2026
release watch
  • Feature Release 26.0910 Sep 2026
  • Send acquisitionJul 2026
connects with
in short·15-second read

Cohash configures, integrates and supports Duck Creek Policy, Billing and Claims.

We move carriers from on-premises installs to Duck Creek OnDemand, the continuously updated SaaS built on Microsoft Azure, and we build regression packs for rating and forms so each Duck Creek Feature Release can be taken on time. We also staff certified Duck Creek configurators and integration developers.

you probably need this if
  • Duck Creek runs on-premises and the OnDemand move keeps sliding a year.
  • Rating changes wait weeks because regression testing is a spreadsheet.
  • A new state filing date is fixed and the configurator bench is empty.
Ask an engineer facts checked 2026-10-20 · 11 sources
how it runs
  1. 01Content and integration inventory
  2. 02Regression from your own policies
  3. 03Migration rehearsal
  4. 04Release routine and handover
you keep
  • Manuscript, rating, forms and integration inventory marked for OnDemand
  • Rating and forms regression pack built from production quotes and policies
  • Migration runbook with rehearsal timings
+ 3 more documents
who does it
Duck Creek Policy configurator (manuscripts and rating)Duck Creek Billing configuratorDuck Creek Claims configurator Policy Configurator Certification Billing Configurator Certification
duck-creek · release timeline
  1. 30 Mar 2023 Vista Equity Partners ownership Vista's take-private of Duck Creek completed in March 2023. Duck Creek remains a Vista portfolio company. source ↗
  2. 28 Apr 2026 Agentic AI Platform launch AI platform for underwriting and claims, with an orchestrator, approval checkpoints and decision lineage. source ↗
  3. Jul 2026 Send acquisition Duck Creek acquired Send, adding agentic underwriting to the core platform. source ↗
  4. 10 Sep 2026 Feature Release 26.09 Duck Creek's numbered feature release. You can run it in production from September 2026. source ↗
  5. today · Oct 22, 2026
the story · duck creek estate

From the first call to a setup your own team can run.

Here's what usually prompts a call about your Duck Creek estate, what we do about it and in which order, and where you end up.

  1. chapter 01 · where it hurts

    Why teams reach out

    • Duck Creek runs on-premises and the OnDemand move keeps sliding a year.
    • Rating changes wait weeks because regression testing is a spreadsheet.
    • A new state filing date is fixed and the configurator bench is empty.
  2. chapter 02 · what we change

    How we solve it

    • Move to Duck Creek OnDemand
    • Policy, Billing and Claims configuration
    • Rating and forms regression
    • Integrations through Integration Hub and APIs
    • Agentic AI scoping
    • Certified staff
  3. chapter 03 · how it runs

    Our approach

    • Content and integration inventory
    • Regression from your own policies
    • Migration rehearsal
    • Release routine and handover
  4. chapter 04 · where you end up

    What changes

    • Rating has been proven on the carrier's own quotes before it moves, and there's a release routine ready for continuous updates.
    • The state goes live on the filed rates and forms.
    • Manuscript, rating, forms and integration inventory marked for OnDemand
    • Rating and forms regression pack built from production quotes and policies
what we do

Our Duck Creek work

6 kinds of Duck Creek work, each run by engineers who have done it on live tenants.

  1. An inventory of manuscripts, rating, forms and integrations on your on-premises install, a plan for what changes on OnDemand, and rehearsed data migration with Active Delivery in mind.

  2. Product, rating and forms configuration for new states and lines of business, built and tested by certified configurators.

  3. A regression pack built from your own quotes and policies, run on every Feature Release so rating differences show up in test.

  4. Interfaces to agency portals, payments, document generation and data platforms, built on the integration layer Duck Creek supports for your version.

  5. Scoping for Duck Creek's Agentic AI Platform, including which underwriting or FNOL workflow to start with, where a person approves and how decisions are logged.

  6. Contract, contract-to-hire and permanent Duck Creek configurators and developers, onsite in the US or from nearshore and offshore teams across time zones.

capability 01 / 06in production

Move to Duck Creek OnDemand

An inventory of manuscripts, rating, forms and integrations on your on-premises install, a plan for what changes on OnDemand, and rehearsed data migration with Active Delivery in mind.

capability 02 / 06in production

Policy, Billing and Claims configuration

Product, rating and forms configuration for new states and lines of business, built and tested by certified configurators.

capability 03 / 06in production

Rating and forms regression

A regression pack built from your own quotes and policies, run on every Feature Release so rating differences show up in test.

capability 04 / 06in production

Integrations through Integration Hub and APIs

Interfaces to agency portals, payments, document generation and data platforms, built on the integration layer Duck Creek supports for your version.

capability 05 / 06in production

Agentic AI scoping

Scoping for Duck Creek's Agentic AI Platform, including which underwriting or FNOL workflow to start with, where a person approves and how decisions are logged.

capability 06 / 06in production

Certified staff

Contract, contract-to-hire and permanent Duck Creek configurators and developers, onsite in the US or from nearshore and offshore teams across time zones.

typical situations

Duck Creek situations we walk into

We pieced these together from Duck Creek situations that come up a lot. They're patterns. You won't find a specific client in them.

case file 01

Commercial auto on an old on-premises install and an OnDemand contract signed

composite · not a client story
  1. Beforethe situation

    Commercial auto and general liability run on an on-premises Duck Creek install with years of manuscript changes. The OnDemand contract is signed, but rating has never been fully tested outside production.

  2. What we dothe work

    First we pull production quotes from across states and build the rating regression pack. Next, every manuscript change gets reviewed against what OnDemand keeps. No date is set until policy and billing data migration has been rehearsed.

  3. Afterwhere you end up

    Rating has been proven on the carrier's own quotes before it moves, and there's a release routine ready for continuous updates.

case file 02

A new state filing and no configurators free

composite · not a client story
  1. Beforethe situation

    Homeowners needs to launch in a new state on a filed date. The in-house configurators are tied up on a billing change, and forms and rating for the new state haven't started.

  2. What we dothe work

    We place certified Policy configurators on the state build, reuse the existing product structure where the filing allows, and add the new state's quotes to the regression pack before release.

  3. Afterwhere you end up

    The state goes live on the filed rates and forms. The regression pack covers it from now on.

approach

How a Duck Creek engagement runs

We don't start a step until the last one has produced something you can check.

  1. step 01

    Content and integration inventory

    We list manuscripts, rating tables, forms and integrations, note which ones are customized, and mark what's going to change on OnDemand.

  2. step 02

    Regression from your own policies

    We turn real production quotes and policies into a regression pack for rating and forms, and run it in a lower environment on every feature release.

  3. step 03

    Migration rehearsal

    We rehearse policy and billing data moves with your Active Delivery contacts, and the timings from those rehearsals set the cut-over plan.

  4. step 04

    Release routine and handover

    When we leave, your team has the regression pack and a routine for reviewing releases, plus a configurator skills plan built around Duck Creek University certifications.

architecture

Where Duck Creek OnDemand sits for a P&C carrier

Agents and policyholders quote and service policies through portals and CRM that call Duck Creek. Policy, Billing and Claims run as SaaS on Azure, and finance and analytics read from a reporting copy.

Where Duck Creek OnDemand sits for a P&C carrier Agents and policyholders quote and service policies through portals and CRM that call Duck Creek. Policy, Billing and Claims run as SaaS on Azure, and finance and analytics read from a reporting copy. 01 · DISTRIBUTION 02 · DUCK CREEK ONDEMAND 03 · DOWNSTREAM quote and bind policy lookups SSO submissions referrals outbound events reporting feed Agency portal quote · bind · endorse Sf Salesforce agent and serviceteams Ex Entra ID staff sign-in DU Duck Creek OnDemand Policy · Billing ·Claims Agentic AI Platform underwriting · FNOL MU MuleSoft payments · documents Fb Microsoft Fabric loss and premiumreporting Underwriters approve · refer
Read the diagram as text
  1. Agency portal → Duck Creek OnDemand: quote and bind
  2. Salesforce → Duck Creek OnDemand: policy lookups
  3. Entra ID → Duck Creek OnDemand: SSO
  4. Duck Creek OnDemand → Agentic AI Platform: submissions
  5. Agentic AI Platform → Underwriters: referrals
  6. Duck Creek OnDemand → MuleSoft: outbound events
  7. Duck Creek OnDemand → Microsoft Fabric: reporting feed
use cases

Typical Duck Creek projects

The work teams usually bring us, and the platforms Duck Creek has to talk to while we do it.

  1. DUC-01 You run Duck Creek on-premises and want to move to OnDemand common request
  2. DUC-02 Rating changes take weeks because nobody trusts the regression testing common request
  3. DUC-03 A new state or line of business needs configuring by a fixed filing date common request
  4. DUC-04 Integrations were built years ago and break on every upgrade common request
  5. DUC-05 You want to pilot Duck Creek's agentic underwriting without losing control of binding decisions common request
you keep

What a Duck Creek engagement leaves behind

These are working documents, written against your configuration, so your team can run them without us.

  • inventory01

    Manuscript, rating, forms and integration inventory marked for OnDemand

    yours to keep
  • tests02

    Rating and forms regression pack built from production quotes and policies

    yours to keep
  • runbook03

    Migration runbook with rehearsal timings

    yours to keep
  • report04

    Feature release review checklist for your products

    yours to keep
  • plan05

    Configurator skills plan mapped to Duck Creek certifications

    yours to keep
  • design06

    Agent approval and logging design for an underwriting or FNOL pilot

    yours to keep
talent and delivery · duck creek

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.

Onsite

Engineers at your sites in the US

Nearshore

Overlapping hours with US teams

Offshore

Overnight progress on your backlog

All time zones

Coverage handed over across time zones

24-hour coverage · US Central time
OnsiteUS business hours
Nearshoreoverlapping US hours
Offshoreovernight progress
Combinedhandover, not hand-off
roles we staff
  • Duck Creek Policy configurator (manuscripts and rating)
  • Duck Creek Billing configurator
  • Duck Creek Claims configurator
  • Duck Creek integration developer
  • Duck Creek OnDemand migration lead
01What changes when we move from on-premises Duck Creek to OnDemand?

OnDemand is continuously updated SaaS on Microsoft Azure, run through Duck Creek's Active Delivery service. The upgrade projects go away. In their place you take feature releases on Duck Creek's timetable, and your testing and change process have to move at that pace.

02How long does an OnDemand move take?

It depends on how much custom manuscript and rating content you carry, how many integrations need rework and how much policy history you migrate. We size it after the inventory.

03Are your configurators certified?

Yes. Duck Creek University runs the certifications, split into business and configurator tracks for Policy, Billing and Claims. Whoever we place holds the one for the product they'll work on.

04Who owns Duck Creek now?

Vista Equity Partners. The acquisition completed in March 2023, and Duck Creek still lists itself as a Vista portfolio company.

05Do you also work on Guidewire?

Yes. After an acquisition some carriers end up running both. We have a separate Guidewire page, and we staff each platform with its own specialists.

services

Related services

Projects on Duck Creek usually end up touching one of these, so they're worth a look.

sources 11 sources linked last checked 2026-10-20 content fingerprint c7a58819
  1. 01Duck Creek: Product Feature Releaseduckcreek.com ↗
  2. 02Duck Creek: OnDemandduckcreek.com ↗
  3. 03Duck Creek: Cloud deliveryduckcreek.com ↗
  4. 04Duck Creek: Microsoft partnershipduckcreek.com ↗
  5. 05Duck Creek: Integration Hubduckcreek.com ↗
  6. 06Duck Creek: Certificationsduckcreek.com ↗
  7. 07Duck Creek: Duck Creek Universityduckcreek.com ↗
  8. 08Duck Creek: Agentic AI Platform launch (28 Apr 2026)duckcreek.com ↗
  9. 09Duck Creek: acquisition of Sendduckcreek.com ↗
  10. 10Vista Equity Partners: acquisition of Duck Creek completedvistaequitypartners.com ↗
  11. 11Duck Creek: Vista Equity Partnersduckcreek.com ↗
Reviewed by the Cohash team Duck Creek is a trademark of its owner, used here to identify the platform. how we handle facts and data →
next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it