The input
More pages than time
Sixty pages arrive and four of them matter, but you cannot know which four without reading all sixty. Every desk below pays that tax daily.
SureThink/Solutions
Solutions
Five desks.
The same discipline.
A document arrives. Somebody has to read all of it. A judgment gets made, and later somebody asks how. That shape is the same whether the file is a bond application or a claim — which is why one pipeline can carry all of them.
The pattern
What these desks have in common.
The decision
A judgment with a name on it
Somebody signs. Their authority is real, their limit is real, and the consequence of being wrong lands on the firm rather than on a dashboard.
The aftermath
Somebody asks, later
A regulator, a reinsurer, an auditor, a claimant’s lawyer. The question is always how the decision was reached, and it is always asked long after everyone forgot.
The desks
Five blueprints. Yours to change.
Each is a pipeline with its stations, rule pack and authority map already wired. None of them is a finished answer: the first week is spent changing one to match how your firm actually works.
01 · Surety & specialty underwriting
The submission that arrives as fourteen attachments.
Statements spread, WIP schedules read, exclusion lists screened, single-job and aggregate limits checked against the rule pack — before an underwriter opens anything.
The pipeline settles
- Completeness and document typing
- Spreads, ratios and backlog figures
- Exclusion and duplicate screening
- Rule-pack findings with codes
The person settles
- Anything the pipeline could only infer
- Exposure above the authority limit
- The final bond decision and conditions
contract_surety v1 · 77 starter rules · four-eyes above $1M
02 · Lending & credit operations
The credit memo that starts written instead of blank.
Spreads assembled with a citation behind every figure, covenants extracted and dated, exceptions listed with the clause that created them. Your analyst edits a draft rather than building one.
The pipeline settles
- Financial spreads and ratio analysis
- Covenant extraction with test dates
- Prior-period comparison
- The first draft of the memo
The person settles
- The credit opinion itself
- Exceptions and how they’re priced
- Anything read from narrative rather than a table
every figure graded and sourced · memo cites its rules
03 · KYC & compliance
Screening that runs the same way on every file.
The failure mode in compliance is not missing a hit — it is inconsistency. The same entity screened twice by two people, two different ways, on two different days.
The pipeline settles
- Entity resolution across documents
- Exclusion and watch-list screening
- Document completeness per policy
- Periodic re-screens on a schedule
The person settles
- Every possible match, by name
- Enhanced due-diligence calls
- The decision to onboard or decline
exceptions in a queue, not a thread · re-screens on a clock
04 · Claims operations
First notice, triaged before anyone reads it.
Coverage checked against the policy as written, reserve indicated, the obvious ones cleared and the difficult ones sent to a handler with the file already assembled.
The pipeline settles
- FNOL intake and document typing
- Coverage position against the wording
- Duplicate and prior-claim checks
- Reserve indication and routing
The person settles
- Coverage disputes and grey areas
- Reserve above the handler’s limit
- Anything with a liability question in it
the record is the file the lawyer will eventually ask for
05 · Legal intake & contract review
The clause you always check, checked every time.
Incoming agreements read against your playbook, deviations surfaced with the standard position beside them, and the ones inside policy cleared without a lawyer opening the document.
The pipeline settles
- Clause extraction and classification
- Deviation from the playbook position
- Missing clauses and carve-outs
- Routing by deviation severity
The person settles
- Every material deviation
- The negotiating position to take
- Anything the playbook doesn’t cover
the playbook is a rule pack · versioned, citable, yours
Where it isn’t the right tool
Worth saying out loud.
Three things people ask us for that we would rather decline than sell badly.
Not this
High-volume, low-stakes triage
If nobody needs to sign and nobody will ever ask how, the accountability machinery is overhead. A simpler tool will be cheaper and faster.
Not this
Fully autonomous decisioning
There is no mode where the pipeline decides and no one signs. If that is the requirement, we are the wrong vendor and will say so on the first call.
Not this
A process nobody has written down
If the rules live only in one person’s head, the first week is spent getting them out — which is valuable, but it is a consulting engagement before it is a software one.
Start with one workflow
Bring the file you’d never
hand to a black box.
Thirty minutes on your own process, whichever desk you sit at. We map it to a pipeline, set your authority limits, and show you the record it produces.
- 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