LIMS Software Development Services
Custom LIMS software development for labs the off-the-shelf vendors were not built for.
A lab manager retyping instrument printouts into a spreadsheet at 6pm has a systems problem, not a staffing problem. A 200-person lab paying per-seat SaaS fees for workflows the vendor never modelled has a cost problem and a fit problem.
RaftLabs builds custom laboratory information management systems for clinical, environmental, pharma QC, cannabis, food safety, and contract testing labs. Sample accessioning, chain-of-custody tracking, instrument integration, and 21 CFR Part 11 audit trails, built around your actual workflows. Fixed price. You own the platform.
Sample accessioning, barcoding, aliquot splitting, and chain-of-custody built around your real workflows
Instrument integration that pulls results straight off analyzers, with no retyping and no transcription errors
21 CFR Part 11 audit trails and e-signatures designed in from day one, not bolted on before the audit
CAP, CLIA, and ISO 17025 support: SOP enforcement, calibration tracking, and audit-ready records
Fixed price, quoted in writing: you own the code, the data model, and the validation package
Bring the problem, the current workflow, or the existing code. We reply with a practical next step within one business day.
Trusted by
The brief
Start with what is not working.
Good software decisions begin with the constraint, not a list of features or a preferred technology.
Technicians retyping analyzer printouts into spreadsheets at the end of every shift?
An auditor asking who touched a sample in March and the answer living in three inboxes?
Per-seat LIMS fees climbing every quarter for workflows the vendor never quite modelled?
Plain answer
RaftLabs builds custom laboratory information management systems for clinical, environmental, pharma QC, cannabis, food safety, and contract testing labs across the US, UK, Ireland, and Australia. A LIMS tracks every sample from arrival to result, and a custom build wins when off-the-shelf vendors cannot model your workflows, your instrument fleet, or your accreditation requirements.
What to remember
- A focused LIMS v1 is delivered at a fixed price, with audit trails designed in from day one
- A LIMS tracks every sample from the moment it arrives to the moment the result goes out, including who handled it at each step
- Buy the SaaS when your workflows are standard; build when your workflows, instruments, or accreditation needs do not fit the template
- Instrument integration removes retyping: results flow straight from analyzers into the system, validated on the way in
- 21 CFR Part 11 means electronic records count like paper: every change recorded with who, when, and what changed, plus signed approvals
The spreadsheet knows the sample ID. It does not know who touched it last.
A lab manager ends the day retyping analyzer printouts into a spreadsheet while the evening shift waits on results. One transposed digit, one row pasted into the wrong column, and a result goes out attached to the wrong sample.
Across the hall, an auditor asks a simple question: who handled sample 4471 in March, on which instrument, and who approved the result. The answer is spread across three inboxes, a paper logbook, and somebody's memory.
Meanwhile the per-seat LIMS bill climbs every quarter, for workflows the vendor modelled for somebody else's lab.
Three problems, one fix: a system built around how your lab actually works, with the custody record to prove it.
A LIMS, a laboratory information management system, is the software a lab uses to track every sample from the moment it arrives to the moment the result goes out the door. For a non-technical reader: think of it as the lab's memory. Every sample gets an identity, every test gets recorded against it, every handoff gets logged, and every result gets reviewed and approved before it leaves. When it works, an auditor's hardest questions become reports instead of scavenger hunts. When it does not exist, or when it is a spreadsheet, the lab runs on memory and hope.
The cost of running on hope shows up in three places.
- Transcription errors: every result retyped from an instrument printout is a chance to attach the right number to the wrong sample, and in clinical or environmental testing that error can have legal weight.
- Turnaround time: when nobody can see where a sample sits in the queue, promised dates slip and clients call for status instead of placing the next order.
- Audit exposure: when the custody record lives in inboxes and logbooks, an inspection becomes weeks of reconstruction instead of an afternoon of reports.
RaftLabs builds custom LIMS platforms for clinical, environmental, pharma QC, cannabis, food safety, and contract testing labs. Adjacent proof: UrShipper, a multi-carrier logistics platform we rebuilt as the fifth delivery attempt, with the initial build phase taking about 14 weeks. Different industry, same discipline: live tracking, mobile workforce apps, and workflow software that has to be right every time. RaftLabs is rated 4.9/5 by clients on Clutch, and our healthcare work covers the regulated-software habits a LIMS demands. The team that scopes it ships it.
This works when the off-the-shelf LIMS was modelled for somebody else's lab.
Everything on the left should already be true for your lab. Even one thing on the right, and a commercial LIMS is the smarter first step.
Workflows the SaaS vendors cannot model: unusual sample types, multi-step approvals, or a research operation a manufacturing-sector LIMS was never designed for.
An instrument fleet the vendor cannot talk to, or data that has to flow into systems the SaaS was not built around.
Accreditation pressure (CAP, CLIA, ISO 17025) or FDA exposure where the audit trail and validation package have to be designed in, not retrofitted.
Standard workflows on supported instruments, where Thermo Fisher, Sapio, Scispot, or QBench already fits and you need to be live this quarter.
A small lab where a spreadsheet plus disciplined process still covers the volume and nothing is regulated.
You want a monthly subscription with vendor support and no upfront build, not a platform you own.
The first decision is not what to build.
It is whether a custom LIMS is the right answer at all. We use four possible recommendations before discussing a development scope.
- 01
Buy
Choose a maintained product when it handles the core workflow and the remaining gaps can be solved with configuration, a connector, or a small process change. Paying for LIMS software you do not have to maintain is often the better trade.
- 02
Repair
Keep the existing product when users still get value from it and the code can be understood safely. Start with evidence: where the code lives, how the data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live.
- 03
Build
Own LIMS software when the workflow shapes margin, customer experience, speed, or a product customers pay for. Start with one complete path and the system connections that path cannot work without.
- 04
Wait
Do not turn a changing policy into permanent software. Stabilise the rules, name the workflow owner, and measure the cost of the current process before paying for a product.
Not sure which path is yours? Bring it to a 30-minute call. Leave with the answer in writing.
What we build
LIMS software development capabilities
Sample accessioning and tracking
Intake built around your receiving bench: log the sample, assign the unique ID, print the barcode, split aliquots as child samples linked to the parent, and track storage location down to the freezer shelf. Every sample findable years later.
Chain-of-custody tracking
Every handoff as a scanned event: received, aliquoted, tested, reviewed, approved, reported. Out-of-order steps get flagged, not silently accepted. The unbroken record auditors and regulators ask for, generated as a byproduct of doing the work.
Instrument integration
Results pulled straight off analyzers into the LIMS, validated on the way in and linked to the right sample, test, and batch. Modern instruments via HL7 or ASTM messaging; older ones via parsed file drops. Raw instrument files archived alongside results for the audit trail. No retyping.
21 CFR Part 11 audit trails and e-signatures
Immutable history on every regulated record: who changed what, when, old value and new value, with a log that cannot be edited or deleted. Approvals captured as e-signatures with stated meaning. Designed into the data model from day one.
Batch, lot, and QC management
Samples grouped into batches with QC samples, blanks, and duplicates placed by your method rules. Control charting on QC results, out-of-spec flags before the batch ships, and lot genealogy for reagents and consumables.
Results review and approval workflows
Multi-level review modelled on your SOPs: analyst entry, technical review, final approval, with electronic signatures at each gate. Failed or out-of-range results route to investigation instead of slipping through.
Inventory, reagents, and calibration
Reagent lots linked to the tests that consumed them. Instrument calibration and maintenance schedules with alerts before they lapse. Stock levels that reflect actual usage, not last month's guess.
Lab data analytics and AI
Turnaround time by test, analyst, and client. QC trend analysis that spots instrument drift before it becomes a failed batch. Anomaly detection on results patterns. The numbers that show whether the lab is getting tighter, built on data the LIMS already holds.
How we run a LIMS build
Compliance designed in, not bolted on
We write the compliance plan in the first phase: audit trail design, e-signature workflow, access controls mapped to your SOPs, and the validation package scoped before any code exists.
Instrument reality, not brochureware
We inventory every analyzer during the workflow audit: what it outputs, what protocol it speaks, whether the vendor exposes an interface. The integration scope is fixed in the quote. No discovering late in the build that the workhorse analyzer only prints.
Honest build-vs-buy advice
We will tell you when Thermo Fisher, Sapio, Scispot, or QBench is the right answer. A custom build has to earn its keep against mature SaaS, and we scope the comparison with you before proposing anything.
Validation documentation included
IQ/OQ/PQ documentation, in plain terms the paperwork proving the software was installed correctly, works as specified, and performs under real conditions, ships with the build. Your QA team reviews it; your auditor reads it.
Fixed price, quoted before code
The workflow audit ends with a written scope and a fixed-price quote. No hourly billing, no per-seat fees that grow with headcount, and scope changes are priced and agreed before any additional work starts.
Parallel run, no hard cutover
Labs do not get maintenance windows. The new LIMS runs alongside the old process on a subset of samples, results are reconciled between the two, then the full lab cuts over with a tested rollback plan.
Custom LIMS build vs off-the-shelf LIMS SaaS
| Off-the-shelf LIMS SaaS | Custom LIMS (RaftLabs) | |
|---|---|---|
| Cost model | Per-seat subscription for software you never own | Fixed build cost, then infrastructure billed at cost; you own the platform |
| Workflow fit | Your lab adapts to the vendor's model; unusual workflows get worked around | Accessioning, approvals, and batch logic modelled on your SOPs from day one |
| Instrument coverage | Only analyzers on the vendor's supported list integrate cleanly | Connectors built for your actual fleet, including older instruments that only print or drop files |
| Compliance | Vendor's validation package; you accept their interpretation of Part 11 | Audit trails, e-signatures, and IQ/OQ/PQ documentation designed around your QA requirements |
| Ownership | You rent access; migrating off means rebuilding your data model | Code, data model, and validation package are yours from day one |
| Time to value | Live in weeks if your workflows fit the template | A focused v1; the honest trade for a system built around your lab |
How much are per-seat LIMS fees costing you this year?
Tell us your sample volume, your instrument fleet, and your accreditation requirements. We will scope the system and give you a fixed price.
How it works
From workflow audit to validated LIMS
- Phase 101
Lab workflow audit
We map your real workflows with the people who run them: accessioning, testing, review and approval, reporting, and every instrument on the bench. Compliance requirements (Part 11, CAP, CLIA, ISO 17025) are mapped to system features. You leave the first phase with a written scope and a fixed-price quote. Development starts only after sign-off.
- Phase 202
Design and compliance plan
UI design for the lab portal approved in Figma before any code is written. Data model, audit trail design, e-signature workflows, and the validation plan (IQ/OQ/PQ) documented and reviewed by your QA team.
- Phase 303
Build in modules
Accessioning and tracking first, then chain of custody, then instrument integrations, then review and approval workflows. QA runs alongside the build. Your team tests each module against real samples in a staging environment as it lands.
- Phase 404
Validation and parallel run
The validation package is executed and documented. The new LIMS runs alongside your existing process on a subset of samples, results reconciled between the two, then the full lab cuts over with a tested rollback plan. Post-launch monitoring and support are agreed as their own arrangement before release.
Pitfalls we plan around
LIMS projects fail in predictable places. We scope for these before the build, not after the first failed audit.
- Compliance as an afterthought
- Audit trails and e-signatures retrofitted onto a finished system are where Part 11 projects struggle. The compliance plan is written in the first phase and the audit trail is part of the data model, not a feature added before the inspection.
- Instruments that only exist as PDFs
- The brochure says the analyzer has an interface; the bench reality is a printer and a shared folder. We inventory every instrument during the workflow audit, test what it actually outputs, and fix the integration scope in the quote before anyone commits.
- Accessioning designed for one lab
- A receiving workflow that works for environmental water samples breaks on clinical specimens with different identifiers, consent rules, and turnaround promises. We design accessioning around every sample type you run, including the ones you plan to add next year.
- Validation nobody wrote down
- Software that works but cannot prove it works fails a regulated audit. IQ/OQ/PQ documentation is a deliverable with what 'done' looks like agreed in writing, reviewed by your QA team, not a document reconstructed from memory the month before inspection.
- Migration from a decade of Excel
- Ten years of spreadsheets means duplicate sample IDs, inconsistent test names, and results in merged cells. We profile the data during the parallel run, flag what needs cleaning, and migrate only validated records, so the new system starts clean.
Proof it works
RaftLabs has shipped production software since 2015 for clients across the US, UK, Europe, Canada, and the UAE. Laboratory software is a neighbouring problem to the logistics and healthcare platforms we have built: live tracking, workflow software that has to be right every time, and regulated data handled carefully.
Adjacent platform work
- initial build phase of the UrShipper platform rebuild
- 14 weeks
- UrShipper, multi-carrier shipping platform
- migrated customers using the portal by June 2025
- 214
- UrShipper project records
- shipments between May 5 and June 2, 2025
- 1,005
- UrShipper project records
We rebuilt UrShipper, a multi-carrier logistics platform, as the fifth delivery attempt. The initial build phase took about 14 weeks, and the platform went on to handle ongoing releases through 2026. A LIMS is the neighbouring problem: the same live tracking, workflow discipline, and careful migration, pointed at samples and analyzers instead of parcels and carriers.
What clients say
What our clients say
Three-year average engagement. Founders and operators describing the work in their own words. No marketing varnish.
Scope sets the price:
- Focused LIMS v1
- Sample accessioning and barcoding, chain-of-custody tracking, 21 CFR Part 11 audit trails and e-signatures, results review and approval, and one or two instrument integrations.
- Full instrument fleet plus validation
- Adds the complete analyzer fleet, batch and lot management, inventory and reagent tracking, calibration scheduling, and the full IQ/OQ/PQ validation package.
- Multi-site and regulated clinical
- Quoted after the workflow audit. Scope depends on site count, method complexity, and the accreditation checklist your assessor will use.
How pricing works
Start with sample tracking and chain of custody.
Accessioning, chain of custody, instrument integration, and Part 11 audit trails at the core, with batch management, inventory, and the full validation package added as your lab needs them.
Commercial LIMS vendors charge per-seat subscriptions for software you never own. Start with the core tracking platform, own it outright, then add batch management and the full validation package as your lab grows.
Starting investment
Starts at $10K
Ongoing infrastructure is billed at cost, not as per-seat SaaS fees that grow with headcount. Start with tracking and custody, then add instrument fleet coverage and validation depth as the lab grows. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.
No hourly billing
Once we scope your first phase, that price is locked in writing. No hourly billing, and scope changes are priced and agreed before any additional work starts, so your capital budget stays under control.
You own it
All code, the data model, and the validation package are yours from day one. No per-seat SaaS fees, no ongoing licence fees, no vendor lock-in: your lab controls the platform.
This platform rarely stands alone. Results flow in through instrument integration, AI for lab data spots QC drift and turnaround patterns in the data the LIMS already holds, and the compliance habits come from our healthcare work. When the LIMS is one system among several, custom software development connects it to billing, reporting, and client portals on the same data layer.
Work with us
Tell us where the work is stuck.
Bring the rough workflow, half-built product, or messy brief. We will map the smallest useful first move, then send scope, timeline, and price in plain English.
- Scope and cost agreed before work starts. No surprises. No obligation.
- Working prototype within 3 weeks of kickoff.
- Pay by milestone. You see progress before each invoice.
- 60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
- All conversations are NDA-protected.
Frequently asked questions
Straight answers to what buyers ask before they scope. Still stuck? .
Buy the SaaS when your workflows are standard, your budget is tight, you need to be live this quarter, and your instruments are all on the vendor's supported list. Thermo Fisher SampleManager, Sapio, Scispot, and QBench are mature products with validation packages and support teams, and for a straightforward lab they are the honest recommendation. Build custom when your workflows do not fit the template: multidisciplinary labs, unusual sample types, or approval chains the SaaS cannot model. Or when per-seat fees have outgrown the value, your instrument fleet includes analyzers the vendor cannot talk to, or you want the data model and the validation documentation to be yours, not rented.
First phases start at $10K, and every build is quoted at a fixed price in writing after the workflow audit. A complete quote names every part of the job line by line: sample accessioning and chain of custody, who does what and who can see and change what, each instrument connection, moving your existing sample and result records over, the audit trail and e-signature work, and the validation package, so nothing your lab needs is left to be billed later. Scope is set by the number of instruments, batch and lot management needs, inventory and reagent tracking, the validation package, site count, and the accreditation checklist your assessor will use. Changes are priced and approved in writing before the work starts, so the quote in the project brief is the final invoice. Regulated software is genuinely more expensive to build well, and any quote far below a credible range is skipping validation, security, or both.
A basic sample tracker, yes. A production LIMS that survives an FDA or accreditation audit needs instrument drivers for analyzers that speak different protocols, role-based access with audit trails on every record, e-signature workflows, a validation package proving the software does what it claims, backups and security hardening, and someone to maintain all of it for years. That is the real risk of the solo build: not the first version, but the fifth year. If you have a dedicated team with regulated-software experience and a long-term maintenance budget, an internal build can work. If the plan is one person in their spare time, buy the SaaS or hire a team that ships regulated software for a living.
21 CFR Part 11 is the FDA rule that lets electronic records and signatures stand in for paper, provided the system meets certain controls. Every create, edit, and delete on a regulated record is logged with who, when, old value, and new value, and the log itself cannot be edited or deleted. E-signatures link a credential entry with a stated meaning, such as reviewed or approved, permanently to the record. Both are designed into the data model from day one. Retrofitting compliance onto a system not built for it is where Part 11 projects typically struggle, so the compliance plan is written in the first phase.
Modern analyzers send structured messages over lab standards such as HL7 or ASTM, which we parse and validate on the way in: sample ID matched, result in range, flags preserved. Older instruments print or drop CSV files, and we build connectors that watch those outputs and load results with the same validation. Results land in the LIMS already linked to the right sample, test, and batch, with the raw instrument file archived alongside. During the workflow audit we inventory every analyzer and fix the integration scope in the quote before work starts.
Chain of custody is the unbroken record of who handled a sample, when, and what they did. It starts at accessioning, where the sample is logged, given a unique ID, and barcoded. Every handoff is a scanned event: received, split into aliquots, tested on a specific instrument by a specific analyst, reviewed, approved, reported. Storage location is tracked so a sample can be found years later. Skipped or out-of-order steps are flagged, never silently accepted. For environmental, forensic, and cannabis labs, where results can end up in court, this record is the product as much as the result.
For some labs the spreadsheet wins. An ELN records what an experiment was; a LIMS tracks samples, tests, results, and custody at operational scale, and many labs run both. You do not need a LIMS if volume is low, nothing is regulated, and errors are cheap to fix. You need one when spreadsheets produce transcription errors at hundreds of samples per week, an accreditor expects controlled records, results carry legal weight, or turnaround promises depend on knowing where every sample sits.
Configuration survives upgrades; customization breaks them. Ask whether you can configure workflows yourself, and whether the system flexes to your workflows instead of forcing a QC-lab model on a research lab. The buyer, not the vendor, is the usual delay in implementation: master data readiness is the bottleneck.
For SaaS, ask where the database is hosted, which security certifications exist, who owns the data, and how easy backups are. Encryption, backups, and access control apply either way. The scaling question: if you add five users, is it a simple fee or a new enterprise tier that changes the cost? Start the cost-of-ownership assessment with how the solution fits your budget.
Accreditation is the lab proving it follows its own procedures, every time. A LIMS generates that proof without the paperwork: required fields, approval steps, and method versions are built into the workflows instead of documents people skim. It tracks analyst training and competency dates, instrument calibration schedules with alerts before they lapse, reagent lots linked to the tests that used them, and corrective actions with owners and due dates. At inspection time, sample histories, audit trails, and calibration logs are reports, not scavenger hunts.
You do, from day one. The code, the accounts, your lab data, and the project notes are yours from the start, not only after delivery, and the accounts are in your name. The operating and validation notes stay current as the work goes, so another capable team can take over at any point. Outside services and open-source pieces keep their own licence terms.
You already hold everything another team would need: the code, the accounts in your name, your data, and notes that stay current through the build. There is nothing to extract from us and no handover to wait for. We do not offer source-code escrow, because nothing is held back for escrow to release.
Penetration testing is taken care of. No production data is used in development, ever: building and testing run on made-up or approved sample data. Backups are tested, not just scheduled. When someone leaves the team, offboarding steps remove their access. The third-party services the system depends on, such as hosting and any service that processes your lab data, are named in the scope document before you sign. We claim practices we can show you, not certifications.
Yes. On projects that handle protected health information, such as patient results in a clinical lab, we sign a Business Associate Agreement before access to that data. The rules themselves stay your lab's obligation: a LIMS can carry the controls your assessor asks for, such as audit trails, e-signatures, and who can see and change what, but your own procedures and agreements complete the picture, and a system is never called compliant until the technical, operational, and legal requirements are all verified.
Support after launch is agreed as its own arrangement, in writing, before the first release. It is not a fixed period bundled into the build price. Running the system also carries standing costs whoever looks after it: hosting, instrument connection upkeep as analyzers and their software change, security updates, and keeping the validation records current when workflows change. We name those costs in the scope so they are in your budget from the start, not discovered after launch.
The calendar is set once the workflow audit shows the scope, and we do not invent a range before that. What fills the calendar is more than writing screens: the workflow audit, the design and compliance plan your QA team reviews, building in modules, and the validation and parallel run, where the new system runs alongside your current process on a subset of samples and the results are reconciled before the full lab cuts over. Dates slip most often when instrument details surface late, when approval reviews wait on a busy lab team, or when scope changes mid-build, which is why changes are priced and approved before work starts.
We work by five principles. 01 Switch to Async: most updates are written, so your lab team can read and reply between benches instead of sitting in meetings. 02 Be Prepared: calls come with the questions and material shared ahead of time. 03 Write: decisions and changes are written down where both sides can find them, not left in a call. 04 Ask/tell: ask when something is unclear, and tell us early when something changes on your side; we do the same. 05 Own: the person working on a piece owns its progress and says so plainly, including when something is late.
Yes. We sign your NDA before anything sensitive is shared, and the workflows, instrument details, and sample data you share for scoping stay confidential.
The team that scopes your LIMS does the work. We do not hand projects off to another team or subcontract the build out. Our teams are in India and Ireland, and the people on your calls are the people on your project, so you can talk to the people doing the work directly.
AI is part of our workflow across the whole build, from testing to writing code, and that work runs through RaftKit, our own AI workflow process at raftkit.com. It works in five phases: Blueprint, Plan, Build, Review, and Compound. Work passes set quality gates, and code goes through a two-stage review before it ships, with serious problems blocking the release. For a regulated system that matters: the question is never whether AI helped write a line, but who checked it, against what checks, before your lab relied on it. A named person stays accountable for what ships.
![Custom LIMS software development for [labs the off-the-shelf vendors were not built for.]](/_next/image?url=https%3A%2F%2Fassets.raftlabs.com%2Fservice-assets%2Flaboratory-information-management-software%2Ffeatured.png&w=3840&q=75)