Ten per cent inputs, seventy per cent processing, twenty per cent outputs
This is what a cautia workflow looks like from the inside. The proportion is the same in underwriting, receivables and member updates, and it shows where the real work sits: not in connecting the inbox, but in understanding the document.
Inputs
10 %Email, form or file upload. cautia reads native and scanned PDF, Excel, Word and images. In the analyst inbox, a classifier works out what you're asking for and routes it to the right workflow; when it isn't confident, it doesn't guess — it asks.
Processing
70 %This is where the craft is. The line of business is identified, information is extracted with AI models against a closed catalogue of coverages and conditions, dates, amounts and policy numbers are normalised, everything is cross-checked against your base or the slip, and the document is built on your agency's template.
Outputs
20 %The deliverable: PDF, Excel or HTML in your brand, back in the same email thread or in your team's inbox. Every deliverable carries the legal footer that matches its type.
The AI builds. A person approves
cautia uses artificial intelligence in every workflow, and we say so on every page because it's information you deserve to have. What the AI does is read, extract, normalise and compose. What it doesn't do is decide for you.
Before a document goes out to your client or to an insurer, it goes through human review. In workflows such as surety bond quoting that approval is a step in the system: the proposal is held until the responsible person authorises it. In comparison tables, the document returns to your team and it's your team that reviews and sends.
When something fails — an unreadable file, a missing field, an incomplete quote — the workflow doesn't invent the data. It flags it as missing and tells you what happened in plain language.
- No output is sent without review.
- Data that can't be read is flagged as missing, never filled in by inference.
- Comparison tables carry the note that they are a provisional quote and do not imply acceptance of the risk.
- Advising and answering to the policyholder remain your agency's responsibility.
The loop doesn't close when the document is built: it closes when someone on your team reviews it and authorises it to go out.
Five phases, one workflow at a time
We don't set up your whole operation at once. We pick the workflow that hurts most, get it running in production and then move on to the next one.
Diagnostic
We look at how your agency works today: what arrives, through which channel, who handles it, how long it takes and what goes out. We leave with the candidate workflow and the real files we'll work with.
Tailoring
We adapt the workflow to your operation: your insurers, your lines of business, your templates, your logo and your legal footer. This is where we define who reviews what, and against which criteria.
Implementation
We connect the inbox or the file source, configure the formats and get the workflow running in a controlled environment.
Activation
We test with real cases from your agency and compare the output against what your team would produce by hand. We fix whatever is needed and switch it on.
Operation
The workflow stays in production with monitoring. Adjustments for insurer format changes are part of the monthly service.
We work with your real files from the first phase, not with demos.
You pay per workflow in production
We don't sell per-user licences or fixed plans. The model has three components and we explain all of it before you sign anything.
- One-off implementation per analyst
- Covers the diagnostic, the tailoring and getting that analyst's first workflow into production.
- Monthly fee per workflow in production
- Charged for each workflow that's running, including format maintenance when an insurer changes its report.
- Usage
- A variable component based on the volume the workflow processes.
Amounts depend on your lines of business, your insurers and your volume; we give them to you in the proposal after the diagnostic. We do not charge per user.
Let's start with the diagnostic
Thirty minutes to understand your operation and decide together which workflow to start with.
Book a pilot