Surety & specialty
Underwriting
Submissions spread and screened overnight, so the only files on your desk are the ones that genuinely need an opinion.
authority limits · four-eyes · refer-up
Workflow software for document-heavy review
Every submission read by morning.
Every decision still signed by you.
SureThink takes the file in however it arrives, reads every page, and screens it against your own rules. What it cannot settle, it hands to the person whose authority covers it — with the figures extracted, each one showing where it came from, and a record that will still replay in two years.
39modules
77rules, day one
100%decisions signed
$0to test a pipeline
Review desk · 09:41
My Queue3 to settle
Meridian Builders · $1.28Mapproval tray · 7drefer
Delta Holdings · KYCfour-eyes requiredhold
FNOL · policy 88214cleared · ready to signclearDecision record · signed
K. OseiSenior underwriter · limit $2Msha256 · 9f2c…41ab · immutable
How a file moves
One file. Five stations.
One signature.
Four of the five stations are automatic and finish in under a minute. The fifth is a person, and it waits as long as it needs to. That is the whole design — the pipeline does the reading, your team does the deciding.
01 · ARRIVES
It comes in
Email, API, watched folder or schedule. Every attachment opened and typed.
14 files · 62 pp
✓ 12 types recognised
02 · READS
It reads
Statements spread, entities resolved, every figure graded and cited.
wip $1.28M · read
✓ 11 fields cited
03 · STOPS
A person decides
One figure it could only infer. So it stops and asks, rather than averaging.
K. Oseisenior underwriter04 · COUNTER-SIGNS
A second pair of eyes
Over the four-eyes threshold, a second signer is required — and the first is excluded.
signer 2 · M. Webb
✓ approved
05 · FILES
It files itself
Letter written, obligations set, webhook fired, record sealed.
letter.pdf · POST
✓ hash-chained
4 min of automated work1 human decision2 signatures1 record, replayable nine months later
01Built for workflows
Work arrives the way it already arrives.
Your brokers email attachments. Your systems post JSON. Your schedule drops a file at seven in the morning. SureThink picks work up from all of it — so nobody has to learn a portal, enforce a naming convention, or retype a PDF into a form.
- Four ways in. Email intake, REST API, watched folders, and schedules — running side by side into the same pipeline.
- Nothing sent back. Scans, spreadsheets, photographs of paper. It opens what it’s given and works out what each one is.
- One queue out. Everything lands in a single queue, filtered to what each person has the authority to settle.
email_watchsubmissions@ · 9 files
api_intakePOST /v1/cases · 3
folder_watch/broker-drop · 2
scheduledaily · 07:00
FS_2025_audited.pdfstatement
wip_schedule_aug.xlsxwip schedule
bond_request_v3.docxapplication
IMG_4471.jpgscan · indemnity
14 files · 62 pages · 12 types recognised · 0 returned to sender
02Customise the process
You build the pipeline. Not a ticket to engineering.
39 modules on a canvas — classifiers, extractors, gates, analysts, letter writers, webhooks. Wire the flow, set each station’s limits, dry-run the whole thing against pinned fixtures for nothing, then publish a version that is frozen. The person who knows the process is the person who builds it.
- Test Bench. Run the pipeline against real fixtures at $0.00 before a single live file touches it.
- Observe mode. A new rule reports for a fortnight before it is allowed to act on anything.
- Frozen versions. Publishing locks the pipeline. Replay a case from March and you get March’s logic, not today’s.
email_watchi0 · submissions@
doc_classifieri1 · 12 types
wip_extractori2 · graded
rule_pack_gatei4 · 77 rules
approval_trayi5 · parks here
record_writei7 · hash-chained
03Structured output, graded
Every figure arrives with its evidence attached.
The file comes out structured — fields, not paragraphs. Each one records how it got there: read off a cited page, computed from figures that were, inferred from prose, or simply not in the file.
ReadLifted straight off a page, cited to it
DerivedComputed from figures that were read
InferredModel judgment — always flagged
AbsentNot in the file, and it says so
Below the threshold you set, the pipeline does not average, round, or take its best guess. It names the one field it cannot stand behind, and stops the file there.
How grading works →Credit summary — Meridian Builders Ltd.pipeline v14 · 09:43
Working capital$612,400derivedcurrent assets − liabilities
Backlog-to-equity3.4×derivedfrom 2 read fields
Contingent liability~$184,000inferrednote 9, prose only — stopped
Surety history, prior 3ynot statedabsentrequested from broker
11 fields · 7 read · 2 derived · 1 inferred · 1 absent — file held at station 03 for a named signer
04Human-driven
The pipeline stops where your policy says stop.
Authority limits, four-eyes approval, refer-up, confidence gates. Not a policy document describing what ought to happen — controls that execute at the station, on every file, whether or not anyone is watching that day.
- Authority limits. Every role carries a ceiling. Past it the file escalates to someone who can settle it; it never falls through.
- Four-eyes, enforced. The second signer is required by the system, and the first pair of eyes is excluded by it — not by convention.
- Corrections keep both numbers. When your underwriter overrides a figure, the file keeps what the pipeline read and what she decided, with her name on the change.
K. Oseisenior underwriter · limit $2Mcase #4471 · Meridian Builders
held on contingent liability
grade inferred · note 9
four-eyes required above $1M
Approve with correctionDecline
05Audit-ready logs
Nine months later, it replays exactly.
Every run, every figure, every correction and every signature — hash-chained, timestamped, attributable. When the auditor asks how this decision was made, you show them the record. You don’t reconstruct it from memory and an email thread.
- Immutable once submitted. A decision can be superseded, never edited. The chain would show it.
- Replay with the original logic. The pipeline version is pinned to the case, so March’s file replays under March’s rules.
- Attributable end to end. Every figure names its source page; every decision names its signer.
✓ Decision recorded — immutablesha256 · 9f2c…41ab
Decision
Approved with conditions
Signed by
K. Osei · senior underwriter
Counter-signed
M. Webb · compliance director
Correction
contingent_liability → $184,200
Pipeline had read
~$184,000 · inferred · note 9
Rule pack
contract surety v1 · in force 8/4/26
09:41:06 intake 14 files · 62 pp
09:43:22 extract 11 fields · 7 read, 2 derived, 1 inferred, 1 absent
09:45:01 gate CS-038 → refer · held for signer
16:22:14 sign K. Osei · correction recorded
16:31:40 counter-sign M. Webb · four-eyes satisfied
16:31:41 seal chained to 8c11…9d02
Who it’s for
Built for the desks where
being wrong costs something.
The discipline underwriters, credit officers and compliance leads already apply — made repeatable, and written down every single time.
Lending & credit ops
Credit
Spreads, covenants and exceptions assembled with a citation behind every figure, so the memo starts written instead of blank.
every field graded and sourced
KYC, claims & legal intake
Compliance
Screening that runs the same way on every file, and an exceptions queue that is a queue — not a thread nobody owns.
hash-chained, replayable records
What you can prove
Every decision still has a name on it.
39modules in the catalog — classifiers, gates, analysts, writers
77starter rules in force on day one, versioned and citable
100%of decisions signed by a named person with authority
Canadadata residency. Your files train nothing, ever.
Start with one workflow
Bring the file you’d never
hand to a black box.
Thirty minutes on your own process. We map it to a pipeline, set your authority limits, run a real file through it, and show you the record that comes out.
- A schematic of your workflow, yours to keep
- The rule pack it would screen against
- Your authority map, role by role
- A sample decision record and a cost per file