Claims operations, end to end, on one system.
Built for third-party claims investigation firms and the insurers who hire them. Intake through settlement to billing, across multiple legal entities, including the document generation and correspondence that actually consumes an adjuster's day.
Active cases
1,518
+4.2%
Awaiting approval
23
−11%
Nearing lapse
35
+2
Billed this month
$8.5M
+6.1%
Cases nearing lapse
| SIN-24187 | Carrier A | Monterrey | 41d | |
| SIN-24203 | Carrier B | Guadalajara | 34d | |
| SIN-24219 | Carrier C | CDMX | 29d | |
| SIN-24240 | Carrier A | Mérida | 22d | |
| SIN-24266 | Carrier D | Chihuahua | 16d |
Case load by office
- CDMX82
- Monterrey71
- Guadalajara64
- Mérida43
- Chihuahua31
- Occidente26
Claims processed for the market's major carriers.
These are the insurers whose claims flow through the platform in production. They are clients of the firm operating the system, not of Novyant.
What it handles today.
- Claims processed per year
- 25,000Claims processed per year
- Concurrent users
- 300Concurrent users
- Legal entities on one system
- 28Legal entities on one system
- Fields tracked and analysed per case
- 200+Fields tracked and analysed per case
Figures from the deployment running now, not a capacity estimate.
Built for the firms doing the work.
Claims investigation and adjusting firms
Independent firms hired by carriers to investigate, document and settle claims, especially those operating as several legal entities under one roof.
Insurers with in-house adjusting
Carriers running their own field operation who need the same lifecycle discipline without replacing a core policy system to get it.
Multi-office, multi-region operations
Where a case belongs to an office, a region and a legal entity at once, and the permission model has to reflect all three without becoming unmanageable.
The toolset it was built to retire.
The firm we built this for was processing roughly 25,000 claims a year on a set of tools that each did part of the job and none of it together.
- 01SmartSheet for case tracking and management dashboardsRetired
- 02Excel workbooks carrying 93 tracked fields per caseRetired
- 03Word templates for every letter, report and settlement documentRetired
- 04Email threads acting as the system of record for carrier correspondenceRetired
- 05Shared drives holding photographs and evidence, organised by conventionRetired
- 06Individual memory for where any given case actually stoodRetired
Twenty-eight legal entities, eight offices, and one place a case actually lives.
The whole lifecycle, not a slice of it.
Most claims software handles the parts that are easy to standardise. The difficulty is everything around them.
Multi-entity architecture
Every case, office, template and invoice belongs to a legal entity. A user can hold different roles in different entities, and every query is scoped accordingly. Designed in from the first table, because it cannot be added later.
Staged case lifecycle
Each stage is a defined step with its own rules about who can act and what must be recorded. The case's status is where it is in the process, not a dropdown someone remembers to update.
Governed document generation
Letters, reports and the full adjustment file generated from templates owned by a specific entity and carrier, with the correct letterhead, legal language and formatting.
Correspondence in the case record
Carrier email and WhatsApp messages attached to the case rather than living in one adjuster's inbox and another's phone.
Role-based access
Director, manager, supervisor, regional supervisor and adjuster, plus intake, control, billing and IT functions, each seeing only the cases and offices they are entitled to.
Reserves, settlement and billing
Precautionary reserves, settlement agreements, invoicing issued by the correct legal entity under its own tax identity, and collections tracked to closure.
Fraud and irregularity review
Flags and review steps inside the workflow, so a questionable case is handled during the investigation rather than discovered after payment.
Dashboards by role
Executive, operational, financial and catastrophic-event views, each scoped to the entities and offices the person viewing them is allowed to see.
Search and archive
Every closed case retrievable with its documents and correspondence years later, which is exactly when a dispute tends to surface.
Collecting from the insured, without leaving the case.
The adjuster writes inside the case and sends it. Email goes out from that adjuster's own mailbox, so the insured sees a person rather than a no-reply address; WhatsApp goes out as a pre-approved template. The return leg is the automatic part. Replies and their attachments are matched back to the case by conversation thread and filed against it, with nothing depending on someone remembering to forward anything.
Hover or select any step to see what the system does at that point.
One page per stage, and the stage is the status.
Moving a case forward is the act of completing a stage, which means status is always accurate without anyone maintaining it.
Intake
Insured, policy, carrier, loss type, line of business, and third parties where they exist. Once saved a case cannot be deleted, only closed with a documented reason.
Capture once. The report assembles itself.
No separate write-up at the end. The document builds from what the stages already captured, in the carrier's own format.
Step through how the report is produced.
Adjustment report
- Reference
- [ empty ]
- Insured party
- [ empty ]
- Policy
- [ empty ]
- Loss type
- [ empty ]
- Amount claimed
- [ empty ]
- Amount determined
- [ empty ]
Template
The carrier's own format, owned by one legal entity: their letterhead, their sections, their required fields. Empty, waiting for a case.
Where your data lives, and who can reach it.
Claims files hold medical reports, financial records and personal data belonging to people who never chose to deal with us. That shapes how the system is built and where it runs.
Your environment or ours
The platform can be deployed inside cloud infrastructure you own and control, in which case we operate the system and never hold your data. Where you would rather we host it, each deployment is isolated. It is your call, and it is made before anything is built.
Access is scoped, not trusted
Role and legal-entity scoping is enforced at the query level rather than hidden in the interface, so a user cannot reach a case outside their entitlement even by URL. Sessions time out, administrative access requires multi-factor authentication, and access can be revoked centrally.
Encrypted at rest and in transit
Databases and document storage are encrypted with managed keys under annual rotation, and every connection is encrypted end to end. Credentials live in a managed secret store rather than in configuration files.
Monitored continuously
Threat detection, posture monitoring against recognised industry benchmarks, a web application firewall, vulnerability scanning and network flow logging, with alerting routed to a person on high and critical findings rather than into a dashboard nobody opens.
Secure development, enforced by the pipeline
Static analysis runs on every pull request. A dependency audit fails the build on any high or critical advisory. Dynamic scanning runs weekly against the test environment. Production branches are protected, so nothing reaches them without review.
Auditable after the fact
Privileged actions and document access are written to an append-only audit log. When a carrier or a court asks months later who opened a file, when, and from where, the answer exists and can be produced.
We hold no formal certification today and will not imply otherwise. What we can provide is documented control evidence, our completed responses to the security questionnaires the major carriers use, and a named contact for vulnerability disclosure.