Company profile · 3 min read
Cartage builds Wilson, an autonomous freight-operations layer for shippers
Cartage's Wilson coordinates loads, carriers, tracking and exceptions for manufacturers and distributors.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
Cartage is building Wilson, an AI freight operator for manufacturers and distributors that want the coordination work around shipping handled end to end.
What it does
The current homepage says Wilson creates loads, books carriers, tracks shipments and manages exceptions. It works from the company’s existing workflow rather than asking a shipper to operate another planning dashboard. Cartage homepage
The company says Wilson handles more than 500 shipments daily, runs 10x faster than a human and makes 98.7% of decisions autonomously. Those are company-reported figures. The site also says Cartage has raised $8m and trained its own model on real freight workflows.
The founder context is relevant. The YC profile describes Abdul Basharat’s Rose Rocket and logistics product background and Josh Lampen’s founding-engineer work on a trucking-ERP workflow engine.
Why I’d look closer
Freight coordination is mostly exceptions: quotes, confirmations, paperwork, carrier changes and the gap between what the plan says and what actually happens. Cartage’s current product story is stronger than “freight software” because it targets the execution layer.
The buyer fit is a shipper or manufacturer with enough recurring freight volume that manual coordination is already a headcount or margin problem.
What could make it the wrong choice
Autonomy in freight creates a high bar for exceptions and accountability. A buyer should ask how the system handles an unavailable carrier, a changed pickup window, a damaged load, a pricing dispute or a shipment that needs a human decision.
Pricing is not published in the checked sources. Company performance numbers need definitions: what counts as a decision, how autonomy is measured, and which shipments or customers are included. A freight operator should also check integration, insurance and carrier responsibility before moving real coordination into the system.
My editorial take
I would shortlist Cartage for a manufacturer or distributor with repetitive freight coordination and a willingness to let the system operate inside clear guardrails. I would not start with a claim about replacing every coordinator. Start with one lane or shipment class where the exception policy is known and a human can review the decisions that matter.
Quick facts
| Field | Sourced detail |
|---|---|
| Product | AI freight coordination and execution |
| Buyer | Manufacturers, distributors, shippers and carriers |
| Public operating claims | 500+ shipments daily and 98.7% autonomous decisions |
| Pricing | Not published in the checked sources |
| Main fit question | Are shipment volume and exception rules clear enough to automate? |
Sources checked
Cartage homepage, about page, YC profile and public launch material were checked on 2026-09-19.
Cohort context
Cartage is listed in Summer 2024. In our 2026-09-18 directory snapshot, 161 of 248 listed companies in that cohort have YC’s primary industry label B2B (64.9%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19T16:16:53.416Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Observed |
| H1 or H2 heading | Observed |
| Typed structured data | Not observed in this response |
| Docs/developer link | Not observed in this response |
| Pricing link | Not observed in this response |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
About the author
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.
First1000 ↗ · X ↗