Company profile · 4 min read
Clicks Health: revenue-cycle AI with human review
AI agents for healthcare back-office operations.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
Clicks is most useful when the workflow is boring, repetitive, and expensive.
What it does
Clicks Health describes itself as an AI-agent platform for revenue-cycle and healthcare back-office work (YC profile). The company says its agents operate inside EHRs, payer portals, spreadsheets, PDFs, and other existing tools, rather than asking a provider to replace the stack (company homepage).
The current RCM workflow page shows the shape of the work: eligibility and benefits, prior authorization, claim cleanup, denial follow-up, payment posting, credit refunds, and forms. That is a more concrete proposition than “AI for healthcare.” It is a queue of repetitive administrative jobs with a named owner and an exception path.
| Fact | What the public source says |
|---|---|
| Buyer | RCM companies, healthcare providers, and operators |
| Workflow | Payer and administrative work across existing systems |
| Operating model | The company says it maps a workflow, builds the agent, and routes exceptions |
| Evidence | The site publishes case-study claims; they remain company-reported |
Where it fits
I would shortlist Clicks for a revenue-cycle leader who already knows which queue is expensive and can define the normal path. The company’s own workflow guide says a good first candidate is high-volume, repetitive, data-ready, clearly owned, and costly. That is a sensible buying frame.
The strongest part is the control boundary. Clicks says the provider keeps control of actions and exceptions, and its examples show human review before the next step. That matters in healthcare operations. The point is not to remove judgment from the process. It is to remove the repeated clicks before a qualified person needs to decide something.
The company also says it works with existing systems including Epic, Oracle Health/Cerner, athenahealth, eClinicalWorks, ModMed, NextGen, and MEDITECH (homepage). Those are company-presented compatibility claims, not an independent integration audit.
What I would resolve
The first question is current scope. The YC launch material began with recruiting and executive-search workflows; the current site leads with healthcare RCM. That may be a deliberate vertical move, but a buyer should ask which workflows are live, which are pilots, and who owns configuration.
The second question is evidence. The site shows prior-authorization and denial-appeal case studies with reported before-and-after numbers. Useful lead. Not a benchmark. I would ask for the baseline, period, workflow definition, exception rate, and what the provider still reviewed.
The founder context is relevant. The YC profile lists Dominik Helmreich as an ETH Zurich graduate, Stanford AI researcher, and former BCG consultant; Oliver Knapp is described there as a repeated AI founder who built enterprise automations. That helps explain the company’s workflow-first posture. It does not prove healthcare outcomes.
Short version: Clicks looks like a fit for a healthcare operator with a defined administrative queue and a tolerance for a forward-deployed setup. It is not yet a reason to hand over clinical judgment.
Sources checked — 2026-09-19
Cohort context
Clicks Health 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:14:57.673Z 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 ↗