Underwriters Technologies
for CareWest

What we are proposing is not a migration from Sapiens. It is a consolidation. CareWest's data does not live in a single system — it lives across dozens of systems, spreadsheets, and manual processes accumulated over years. The right framing for this engagement is: Ink Digital's platform becomes the platform of reference. Every source feeds in. Data is normalized. From day one, there is one system of record.

Our platform is a production workers' compensation core system. We have WC carrier customers live today. Our team has direct UNIT-STAT implementation experience. Our agentic AI is in production. And we are already inside CareWest's data.

The platform handles any line of insurance rating codes — standardized or otherwise. Workers' compensation is in production with current customers. Class codes, experience modifications, schedule credits and debits, credit/debit tables, eligibility rules, and cap percentages are all configurable by operations staff without a development engagement or PS involvement.

Day-to-day WC quoting is handled natively by the rating engine. Complex and multi-entity accounts are fully supported — this is not a partial RES replacement. Underwriters can export rating worksheets to Excel and import class code and payroll data via spreadsheet to build a submission.

Inbound submission API accepts structured data from any source via POST. Core system stores ACORD data and loss runs in structured form — not as attached PDFs. Document extraction from ACORD forms is native. Submission pipeline tracking with status and aging is operational. Post-bind data push to agents — dec pages, endorsements, claims status — is live, including IVANS Download for direct AMS delivery.

We have existing Applied Epic integrations in production. The Applied Epic Leads Inbox API — REST/JSON, tenant ID and API key authentication — is a near-term committed roadmap item. The remaining work is schema mapping and certification against Applied's sandbox. Estimated delivery: one quarter out.

The employer-facing portal for direct payroll submission and inbound payroll API were fully built and operational as part of a complete WC carrier platform developed for a venture-backed operation during COVID. That company is no longer in existence — the principal passed away and the operation was wound down. We were left with unpaid invoices. We own the code outright. That payroll capture capability is ours to deploy.

Image-based PDF extraction is in production across multiple document types — loss runs, property schedules, driver schedules, and more complex formats including multi-entity and specialty schedules.

Direct integration with payroll providers is on committed roadmap. Our recommended approach is Finch — a unified payroll API aggregator covering 220+ providers including ADP and Paychex. One integration, not dozens.

Centralized audit pipeline with status tracking and overdue flagging is operational. Audit completion to billing handoff requires no manual re-entry. Flexible report formatting handles complex multi-entity accounts.

The platform has a documented integration pattern for external TPAs. Policy data changes push outbound automatically. Claims and reserve data feed back inbound. This is operational.

We do not have an existing integration with CareMC or Corvel. Any experienced integration team will tell you the same thing: the limiting factor in TPA integration is almost always the TPA's own API surface and their willingness to expose it. Many TPA systems are mature, have strong opinions about remaining the system of record, and have limited API documentation. Our architecture handles the integration side cleanly.

We would welcome an introduction to CareMC's technical team early in implementation planning.

Our team has hands-on UNIT-STAT implementation experience from prior work at Virtual MGA and from direct system builds for professional liability carriers. We know the WCIRB Statistical Reporting Specifications in detail. We have worked through CDX submission via SFTP, BEEP validation, error correction cycles, and multi-year correction workflows. This is not greenfield capability — it is team-level institutional knowledge.

We understand what is involved: WCSTAT/ASWG fixed-width record generation at byte-level precision, CA-specific code table maintenance with annual WCIRB updates, CDX/SFTP integration, BEEP error handling workflows, and submission lifecycle management including historical corrections.

We also understand the PALS question. CareWest's concern is not just the Sapiens migration — it is that the upstream data preparation function that fed the UNIT-STAT pipeline may have lived in PALS as a Sapiens component. That function needs to be rebuilt on the new platform, not just migrated.

The platform includes a drag-and-drop report and dashboard builder that operations staff and department heads can use without IT involvement. Pre-configured templates cover all operational areas at implementation — claims oversight, renewal pipeline, premium audit pipeline, risk control activity, executive and finance views, and broker performance.

Role-based dashboard access is native. A claims manager sees their operational data. A broker sees their book. An executive sees financial and loss ratio views. Sensitive data does not cross role boundaries without explicit configuration.

