Fertility Clinic Software: Build or Buy, and Why the Spreadsheets Already Answered It

When is off the shelf genuinely the right call here?

Keep eIVF or IDEAS if you are a single site doing under roughly 300 retrievals a year, your donor work is referral only, you bill insurance rather than running refund programmes, and your laboratory director is comfortable with the workbook. Both are real products maintained by people who understand assisted reproduction, and rebuilding demographics and scheduling to own them is a poor trade at that scale.

Keep your practice side products too, at any size. Epic or athenahealth for the practice, EngagedMD for consents, RI Witness or Matcher for witnessing at the bench. The witnessing systems do their job well: RI Witness will not let an embryologist open two patients dishes at one station, and nothing you commission improves on that.

Buy also if your constraint is capacity rather than coordination. A clinic whose real problem is embryology staffing or theatre availability will not be helped by software, and no amount of workflow improves a bottleneck that is physical.

There is also a purchase below the build bands worth naming so nobody mistakes it for a platform. A tool that replaces one spreadsheet, typically a cryogenic storage register with billing anniversaries attached, costs $25,000 to $45,000. That is often a sensible buy, because the storage spreadsheet is where the liability sits, but it is not a clinical system.

The signal that buying is still right is that no critical process has escaped the product. What ends the buy case is the moment you notice the workbook is the system of record and the vendor is a document store.

When does a custom build actually pay off?

The distinction that decides this is simple. Packaged assisted reproduction software documents a cycle after it happened. What a high volume group needs is software that runs the cycle while it is happening, and those are materially different pieces of engineering.

Build when three signals appear together.

• You are multi site or acquiring, and protocols differ enough that no configuration screen reconciles them. One group coasts above a threshold the medical director set, the practice you bought last year starts antagonist on a different rule, and the protocol lives in a senior nurse's head. When she is out, the day slows and the calls get inconsistent.
• Your highest value operations already live outside the vendor product. The donor programme with its eligibility clocks and family limits, the refund programme, the cryogenic ledger on a laminated tank map with pencil corrections. Each of those is custom software already, with no audit trail.
• You asked your vendor for a change that affects margin and got a roadmap answer measured in years.

The picture behind those signals is a Saturday monitoring bay: fifty five patients drawn before half past eight, results posting mid morning, two coordinators reaching all of them before noon with a dose change, a hold, or a trigger time to the minute. That decision touches four systems and a phone call, and the reason for it ends up as free text nobody can query later.

The other half is the handoff to genetics. Three weeks after you ship a biopsy tray, a result arrives keyed to the testing laboratory's tube identifier rather than your embryo identifier, and somebody maps them by hand.

How do they compare on the things that matter in this industry?

On demographics, scheduling and document storage, buying wins outright.

On witnessing at the bench, buying wins absolutely.

On the monitoring day, a build wins because a protocol is logic rather than a field. Scan measurements entered once by ovary and size bucket, results arriving on the cycle the moment they resolve, protocol rules evaluated live with site level variation, and a ranked call queue telling the coordinator who needs a call and what changed. Every dose change writes an immutable audit row carrying the values on screen when it was made.

On chain of custody, a build wins because it owns both ends of a handoff no vendor spans. Every gamete and embryo carries a durable identifier from the moment it exists, with a lineage graph recording which oocyte, which sperm source, which fertilisation method, which grading events, which biopsy and which result. Ingestion is built per laboratory, because Cooper Genomics, Natera and Igenomix do not agree on a format, and the match should be proposed for an embryologist to confirm rather than committed automatically.

On cryogenic storage, a build wins because three facts have never been in one place: what is in the tank, who stopped paying storage fees, and who has a signed disposition consent. Treat inventory as a ledger where every move is a transaction rather than an edit, and the abandoned specimen report becomes a query instead of a project.

On integration burden, buying wins, because laboratories change message formats and record vendors upgrade on their own schedule.

On portability, building wins, and here the records outlive most vendors.

What does total cost of ownership look like at your scale?

A focused first release runs $60,000 to $130,000 over 12 to 16 weeks, and in this category it is almost always the cycle engine plus the monitoring day workflow, running alongside eIVF or IDEAS rather than replacing them. A full platform covering embryology, the cryogenic ledger, donor matching, billing and reporting runs $150,000 to $400,000 phased over 6 to 12 months.

