Company profile · 4 min read
Andco: autonomous pre-litigation casework
Andco retrieves records, opens claims and organizes personal-injury case context across the channels plaintiff firms already use.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
What it does
Andco’s agents run the pre-litigation workup for personal-injury and plaintiff law firms. They retrieve police and accident reports, open insurance claims, request medical records and bills, follow up across fax, email, mail, portals, SMS and voice, and organize the context needed for a demand. The YC profile describes the first 24 hours of that workflow; the homepage shows records retrieval, casework, clientwork and insurer coordination in one system.
The fit is a plaintiff firm whose caseload is constrained by document chasing rather than legal strategy. Andco is not selling an automated legal judgment. Its FAQ says attorneys and staff retain control of strategy, review and approval while the agents handle operational casework. That is the right boundary to inspect: the product’s value is getting the case context in earlier and with less staff overhead.
Why I’d look closer
The product is specific about the messy channels it has to handle. A case can spawn parallel requests to police departments, insurers and providers, then keep following up until records and bills arrive. The homepage says Andco powers thousands of cases each month across named plaintiff firms and quotes a customer who says the team cleared 100+ backlogged cases without adding staff. It also displays a 10x case-management-throughput figure. These are company-reported and customer-selected claims, not independent benchmarks.
The founder context fits a workflow company. The YC biographies describe Ryan Xue as a repeat founder with Origin and McKinsey/Google experience, David Lee as a two-time founder/CTO with NoxuData, Seek AI and DataFox experience, and Michael Lemm as a Layup co-founder and former Kirkland & Ellis attorney. The About page presents the team’s mission as reducing the paperwork between intake and representation.
What I’d ask
Which agencies, payers and providers are covered, and how does the system handle a request that needs human consent or an unusual form? I’d inspect chain of custody, audit logs, attorney approval, client communication, error recovery and the exact boundary between retrieval and legal analysis. Pricing and a full implementation guide were not exposed in the sources checked, so a buyer should scope one case type and one jurisdiction before extrapolating.
My editorial take
Andco is one of the clearer legal-operations fits in this batch. The wedge is painful, repetitive and measurable, and the public workflow makes the promise testable. I’d start with a cohort of real pre-lit cases and compare time-to-complete, missing-record rate and staff review burden—not only the number of automated requests.
Quick facts
| Field | Sourced detail |
|---|---|
| Buyer fit | Personal-injury and plaintiff law firms |
| Workflow | Pre-litigation records, bills, reports and insurance workup |
| Proof signal | Company reports thousands of cases/month and displays a customer throughput claim |
| Human boundary | Attorneys and staff retain legal strategy, review and approval |
Sources checked
Checked 2026-09-19.
| Source | Used for |
|---|---|
| YC company profile | Product workflow, founders and launch claims |
| Andco homepage | Current platform, customer references and workflow details |
| About Andco | Company mission and leadership surface |
Cohort context
Andco is listed in Spring 2026. In our 2026-09-18 directory snapshot, 112 of 193 listed companies in that cohort have YC’s primary industry label B2B (58.0%). 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:03.420Z 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 | Observed |
| 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 ↗