Teams that run agents like infrastructure.

Meridian's support team was drowning in tier-1 volume: password resets, statement questions, and dispute intakes consumed 70% of agent hours. Their first LLM pilot drafted good answers but couldn't be trusted to send them — every reply still needed a human, and the pilot stalled.

On Ballast they rebuilt the flow as a gated workflow: classify, draft, then a human gate for anything touching money movement. Low-risk categories auto-send; regulated ones pause for approval with full context. Compliance signed off because every decision lands in the audit log with the exact state the approver saw.

“The human gate is what got this past our compliance team. Approvals are in the trace, next to the model output they approved. That is the whole audit conversation.”

Northbeam processes bills of lading, customs forms, and rate confirmations from 300+ carriers, each in a different format. Their extraction scripts broke weekly, and a single crash mid-batch meant re-running thousands of documents from zero.

They moved the pipeline to Ballast: an extraction agent fans out per document, a condition node routes low-confidence extractions to a review gate, and checkpoints mean a worker restart resumes mid-batch instead of restarting it. The pipeline has survived 14 deploys and 2 node failures without losing a document.

“We used to schedule extraction runs around deploy windows. Now we deploy whenever we want — the runs just resume from their last checkpoint.”

Structa's inbound leads sat for a median of 9 hours before routing. Reps did their own research, wrote their own outreach, and skipped the CRM hygiene. Every attempt to automate it stalled on one question: what did the system actually do with this lead?

Their RevOps team built the routing workflow in the visual builder without an engineering ticket: score, qualify, parallel research and outreach drafting, merge, then hand off to Slack. Every run is versioned against the workflow that produced it, so when scoring logic changes, they can answer exactly which leads were scored by which version.

“I am not an engineer. I built the workflow our AE team runs 2,000 times a day, and I can defend every routing decision it has ever made.”