Guide · Buying lab software
Questions to ask before buying lab software
Every vendor demo looks good for twenty minutes. What separates a lab that is happy a year later from one that is quietly planning its next switch is usually a handful of questions nobody asked up front: about price transparency, whose name is actually on the report, who owns the WhatsApp number, whether payouts really get paid, and what happens the day you want your data back. This guide is a neutral list of those questions, grouped by theme, with what a good answer actually sounds like.
In short
Before signing with any diagnostic lab software vendor, get straight answers on eight things: public pricing, whose branding appears where, who owns the WhatsApp sending number, whether referral commissions are actually settled or only reported, whether you can export your own data, who sets up your catalogue, how migration is handled, and what the all-in monthly cost really is once every add-on is counted. A vendor confident in its product will answer every one of these directly, in writing, without a follow-up call.
Pricing and transparency
Is the price public, or do you have to "talk to sales" to find out? A price hidden behind a contact form is usually hidden for a reason: either it moves depending on how much you seem willing to pay, or it is higher than the vendor wants to lead with. A vendor that is comfortable with its own pricing puts it on the website.
Is it month-to-month, or does it lock you into an annual contract to get a workable price? Long-term contracts can be a reasonable trade when the discount is real and disclosed upfront. They are a problem when they are the only way to avoid an inflated monthly rate, or when leaving before the term ends triggers a penalty that was never mentioned in the sales call.
What does the number on the page actually include? A quoted monthly price that quietly assumes one branch, a handful of users and a message allowance you'll blow through in the first busy week is not really the price. Ask for the total at your actual branch count, user count and expected WhatsApp volume before you compare it to anything else.
A good answer sounds like a number you can find yourself on the pricing page, plus a plain statement of what triggers overage and what that costs, not a promise to "work something out" once you're already a customer.
White-label and branding
Whose name appears on the printed report, the bill, and the WhatsApp message the patient receives? This matters more than it sounds. Patients associate the brand on their report with the lab they trust, not with a piece of software they've never heard of. If the vendor's logo, colours or watermark show up anywhere a patient can see, that is not really white-label.
Which plan does white-label actually require? Some vendors sell "customisable branding" as a headline feature and then reveal, once you're negotiating, that it only applies above a certain tier, or costs extra per document type. Ask for this in writing before you compare a "branding included" product against one that is upfront about gating it.
For its part, HealthFlow puts the lab's own logo, letterhead and colours on every report, bill, WhatsApp message and QR page the patient sees, with white-label branding available on a higher plan, not on the entry plan. That gate is stated plainly, not discovered later.
WhatsApp delivery: whose number is it, really?
Does the lab get its own dedicated WhatsApp sending number, or does the message arrive from a shared number used by hundreds of other businesses on the vendor's platform? This is one of the most consequential and least asked questions in the entire buying process. A shared sending number means the lab's delivery reputation is tied to every other tenant on that number. If one of them gets flagged for spam, the lab's own patients may stop receiving messages, through no fault of the lab's own.
Can you see delivery status per message (sent, delivered, read), or just a generic "message queued" confirmation? And does the system honour a patient's STOP request automatically, or does someone have to remember to suppress that number by hand?
Read more in our dedicated guide to how WhatsApp report delivery actually works for a diagnostic lab, including why the sending number is the detail worth checking first.
Referral payouts: does it settle, or only track?
When you ask about "doctor referral management," does the product settle the payout, or does it just produce a report of what you owe? This is the single question most likely to reveal a gap between marketing copy and what actually ships. Nearly every lab software claims a referral feature. Far fewer actually move the money.
Ask directly: "If I set a commission rule per test, per doctor, does one run pay every referrer (consultants, collection centres and outside labs) with a statement per payee, or do I still export a spreadsheet and pay each of them myself?" The honest answer to that question separates a report from a settlement.
We wrote a full breakdown of this exact gap, including how TDS and reconciliation against bills should work, in our doctor referral payouts guide. HealthFlow's own answer: a single Pay-Run computes each commission per test as it is billed and settles referring doctors, consultants, collection centres and outside labs together, with a WhatsApp payslip, a printable statement and an Excel export, available on a higher plan.
Data ownership and export
Can you export all of your data (patients, bills, reports, referral history) on your own, without opening a support ticket and waiting? A vendor that makes export slow or support-gated is making it harder to leave than it should be.
Where is your data actually hosted, and is it isolated from other labs' data, or does it sit in a shared database with row-level separation that depends on the application code never having a bug? Ask specifically whether each customer gets its own database or shares one with everyone else on the platform. The answer changes what a single application-level mistake can expose.
HealthFlow gives every lab its own isolated PostgreSQL database, not a shared table with a tenant column: hosted in the EU (Germany), encrypted in transit, with an append-only audit trail and a signed data processing agreement. Data export is available any time, not only on request. Full detail is on our security page.
Support and onboarding
Who actually builds your test catalogue, reference ranges and price list, you, typing it in from scratch, or the vendor, working from files and registers you already have? A lab with hundreds of tests and years of historical records should not be starting from a blank screen.
What is the realistic response time when something breaks at 8pm during a busy shift? Be suspicious of any promise of round-the-clock support with no specifics attached: ask for the actual committed response window in writing, and treat a vague "we're always here" as a non-answer.
HealthFlow's onboarding sets up the test catalogue, reference ranges, price list, doctor list and commission rules directly from the lab's existing files or registers, with full historical data migration available from ₹9,999. Support response is committed at within one business day, stated plainly, not oversold.
Migration: parallel run, or a leap of faith?
Do you run old and new side by side for a period before the old system is switched off, or is it a single cutover weekend with no way back? A vendor that insists on an all-or-nothing switch is asking you to bet a live, billing-critical system on a single day going perfectly.
What is the plan if something is wrong on day one: a missing test, a wrong price, a doctor left off the referral list? Ask for this answer before you sign, not after you've already given notice to your old provider. See our companion guides on how HealthFlow compares on this and other points if you are actively evaluating options.
Hidden costs: read the fine print on "per"
Is the price per branch, per user, or genuinely per lab? A quoted price that looks competitive can double or triple once you add your real branch count and staff headcount. Get the per-branch and per-user add-on cost in writing before you commit.
Is there a setup fee, a mandatory training charge, or a fee to migrate your own historical data in? None of these are automatically unreasonable (data migration is real work), but they should be disclosed upfront as a line item, not discovered on your first invoice.
What happens when you exceed your message allowance: does delivery silently stop, or does it meter at a disclosed rate? A silent cutoff mid-month means patients stop getting their reports with no warning to you or them.
See HealthFlow's full pricing, with every add-on disclosed →
Frequently asked questions
What is the single most important question to ask before buying lab software?
If you can only ask one: "Can I export all my data, on demand, in a format I can actually use, and what happens to my reports and history if I leave?" Almost everything else (pricing, support, migration) is negotiable or fixable after the fact. Being unable to get your own patient and billing data out is not.
Should I trust a demo over a written feature list?
Trust neither in isolation. A feature list can say anything; a demo can be staged around the strong parts. Ask the vendor to run the demo on a scenario you bring (your own price list, your own referral rules, a cancellation and refund) and watch what happens when the answer isn't rehearsed.
Is cheaper lab software always the worse choice?
No, but the price on the page is rarely the price you pay. A lower headline price with per-seat charges, per-branch charges, a mandatory setup fee and paid support add up fast. Ask for the all-in monthly cost at your actual branch and user count before comparing numbers across vendors.
Related
Ask us these questions directly.
A 20-minute WhatsApp demo, on your tests, your referrers and your rules.
WhatsApp us for a demo