Production systems. Measured results.
Real builds inside real operations, from purchase order automation to logistics consolidation ahead of an ERP modernization. Download the full write-ups or book a call to talk through what would apply to your business.
How we eliminated 11 hours of weekly admin labor without writing a single line of custom ERP code
The problem
Twenty minutes per purchase order. Every single one. Customer Service received PO files and keyed each one into the legacy ERP by hand, field by field, correcting defaulted ship dates, payment terms and shipping methods, navigating a live routing screen for every order and entering every line item individually. Future-dated POs committed inventory immediately, creating warehouse cleanup work.
The insight
The obvious answer was to automate manual entry into open orders. But the ERP's routing engine needs live shipment data mid-workflow, which would have required custom ERP code. Instead we built a batch processing layer targeting Future Orders. Orders enter the ERP without committing inventory, and routing activates later with live data, exactly as the ERP was designed. Zero custom ERP code. We just changed where in the workflow the data enters.
The architecture: Microsoft Power Platform + Fabric
Deliberately kept out of v1: no direct routing integration, no writeback into open orders, no live API concurrency with the ERP, one active batch at a time, and a manual Customer Service audit before any upload. The goal was to eliminate work that should never have required human attention, not to replace the humans who bring operational context.
Why we consolidated three logistics channels before touching the ERP
The problem
Three disconnected systems and one broken operation. Contract freight lived in a carrier portal, spot market capacity on load boards, and the private fleet in spreadsheets. No shared data, no single view of carrier capacity, no unified load lifecycle. The result was roughly 15 hours a week of manual cross-system coordination and a 30 to 45 day financial reconciliation lag.
The sequencing insight
Modernizing the ERP first would have meant feeding a new system from three disconnected sources in three formats, with custom integrations per source. Garbage in, garbage out. We consolidated first: unify the three channels, standardize the load lifecycle, let a single clean data model emerge, and reduce the ERP integration to three clean events.
One dispatch interface. Three carrier types. One lifecycle.
Asset-based carriers, owner-operators and brokered capacity each kept their own onboarding, compliance and payment logic, but shared the same dispatch workflow and a unified load lifecycle with defined inputs, outputs and system handoffs at every stage.
ERP integration became event-driven instead of monthly batch: carrier acceptance auto-creates the purchase order, proof of delivery auto-generates the AP voucher, and cleared payment terms post the settlement. Every event posts in real time.
Additional engagement outcomes
Outcomes from client engagements across distribution, manufacturing and portfolio operations.
Agentic approval routing
Deployed an agentic approval-routing workflow for a family-owned manufacturer. Procurement cycle time dropped 60% and four manual handoffs were removed from the process.
LLM integrated with an existing ERP
For a portfolio company's operations team, automated routine data entry across three departments and cut error-related rework by nearly half.
ERP migration in under six months
Moved a regional distributor from a 15-year-old system to a modern cloud platform in under six months with zero data loss.
ERP connected to WMS and EDI
Connected a mid-market ERP to the warehouse system and EDI feeds, reducing order processing time by 60%.
AI reporting layer for a manufacturer
Replaced weekly manual exports with real-time dashboards built on top of the existing ERP data.
Invoice matching and approvals
Invoice matching time reduced 60%, and approval cycles brought under six hours from a previous four days.
Want results like these in your operation?
Book a strategy call. We will walk through which of these patterns applies to your systems and where the first structural target is.