LanePilot

We've been heads-down on the inbound side of LanePilot. This week we shipped the receiving dock module: every account gets the core tools for free, so teams can log what arrived, flag discrepancies, and generate a chargeback letter to the vendor ready to file. (The letter goes out from the shipper, same way we handle freight invoice disputes on the outbound side.) For accounts that want the full receiving workflow, an add-on tier unlocks the deeper features. The goal is to make LanePilot useful on both ends of the freight operation, not just when the carrier invoice hits your inbox.

Shipping invoices come with a lot of moving parts, and one scenario kept nagging at me: what if the wrong documents get paired together? If someone runs an audit against an invoice matched to the wrong quote (different carrier, different route), the system could check all the line items, find no discrepancies, and return a "clean" verdict. Technically correct on those numbers, fundamentally wrong about the shipment. This week LanePilot got smarter about that. The audit now checks whether the invoice and quote actually describe the same shipment before it evaluates the charges. A carrier mismatch or route mismatch triggers a red MISMATCH flag, and the dispute letter stays hidden until you confirm the pairing or re-upload the right document. It sounds like an edge case, but it goes to the core of what I'm building here. An audit that cannot confirm it is comparing the right documents should not be telling you anything is clean.

Build-in-public update: not a flashy week, all polish. Went through the entire app and cleared out the bugs, tightened the rough edges, and smoothed every flow end to end, quoting, booking, the invoice audit, and the dispute-letter builder. No new feature to show off, just the unsexy work that turns a demo into something solid. This is the pass you do before real users ever touch it. Founding-partner cohort opens in August, and I want it clean when they walk in.