LanePilot

The sprint before opening was mostly reliability work, not new features. Self-serve account restore shipped, so a customer who soft-deletes their account can bring it back from the dashboard inside a 29-day window without contacting support. Pause-tier enforcement was tightened across roughly 25 write surfaces, because "read-only while paused" needed to mean read-only everywhere, not just in the obvious spots. KPI reports now save server-side and share via a 30-day expiring link scrubbed of account and billing identifiers, so a freight manager can hand a snapshot to their boss without giving them a login. LanePilot is open, the free plan requires no card, and the first 25 organizations get 10% off, terms apply, at lanepilottech.com/signup.

One of the most confusing things I used to see on the carrier side, after nearly a decade at UPS Freight, XPO Logistics, and Lake Erie Trucking, was shippers quoting a guaranteed delivery service alongside standard transit and not realizing they were comparing two completely different things. This week I wrapped up guaranteed-service filtering across all the connected carrier adapters, so when a carrier on your account offers a time-definite or guaranteed window, it shows up clearly labeled in your results instead of sitting mixed in with standard options. It looks like a small detail but it changes how useful the rate comparison actually is on time-sensitive lanes. It also sets up the invoice audit side correctly: if you booked a guaranteed service, the system now knows to look at the right rate bucket when it checks your invoice against the quote. With the August 31st open launch coming up, getting the rate layer airtight before we open the doors is the priority.

The warehouse module just got its outbound half. Pick and pack, wave picking for high-volume runs, and per-SKU serial tracking are all live now, each pick reserving directly against real on-hand stock so nothing oversells. Spending nearly a decade on the carrier side at UPS Freight, XPO Logistics, and Lake Erie Trucking meant watching a lot of small shippers run their inbound and outbound on disconnected systems, then patch the gap with spreadsheets. LanePilot Warehouse now handles the whole loop: receive it against the PO, store it, pick it, ship it. We open for real accounts August 31. In the meantime, drop your invoice and original quote at lanepilottech.com/try for a free invoice audit, no account needed.

This week we discovered our marketing pages were taking 12-13 seconds to load. Not great timing with launch weeks away. After a three-attempt chase, the root cause turned out to be our auth library sitting in the root layout of the site, forcing every public page to render dynamically instead of building fully static. We moved it out, and the login page alone dropped from a 5-second baseline to under 2 seconds. We also ran a full site audit and found four unauthenticated test endpoints in the API that should have come out months ago. One of them was writing a real record to the production database on every anonymous call. Found it, removed it. This is the part of building software nobody talks about: the stuff that is quietly wrong and only shows up when you go looking. We went looking. If you ship LTL freight and want to see what your carrier invoices actually say versus what you were quoted, the free audit at lanepilottech.com/try takes your carrier invoice and your original quote and flags every discrepancy.

One thing kept coming up in demos: shippers could see individual audited invoices but had no quick way to see the aggregate picture. I built a stat header for the Invoice Audit view. Pick a timeframe from 30 days to all time and the summary cards update, including a discrepancy rate that only counts audits with an actual unauthorized charge, not just any dollar difference, so the number actually means something. There's a drill-down that breaks recovery into dollars and count. If you want to see it on your own freight, the free audit at lanepilottech.com/try takes an invoice and the original quote and runs in under 60 seconds.

We put our full pricing page live this week, so anyone can see what LanePilot costs before signing up (free plan, four paid tiers, and a founding-member discount for the first 25 paying customers). Sign-ups are still waitlist-only, but the numbers are out there. On the build side, we finished direct API integrations for 17 LTL carriers this week, including XPO, FedEx Freight, ArcBest, Estes, Saia, ODFL, and R+L. Each adapter handles some mix of quoting, tracking, document retrieval, and booking using that carrier's own API, so rates come from the shipper's actual contracted account, not a generic market feed. XPO is fully live-proven end to end; the others are code-complete and sitting in the carriers' own onboarding queues.

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.