Meiborg Brothers Trucking
Strategic findings and top-line recommendations for Meiborg Brothers Trucking's AI journey
Invoice remittance processing is the selected Phase 4 use case. FAI is building it directly on the Foundry AI Platform. Gmail connection and McLeod API node are already live.
HappyRobot's inbound carrier sales and track & trace agents are live in brokerage, handling 300–370 calls/day and delivering measurable FTE savings.
Regulis has been active for 2+ months at $2K upfront + $950/mo with no working McLeod integration delivered. FAI is building the remittance automation directly — one accountable partner, no vendor sprawl.
Meiborg Brothers Trucking enters Phase 4 with a clear mandate and a strong foundation: the Phase 3 use case selection process identified invoice remittance processing as the highest-priority, most implementation-ready opportunity. Foundry AI Partners has already established the two critical integrations — Gmail connection and McLeod API node — that were blocking progress under the previous vendor arrangement.
Regulis AI was engaged for this use case but was unable to deliver a working solution after 2+ months at $950/month. The primary blockers — Google Workspace email integration and McLeod API access — were resolved by FAI in a fraction of the time. FAI is now building the remittance automation directly on the Foundry AI Platform, eliminating third-party dependency and ensuring end-to-end accountability.
Beyond Phase 4, Meiborg faces a structural risk: vendor sprawl. HappyRobot, Regulis, Mode AI, Augment, and TransFlow have all been introduced within a short window with no unified strategy. The Foundry AI Platform offers a strategic alternative — a single orchestration layer for building and managing all AI automations, with FAI as the coordinating partner. It is not a replacement for every vendor; it is the connective tissue that makes the ecosystem manageable. If a vendor has an API, FAI can connect to it — for working vendors, this means monitoring and visibility, not replacement. As part of the SOW, FAI committed to delivering a working use case. The invoice remittance automation agentic workflow is included at no additional cost. Long-term platform access and pricing to be discussed separately.
Operational landscape, technology stack, and identified friction points
Daily manual matching of customer payments (PDF, Excel, CSV, inline email) to open invoices in McLeod. Parallel NACHA/ACH reconciliation also manual.
Vendor invoices keyed manually into McLeod with human routing between two databases. Prior automation attempt (Mode AI) failed on routing logic.
Driver documents submitted via ELD with no automated completeness audit. Missing pages delay billing and create revenue leakage on the asset side.
7–8 overseas workers perform tedious data entry tasks that are candidates for automation. Represents direct cost reduction opportunity.
McLeod API is poorly documented and difficult to integrate. Every AI vendor has encountered this blocker. Requires dedicated integration work.
Multiple AI vendors active or evaluated (HappyRobot, Regulis, Mode AI, Augment, TransFlow). Without coordination, fragmented ownership creates process gaps.
Systematic evaluation of each identified opportunity across four dimensions
| Use Case | Division | Business Value | Complexity | Risk | Timeline | Priority |
|---|---|---|---|---|---|---|
AR Remittance Processing Automation | Finance / AR | Low | 6–8 weeks | Highest | ||
AP Invoice Processing Automation | Finance / AP | Medium | 8–10 weeks | High | ||
Driver Document Intake & Unbilled Revenue Audit | Fleet Operations (Asset) | Medium | 10–12 weeks | High | ||
Inbound Carrier Sales Automation | Brokerage | COMPLETE | COMPLETE | Complete | ||
Track & Trace Automation | Brokerage | COMPLETE | COMPLETE | Complete | ||
Dispatch & Load Matching Optimization | Fleet Operations (Asset) | High | Phase 2 (post-foundation) | Future |
Detailed profiles for each identified opportunity — click any card to expand
Customer payments arrive via email in four distinct formats — PDF attachments, Excel files, CSV exports, and inline email body text. Accounting staff manually reads each remittance, cross-references open invoices in McLeod, and posts the cash receipt. The parallel NACHA/ACH workflow requires a separate manual step to pull bank reconciliation reports. Both processes run daily and are entirely dependent on human availability.
An AI agent monitors a dedicated Google Workspace remittance inbox, extracts payment data regardless of format using document-understanding models, matches each line item to open invoices in McLeod via API, and posts cash receipts automatically. A human-in-the-loop review step flags exceptions before final posting. The NACHA reconciliation workflow is similarly automated using structured bank report parsing.
Remittance Processing Automation is the committed Phase 4 deliverable per SOW FAI-SOW-MBT-2026-001. Foundry AI Partners is building this directly on the Foundry AI Platform. The Gmail connection and McLeod API node are already live. Implementation is underway.
The remaining use cases in this menu — AP Invoice Automation, Driver Document Intake, and others — represent the Phase 5+ roadmap. The McLeod integration layer and Foundry AI Platform infrastructure built for Phase 4 will accelerate delivery of all subsequent workflows.
Strategic path from quick wins through transformation — as committed in SOW FAI-SOW-MBT-2026-001
The antidote to vendor sprawl — one platform, one partner, no fragmentation.
Meiborg is evaluating or actively using 13+ AI vendors across three AI modes — Automation (Transflo, Motive, Optimal Dynamics, Trucker Tools, Four Kites), Augmentation (HappyRobot, Augment, Navix, PS Logistics), and Agentic/True AI (Hwy Haul, Qued) — with no unified integration strategy. Each solves one piece. None talk to each other. This is the vendor sprawl scenario Ted described — a cluster mess in six months. The Foundry AI Platform gives Meiborg a unified toolset to build and manage all automations in one place, with FAI as the coordinating partner.