End-to-end workflow automation

custom-built for every insurance team.

Tell the Architect how your team works. It builds the tables and actions, and every run keeps a record.

Demo: the Email table of Submission Triage, a made-up London market underwriter. Five broker emails arrive with their attachments. The triage agent reads each one against the Appetite Rules table and fills in the class, the appetite with a one-line reason, and the priority: three are In appetite, one is Refer (political violence in Ghana goes to the class underwriter) and one is Decline (offshore Gulf of Mexico platforms are excluded). The three In appetite emails become new rows in Submissions.

Insurance doesn’t fit in a neat box.

Insurance doesn’t fit in a neat box.

So we built a platform that fits around it.

So we built a platform that fits around it.

Workflows for insurance operations.

Workflows for insurance operations.

Inbox triage

Each email becomes a row. Actions sort it, read the attachments and send it to the right queue.

SOV cleaning and enrichment

Clean every schedule into one format, then add geocodes and hazard data.

Bordereau validation

Check every line against the binder before it reaches your books.

Policy extraction and checking

Read the policy into rows, then compare it with the quote.

Aggregates and limits

See exposure by location, peril and treaty as each risk comes in.

Claims intake

Turn each first notice of loss into a row that is ready for a handler.

Tables store your data, including files.

Each column has a type: text, numbers, money, dates, and files such as spreadsheets and PDFs, while references link tables together. Each file stays on its row.

Demo: the Data screen of the Example Shop workspace. A pointer points at each reference column of Orders and clicks the table it references.

Actions plug straight into tables.

Each action maps columns of the table to its inputs and outputs. When new data arrives, the actions run on the new rows one after another, in the order you set, and each step fills in more of the row.

Demo: the Actions view of the Orders table. A pointer opens three of its actions in turn and goes back to the list after each one. Each action shows which columns feed its inputs and take its outputs. The pointer then clicks Data: five new orders arrive, and each action fills in its columns. One order is over 500, so Flag Large Order links it to its Large Orders row.

Describe the system you need. The Architect will build it.

Tell the Architect what you want in plain words. It asks what it needs to know, then builds the tables and the actions for you.

Demo: a person asks the Architect for a way to track orders. The Architect asks one question, then builds a Customers table, an Orders table and a thank-you email for each new order.

View the entire system in a single graph.

The Map shows every table and every action in the workspace. Each line shows where data goes: from a table into an action, and from an action into the next table.

The Map page of the Example Shop workspace: every table and action, and the lines between them.

Audit and observability, as standard.

Every row keeps its history. Each change records what changed, when, and who made the change: a person, or the action that ran. You can see how any value got there.

Demo: the page of one order in Orders. It shows the fields and the system fields, then the History: each change, the action or person that made it, and when.

Security and compliance.

ISO 27001, SOC 2 Type 2 and GDPR are in progress. Oneleet shows the live status of each certification.

Oneleet compliance badge: ISO 27001Oneleet compliance badge: SOC 2 Type 2Oneleet compliance badge: GDPR
Oneleet compliance badge: ISO 27001Oneleet compliance badge: SOC 2 Type 2Oneleet compliance badge: GDPR
Oneleet compliance badge: ISO 27001Oneleet compliance badge: SOC 2 Type 2Oneleet compliance badge: GDPR

© 2026 Morphcloud