Aminova Annual Letter 2026

Aminova builds the operating system for modern optimization clinics — practices running hormone therapy, medical weight loss, peptide and longevity programs, functional and integrative medicine, aesthetics with a medical arm, IV therapy. This letter is about why the company exists, what we chose to build, and where the work goes from here.

The problem we started with

Walk into a modern clinic and count the software. An EHR designed for insurance-billed primary care, bent into shape for everything else. A scheduling tool. A forms product for intake and consents. A payments account. A lab portal. An e-prescribing bolt-on. An inventory spreadsheet. A membership platform. A messaging app. Each one holds a fragment of the patient.

None of them talk to each other, so the staff becomes the integration layer. The front desk re-types demographics from the intake form into the chart. A provider signs a prescription in one system and an assistant deducts the vial in another — or forgets to. A lab result arrives as a PDF in an inbox, and someone files it, eventually, into the right record. Every handoff between systems is a place where information can be late, wrong, or lost. In medicine, those gaps are not just inefficient. They are where mistakes live.

This is not a technology problem in the usual sense. Each tool works fine on its own. The problem is the seams. Our thesis, from the beginning:

A clinic's systems should operate as one connected platform, built around a single patient record — so that anything that happens only has to happen once.

That sentence is the company. Everything below is an elaboration of it.

What we focused on building

An annual letter is not a changelog, so we will stay at the level of shape. The platform covers three layers, all reading and writing the same record.

The clinical core

Charting built for protocol-driven care: notes composed of structured fields — product, dose, quantity, site, lot — rather than free-text paragraphs, so the note that documents a visit can also feed trends, inventory, and the next titration decision. Labs ordered from the chart, with results returning as discrete values that plot across every draw, out-of-range markers flagged for review, and critical values held until a provider signs off. E-prescribing from inside the encounter, with safety screens on every compose and EPCS and PDMP flows for controlled substances — each provider transmitting under their own identity, never a shared clinic account. Telehealth inside the chart. An AI scribe that drafts the note for the provider to edit and sign. Care plans and protocols built once and reused.

The operational spine

Scheduling and intake, with forms and consents flowing into the chart instead of a filing cabinet. Inventory with lot and expiry tracking, earliest-expiry-first depletion, and a separate ledger for controlled substances. Dispensing that deducts stock, charges the card on file, and creates the shipment in one step. Memberships that renew, retry, and report themselves. Insurance eligibility, claims, and remittance posting alongside cash-pay revenue, not instead of it. Reporting that reads from the same ledger as everything else.

Payments deserve a specific word. A clinic takes money five ways — card on file, terminal, HSA/FSA, ACH, cash — and every tender lands in one ledger, tied to the visit, the invoice, and the membership. Routing matters more than most clinics realize: the general-purpose card processors most businesses run on prohibit prescription sales, and enforcement means a frozen account with the clinic's money inside it.

The patient's side

A white-labeled app and portal under the clinic's own brand — its name, its icon, its colors on the patient's home screen. Inside: protocol reminders, check-ins, secure messaging, refill requests, lab results, booking, and payments. Patients see their clinic. Aminova runs underneath. Every action a patient takes lands in the clinic dashboard in real time — no separate logins, no double entry.

Connected beats comprehensive

It would be easy to read the list above as a feature inventory. That is the wrong way to read it. The value of the platform is not the number of modules; it is what happens when one event moves through every system it touches.

• An appointment ends, and the charge posts to the ledger — tied to the visit and the invoice, worded on the receipt the way the clinic wants it.
• A provider signs a prescription and, if it dispenses in-house, the lot depletes, the card on file is charged, the shipment is created, and the patient is notified — one step.
• A lab result comes back and lands in the right chart as data: flagged if out of range, held for sign-off if critical, plotted next to the dose that produced it.
• A refill request arrives already carrying supply, history, and context. One signed approval sends it — and tells the patient.

In each case the event happened once. Nobody re-typed it. Nothing needs reconciling later, because there is only one version of it. Feature checklists cannot express this. Two products can list identical modules and behave completely differently, because the question that matters is not which boxes exist but whether they share a record.

Building for clinics as they are

Most clinical software descends from hospital-era assumptions: one provider per visit, episodic fee-for-service care, a chart organized around billing codes, notes as prose. Modern clinics break every one of those assumptions. A single visit might involve a nurse practitioner who prescribes, a nurse who injects, and an aesthetician who follows up. Care runs on protocols measured in months, not encounters. Revenue is memberships and cash-pay alongside insurance. The medications are often compounded, cold-chain, and dispensed in-house. We chose to build for that reality directly rather than keep adapting software built for a different one.

The same choice shows up in how the platform treats compliance — as architecture, not paperwork. A script will not transmit if the patient's state is not on the prescriber's license; overrides are possible, and logged with who, when, and why. Every record is encrypted in transit and at rest. Access is role-based, so staff see what their role allows. The audit trail records everything — including the denials.

What comes next

We are not going to publish a roadmap with dates on it. But the direction is no secret, because it follows from the thesis. Deeper integrations, so the systems around a clinic — accounting, payroll, pharmacies, labs — stay in step without anyone re-typing. More automation of the operational work that repeats: reminders, reorders, follow-ups, recalls. A better patient experience, because the patient's app is where the connected record becomes visible to the person it belongs to. Less time spent operating software; more time spent on care.

The measure of progress is unglamorous: fewer times a staff member enters the same thing twice. Fewer tabs open. Fewer gaps for something important to fall through.

Modern medicine — longevity, optimization, prevention — is being built by independent clinics, not hospital systems. Those clinics deserve infrastructure designed for how they actually work, and that is what we intend to keep building: one record, one platform, one connected workflow at a time.

Thank you for reading. And to the clinicians and operators who push us to get the details right — thank you for that, too.

— The Aminova team