Catalog · 22 systems in production
Every system, one card each. Pick the one that looks like your problem.
Each card is a discrete build with its own problem, its own safety rule and its own result. Most shipped in days, inside a live operation. Filter by the kind of system, or by whether it runs a freight desk or my own practice.
Showing 23 of 23
The carrier negotiation bot
Haggles with carriers by email. Every dollar comes from a deterministic ladder; the AI only reads.
Email bots
The carrier ETA bot
The morning status chase, drafted, classified and followed up unattended every 20 minutes.
Email bots
The morning appointment run
One click rolls stale pickup dates forward in the TMS and drafts the shipper's appointment emails, day-of or the day before, never earlier.
Email bots
Auto-cancel noise suppression
Releases timed-out loads before the shipper's noisy email is ever generated. A one-way door with double guards.
Email bots
The load-board refresh bot
Every 15 minutes a desk PC pulls the board from the TMS, wipes the stale postings on the load board, uploads the fresh file and posts it. Nobody touches it.
Browser automation
The shipper portal pull
The shipper's carrier portal has no feed, so a bot searches it, exports the grid, parses the legacy spreadsheet and feeds two dashboards every 15 minutes.
Browser automation
The carrier purge
Given a list of DOT numbers, delete those carriers from the TMS the way the UI does, and prove each one is gone.
Browser automation
The load-posting converter
Replaced a silently corrupting Excel macro on day one. 4,342 loads posted in its first days, zero corrupted fields.
API integrations and data sync
The uncovered-loads auto-classifier
Ends rate guessing: an unclassifiable load is held for review, never posted at a guessed rate.
API integrations and data sync
Delivery and pickup date adjustments
Paste the shipper's table, review the plan, click Apply. Every write is read back to verify.
API integrations and data sync
The covered sweep
Never quote a taken load: a 15-minute cron reconciles open loads against the TMS and closes them down, never up.
API integrations and data sync
Dispatcher-email backfill
Fills blank carrier-dispatcher emails from the rate confirmation's own recipient line, and only when it is certain.
API integrations and data sync
Rate overrides and the margin floor
Every rate in the platform flows through one chokepoint: a hand-set override beats the percentage rules, and no rung of the ladder can book a loss.
API integrations and data sync
The operations platform
A single-user script became a 16-page production platform three operators use at once, with 30-plus tables, 4 cloud crons and 3 desk-side workers.
Web tools for teams
The pick tracking board
The shipper's daily tracking sheet lives in the platform now, mirrored against the TMS every 15 minutes and fed by the portal pull.
Web tools for teams
The priority board
Paste a handful of shipment IDs and get live TMS status plus the truck's last GPS ping and its age. Read-only on day one, on purpose.
Web tools for teams
The auction-board converter
The second load program arrives as an email table, not a file. Paste it; the parser forgives prose, restores ZIP codes and prices from an owner-editable table.
Web tools for teams
The report discrepancy checker
Replaced the owner's Excel compare macro: the TMS and the shipper's portal reconciled with a status vocabulary map and seven exception views.
Reconciliation and reporting
The profit ledger
A load counts as profit only if the hand-off email exists and the TMS shows a carrier. The agreed rate is read from the thread, because the database field lies.
Reconciliation and reporting
The pain-signal lead engine
Job postings are pain signals. A scraper reads who is hiring for manual ops work, scores the pain and prices the pitch from the salary they posted.
Practice tooling
The outreach system
A cold-email and calling machine built the careful way: scripted DNS, verified addresses only, one suppression table, and a human on every send and every dial.
Practice tooling
Meeting transcription and diarization
Every client call becomes a build brief: local transcription with speaker attribution, then a requirements doc, then the plan.
Practice tooling
The second-brain recorder
An Android app that records a conversation and uploads it to a backend on my own PC, where it is transcribed and searchable. Own data, own code, end to end.
Practice tooling
// client details anonymized; every metric from production logs and commit history