IMPLEMENTATION
Implementation in Weeks, Not Years
Every VCA implementation starts with discovery and lands in one of three license bands, each with a published range you can plan around.
VCA is built to go live in weeks, beside the policy system you already run. A multi-year core replacement is a different purchase.
VCA CLAIMSCORE: THE THREE LICENSE BANDS, TO SCALE
Standard LicenseLive in 3 to 4 weeks
Enterprise LicenseLive in 8 to 16 weeks
Carrier LicenseLive in 12 weeks to 6 months
- Standard LicenseVCA ClaimsCore as it ships, configured to your workflows.
- Enterprise LicenseCustomizable beyond the Standard License configuration.
- Carrier LicenseCustomizable, beside the policy and finance systems a carrier keeps.
Discovery comes first on every band, and which band you are in is scoped at quote.
BEFORE YOU COMMIT
The slow end is published on purpose
An operation replacing a system it has run for a decade needs to see the long end of the range, not only the short one, so the Carrier License band is published beside the other two.
Speed comes from focus. VCA concentrates on the essentials of claims and does not get pulled into everything else a suite has to build. The weeks go to configuring the claims layer around how your team already works.
FIVE THINGS TO ASK FOR
Before you sign, ask every vendor you compare, VCA included, to put these in writing:
- Your band, and what would move you out of it
- The implementation fee, and what it includes
- What configuration changes cost after go-live
- Response times and service levels
- How your claims data comes back when an agreement ends
BETWEEN SIGNING AND GO-LIVE
How Implementation Runs, Discovery First
What happens between signing and go-live, from the workflow assessment to live claims.
| Step | What Happens |
|---|---|
| Discovery | It starts with a workflow assessment of how your team works: claims intake and assignment, day-to-day claims handling, billing and reporting. |
| Configuration | VCA ClaimsCore is set up around your process: statuses, templates, letters, workflows, and authority limits that match how a claim really gets handled. We configure what matches the work and skip the rest. |
| Data Migration | When your claims come from another system, open and historical claims can move into ClaimsCore. |
| Training | Before user training, VCA reviews your account, and you choose what your team is trained on. |
| Go-Live | Live claims run in ClaimsCore, and configuration keeps adjusting as your team settles in. |
DATA MIGRATION
Your Claims Data, in and Out
Open and historical claims can move into VCA ClaimsCore.
COMING IN
Open Claims
Move with the rest of the book and keep being worked in ClaimsCore from the switch-over date.
Claim History
Closed claims come across as history, so the record behind your open book sits in the same platform.
A Lloyd's DCA's Migration
Vanguard Claims moved 36,000 claim files onto VCA in four months.
GOING OUT
While You Run VCA
DataBridge, an add-on to ClaimsCore, delivers your claims data into your own data warehouse on a schedule you set, as often as hourly.
TRAINING AND SUPPORT
Short Training, and Configuration That Keeps Up
Your team is trained on an account already set up for its work, and client services picks up after go-live.
TRAINING
30 to 60 minutes of training is what a file handler typically needs
Before user training, VCA reviews your account, and you choose what your team is trained on.
AFTER GO-LIVE
Client services picks up when the project closes
Reach client services at clientservices@vcasoftware.com. Configuration keeps evolving as new programs, clients or lines arrive, on one rule: configure what matches the work, skip the rest, add later.
Questions About Implementation
How long does a VCA implementation take?
Weeks, not years. Every VCA implementation starts with discovery, which maps how your claims actually move before anything is configured. On a Standard License, configured to your workflows, VCA ClaimsCore goes live in 3 to 4 weeks. An Enterprise License deployment runs 8 to 16 weeks, and a Carrier License deployment 12 weeks to 6 months. Which band you are in is scoped at quote.
What does implementation cost?
Which band you are in is scoped while your quote is built. For a carrier, a claims layer beside the systems it keeps comes in at a fraction of the cost of a core replacement. Ask for the implementation fee and what it includes in writing before you sign.
Does VCA replace our policy administration system or ERP?
No. VCA is built to go live in weeks, beside the policy system you already run. Your policy administration system keeps administering policies and your ERP keeps the books. VCA ClaimsCore runs the claims layer between them and its claim transactions are reachable through VCA's APIs for a custom link to your ERP. A multi-year core replacement is a different purchase.
Do we need our IT team to run the implementation?
Not to lead it. The people who work the claims shape the configuration, and IT joins where another system connects. Policy data comes onto the claim through PolicyConnect, an add-on to VCA ClaimsCore. Finance and partner systems connect through VCA's API framework.
Can you migrate our existing claims, including the open ones?
Yes. Open and historical claims can move into VCA ClaimsCore. Vanguard Claims moved 36,000 claim files onto VCA in four months.
Can we get our claims data back out?
Yes, on a schedule, with DataBridge, an add-on to VCA ClaimsCore that delivers your claims data into your own data warehouse, as often as hourly. How your data comes back at the end of an agreement is a contract term: ask for its format, timeline and cost in writing before you sign.
How much training will our adjusters need?
Typically 30 to 60 minutes of training for a file handler. Before user training, VCA reviews your account, and you choose what your team is trained on.
Who do we contact after go-live?
Client services, at clientservices@vcasoftware.com, once your claims are live. Ask for response times and service levels in writing before you sign.
Bring us a claim where the promise was hard to keep
Tell us what you're replacing and how much claim history has to move. We'll walk through which band fits and why, using a claim like yours worked in the product as it runs today, and you can set our answer beside your current system's.
Request a Demo