// Get a read on one workflow

Bring us one workflow.

No commitment. Bring your process documentation, whatever form it is in, and a sample of the real files: submissions, claim files or bordereaux. No inbox access needed, and the terms are written out in full on How we work.

If the answer is that you should not build it, that is what the assessment will say.

What happens next

A named senior engineer replies within one business day to book the session. Five business days after it, you get the written assessment. Every message from us carries a new artifact or it does not get sent.

Workflows we’re asked about most

Submission intake and triageWrite-back into the system of recordLoss-run normalizationClaims document structuringBordereaux and delegated-authority reportingSOV normalization and exposure dataSemantic layer over a core-system replicaGovernance file for an existing modelUnderwriting referral rulesSomething else

Or start with Discovery.

If you already know the workflow is worth four weeks, skip the read. Discovery is four weeks, fixed scope, and returns a buildable spec.

Still deciding which workflow to bring us?

Every senior engineer on staff has run this conversation before. Bring the messy version — that's the one we actually want.