ACTELUS
Discuss a workflow

Systems and demos

This page is called Systems and Demos rather than case studies, because a case study implies a finished client engagement with a measured outcome. Neither system here has been published as one, so calling them that would be a lie that is easy to tell.

Systems
Two
Data shown
Synthetic only
Client engagements
None published
Verified outcomes
None yet

Four labels, and their meaning

Every demonstration on this site carries one of these labels, in the panel itself, so you never have to guess what you are looking at.

  • Working demo

    Software you can be shown running, end to end, on data we can share. What you see is what it does.

  • In development

    Built and working on sample data, with parts still unfinished or deliberately switched off. We will say which parts.

  • Illustrative interface

    A mockup that shows the shape of an output. It is not a screenshot of a running product, and it is never presented as one.

  • Not offered yet

    Something that exists but is not for sale yet, usually because a control or a decision is outstanding.

There is a fifth category this page does not have yet: a verified customer outcome. When one exists, it will appear here with the client named, with their permission, and with the figure sourced.

What has been built

Supplier Price Update Sprint

Distributors receive a new supplier price list and have to work out, row by row, which of their own catalogue lines changed. This compares the two lists against the catalogue and produces a change file a buyer can review.

In development Data used: Synthetic distributor catalogue and supplier price lists. No client data.

See what the sprint includes

What it does

  • Matches supplier rows to catalogue lines and reports the change per line.
  • Separates confident matches from rows that need a human decision.
  • Produces one import-shaped file plus a list of unmatched rows.

What it does not do

  • Write to a live ERP, pricing table or catalogue.
  • Guess a match it is not confident about.
  • Replace the approval and import process you already run.

Commercial Insurance Submission Engine

An account manager re-reads a submission package to find what is missing or contradictory before it goes to a carrier. This reads the package and lists findings with a link back to the page each one came from.

Live product Data used: Shipped as PacketSlip. The demonstration here ran on synthetic ACORD 125 and 126 documents.

Open PacketSlip

What it does

  • Reads a package of PDF and text files and lists findings with their source.
  • Flags missing fields and values that conflict between documents.
  • Produces a summary for the account manager to check before the next step.

What it does not do

  • Replace an agency management system.
  • Underwrite, quote, bind or submit anything to a carrier.
  • Send a message or take an action without a person approving it.

What the outputs look like

Supplier price reconciliation

The change file is the deliverable. Confident matches are separated from rows a buyer has to decide on, which is the part that saves the time.

price-change-review.xlsx
SKU Old New Change Outcome
CBL-TE-2.5-100 68.40 72.10 +5.4% Matched
MCB-B16-6KA 3.95 4.12 +4.3% Matched
HVAC-FLT-G4-595 11.20 11.20 0.0% No change
CU-8W-SPD 142.00 151.75 +6.9% Matched
— — 18.60 — Needs review
TRK-LGT-3C-2M 44.50 41.90 -5.8% Matched
412 catalogue rows compared · 381 matched · 23 flagged for review · 8 supplier rows with no catalogue match Illustrative interface Illustrative interface. Synthetic catalogue and supplier price list data, not a client file.

Submission package review

Each finding carries the document and page it came from, so checking the system takes seconds rather than re-reading the package.

submission-review · package-0042
Finding Status
Requested effective date is blank Needs review
Annual payroll differs between the application and the supplement Needs review
Prior carrier named without a policy number Needs review
Insured entity name matches across all three documents Checked
Classification code present and consistent Checked
3 items for the account manager to resolve · 2 checks passed · every finding links to its source page Illustrative interface Illustrative interface built from synthetic ACORD 125 and ACORD 126 sample documents. No agency or insured data.

What the labels mean

Every panel above carries one of four labels, in the panel itself rather than in a footnote, and both systems run on data generated for the purpose. What each label means, and the rule the whole site is written to, is on the claims page.

Judge it against your process

The useful test is not whether a demo looks convincing, but whether it produces the output your team would actually act on. Describe the process and we will tell you honestly whether it is close.

Discuss a workflow What we build