For bench scientists who are done doing spreadsheet surgery

Your experiment is not a spreadsheet.

Drop the ugly export. Keep the biology. AssayPilot turns recurring wet-lab files into the same traceable analysis every time — without rebuilding plate maps, remembering last week's formulas, or pretending technical triplicates are n=3.

Try a live demo — no signup Use your own data

ELISA / BCA · Dose-response · qPCR · Enzyme kinetics · Growth curves

The actual pain

Built around the moments wet-lab people hate.

The 96-well dump

Your reader gives you a matrix or a giant table. AssayPilot maps wells to the experiment instead of making you rebuild it by hand.

The replicate trap

Technical replicates are QC first. They do not silently become biological n.

The “what did we do last time?” problem

Save a lab workflow once — assay type, plate map, controls, qPCR normalization — then reuse it.

The reviewer question

Every run keeps the settings, assumptions, QC and calculated table with the figure.

Not another Prism clone

Graphing starts after the experiment has been understood.

Generic graphing tools are good at graphs. AssayPilot is for the mess before that: wells, standards, controls, dilutions, technical replicates, biological samples and recurring lab conventions.

A small promise

If the file is ambiguous, stop.

No silent outlier deletion. No invented sample groups. No “AI picked a test, trust us.” The software should make scientific decisions easier to inspect, not harder to see.

Your lab has muscle memory. The software should too.

Save the workflow, not just the graph.

Create “Our IL-6 ELISA”, “Our viability plate”, or “Our qPCR normalization”. Next run, choose that workflow and drop the new export.

Start with 5 analyses free