The 50–100 truck reality
Hundreds of RFQs and document packets a month mean the question is no longer whether to automate but how to automate without losing the controls a business this size needs — who approved what, why this price, why this document filed where it did.
Every agent run is persisted with its analysis and outcome. Document filing is gated by sanctions screening, order-match confidence, and extraction grounding; overrides are acknowledged and logged.
What matters at this size
- Throughput with dedup guarantees: retries and redeploys never double-process a message or double-file a document.
- Compliance posture: sanctions screening on packets, restricted-party alarms, and logged operator overrides.
- Cost accounting finance can check: per-action credit charges derived from real model spend, with an itemized ledger.
- Scoped multi-team access — capability matrix plus assignment scope — enforced at the database layer, not just the UI.
Where humans stay in the loop
Client sends, sanctions overrides, and ambiguous document filings always require a human decision. The system is designed so scale increases the number of drafts, not the number of unreviewed actions.
Frequently asked questions
Can we require human approval on every document packet?
Yes. Auto-filing of safe packets is a per-workspace control and can be switched off entirely, forcing a human tap on every packet.
How is usage billed at high volume?
Credits meter per completed AI action at real model cost. Plans carry monthly allowances; top-up packs never expire and burn last.