From you
One process owner
Someone who has done the work, not only managed it. Ninety minutes on Monday, an hour on Wednesday, and answering questions in between.
SureThink/Getting started
Onboarding · week one
Live by Friday.
Trusted by the month after.
A pipeline reading live files takes about a week. Letting it act without someone watching takes longer, and it should — that is the whole argument of the product, and we are not going to contradict it during onboarding.
Your first week, day by day.
This is the real cadence, not a best case. The only thing we need from you on day one is one workflow and one person who knows how it actually works — not how it is documented.
- Mon01
Map the workflow
Ninety minutes with whoever owns the process. We draw the stations on a canvas while they talk — where work arrives, what gets checked, who signs what, and the case that always goes wrong.
Out: a schematic, and the list of rules nobody had written down
- Tue02
Set the guardrails
Authority limits per role, the four-eyes threshold, and which confidence grades are allowed to pass without a person. These are policy decisions, so they are made by whoever owns the policy — not by us.
Out: an authority map your compliance lead has signed off
- Wed03
Test against files you’ve already decided
Pin thirty or forty real cases from the last year as fixtures and run the pipeline at them for nothing. Where it disagrees with what your team decided, one of the two is worth understanding.
Out: a disagreement list — usually the most useful artefact of the week
- Thu04
Publish a version, turn on observe mode
The pipeline goes live on real intake and reports what it would have done without being allowed to act. Your team keeps working exactly as before, and now has a second opinion arriving beside them.
Out: v1 frozen, live intake flowing, nothing acting yet
- Fri05
Invite the team
Queues, authority and trays configured per person. Thirty minutes of training, because if it needs more than that we have built the wrong thing.
Out: everyone signed in, first cases in real queues
Then, over the following fortnight
You read the observe-mode report. Where the pipeline has been right consistently, you let it act. Where it hasn’t, you change a rule and watch again. Most teams let it clear routine cases in week three and keep everything else parked for a person indefinitely — which is a legitimate end state, not a failure to finish rolling out.
What it costs you
Four hours of the right person’s time.
Not a project team, not a steering committee. The most common reason an onboarding stalls is that the person who actually knows the process was never in the room.
From you
Thirty real files
Cases you have already decided, redacted however you need. They become the fixtures, and they are what makes the Wednesday test meaningful rather than theatrical.
From you
One policy decision
Who can sign what, and at what number a second pair of eyes is required. If that is genuinely unsettled, the week surfaces it — which some teams find more valuable than the software.
Help & docs
You won’t onboard alone.
Every plan
Docs written for the process owner
Module reference, rule-pack authoring, and a worked example for each blueprint — written for someone who knows underwriting, not someone who knows APIs.
39 module pages
5 blueprint walkthroughs
searchable, versioned
Growth and above
A solutions engineer with a name
The same person through the whole week and afterwards. They will have read your schematic before the call, and they will tell you when a rule you want is a bad idea.
week one: 4 sessions
after: as needed
same person throughout
Every plan
Blueprints you can start from
Surety, credit, KYC, claims and legal intake — each a wired pipeline with its rule pack and authority map, which you then change rather than build.
5 blueprints
77 starter rules
yours to edit on day one
Start with one workflow
Your first pipeline
is a week away.
Ninety minutes on Monday with the person who owns the process, and thirty real files. That is the whole ask.
- 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