Contact
One inbox, and the team that wrote the code reads it.
There is no sales team to be routed to and no ticket queue to be numbered by. Describe your bench and you will get an answer from the LabFlow team, or an honest no.
This is the component library, not a picture of it. Change the theme in the header and it changes with the rest of the page.
Four reasons people write, and only one of them needs this form.
Three of these are answered faster somewhere else on this site. Reading two paragraphs now beats waiting three days for the same two paragraphs.
Does it do what my bench needs
This is the one worth writing about. Feature lists cannot answer it, because the question is never whether a capability exists, it is whether it expresses how you already work.
What would it cost
There is no price list, so this is a conversation. Read what drives the number first and bring three figures with you, and the conversation starts one round further along.
List my laboratory
The marketplace application is its own five-state process with a person reading it. It does not start here and sending it here only adds a step.
The awkward questions
Who builds it, how many laboratories run it, whether there is a BAA, what happens if the LabFlow team stops. All answered in writing already, including the uncomfortable ones.
Tell me about one bench.
Not your whole organisation. One department, one workflow that currently costs someone an afternoon a week, and roughly how much of it there is. That is enough to say honestly whether this fits.
There is no attachment field, deliberately. An upload on a contact form invites a spreadsheet of results, and a laboratory sending real specimen data to a stranger's inbox is a problem this form should not create. If a sample message matters, paste a de-identified fragment into the message using the code button.
Four things that make the first reply useful instead of a question back.
None of these is a qualification hurdle. They are the four things that otherwise have to be asked, which costs a round trip and about three days.
The shape of the work, not the size of the organisation
Tests per month, how many sites, how many people touch a specimen between the draw and the release. A laboratory running 3,000 tests across one bench and one running 3,000 across four collection points are different problems with the same number in them.
Order of magnitude is enough. Nobody is going to hold you to it.
The workflow that currently costs someone an afternoon
The recurring irritation is more diagnostic than the requirement list. Chasing a specimen by telephone, retyping a result into a second system, reconstructing which control run was in force six months ago. That is the sentence worth writing.
If it fits in one sentence you have already written the most useful part of the message.
What has to keep working on day one
The analyser middleware, the billing system nobody is allowed to touch, the accreditation report that has to come out in a specific shape. These are what decide whether a migration is a month or a year, and they are usually the last thing anyone mentions.
This is also where most honest answers of no come from, and earlier is better for both sides.
What you have already ruled out, and why
If you have looked at a larger system and stopped, the reason is the most useful paragraph in your message. It says what you are actually optimising for far better than a feature checklist does.
The comparison pages exist for the same reason, and they name where the other product wins.
Never put patient data in a contact form. Not this one, not anybody's.
This needs saying plainly on the page rather than in small type under a button, because it is the single most common way a laboratory creates a breach out of an ordinary Tuesday afternoon.
Do not send names, dates of birth, medical record numbers, accession numbers, requisitions, result exports or screenshots of a live system. A message describing the workflow answers the question just as well and creates no obligation for either of us.
Instead of a result export
Describe the columns. "Analyte, value, unit, flag, one free-text comment per result" tells the whole story and identifies nobody.
Instead of a screenshot
Say what is on the screen and what you have to do next. Screenshots of live laboratory systems carry patient data in places nobody remembers to redact, including window titles.
Instead of a real message
Replace every identifier with a placeholder before you paste an HL7 segment. The segment structure is the part that matters and it survives de-identification intact.
If patient data has already been sent to this inbox by mistake, say so in a follow-up message. It will be deleted and you will be told when, in writing. That is a stated practice, not a contractual undertaking, and there is no business associate agreement behind it.
Four steps, and none of them is a nurture sequence.
Writing this down is the whole point of the section. A process nobody has described is a process the reader has to assume, and most people assume the version with a sales cadence in it.
One consequence worth stating. One team in one time zone with no rota means a message sent on a Friday evening is read on a Monday, and a message sent during a week of heavy development waits behind it. That is the honest shape of a product with no rota, and it is the same shape as the support answer.
Three answers you might get, and all three are real outcomes.
A vendor site that only describes the yes is describing one third of what happens. The other two are more common and both are more useful than a demo booking.
The workflow maps onto what exists. The reply says which parts map cleanly, which need configuration, and which need work that is not built yet, with that last list stated rather than absorbed into a timeline.
The common one. Most of a laboratory fits and one thing does not, usually billing, calibration or a specific accreditation report. The reply names it as a gap rather than a roadmap item.
If revenue cycle is the requirement, or you need a signed BAA, or you run overnight and need someone reachable at 03:00, this is the wrong product. The reply says so and points elsewhere.
The ledger
Things a contact page usually implies, that this one does not have.
Every row here was either advertised on the previous version of this site or is simply assumed by anyone who has contacted a software vendor before.
Previously advertised on this site. There is no rota, no on-call engineer and nobody further to escalate to. A laboratory that runs overnight should weigh this before anything else on this page.
A few working days is a description of what usually happens, not a commitment. Nothing on this page is contractual, and an SLA the LabFlow team cannot honour is worse than none.
None exists today, which is exactly why the section above tells you not to send patient data. LabFlow is HIPAA conscious in its design. It is not certified, and no software can be.
There is no sales team to run one. There is also no hosted demo environment to sign into and no trial to start, so this site offers neither. The conversation is the honest first step.
A message reaches a real inbox rather than a queue. That is a consequence of the size of the team rather than a service promise, and it means there is no reference number to quote back.
Publishing an address that is somebody's home to look like a company is the kind of small dishonesty this site is being rebuilt to remove. A real one is provided in writing when a contract needs one.
Answered faster somewhere else
What happens to the message itself.
Short, because there is not much to describe. A contact form that needs three paragraphs to explain its data handling is usually explaining a marketing stack.
- It goes to one inbox and is read by the LabFlow team.
- It is not added to a mailing list, because there is no mailing list.
- It is not passed to a customer relationship system, an enrichment service or an advertising platform. None of those is connected to this form, and the message is never used to target anything at you.
- It is kept while the conversation is useful and deleted when it is not. There is no published retention period and inventing one would be a claim nobody is auditing.
- If you ask for it to be deleted, it is deleted and you are told when.
The full statement, including what the product itself does with laboratory and patient data, is in the privacy policy. This section covers only the contact form, which is a different and much smaller question.
Two versions of the same message.
Both are polite, both are reasonable, and only one of them can be answered without a round trip. The difference is about ninety seconds of writing.
"Hello, we are a laboratory looking at replacing our current system. Could you send some information about your product and pricing, and let me know if you offer a demo? Thanks."
Every answer to this is a question. What kind of laboratory, how much of it, replacing what, and for which reason. Three days pass and the conversation has not started.
"Two sites, about 18,000 tests a month, mostly chemistry and haematology. We are on a system that cannot tell us which control run was in force for a result six months ago, which came up in our last assessment. Analyser middleware stays. Is that a fit, and roughly what would it cost?"
Volume, sites, the actual pain, the constraint, and the two questions. This gets a real answer, including the parts that are a no.
There is no wrong way to write to a person. This section exists because the second version gets an answer three days sooner, not because the first one will be ignored.
The worst outcome here is a polite no, and it arrives quickly.
Nothing on this page is a qualification funnel, because there is nothing to qualify for. There is no trial to start, no seat to reserve and no quota to hit. The only thing a message can produce is an accurate answer about whether a piece of software fits a laboratory.
If it does not fit, you will be told that, and told what to look at instead. That is cheaper for both of us than a discovery call.
One inbox, read by the LabFlow team, and no case number coming. If the awkward questions are what is holding you up, they are already answered on the FAQ.