Layer 04 · Shared workflows

The steps run.A person approves the exit.

AI in the loop, on top of human in the loop. Nothing leaves your building without a name against it.

See the safety modelBook a discovery call
The layerOne real run

Thirty steps,and one of them is a person.

Claims intake from scanned instructions — the workflow behind the insurance case study below. It traces itself; click any step to stop and read it.

low confidenceconfidentapproved
  • Trigger
  • Extraction
  • Lookup
  • Triage
  • Rule
  • Branch
  • Human gate
  • System write
  • Outbound comms
  • Outcome
In production

Two teams where the gateis the whole product.

Insurance · Agentic AI inbox for claims

30h → 30m

30h → 30m of weekly claims email work, from three people to one

An Agentic AI Inbox for Insurance Claims Intake

Read the case study

Legal · Client correspondence

60%+

60%+ reduction in non-billable email time

AI Client Correspondence Automation for a Legal Practice

Read the case study
What we have published

Who decidesthe next step.

Every framework on this page runs a tool-calling loop. What separates them is whether you draw the path in advance or let the model choose it, and that is the decision worth reading about before you commit.

9 min readWhat is an agentic workflow?An agentic workflow blends deterministic steps with model-driven decisions, giving an AI freedom where judgment is needed and structure everywhere else.8 min readStrands Agents vs LangGraph: Who Decides the Next Step?Strands lets the model choose what to do next. LangGraph makes you draw the path first. That single difference decides which one fits your problem.8 min readStrands Agents vs Mastra: Agent Runtime or Application Framework?Strands gives you an agent and gets out of the way. Mastra gives you the application around it. Pick by how much of the product you still have to build.8 min readHuman-on-the-Loop vs Human-in-the-Loop: Supervise or ApproveHuman-on-the-loop supervises a system that acts on its own; human-in-the-loop gates it. Which one a workload deserves comes down to reversibility, not trust.
Start with one workflow

Book a discovery call.

Start with the map of your organization, or with the one job that hurts. Measured in hours and money, and everything we build stays yours.

Loading form…