We are already heavily integrated with HubSpot. The CarePoint project currently underway with CareWest is moving the bulk of the broker sync, event-driven notifications, and data flow into production as active work. What remains after the CarePoint build is a natural extension of what is already built — not a new integration effort.

Broker record read/write API covering contacts, licenses, and appointments is operational. Event pushes to HubSpot from premium audit, submission, risk control, and claims events are covered within the active CarePoint scope. Producer license expiry alerts follow the same event architecture.

Task assignment uses a configurable tagging system. Triggers are built for every policy lifecycle event: new business, endorsement, renewal, cancellation, and reinstatement. Claims triggers cover any change in loss reserve, claim amount, IBNR, and LAE.

Recommendation tracking with full status history persists across policy years. Account history is accessible via direct search or Kanban view. The Kanban is worth noting — it is the view our own team uses internally. We did not build it for a client demo. We built it because it is the most effective way to understand what is open, what is overdue, and where attention is needed.

CareWest can operate all states from a single instance. No separate groups or siloed deployments. Cross-state aggregate reporting runs in a single query against the unified data model.

Adding a new state is configuration work, not development — with two documented exceptions requiring CareWest's domain input: West Virginia underground mining specialty class codes, and Longshore and Harbor Workers (USL&H) federal coverage. Both are achievable. Neither is a blocker.

The reason this response exists is because the CarePoint engagement demonstrated that Ink Digital can execute inside CareWest's environment. CareWest is not evaluating a hypothetical portal — they are watching their portal get built.

Broker agencies and insureds are first-class data entities in the API. Full read/write REST coverage across policy, claims, audit, and billing. API stability is maintained through all product and rating configuration changes — the only scenario requiring a new API field is a brand-new WC rating factor, which is a near-theoretical event given the long-term stability of WC rating methodology.

Production references: CareWest (active build), Bluesky (live production deployment). Our team also built a complete end-to-end WC carrier platform for a venture-backed operation — full-stack carrier capability demonstrated on this platform.

The platform's native drag-and-drop reporting layer handles operational reporting without IT. For external BI tooling, data science, and agentic AI workflows, the platform exposes well-structured, granular data via webhooks that fire on every significant event.

Those webhooks point at any external endpoint — including Snowflake via Snowpipe for near-real-time ingestion. CareWest can replace SAP Business Objects with UT's native layer, their own BI tooling against a Snowflake warehouse, or both. The pipeline to get data wherever CareWest needs it is already built and operational.

The carriers that get the most out of this platform invest in defining their processes before configuring the system, and then hold those processes stable. We have tried it the other way. It does not produce better outcomes — it produces drift, inconsistency, and staff who are never sure what the current process is. CareWest is at exactly the inflection point where that investment pays the highest return.

• Document templates: AI-generated within client-set parameters. Fully self-service.
• User-defined fields: Adding a field to a screen is self-service. Logic built on custom fields requires UT.
• Workflow and task routing: Defined during implementation, held stable. Changes require deliberate UT engagement.
• Underwriting criteria: Fully self-service, changeable on the fly at any time.
• Upgrade safety: All configurations survive platform releases. No exceptions.

The challenge is not Sapiens. The challenge is that CareWest's data does not live in one place. It lives across dozens of systems, manual processes, and spreadsheets accumulated over years. A migration strategy that focuses on extracting from Sapiens misses the actual problem.

Our approach: become the platform of reference. We do not migrate CareWest from Sapiens — we build the correct data model in UT's platform, instrument every source system, normalize the data, and establish UT as the single system of record. Sapiens is one source among many. The migration is a data consolidation, not a platform swap.

Our team has completed migrations across multiple legacy platforms including Aetna Gemini. Post-migration reconciliation is a defined process: parallel operation period, automated record-count and financial reconciliation against source systems, exception reporting, and sign-off at each data domain before any source system is decommissioned.

First: You are not starting from zero with us. The CarePoint work has already demonstrated how we operate. That matters more than any capability checklist.

Second: The most important work in this engagement happens before a line of code is written. It is the process definition work — mapping what CareWest actually does, where the data actually lives, and what the right workflows actually are. We treat that phase as seriously as the technical build. Carriers that skip it get a fast implementation and a slow platform. Carriers that do it right get a system that runs the way they actually want to run.

We are ready to go deeper on any of the fifteen areas above. We have requested CareWest's UNIT-STAT sample files, which will allow us to sharpen the Question 6 answer into a specific implementation commitment.