If a loop isn’t covered by the standard five ABs, LeedAB builds a custom one. Same architecture, same brain, same messaging interface. Any workflow your team runs by hand — operations, finance, logistics, HR, customer support — can become an AB. Included with the production tier.Documentation Index
Fetch the complete documentation index at: https://docs.leedab.com/llms.txt
Use this file to discover all available pages before exploring further.
Examples
| Loop | What the AB does |
|---|---|
| Payroll reconciliation | Reads timesheets, cross-checks against payroll records, flags discrepancies |
| Supplier follow-up | Chases open POs and acknowledgements on a schedule, logs every response |
| Tariff reclassification | Watches tariff changes, models cost impact, drafts filings |
| NPI risk | Reads new BOMs, flags single-source and long-lead items before pilot |
| Inbound quality holds | Watches QMS for hold flags, notifies supplier, tracks CAPA completion |
| Customer onboarding | Collects documents, screens new customers, routes to the right approver |
| Invoice matching | Matches invoices to POs and receipts, flags mismatches for finance review |
Process
Describe the loop
A paragraph in plain language — what it watches, what triggers it, what it produces. That’s enough to start.
Scoping call
One hour with your team and a solutions engineer to map the description to AB architecture.
Specification review
Solutions engineering sends a one-page spec. You confirm before the build starts.