We built it for the lab down the road.
Not for a hospital group, not for a chain. For the two-room lab on the main road with a busy front desk and a paper register behind it.
A pathology lab is where you give a sample and, later, get a report. Running one means a lot of small steps in a particular order: booking the patient, collecting the sample, entering the results, printing the report, and taking the money. Most small labs still do all of it on paper, and retype every report by hand in Word.
Why small labs get ignored
Serious lab software exists. It is built for hospital groups, priced for hospital groups, and takes weeks and a consultant to set up. An independent lab looks at it once, sees the number, and goes back to the register.
So the tools that actually run most labs in this part of the world are a paper register, a Word template, and a calculator. They work — until it is five o'clock, the phone is ringing, and someone needs yesterday's report reprinted.
What we decided to build
One application that covers the whole day, from the patient walking in to the bill being paid. Not a suite of modules to buy separately. Priced so an independent lab can say yes without a meeting, and simple enough that the person at the front desk can use it the same afternoon.
That last part is the hard one, and it is the constraint we design against. Anything that makes the busy path slower gets cut, however clever it is.
Where it's going
Toward labs with more than one branch under a single account, labs able to refer work to each other on one platform, and deeper pathology — barcode sample tracking, and results arriving from the analyser instead of being typed.
None of that is built yet, and we say so on the features page rather than letting a roadmap sell the product.
§ Non-negotiables
What we will not trade away.
- 01Your lab's data never mixes with another lab'sComplete isolation between labs is the first rule of the system, not a setting. We do not trade it for convenience, ours or anyone else's.
- 02Every screen has to work for a tired technician at rush hourIf a feature makes the busy path slower, it does not ship. Simplicity beats feature-richness, every time we have to choose.
- 03A wrong result is never acceptableClinical correctness comes before speed of delivery. We would rather be late than ship something that puts a number on the wrong report.
- 04It has to work on the internet and the computers you actually haveNot on a fibre line and a new machine. On a patchy connection, on the PC already sitting at your front desk.
— the Limware team
§ Built here
Built here, for here.
Prices in Rupees. Cash and part payments treated as normal, because they are. Reports that print correctly on the letterhead paper you already buy. An interface in English, on a connection that is not always there.
These are not localisation settings bolted onto software designed somewhere else. They are the assumptions the product was built on, which is why it fits.
If you would rather ask a question than read a website, that is genuinely fine — call or message and you will get one of us, not a queue.