PRICING
Priced by quote. Here's how to read one.
VCA Software prices by quote, tailored to each operation, and publishes no price list. Whichever vendors you are weighing, ask each one for the same six lines.
SIX LINES TO ASK FOR ON ANY CLAIMS SOFTWARE QUOTE
- Platform and Add-OnsVCA ClaimsCore first, then each add-on you run, one line each.
- ConfigurationScoped as defined work with an end date.
- Data MigrationThe number of claims and source systems, spelled out.
- IntegrationsOne line per connection, so each can be weighed.
- TrainingThe plan, and how it is priced.
- Support After Go-LiveWho picks up once the project closes, and how you reach them.
THE CASE FOR VCA
For a finance lead, the case for VCA is capital efficiency: the claims layer beside the systems you already run, at a fraction of the cost of a core replacement.
WHY THERE IS NO PRICE LIST
Why is VCA pricing quote-based?
Because different kinds of claims operation typically run different add-ons on the same platform.
A TPA reporting into several carriers, with SLAs, authority limits and bordereau obligations, runs more of the platform than a property firm working one program. The typical package for your kind of operation, drawn here, is where the conversation usually starts.
VCA doesn't use per-user pricing.
A TYPICAL PACKAGE, BY OPERATION
| Operation | InsuredConnect | PolicyConnect | DataBridge | ClientPortal | ClaimsPay | VCA Insights | LloydsConnect |
|---|---|---|---|---|---|---|---|
| Domestic Market | |||||||
| Adjusting Firms | InsuredConnect: not typical | PolicyConnect: not typical | DataBridge: not typical | ClientPortal: not typical | ClaimsPay: not typical | LloydsConnect: not typical | |
| TPAs | PolicyConnect: not typical | DataBridge: not typical | LloydsConnect: not typical | ||||
| MGAs and Programs | InsuredConnect: not typical | DataBridge: not typical | ClientPortal: not typical | ||||
| Brokers | InsuredConnect: not typical | PolicyConnect: not typical | DataBridge: not typical | LloydsConnect: not typical | |||
| Carriers | DataBridge: not typical | ClientPortal: not typical | LloydsConnect: not typical | ||||
| Captives and Self-Insureds | InsuredConnect: not typical | PolicyConnect: not typical | ClaimsPay: not typical | LloydsConnect: not typical | |||
| Public Entities and Government | InsuredConnect: not typical | PolicyConnect: not typical | DataBridge: not typical | ClientPortal: not typical | LloydsConnect: not typical | ||
| Law Firms | InsuredConnect: not typical | PolicyConnect: not typical | DataBridge: not typical | ClaimsPay: not typical | LloydsConnect: not typical | ||
| Lloyd's Market | |||||||
| Delegated Claims Administrators (DCAs) | InsuredConnect: not typical | PolicyConnect: not typical | DataBridge: not typical | ||||
| Coverholders | InsuredConnect: not typical | DataBridge: not typical | ClientPortal: not typical | ||||
| Lloyd's Brokers | InsuredConnect: not typical | PolicyConnect: not typical | DataBridge: not typical | ClaimsPay: not typical | |||
| Syndicates and Managing Agents | InsuredConnect: not typical | PolicyConnect: not typical | ClaimsPay: not typical | LloydsConnect: not typical | |||
Domestic Market
- Adjusting Firms
ClaimsCoreVCA Insights
- TPAs
ClaimsCoreInsuredConnectClientPortalClaimsPayVCA Insights
- MGAs and Programs
ClaimsCorePolicyConnectClaimsPayVCA InsightsLloydsConnect
- Brokers
ClaimsCoreClientPortalClaimsPayVCA Insights
- Carriers
ClaimsCoreInsuredConnectPolicyConnectClaimsPayVCA Insights
- Captives and Self-Insureds
ClaimsCoreDataBridgeClientPortalVCA Insights
- Public Entities and Government
ClaimsCoreClaimsPayVCA Insights
- Law Firms
ClaimsCoreClientPortalVCA Insights
Lloyd's Market
- Delegated Claims Administrators (DCAs)
ClaimsCoreClientPortalClaimsPayVCA InsightsLloydsConnect
- Coverholders
ClaimsCorePolicyConnectClaimsPayVCA InsightsLloydsConnect
- Lloyd's Brokers
ClaimsCoreClientPortalVCA InsightsLloydsConnect
- Syndicates and Managing Agents
ClaimsCoreDataBridgeClientPortalVCA Insights
THE PLATFORM UNDER EVERY ADD-ON
What ClaimsCore Does on Its Own
Add-ons join ClaimsCore for specific jobs. The three below are part of the platform itself, before anything is added.
- Per-Client SetupEach client or insurer has its own profile, and its rates, protocols and instructional documents carry into every claim handled for it.
- Authority and ReservesAuthority limits are set per client or per program, and every claim keeps its transactional reserve history: each movement, who made it, and which fund account it came from.
- Reporting From the ClaimSet up the UMR once and Lloyd's bordereaux fill in per claim. Statutory reporting in the US, Canada and Australia is configured from the codes, dates and dollars captured on the claim.
THE THREE DEPLOYMENT BANDS
Three Licenses, One First Step
Every deployment runs on a Standard, Enterprise or Carrier License, and every one starts the same way: discovery, where VCA maps how your claims actually move, from intake sources and assignment rules to authority levels, reporting obligations and handoffs, before anything is configured. Ask which license a quote assumes, and what would move you from one to the next.
BAND ONE
Standard License
Configured to your workflows from defaults, for an operation that already works close to them. It is the narrowest band.
BAND TWO
Enterprise License
Customizable, for an operation with more than the defaults cover: integrations through the API framework, migrated claim history and multi-program structures.
BAND THREE
Carrier License
Customizable, claims first, beside the policy and finance systems you keep, with the integrations and claim history a carrier book brings. Weigh its connection and migration lines with the most care.
The timeline for each band is published on the implementation page, alongside the five phases every deployment runs through.
READING THE QUOTE
What a Quote Should Itemize
The line between what is included and what is priced separately is where surprises live. Here is what to look for on each of the six lines.
| Line Item | What to Look for on the Line |
|---|---|
| Platform and Add-Ons | ClaimsCore first, then each add-on you actually run, named: InsuredConnect, PolicyConnect, ClientPortal, DataBridge, VCA Insights, ClaimsPay and LloydsConnect, whichever apply. DataBridge delivers your claims data into your own data warehouse or BI tool, on a schedule you set. ClaimsAI by VCA™ by the end of 2026 is an add-on on the same platform. Ask for each line marked live today or planned, with a date for anything planned. A bundle you didn't ask for is a line worth questioning. |
| Configuration | Statuses, templates, letters, workflows, authority limits and client reporting formats, named against the work they support. Look for it scoped as defined work with an end date, not as a development budget with an hourly rate. |
| Data Migration | Open and historical claims moved into the platform and checked against the source before go-live. Look for the scope stated: how many claims, from how many systems. A history deeper than the plan assumed should show up as a line while you are still deciding, not as an argument later. |
| Integrations | Each connection on its own line, so you can see what a finance connection costs next to an estimating one and decide which you want on day one. VCA's API framework carries policy-system, partner and finance connectivity, and claims financials post to your ERP or general ledger through it. See the integration list. |
| Training | The training plan stated, and how it is priced. Weigh the line against the learning curve: file handlers typically learn the platform in about 30 minutes. |
| Support After Go-Live | Who picks up after the project closes, how you reach them and how fast. At VCA that is the client services team; ask for its response commitments to be written into the agreement, as you would with any vendor. |
COMPARING VENDORS
Compare the whole cost, not the license line
License cost is the least comparable number in a claims software decision, because vendors draw the line between license and services in different places. Two quotes that look far apart on the first page can land much closer once every line above is in the same total, over the same period.
TWO QUOTES, ONE TOTAL TO COMPARE
Quote ALong license line, light services
Quote BShort license line, heavy services
Then add your own team's hours: a claims lead sits in discovery, makes the configuration decisions, checks migrated data against the source, and joins training. None of those hours lands on an invoice, and they are where a slow implementation gets expensive without anyone billing you for it.
RENEWAL
What to Settle Before a First Term
Ask any vendor one question: what can move the number between terms?
A third of VCA's enterprise clients renewed in 2026, Accelerant among them. The Renewal Record →
HAVE THIS IN WRITING
How the Renewal Works
What can move the number between terms, and where the agreement says so.
Growth During the Term
How a new program, client or line added mid-term is priced.
Service Levels
Uptime, support response and service credits, in the agreement.
Your Data at the End
How your claims data comes back to you if you leave: format, timeline and cost, in the agreement.
Questions About Pricing
How much does VCA Software cost?
VCA Software prices by quote, tailored to each operation, and publishes no price list. VCA doesn't use per-user pricing. To compare a VCA quote with any other, ask every vendor for the same six lines: platform and add-ons, configuration, data migration, integrations, training, and support after go-live.
Can we start with VCA ClaimsCore and add the rest later?
Yes. VCA ClaimsCore is complete on its own, no add-on is sold without it, and a client running only ClaimsCore is never at a disadvantage. Configure what matches the work, skip the rest, and add it later.
How should a storm season figure in a claims software quote?
Describe your heavy season while the quote is being built, so it reflects your real year and not your quietest month. Then ask every vendor, VCA included, to put in the agreement how a season like that is treated during the term.
Is VCA built for operations our size?
VCA ClaimsCore is the same platform whether it runs a small independent adjusting firm or a carrier deployment. VCA serves independent adjusting firms, third-party administrators, MGAs, specialty carriers, captives and self-insured organizations, and Lloyd's market coverholders. It is built for operations that need to be live in weeks, beside the policy system they already run; a multi-year core replacement is a different purchase.
Who should be on the call when you build the quote?
Whoever knows how a claim is worked in your shop, usually a claims manager or an ops lead, plus the person who owns the budget. IT can join later, once the conversation reaches connections. Getting the right two people in one conversation answers more than a round of RFP email will.
Do we need to sit through a demo before we can get a quote?
No. Some buyers want to see the platform and then talk money, and some want it the other way around. Either order works, and the demo is a working session on your claims flow whichever one you pick.
Get a quote built on your operation
One conversation about how your claims move, then a quote in writing. A quick no is fine too.
- Tell us how a claim is workedThe programs and clients you administer, and how your claim year runs, flat or shaped by weather.
- We walk through what you connect and moveEach system VCA would connect to, and the claim history that moves with you.
- You read it against any otherLine by line, with your finance lead, as you would read any vendor's quote.
Not ready to talk? The Questions to Put to Any Vendor →