SureThink/Pricing
Pricing · billed annually
Per-document pricing makes you ration the thing you bought. You end up deciding which files are worth reading properly, which is exactly the decision the software was supposed to remove.
Team
$79/user/mo
For one desk getting its first pipeline into production.
Growth most firms
$149/user/mo
For several desks, several pipelines, and an audit function that asks questions.
Enterprise
Let’s talk
For firms whose risk committee needs to read the architecture before the contract.
Annual billing. Monthly is available at a 20% premium — we would rather say that than print a monthly price and hide the annual discount in a footnote.
AI usage · metered separately
Model calls cost money. Bury that in a seat price and you are either overcharging the light users or quietly throttling the heavy ones. So it is metered, itemised, and shown to you.
1,120 calls · 2 failed, billed for what they produced
0 calls unpriced
no cost per case, on purpose
On every plan
The accountability machinery is not an upsell. A four-person team carries the same risk per decision as a four-hundred-person one.
| Capability | Team | Growth | Enterprise |
|---|---|---|---|
| Hash-chained decision records | Included | Included | Included |
| Human approval stations | Included | Included | Included |
| Sourced-confidence grading | Included | Included | Included |
| Test Bench (zero spend) | Unlimited | Unlimited | Unlimited |
| Canadian data residency | Included | Included | Included |
| Org-wide two-factor (TOTP) enforcement | Included | Included | Included |
| Pipelines | 3 | Unlimited | Unlimited |
| Four-eyes & authority maps | Single map | Per pipeline | Per pipeline |
| Observe mode | — | Included | Included |
| Replay with pinned versions | — | Included | Included |
| Custom rule-pack authoring | — | — | Included |
Before you ask
You export everything — documents, structured output, decision records with their chains — in a format that stands on its own. The records are evidence about your business, not a feature of our subscription, and holding them hostage would be indefensible.
Not for the pipeline itself. The builder is for the person who owns the process. Files go in by drag and drop, and everything that comes out — memos, letters, records, audit packs — downloads from the case.
It is designed to be wrong in one direction: it stops rather than guesses. When it does misread something, your reviewer corrects it and the file keeps both figures with her name on the change — so the error becomes evidence rather than a silent bad number.
About a week to a first pipeline running on live files in observe mode, and a further two to four weeks before most teams let it act unsupervised on routine cases. We would be suspicious of anyone promising faster.
You should. The 91 starter rules are a starting point for contract surety specifically; every firm edits them. Rules are versioned, so changing one does not rewrite the cases decided under the old version.
No. Not ours, not a vendor’s, not in aggregate, not anonymised. There is no setting for this because there is no other mode.
Start with one workflow
Thirty minutes on your own process. We'll estimate your real cost per case from a real file rather than quoting you a range that means nothing.