Softwr

Insurance · head to head

Duck Creek Policy vs Riskonnect

Duck Creek Policy logo

Duck Creek Policy

Insurance

Flexible policy administration for modern insurers

From
On request
Rated
-
Riskonnect logo

Riskonnect

Insurance

Integrated risk management and claims administration for corporate risk teams

From
On request
Rated
-

The short version

  • Each has a real cost: Duck Creek Policy no pricing published on vendor website; enterprise solution requires custom engagement; Riskonnect total first year cost is dominated by implementation rather than licence; vendor professional services frequently approach the annual licence figure and the internal staff time to define data structures and migrate historic claims is a comparable third cost that never appears in the quote.
  • They diverge on capability: Duck Creek Policy covers Policy lifecycle management, Riskonnect covers Claims administration.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Duck Creek Policy and Riskonnect actually diverge.

Attributes where Duck Creek Policy and Riskonnect differ
AttributeDuck Creek PolicyRiskonnect
PlatformsWebWeb, iOS, Android
Founded2000Unknown

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated), category (Insurance).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Duck Creek Policy

  • Policy lifecycle management
  • Product configuration
  • Rating engine
  • Underwriting workbench
  • Forms management
  • Billing integration
  • Multi-line support
  • Real-time quoting

Only in Riskonnect

  • Claims administration
  • Total cost of risk reporting
  • Policy and exposure management
  • Enterprise risk management
  • Health and safety
  • Business continuity
  • Third party risk
  • Data integration

What people use each for

The jobs each tool is most often brought in to do.

Duck Creek Policy

  • Policy administrationnot Riskonnect
  • Underwriting workflowsnot Riskonnect
  • Rating and pricingnot Riskonnect
  • Claims managementnot Riskonnect
  • Billing operationsnot Riskonnect

Riskonnect

  • A self insured employer that wants to own its workers compensation loss data rather than depend on the broker or TPA system it will lose at renewalnot Duck Creek Policy
  • A risk manager building a defensible total cost of risk figure for the CFO across claims, premium, retained losses and collateralnot Duck Creek Policy
  • A third party administrator running claims for multiple clients that needs separate entity structures on one platformnot Duck Creek Policy
  • A multinational consolidating claims, safety incidents and enterprise risk registers onto one entity hierarchy for board reportingnot Duck Creek Policy

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Duck Creek Policy

  • No pricing published on vendor website; enterprise solution requires custom engagement
  • Modular product architecture means customers can mix/match components, making standard pricing impossible

Riskonnect

  • Total first year cost is dominated by implementation rather than licence; vendor professional services frequently approach the annual licence figure and the internal staff time to define data structures and migrate historic claims is a comparable third cost that never appears in the quote.
  • The platform grew through acquisitions including Ventiv and Sword GRC, so module interfaces and administration models are not uniform and staff trained on one module do not transfer cleanly to another.
  • Licensing is modular, so the price quoted for a claims deployment rises materially the first time the risk team wants ERM or business continuity, and there is little negotiating leverage once the claims data is migrated.
  • Configuration depth means most changes go through an administrator or the vendor rather than an end user, and risk teams without a dedicated system administrator find that change requests queue for weeks.
  • Historic claims data migration quality depends entirely on what the outgoing broker or TPA will export, and incomplete legacy data undermines the multi year trend reporting that was the reason for buying.

Pricing, plan by plan

Duck Creek Policy

On request

No published plan breakdown. See the Duck Creek Policy review.

Riskonnect

On request
  • Riskonnect Platform$undefined/year
    • Licensed by module, named user count and entity structure
    • Claims administration and RMIS core
    • Optional ERM, safety, continuity and third party risk modules

Which should you pick?

Choose Duck Creek Policy if

  • You need policy lifecycle management.
  • You also want product configuration.

Choose Riskonnect if

  • You need claims administration.
  • You work on Web, iOS, Android.
  • You also want total cost of risk reporting.

Questions people ask

Is Duck Creek Policy or Riskonnect better?
Neither clearly leads. Duck Creek Policy starts at On request and Riskonnect at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Duck Creek Policy or Riskonnect?
Duck Creek Policy starts at On request and Riskonnect at On request.
Does Duck Creek Policy or Riskonnect run on more platforms?
Duck Creek Policy runs on Web. Riskonnect runs on Web, iOS, Android.
What is Duck Creek Policy best used for?
Duck Creek Policy is most often used for policy administration, underwriting workflows, rating and pricing, claims management. Of those, policy administration and underwriting workflows are not what Riskonnect is typically brought in for.
What can Duck Creek Policy do that Riskonnect cannot?
Duck Creek Policy covers Policy lifecycle management, Product configuration, Rating engine, Underwriting workbench. Riskonnect covers Claims administration, Total cost of risk reporting, Policy and exposure management, Enterprise risk management.

Answered from the vendors’ own pages

Duck Creek Policy: How much does Duck Creek Policy cost?

Duck Creek does not publish pricing. Policy is an enterprise solution for insurance carriers where implementation scope, data migration complexity, and customization requirements determine total cost of ownership. Interested prospects must contact Duck Creek's sales team through their 'Talk to Sales' call-to-action.

Source
Riskonnect: What does Riskonnect actually cost?

Nothing is published. Reported deals range from roughly 35,000 US dollars a year for a narrow deployment to well over 250,000 for a multi module enterprise programme, with implementation services quoted separately and often of similar magnitude in year one.

Duck Creek Policy: Is Duck Creek Policy a modular system?

Yes, customers can adopt Duck Creek products individually (Policy, Rating, Billing, Claims, etc.) or in combination. This modularity means pricing varies based on which products and integration depth customers require.

Source
Riskonnect: How long does implementation take?

Three to six months is typical for a claims and RMIS deployment, longer where historic loss data from several brokers or TPAs has to be normalised.

Riskonnect: Why not just use the broker supplied RMIS?

Because you lose it when you change broker, and the data model serves the broker reporting rather than yours. Owning the system is the main reason companies pay for one.

Riskonnect: Is it a GRC platform or a claims system?

Both, but the claims and insurable risk core is the mature part. If you want pure GRC without claims, you are buying more platform than you need.

Share

Related pages

Other head to heads