Freight brokerage — document intake
An operations team was keying BOLs, load confirmations, and rate confirmations by hand. We built the document-intake service that classifies and parses all three into structured records. Manual data entry: gone.
Is this you?
Tick the ones that are true this quarter. One is enough.
The pattern
Most assessments end in a recommendation. That recommendation goes to a second firm to scope. That firm scopes it differently than the people who diagnosed it. By the time anyone is building, the original analysis is two handoffs old — and the economics have changed.
The other pattern: the audit recommends automation, a platform gets selected, and a year later the team is still working around it.
Neither of those is a decision. They are deferred decisions — with real money still walking out the door while you wait for the next round of scoping.
The five audit steps
5 steps · scroll to trace
The processes we examine and who runs them.
What each workflow costs today.
Which workflows have a credible economic case for automation.
The simplest technology for each — or a clear no.
The first sprint defined and priced. If nothing is worth automating, the audit says so and you keep the analysis.
What you walk away with
With the economics attached: here is the workflow, here is what it costs you now, here is what changes it, here is what that costs to build.
The same engineers who map the process and run the cost analysis are the ones who would build the fix. If no workflow clears the bar, the audit says so. That is not a failure outcome. It is the finding the engagement was designed to produce.
The commitment
The range covers the full five-step process. The scope, timeline, and fee are written down before any work begins. You keep every deliverable whether or not you build anything.
The exact figure is agreed before kickoff based on the number of workflows and systems in scope. The fee does not expand once set. If the scope puts the number outside that range, you will know before anything starts.
Built, not modeled
01 / 03
An operations team was keying BOLs, load confirmations, and rate confirmations by hand. We built the document-intake service that classifies and parses all three into structured records. Manual data entry: gone.
Thousands of agreements routed through OCR, layout analysis, and structured extraction, then confidence-scored. High-confidence records processed automatically; low-confidence routed to human review.
Lead generation, enrichment, AI vetting, quality scoring, and CRM handoff were five separate manual handoffs. We built it as a single pipeline with per-call cost and latency logged under one audit trail.
Who runs it
Thirty years of shipping production systems across logistics, healthcare, contract management, and operations-heavy software.
Five founder-run companies. The audit is run by someone who has carried the operational risk being examined — not modeled it from a framework. The person doing the audit is the same person who would design and build the fix: no handoff, no translation loss between the diagnostic and the build, and no second firm that scopes the work differently than the people who found the problem.
Before you call
If yours is not here, it is a two-minute email and a direct answer within a day.
The output is a build/no-build recommendation with the economics behind it and the first sprint scoped. A call: here is the workflow, here is what it costs you now, here is what changes it, here is what that costs to build.
Take it when
You can point at manual coordination that is costing real money — rekeying between systems, hand-offs that break, reporting rebuilt by hand — and you want a priced, buildable answer on which of it is worth fixing first.
Pass when
More developers for an existing team, a broad AI transformation program with no specific workflow, or commodity content at scale.
Tell us the problem — two minutes.
Direct answer within 24 hours on whether it’s a fit.
If it is: a 30-minute scoping call.
Written scope, timeline, and fixed fee before any work starts. You keep everything delivered.
The $3,000–$7,500 range is typical for the scope described. The exact figure is agreed in writing before work begins.
Final step
Book the audit, and walk away with a plain answer on which workflows are worth building, which ones are not, and what the first sprint would cost — ready to act on the day you receive it.
No pitch. No prep. If it is not a fit, I will tell you.
— Brandon Shuey, Principal