A worked shape. A three site group at roughly 900 retrievals a year, on eIVF for demographics with a stimulation workbook on a shared drive: discovery capturing each site's protocol rules with the medical director $9,000, cycle object with state machine and site level rule versioning $28,000, monitoring day workspace with scan entry, live protocol evaluation and a ranked call queue $24,000, health data interface to the primary reference laboratory $14,000, drafted call scripts generated from the actual values for coordinators to edit $8,000, role based access with immutable audit rows and electronic signature handling $16,000, and hosting with a security review and validation documentation $10,000. That is $109,000, and coordinators use it the first Saturday after go live.

Compliance is about a quarter of that release. Audit trails, role based access, electronic signature handling to a 21 CFR Part 11 standard and the validation pack your College of American Pathologists inspector will ask for are deliverables with hours attached, not a quality that appears at the end.

Interface count moves the number more than retrieval volume does. Each reference laboratory, each electronic medical record connection, each testing laboratory and each witnessing vendor is priced separately, and witnessing in particular is a commercial negotiation before it is engineering. Running costs are 15 to 20 percent of build a year, with interface maintenance and compliance upkeep as the two recurring lines.

What does the hybrid look like, and when is it the honest answer?

In this category the hybrid is the recommendation for nearly every clinic that builds, and it is not a compromise. Keep eIVF or IDEAS. Keep Epic or athenahealth. Keep the witnessing system. Then build the cycle engine and monitoring day beside them, because that is where coordinator hours go and where a transcription error costs the most.

The scoping discipline matters as much as the decision. Scan entry, laboratory results, protocol evaluation, a ranked call queue and an audit row per dose change is a complete and useful release. Adding embryology grading, donor matching and billing to release one is how a twelve week project becomes a twelve month gap between payment and value, in a clinic with patients starting stimulation next Monday.

Take one reference laboratory interface first. Most clinics send the large majority of monitoring bloods to a single laboratory, and the second and third interfaces can wait without slowing a single monitoring day. Migrate forward rather than backward: bring across open cycles, current cryogenic inventory and active donor records, and leave closed historical cycles queryable in the legacy system. Full historical migration is sometimes necessary and always expensive, so make it a deliberate decision rather than an assumption.

Then sequence the cryogenic ledger and donor matching as phase two at $55,000 to $90,000, depending on whether tank telemetry is included. They carry the liability, which is why clinics want them first, and they should not be first, because they need a physical inventory verification alongside the software and that is an operational project your laboratory has to schedule.

Which should you choose, by operator size and stage?

Single site under 300 retrievals, referral only donor work, insurance billing: keep eIVF or IDEAS and buy nothing else. Revisit when a second site arrives or when a refund programme starts.

Single site with a growing donor programme or a storage backlog: still keep the incumbent, and buy the narrow tool. A cryogenic register with billing anniversaries and consent state attached at $25,000 to $45,000 addresses the liability directly. Before that, do the free thing: write your protocol down. Capturing the rules that live in a senior nurse's head is worth doing whether or not you ever build, it costs clinician time rather than developer time, and it is the single most valuable artefact a future project would start from.

Multi site at 500 retrievals or more with differing protocols: build the cycle engine and monitoring day at $60,000 to $130,000, alongside your incumbent. One laboratory interface, one workflow, real cycles running through it inside four months.

Groups running donor banks, refund programmes or an acquisition pipeline: the full platform at $150,000 to $400,000 phased across three releases. Sequence cycle first, cryogenic ledger and donor matching second, billing and reporting third. Annual outcome reporting improves once a full year of cycle data has been captured properly, because the fields the submission needs become the fields the coordinator filled during the cycle rather than fields somebody chases in March.

Whoever you hire, ask them to model an embryo on a whiteboard before you discuss price. If they draw a table with a grade column, they have not built this. The right answer involves lineage from oocyte and sperm source, an event stream of grading, biopsy, freeze and thaw, and a cryogenic position that is a transaction history rather than a field you overwrite. Ask which interfaces they have shipped, by vendor name, and what they will hand your inspector. Then ask what they would refuse to build first, because anyone who says yes to the whole platform in release one is selling you a long gap between payment and value.

If you would rather someone argued with your brief than agreed with it, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. Nothing about that commits you to the build.