Company profile · 3 min read
Caucus: constituent-service software with an inactive YC status
Government CRM and constituent-service platform; current product availability requires status verification.
Published · Updated
Caucus was aiming at a real government problem: staff work is fragmented across systems that were never designed to share context.
What it does
Caucus describes itself as an AI CRM for government, starting with congressional offices. The YC profile says the product connects workflows and reduces repetitive public-service work.
The current website presents a constituent-services system: centralize email, webforms, mail, and phone calls; triage inquiries; track cases; and analyze issues.
| Fact | What the public source says |
|---|---|
| Buyer | Government offices and public-service teams |
| Workflow | Constituent intake, casework, response, and issue analysis |
| Status | YC currently lists the company as Inactive |
| Founder context | Amir Farahani previously founded Turbo Legi; Tyler Chen is listed with Yale Physics and CS |
What looks useful
The product direction is practical. A constituent case does not belong in one clean CRM record from the start. It may arrive as an email, form, phone call, or letter, then move through staff, departments, and follow-up. A system that unifies that path could matter more than another chatbot.
The website’s public claims include 24/7 access, automated support, and a claimed reduction in response time. Those remain company-presented claims. A government buyer would need to understand data retention, public-record obligations, staff review, escalation, and accessibility before treating the product as deployable.
The founder story is relevant. YC says Amir Farahani previously built Turbo Legi, an AI legislative-solutions company acquired by FiscalNote, while Tyler Chen brought physics, computer-science, and AI research experience.
What I would resolve
The directory status matters. YC lists Caucus as Inactive even though the company page remains available. That does not establish an active product or current procurement path. A buyer looking for a live system needs a current company statement before going further.
If the product is active again, the fit question is which office workflow it owns first: constituent correspondence, casework, internal routing, or staff knowledge. Government procurement is not only a feature comparison. It is also governance, records, security, and continuity.
Short version: Caucus is a strong example of a government-specific workflow problem and a weak current availability recommendation until the status is reconciled.
Sources checked — 2026-09-19
Cohort context
Caucus is listed in Spring 2025. In our 2026-09-18 directory snapshot, 2 of 143 listed companies in that cohort have YC’s primary industry label Government (1.4%). 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:34.084Z 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 | Not observed in this response |
| 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.
