Company profile · 4 min read
Lunavo: AI execution for carrier operations
Lunavo connects to carrier systems and executes repetitive freight back-office work while escalating operational exceptions to dispatchers.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
What it does
Lunavo is an AI execution layer for trucking carriers and freight-forwarding operations. It connects to a carrier’s TMS, email and portals, reads incoming work, performs repetitive back-office tasks and escalates exceptions to dispatchers. The YC profile describes the product as an assistant that runs carrier operations; the homepage makes the sharper promise: add capacity without adding headcount.
The buyer is an operations leader at a carrier or forwarder where order intake, tracking, appointment coordination, billing preparation and exception handling are spread across too many tools. The product is not most compelling as another dashboard. It is compelling if it can safely execute the small, repetitive actions that currently consume dispatch time while keeping a human in the loop for margin, service and safety decisions.
Why I’d look closer
Lunavo’s public demo is specific about the work. It shows order intake from a portal email, extraction of multiple shipments, matching against a master service agreement, TMS creation, customer confirmation and a dispatch-channel summary. The homepage also presents agent roles for dispatch, order intake, track-and-trace, billing, appointments and exceptions. That is a better starting point for evaluation than a generic “copilot” label.
The homepage reports a live intermodal-forwarder example with 180+ orders per day, 5,300+ emails per month and 85% of tickets resolved without humans; it also claims a GPS delay can trigger a customer notification in 11 seconds. These are company-reported operating claims, not independently measured outcomes. The page’s status-quo numbers—50–100 emails per hour, ten or more disconnected tools and 7–14 days of DSO drag—are similarly contextual claims.
The founders have relevant operating and technical backgrounds. The YC biographies describe Felix Lösch as former McKinsey and managing director at a robotics-logistics startup, and Niclas Heun as a computer-science researcher and former Siemens AI leader for shop-floor operations. That combination helps explain the focus on exceptions and execution rather than a new reporting layer.
What I’d ask
Which TMS, load-board and portal connectors are live, and how does Lunavo learn a carrier’s rules without silently changing them? I’d ask for an exception log, approval controls, audit history and a replayable test set from one lane. Pricing, data retention and operational liability were not exposed in the sources checked, so those belong in the first buyer conversation. The real proof is whether a dispatcher can inspect and correct an action before it becomes a customer problem.
My editorial take
Lunavo is a strong fit-based profile for carriers with high repetitive volume and a measurable back-office bottleneck. I’d start with order intake or track-and-trace, not turn on every agent at once. The company’s own workflow examples are concrete enough to justify a pilot; its efficiency claims still need a controlled baseline.
Quick facts
| Field | Sourced detail |
|---|---|
| Buyer fit | Trucking carriers and freight-forwarding operations teams |
| Workflow | TMS/email/portal execution with exception escalation |
| Traction signal | Company reports 180+ orders/day and 85% ticket resolution without humans |
| Public pricing | Not exposed in the sources checked |
Sources checked
Checked 2026-09-19.
| Source | Used for |
|---|---|
| YC company profile | Product definition and founder backgrounds |
| Lunavo homepage | Current agent workflows, operating example and company-reported metrics |
Cohort context
Lunavo is listed in Fall 2025. In our 2026-09-18 directory snapshot, 90 of 146 listed companies in that cohort have YC’s primary industry label B2B (61.6%). 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:15:10.946Z 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 ↗