Software for small labs and technical firms
Research is a large part of how this region earns its living, and much of it is done by small teams between South San Francisco and Emeryville. If you run a lab of fifteen people there, you know what holds it together: a shared spreadsheet for where each sample is, another for which lot of a reagent went into which run, an instrument calendar kept by hand, and a colleague who notices that a supply is about to run out. A design studio in San Francisco lives the same way, with projects and client approvals where you have samples.
In place of those sheets we would build you a single working record. A sample gets a label and an entry when it arrives. The reagent lot is picked from a list when a run is logged, so nobody types it from memory. When stock falls below a level you set, a supply order is drafted and waits for whoever signs for purchases in your lab; the software does not spend your money. The instrument calendar shows a clash before it happens. First, though, you and we write down what the records are and who may change them, and we check whether a product you can buy already does the job, because for common lab work one often does. Price and scope are fixed in a brief before building starts.
Suppose a group in Boston writes to ask whether you can run a set of samples. You have never met them and you have nobody there. With the record in place, the job runs from your bench in Emeryville. Their inquiry becomes a quote that you approve before it is sent. Their samples are logged the morning the courier arrives. They sign in to a view of their own samples and nobody else's, so they can check progress without writing to you. When the run is finished, the report and the invoice are attached to the same job. The next inquiry could as easily come from San Diego or Basel.



