Many Duck Creek programs are discovering that the hardest part in modernization begins after go-live. As insurers move into continuous releases, cloud operations, and AI-enabled delivery, the key question is whether the organizations can absorb change at the pace the platform and ecosystem now demand.
As insurers move beyond implementation to steady-state operations, the more important issue becomes clear: do insurers have the operating model required to manage continuous change, govern Artificial Intelligence (AI) at scale, and convert platform investment into measurable business outcomes?
This shift is fundamentally changing the narrative. What was once a configuration-led transformation is now a build-and-run operating model challenge. Duck Creek remains an essential core system for Property and Casualty (P&C) carriers, but the next differentiation phase will depend on how effectively insurers scale change across the full life cycle, from value intake and prioritization to engineering, operations, governance, and continuous learning.
Connect with us to discuss this topic in depth.
Implementation is no longer the primary challenge
The Duck Creek market has entered a new phase where the core challenge is operational readiness. Most carriers now know how to execute a modernization program. The harder question is whether they can run Duck Creek as a continuously evolving system without increasing delivery friction, governance burden, or operational strain.
This challenge is especially visible in Active Delivery. Providers consistently report that customers struggle to keep up with bi-weekly release cycles and the production level readiness required. Many carriers lack embedded regression automation, structured release governance, and strong observability.
When these capabilities are missing, pressure builds across the system, impacting both upstream configuration and downstream operations. As a result, the market is shifting from implementation capability to operating model maturity. The real question insurers are now asking is: Can we run Duck Creek in a way that makes change safe, repeatable, and cost-effective?
Why AI-led operating models matter now
The AI-led operating models can fundamentally change the equation. Most AI discussions in insurance still focus on isolated use cases, coding assistants, claims summarization, or document extraction. While these use cases are valuable, they do not materially shift economics unless they are embedded into how work is prioritized, built, governed, and run.
An AI-led operating model embeds AI directly into enterprise delivery instead of treating it as a productivity tool. In practice, that means value intake and prioritization become more structured, with AI investments tied to business outcomes, decision rights, risk thresholds, and measurable success criteria. It means the build lane changes as well, with AI-enabled delivery pods compressing requirements analysis, design, code generation, testing, and modernization work, while shifting engineers toward supervision, refinement, validation, and reuse. Just as importantly, the run lane evolves. AI-enabled operations can support incident triage, remediation, Site Reliability Engineering (SRE), Development, Security, and Operations (DevSecOps), audit evidence, and runtime controls. This is vital in Duck Creek environment because insurers often lose value not during implementation, but while sustaining platform change over time.
Finally, the operating model needs a continuous learning loop, where outcomes are measured, playbooks are reused, controls are refined, and model behavior is monitored over time. Without this loop, AI drives activity without impact. With it, AI becomes a scalable engine for continuous improvement.
Governance must move into the system
This evolution also reshapes governance. Historically, governance sat outside workflows as a review layer. In an AI-led operating model, governance must be embedded directly into systems. Guardrails, evaluation mechanisms, auditability, approved models, logging standards, and risk controls need to be integrated directly into delivery pipelines and runtime processes. This is particularly important in Duck Creek ecosystems, where the data and AI stack remain fragmented. Providers often note that Clarity and Insights require enterprise data warehouse dependencies, which means many carriers do not realize a true single-suite reporting model.
At the same time, service providers are building AI wrappers and accelerators around the platform, creating variability in outcomes and governance approaches across implementations.
An AI-led operating model addresses this by standardizing how AI is governed across the ecosystem, clarifying what is platform-native versus partner-native capabilities, and embedding controls across both build and run workflows.
Commercial models will evolve
The shift will also reshape commercial models. As AI reduces effort-based work, insurers are reassessing how they buy services. Enterprises are consolidating toward fewer accountable partners, demanding stronger governance, and moving toward outcome- or KPI-linked commercials.
In the Duck Creek market, this is reinforced by increasing scrutiny on the total cost of ownership, especially around forms, integrations, testing, and adjacent layers that expand program cost beyond the core platform.
The implication is clear: traditional Full-time Equivalent- (FTE) led delivery models will become harder to sustain. Service providers will need productized offerings, reusable accelerators, migration factories, and clear outcome commitments. Buyers will prefer partners that can reduce cost-to-change and improve long-term economics. In that sense, the AI-led operating model is not only a delivery construct but also a governance, margin, and vendor strategy construct.
What insurers should prioritize next
Duck Creek’s next transformation phase requires a deliberate shift from implementation to operating model design. Insurers should prioritize:
- Defining clear business outcomes, such as faster product updates, lower testing effort, fewer release disruptions, or more scalable managed services
- Establishing an AI control plane with approved models, data controls, audit standards, and clear accountability across business and technology teams
- Designing AI-enabled build and run workflows rather than layering AI onto legacy work practices
- Measuring success at the workflow level. Metrics such as reduction in release effort, improvement in testing productivity, incident triage speed, and lower cost-to-change will matter far more than the copilots deployed or experiments completed
Exhibit 1 illustrates how Duck Creek operating models are evolving from fragmented, AI bolt-on approaches to fully integrated, AI-enabled systems of execution.
Core transformation is now the starting point
Duck Creek implementation is no longer the finish line; it is the starting point. The next competitive divide will not be defined by who has implemented the platform, but by who can operate it most effectively. Two insurers can invest in the same core platform and achieve very different business outcomes. One may gain modernization benefits but struggle with continuous change. Another may use an AI-led operating model to improve speed, reduce operational tax, and scale with confidence. This is why the next value battle in Duck Creek services will be driven by AI-led operating model excellence, not by implementation capability.
If you enjoyed this blog, check out, AI-powered observability: The next frontier in modern operations – Everest Group Research Portal, which delves deeper into another topic relating to AI.
These themes and their implications for the Duck Creek ecosystem will be explored further at Formation. To continue the discussion, connect with Aaditya Jain ([email protected]) at Formation or reach out to Ahmad Khan ([email protected]) and Rugved Sawant ([email protected]).