SureThink/Product/Pillar 01

Pillar 01 · Built for workflows

Work arrives the way
it already arrives.

Every document workflow already has an inbox. The question is never how to invent a better one — it is how to stop a person being the thing that opens it.

4ways in
12document types
0portals to roll out
1queue out

Four ways in. One pipeline.

They run side by side into the same flow, so a broker who emails and a system that posts JSON are handled identically from the second station onward.

email_watchmost used

An address your brokers already write to

Each pipeline gets its own inbound address. Forward your existing submissions box at it and nothing changes for the people sending you work — no portal, no login, no training email.

Replies and follow-ups thread onto the same case.

api_intake

A REST endpoint for your own systems

POST /v1/cases with the metadata you already hold and the files attached. The response carries the case id, so your system can follow it without polling a dashboard.

Webhooks fire back at every state change.

folder_watch

A folder somebody already drops into

Point it at a shared drive and it picks up what lands there. For teams whose current process is “save it to the broker folder”, this is a zero-change migration.

Sub-folders can route to different pipelines.

schedule

A clock, for the work nobody sends you

Renewals, expiring obligations, watch-list re-screens. The trigger is a date rather than a document, and the pipeline assembles the file itself from what it already holds.

Also how overnight batch runs are set up.

Classification

It opens what it’s given.

Scans, spreadsheets, a photograph of a page someone signed and put on a windowsill. The classifier types each one before anything downstream touches it, so a mislabelled attachment doesn’t become a mis-read figure.

doc_classifier · i1 14 of 14
FS_2025_audited.pdffinancial statement
wip_schedule_aug.xlsxwip schedule
bond_request_v3.docxapplication
IMG_4471.jpgscan · indemnity
owner_contract_siteB.pdfcontract
RE_ FW_ bond docs.emlcorrespondence

14 files · 62 pages
12 types recognised
2 filed as correspondence
0 returned to sender

What “opened” actually means

  • Split. A 62-page PDF that is really four documents is separated into four, each typed on its own.
  • De-duplicated. The version the broker sent twice is one document on the case, with both arrivals in the log.
  • Read as text. Scans and photographs go through OCR before typing, so an image of a page is a page.
  • Kept whole. The original file is never modified. Everything downstream cites back to it by page and line.
Nothing is ever sent back for formatting. If a document cannot be typed, it is filed as correspondence and the case continues — a human decides whether it matters, rather than the pipeline refusing the submission.

The other end

Four ways in. One queue out.

However a file arrived, it leaves the same way: in one queue, filtered to the people who are allowed to settle it, with the reason it is waiting written on the row.

surethink.app/my-queue filtered to your authority · limit $2M
Meridian Builders · $1.28M performance bondarrived by email · held: contingent liability could only be inferredrefer7d
Delta Holdings · KYC screenarrived by API · four-eyes required above thresholdhold2d
Northcape · renewal reviewraised by schedule · obligation expires in 14 daysreview1d
FNOL · policy 88214arrived in the broker folder · cleared every gateclear4h

4 to settle · 11 parked elsewhere · 38 filed today without anyone opening them

Filtered to authority

You only see what you can settle

A case above your limit is not greyed out in your queue — it is not in your queue. It is in the queue of the person whose authority covers it.

Nothing unowned

Every parked case has a name

A file that is waiting is waiting on somebody specific, and the row says who and for how long. There is no “pending” state with nobody behind it.

Why, not just what

The reason is on the row

Refer, hold, review, clear — and the sentence that caused it. You know what the case needs before you open it.

Connectors

And the systems you already run.

Intake is four triggers today. Connectors are how a pipeline reaches into the tools your team is already in — reading from them, and writing decisions back.

Webhooks, both waysLive
REST APILive
Inbound email per pipelineLive
Gmail & OutlookComing
Google Drive & SharePointComing
Slack notificationsComing

We mark these honestly. Three are shipped and documented. Three are designed and not yet built — and we would rather you knew that before a pilot than after one.

Start with one workflow

Show us where your
work actually arrives.

Thirty minutes. We look at one real inbox, folder or feed, and map what would have to be true for a pipeline to pick it up unchanged.

  • 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

No deck. We’ll ask you to bring one real file, redacted however you need it.