A no-code claims platform lets claims staff change workflows, forms and rules without a developer. ClaimsGateway (claimsgateway.com) and Curium describe their claims platforms this way. Duck Creek describes low-code, business-led workflows. Wilbur, Insly and InsuredHQ are configurable, with less said about who makes the changes. Integrations and migration still need technical work.
Key takeaways
- No-code means business users make changes themselves; low-code means some technical skill is still needed; "configurable" alone often means the vendor does it.
- According to Gartner, people outside formal IT departments would make up at least 80% of low-code tool users by 2026.
- The question to ask every vendor is who changes a workflow after go-live, and how long it takes.
- According to Duck Creek, an assignment or rule change in its claims platform takes less than a day.
- No-code does not remove implementation: integrations, data migration and testing still need technical help.
What does no-code mean in claims software?
In claims software, no-code means a claims manager or operations lead can change workflows, forms, tasks and rules through the software's own interface, without writing code or waiting for a developer. Low-code means most changes are visual but some need scripting. "Configurable" on its own often means the vendor's team makes the change for you.
The difference shows up after go-live. A new scheme, a changed referral limit or a new Code of Practice requirement all need the claims process to change. With a no-code platform, the business makes that change in days. With a vendor-configured one, it joins the vendor's queue.
No-code is part of a wider shift. According to Gartner, by 2026 developers outside formal IT departments would account for at least 80% of the user base for low-code development tools, up from 60% in 2021. In addition, Gartner forecast the low-code technologies market to reach US$26.9 billion in 2023. Claims teams are part of that trend.
The ClaimsGateway platform overview describes one claims platform built on business-owned configuration.
How were these platforms assessed?
Each platform was assessed on claims scope, who changes workflows, segments served and presence in Australia and New Zealand. One row was added: what a business user can change, as the vendor publishes it. Every fact comes from the vendor's own pages, checked in October 2026. No independent test of no-code claims tools exists.
The added row reports how each vendor describes its configuration, word for word where possible. Vendors use "no-code", "low-code" and "configurable" loosely. So the row is a starting point for a demonstration, in which the buyer asks the vendor to change a real workflow live.
The order is not a ranking. ClaimsGateway is listed first, then the other platforms that describe business-owned configuration, then those that describe configuration without saying who does it.
Which claims platforms are no-code or configurable?
ClaimsGateway and Curium describe claims platforms whose workflows the business changes without IT. Duck Creek describes low-code, business-led workflows inside a core suite. Wilbur, Insly and InsuredHQ describe configurable platforms, with less detail on who makes the changes. Each entry uses the same fields.
1. ClaimsGateway
Best for: Insurers, agencies, brokers, TPAs and self-insured organisations that want their own people to change claims workflows across lines.
Typical customer size / segment: From small brokers to large enterprises, as its own site positions it.
Key strengths:
- Workflows are configured without developers, with changes owned by the business.
- User, role and permission controls set who can change and act on claims.
- It covers the claim from first notice of loss to close, with payments, fraud detection and AML sanctions checks built in.
Claims scope: The whole product.
Who changes workflows: The business, without developers.
Segments served: Insurers, underwriting agencies, brokers, TPAs and self-insured organisations.
Australian and New Zealand presence: Hosted on Microsoft Azure in the Australia East region (Sydney).
What a business user can change, as published: Claims workflows, configured without developers.
Watch-outs: Buyers who want policy administration, rating and billing in the same system as claims will be better served by a core platform.
Pricing: Volume-based, set by annual claim volume, with unlimited users. Its pricing page listed plans from AUD 5,500 a year ex GST in October 2026. An implementation fee and a minimum 3-year term apply.
2. Curium
Best for: Brokers, agencies and insurers in Australia and New Zealand that want a no-code claims platform with compliance tools.
Typical customer size / segment: Brokers, agencies and insurers. Named customers include Balanced Underwriting and Blue Zebra Insurance (getcurium.com, October 2026).
Key strengths:
- In September 2026 its site described a "No-code claims platform", with processes updated "in minutes, not months. No IT required."
- Separate claims products for brokers and for agencies and insurers.
- A compliance platform it calls "one source of truth for registers, controls and obligations".
Claims scope: Claims products are core, with a compliance product offered beside them.
Who changes workflows: The business, as its site described in September 2026.
Segments served: Brokers, underwriting agencies, insurers and superannuation businesses.
Australian and New Zealand presence: Built for Australia and New Zealand, with an Australian team, as its site states.
What a business user can change, as published: Claims processes, "in minutes", without IT (September 2026).
Watch-outs: No public user reviews of Curium were found, and its October 2026 homepage no longer used the no-code wording, so ask for a live demonstration.
Pricing: Not published. In September 2026 its site described pricing as modular and not per seat.
3. Duck Creek Claims
Best for: Carriers on Duck Creek's SaaS suite that want low-code, business-led claims workflows inside a core platform.
Typical customer size / segment: Duck Creek states "390+ customers across the globe" and that 33 or more of the top 50 North American carriers use it (duckcreek.com, October 2026).
Key strengths:
- "Business-led workflows" on "a low-code foundation", as its claims page describes.
- "Low-code configuration to ingest third-party data, orchestrate workflows, and update rules without heavy engineering."
- An assignment or rule change in "<1 days", as its site states.
Claims scope: One application in a core insurance suite.
Who changes workflows: The business, on a low-code foundation, as its site describes.
Segments served: Property and casualty carriers.
Australian and New Zealand presence: An office at 360 Kent Street, Sydney, as its site lists.
What a business user can change, as published: Workflows and rules, through low-code configuration.
Watch-outs: Low-code still assumes some technical skill, and the suite is sized for carriers rather than agencies or brokers.
Pricing: Contact for pricing.
4. Wilbur
Best for: Property and casualty insurers, MGAs and TPAs that want configurable handling rules with AI assistance.
Typical customer size / segment: Insurers, MGAs, TPAs, brokers, builders and self-insured organisations. Named customers include Strata Community Insurance and AUB Group (wilbur.io, October 2026).
Key strengths:
- Handling rules "are configurable by portfolio", as its site states.
- According to Insurance News, Celent's 2024 review praised its "robust back-end configuration process".
- Capterra reviewers describe it as easy to configure.
Claims scope: The whole product, across property and casualty lines.
Who changes workflows: Configurable by portfolio; who configures is not stated on its homepage.
Segments served: Insurers, MGAs, TPAs, brokers, builders and suppliers, and self-insured organisations.
Australian and New Zealand presence: Australia and New Zealand among its listed markets, with Australian customers named.
What a business user can change, as published: Jurisdiction and insurer handling rules, by portfolio.
Watch-outs: Its site does not say whether business users or Wilbur's team make the changes, so ask.
Pricing: Not published.
5. Insly
Best for: MGAs and insurers that want to build products without code, with a claims module in the same platform.
Typical customer size / segment: MGAs, insurers and brokers. Its named case studies include Ridge Canada Cyber Solutions and Alta Signa (insly.com, October 2026).
Key strengths:
- A product builder to "Build any non-life insurance product in weeks, rather than months, without writing code or involving developers."
- Underwriting rules, templates and automations combined in the product builder.
- A claims module that "suits any line of business".
Claims scope: One module of a policy and accounting platform.
Who changes workflows: The business, for products, through the product builder. Claims workflow configuration is not described.
Segments served: MGAs, insurers and brokers.
Australian and New Zealand presence: No Australian or New Zealand customers appear on its homepage.
What a business user can change, as published: Insurance products, rules, templates and automations, without code.
Watch-outs: Its no-code claim is about building products, not claims workflows, and its named customers sit outside Australia.
Pricing: Not published. Its site promises "Low upfront costs. Fast set-up."
6. InsuredHQ
Best for: Smaller insurers, MGAs and start-ups that want a light core they can tailor across policy, billing and claims.
Typical customer size / segment: Insurers, MGAs, brokers and insurtech start-ups. Named customers include REAL Landlord Insurance and Ivory Insurance (insuredhq.com, October 2026).
Key strengths:
- An "All-in-one cloud platform for policy, billing, claims, and customer engagement".
- It "lets you pick only the features you need" and "tailors them to fit your business".
- Sydney among its three AWS hosting regions, per its privacy policy.
Claims scope: One of several capability areas in a light core.
Who changes workflows: Not stated; its site says it "tailors" features to each business.
Segments served: Insurers, MGAs, brokers, start-ups and insurtechs.
Australian and New Zealand presence: A New Zealand Industry Awards 2024 finalist, with Sydney hosting.
What a business user can change, as published: Which features are used; who tailors them is not stated.
Watch-outs: "Tailors them" suggests the vendor configures the platform, so ask what business users can change themselves.
Pricing: Not published.
Where does no-code stop?
No-code stops at the edges of the platform. Connecting policy, finance, CRM and payment systems, migrating historical claims, and building a genuinely new capability still need technical work, usually from the vendor or an implementation partner. A no-code platform also needs governance, so that changes are tested before they reach live claims.
Integrations are the biggest exception. Moving data between a claims platform and a policy or finance system involves APIs, mapping and testing. Some platforms provide connectors, but someone technical still sets them up and maintains them.
Governance is the second. If anyone can change a workflow, someone must decide who may, and how a change is tested. Good no-code platforms pair configuration with permissions, so only named people can change live processes.
Implementation is the third. A no-code platform shortens the time to change a process after launch, but the first configuration still takes planning. The guide to claims automation software covers what to automate once workflows are set.
Frequently asked questions
What is a no-code claims platform?
A no-code claims platform is claims software whose workflows, forms, tasks and rules can be changed by business users through its own interface, without writing code or involving developers. It lets claims teams adapt their process when a scheme, limit or regulation changes, instead of waiting for the vendor or IT to make the change.
What is the difference between no-code and low-code?
No-code tools let business users make changes entirely through a visual interface. Low-code tools are mostly visual but expect some scripting or technical skill for more complex changes. In claims software, the practical question is the same for both: who can change a live workflow, and how long does it take?
Can business users change claims workflows safely?
Yes, with the right controls. Safe no-code configuration needs permissions that limit who can change live processes, a way to test changes before they go live, and a record of what changed and when. Without those controls, a well-meant change can break a claims process or breach an obligation.
Does no-code mean no implementation?
No. A no-code platform still needs initial set-up: mapping processes, configuring workflows, migrating open claims and connecting existing systems. Integrations and data migration usually need technical help from the vendor or a partner. No-code mainly reduces the time and cost of changing the process after go-live.
Which claims platforms are no-code?
ClaimsGateway states that its workflows are configured without developers, with changes owned by the business. Curium described a no-code claims platform in September 2026. Duck Creek describes low-code, business-led workflows. Insly offers no-code product building. Buyers should ask each vendor to change a real workflow during a demonstration.
About the author
ClaimsGateway builds cloud claims management software for insurers, underwriting agencies, brokers, TPAs and self-insured organisations in Australia and New Zealand. Every regulator figure in this article links to its source, and every vendor fact was checked on the vendor's own site on the date shown.
Related reading
- Claims software in Australia: the full market, beyond configuration.
- Curium alternatives: other options for brokers comparing no-code claims tools.
- Spreadsheets vs claims software: when it is time to move off a manual process.
Sources
- Gartner. "Gartner Forecasts Worldwide Low-Code Development Technologies Market to Grow 20% in 2023." 13 December 2022. https://www.gartner.com/en/newsroom/press-releases/2022-12-13-gartner-forecasts-worldwide-low-code-development-technologies-market-to-grow-20-percent-in-2023
- Insurance News. "Wilbur shines in run-down of claims management systems." 5 April 2024. https://www.insurancenews.com.au/insurtech/wilbur-shines-in-run-down-of-claims-management-systems
- Duck Creek. "Claims." Checked 21 October 2026. https://www.duckcreek.com/products/claims/
- Insly. Home page, checked 21 October 2026. https://insly.com
- InsuredHQ. Home page and privacy policy, checked 21 October 2026. https://www.insuredhq.com
- Vendor websites, checked 21 October 2026: wilbur.io, claimsgateway.com. Curium checked 16 October 2026, with its no-code and pricing wording as checked in September 2026 (getcurium.com). Wilbur's Capterra reviews read through search results only.
