Overview
Remedy is a Fall 2025 YC company building AI agents for pharmacy operations. Its live product handles prescription data entry and routine inbound calls while routing clinical questions to pharmacy staff.[1][2]
Its outcome is unresolved. Repository metadata says active, YC labels it acquired, and the product site still accepts demo requests. YC names no buyer, date, terms, or product disposition. The evidence supports a live product footprint and a possible ownership change, not a shutdown or failure story.
Founding Story
YC lists Vishnu Sreenivasan as founder and CEO, Nikhil Devaraj as founder, and Sai Mandhan as a former founder. It reports a two-person team.[1] Sreenivasan publicly announced a YC pre-seed, while YC's standard deal invests $500,000 in accepted companies.[3][4]
Public evidence does not explain how the founders met, how they chose pharmacy operations, or how they secured their first customer. Mandhan later described the ambition as an AI-native operating system for pharmacies and claimed nationwide use, including an unnamed large independent chain.[5] That is founder positioning, not independent customer verification.
Timeline
- 2025: Remedy was founded and joined YC's Fall 2025 batch.[1]
- Fall 2025: Sreenivasan announced YC pre-seed financing.[3]
- Later: Mandhan left for OpenAI; the remaining founders' public profiles later showed NimbleRx roles.[6]
- Current: YC says acquired, repository metadata says active, and Remedy's product and demo pages remain live.
What They Built
The Data Entry Agent processes faxes, images, electronic prescriptions, and feeds, validates prescription information, and prepares it for a pharmacy management system. The Voice Agent handles refill requests, prescription status, pickup scheduling, hours, insurance, copays, vaccines, and wait times.[2]
Remedy says the system reads and writes pharmacy data in real time, runs in the cloud, and needs no new hardware. Clinical questions go to pharmacy staff. That boundary matters: the product is useful only when automation, current system data, and safe human escalation work together. Its Trust Center claims HIPAA compliance, encryption, access reviews, incident procedures, and 74 monitored controls, though no independent audit was publicly accessible.[7]
Market Position
Target Customers
The product targets independent pharmacies burdened by routine calls and prescription intake. An NCPA survey found 80.3% of respondents said financial health declined in 2024, making measurable labor savings attractive and purchasing scrutiny severe.[8]
Market Size
No supportable reachable-market estimate was found. Public customer-group evidence establishes that multi-location independent-pharmacy networks exist, but not Remedy's penetration.
Competition
TJM Labs and Thinkrr market overlapping pharmacy intake, refill, voice, and patient-communication workflows.[9][10] The evidence suggests generic voice generation is weak differentiation. Reliable writeback, clinical escalation, deployment across groups, and measured workload reduction are the harder product tests.
Business Model
Remedy uses a demo-led sales motion and publishes no pricing.[2] Revenue, contract value, implementation cost, gross margin, retention, and payback are unknown. A buyer would likely compare fees against staff time, missed calls, and turnaround, but the evidence provides no unit economics.
Traction
Remedy claims more than 35,000 calls handled and automation of up to 75% of inbound calls. A site testimonial attributes roughly half of staff-handled calls at Chinook Pharmacy to its agent.[2] These are vendor-published signals without an independent case study, contract scope, retention data, or audit.
Post-Mortem
No post-mortem is supportable
The evidence does not show failure. YC's acquired label conflicts with active repository metadata and a live commercial site. Founder moves to OpenAI and NimbleRx are signals, not transaction records. They do not identify a buyer, price, closing date, or whether customers and product continued.
Observable product risks can be stated only as inference. Pharmacy automation must avoid clinical judgment, maintain accurate system writeback, prove compliance, and produce savings for financially pressured buyers. Competitors advertise similar workflows. Remedy's public materials address these requirements, but do not independently prove reliability, economics, or defensibility. These are diligence questions, not causes of failure.
Key Lessons
- Resolve identity before outcome. This is a 2025 pharmacy company, not the older namesake suggested by stray historical references.
- The safety boundary is part of the product. Call automation has little value without current pharmacy data, dependable writeback, and clinical escalation.
- Vendor metrics are leads. Call volume and workload-reduction claims warrant testing, not conversion into verified traction.
- Affiliation does not prove a deal. Directory labels and founder employment cannot substitute for transaction documentation.