We have no star ratings, no review-site profile and no customer count to show you, so this page is the only proof we can offer instead: a dated list of things dental labs asked us for, what we built, and the day it went live.
No lab is named and nothing here is a quote. Each request is described by the kind of work the lab does, because we do not yet have written permission to name anyone or quote anyone. Every date is the day the change reached production.
16 requests, newest first.
Went live
Asked by a crown & bridge lab
Asked for: they wanted the case to move down the line on the board when the work is done, instead of having to open each case to see which step it is on.
Shipped: a production board with one column per step in your own workflow. Scan the case label and the case moves to the next step; scan it at the last step and it goes to QC.
Went live
Asked by a lab whose owner was the only account
Asked for: they wanted a second person to run the day — cases, doctors, invoices — without seeing the subscription and payment details.
Shipped: a Manager role: everything the owner can do except Billing. The owner switches a technician to Manager in Settings.
Went live
Asked by a digital design lab
Asked for: they wanted to read their cases out of SimpleLabOS into the systems they already run, rather than open a browser tab to check.
Shipped: a read-only customer API with keys you create yourself: your lab, cases, doctors, implant details, doctor preferences and case history.
Went live
Asked by a one-person lab
Asked for: they wanted to find a case by scanning it instead of typing, the way the barcode systems they had priced locally work.
Shipped: printable Code 128 case labels in two sizes, and a plug-in USB scanner that pulls up the case. Check In and Mark Ready can be scanned in a batch. Included on every plan.
Went live
Asked by a crown & bridge lab using one business inbox for everything
Asked for: they said it is hard to get dentists to send to just one address, and there was no way to stop everything else in that inbox from turning into a case.
Shipped: a per-lab list of approved senders. Only mail from an address on that list creates a case; everything else waits for you to look at it.
Went live
Asked by a crown & bridge lab
Asked for: their dentists did not recognise invoice emails, because the sender was us and not the lab. They also wanted to know when an invoice was paid.
Shipped: doctor-facing mail now goes out under the lab's own name, and the lab gets a notification the moment a payment lands.
Went live
Asked by a one-person lab
Asked for: the dentist is not the person who pays the bill — the clinic's bookkeeper is, at a different address.
Shipped: an optional separate billing email on each doctor. Invoices and statements go there; everything else still goes to the dentist.
Went live
Asked by a lab that reports its units to an accountant
Asked for: they wanted a monthly report of how many units were completed, without counting them by hand.
Shipped: a monthly production report: units completed, broken out per doctor, downloadable as CSV.
Went live
Asked by a one-person lab
Asked for: they wanted to give a discount to the dentists who send a clean digital file, and have it show on the invoice.
Shipped: a discount on the invoice that carries through the PDF, the accounting exports and any saved-card charge, so the numbers agree everywhere.
Went live
Asked by a crown & bridge lab
Asked for: a case can have several teeth in different shades, and only one shade was printing on the work ticket.
Shipped: the work ticket prints each unit's own shade instead of one case-level value.
Went live
Asked by a CAD design lab
Asked for: they wanted their designers to see only the cases assigned to them — not the rest of the lab's work, and not prices.
Shipped: a Designer role sealed to assigned cases, enforced in the database and not just in the screen. A designer can download a case's files and send a finished design straight to QC.
Went live
Asked by a lab that finds cases on the bench by pan
Asked for: they track cases by patient name but also by pan number, and the pan number was not on the internal work ticket.
Shipped: pan number on the case and printed on the internal work ticket. Pan colour followed later.
Went live
Asked by a lab that asked on its first day and left before we answered
Asked for: they asked how to create a monthly bill for a doctor. No one replied, and they cancelled three weeks later.
Shipped: a monthly statement of account per doctor, summarising the invoices already raised, with a PDF the clinic can pay against. It went live the day after they cancelled. We are keeping this one on the list because that is what happened.
Went live
Asked by a lab weighing us against the system it already ran
Asked for: they looked up old prescriptions by shade in their old software, and wanted to see at a glance how many cases and units were in the lab.
Shipped: search cases by shade or material, including archived ones, and active case and unit counts on the dashboard.
Went live
Asked by labs whose dentists will not use a portal
Asked for: they wanted the dentist to pay the lab bill without being asked to create an account and log in first.
Shipped: every invoice email carries a payment link that opens straight to the bill. Card and ACH, paid into the lab's own Stripe account.
Went live
Asked by a removable lab
Asked for: the case form was built around crown & bridge, and there was nowhere sensible to enter a denture.
Shipped: a removable case type with its own form — the fields a denture case actually needs, not crown & bridge fields renamed.
This list is not everything we built, and it is not everything labs asked for. Plenty of requests are still waiting, and a few we decided not to build. These are the ones where a lab asked, we built it, and we can point at the day it went live.
Describe the job, not the feature. "The bookkeeper at the clinic cannot read the invoice when it prints" tells us far more than "improve the invoice layout", and it is the kind of sentence that turned into most of the lines above.
If your lab pays for SimpleLabOS, the reply comes from the founder rather than a ticket queue. Not every request gets built — some are wrong for other labs, some are too big for now, and a few we get wrong and have to fix twice.
We will not promise you a date before we understand the request. What we will do is tell you honestly whether it is a yes, a no, or a not yet — and if it ships, it shows up on this page with the date on it.
Most of the list above started as one sentence from a lab that had just hit something awkward. If you hit one, write to us.