FertilityWindow Book a demo
The author

Jimenez Julien, the person accountable for FertilityWindow

I build one product at a time, for one trade at a time. This one is for the coordinator who holds the cycle calendar for forty women at once.

Portrait of Jimenez Julien, founder of MLJ and author of FertilityWindow

Contact the author

Write to jimenezjulien42@gmail.com. Product questions, corrections and pricing questions all reach me directly, and I answer within one business day.

Why I built a calendar product for fertility clinics

I started this work after sitting in on a Tuesday morning at a two physician practice outside Louisville. The coordinator had a legal pad with fourteen names on it, and beside each name a time she had already tried calling. Every one of those calls existed because a piece of information that was completely settled inside the clinic had not reached the patient. The protocol was not in doubt. The dose was not in doubt. The date of the day 8 scan was not in doubt. The only thing missing was a reliable way to put that certainty in a woman's hand and get an acknowledgement back.

That gap is what FertilityWindow closes. It is not a diagnostic tool, it does not make clinical decisions, and it has no opinion about your protocols. It takes what your physicians have already decided and renders it as a dated calendar the patient can follow, then carries her confirmation back to the person who needs it. Everything else in the product exists to serve that loop.

What I learned about this trade

Three things, all of which changed the software. First, fertility coordination is not appointment scheduling. A stim cycle is a moving object: the day 6 estradiol result can shift the dose, which shifts the trigger, which shifts the retrieval, which shifts everything downstream. Any tool that treats the schedule as fixed will be wrong by the middle of the second week. So the calendar had to be built to reissue itself and to keep the previous version, because a coordinator who cannot show what a patient was told last Thursday is exposed.

Second, patients in treatment are carrying a great deal, and the interface has to be quieter than a normal consumer app. The early prototypes showed the full cycle grid, and coordinators told me plainly to stop. A woman on stim day 4 does not benefit from staring at a retrieval date that may move. We now show today, tomorrow and what needs confirming, and nothing else unless she asks for it.

Third, the coordinator is the operator, not the physician. She is the one who will use this forty times a day, and she has almost certainly been handed software chosen by someone who does not do her job. So the decisions in this product are hers: what a cycle looks like, what the morning list sorts by, what gets exported to the chart. When a physician and a coordinator disagreed about a feature during a design call, I built it the coordinator's way and it has never been the wrong call.

How I work with clinics

I run the demo calls myself. That is not a growth strategy, it is how I keep the product honest: I hear the same objection three times in a week and I know what to fix. Onboarding is a working session with your lead coordinator, entering your protocols in your language. I do not ask clinics to change how they prescribe to suit a data model. If your practice writes a mini stim differently than the practice down the road, both versions live here without argument.

What I am accountable for is narrow and specific. The calendar a patient receives must match what her clinic entered. Changes must be time stamped and attributable. Patient links must expire when the cycle closes. Billing must be simple enough to explain in one sentence, and cancellation must never require a phone call. If any of those breaks, it is my name on it and my inbox that hears about it.

Experience and expertise

  • Founder of MLJ, SASU, the French company that publishes FertilityWindow and a small number of other operator focused products.
  • Fourteen years building scheduling and coordination software for small operators, with the last four spent in clinical settings.
  • Design work grounded in on site observation: I sit through monitoring blocks before I write a line of interface.
  • Direct working relationships with lead nurse coordinators in practices from 40 to 400 cycles a year across the United States.
  • Responsible for the product roadmap, the pricing, the support inbox and the words on this website.

How this product is built and maintained

FertilityWindow ships small, frequent updates rather than large releases, and every change that touches a patient facing calendar goes to two clinics first. Nothing on this website is written by a marketing department: every number here comes from either our own usage data or the annual coordinator survey, and if a figure cannot be sourced it does not appear. When we get something wrong, we correct the page rather than quietly deleting the claim.

Editorial standards are the same ones I would want as a buyer. We do not publish invented testimonials, we do not compare ourselves to named competitors, and we do not describe a feature that is not shipped and running in production today. Support is answered by people who have watched a monitoring block, and escalations come to me. The product is funded entirely by subscriptions, which means clinics are the customer and there is no advertiser to please.

Published articles

Everything below appeared in Cycle Desk, the FertilityWindow magazine, where I answer the questions fertility coordinators and clinic managers actually put to me.

Find me elsewhere

Ready to see the product against one of your own protocols? Book a demo or read the frequently asked questions first.

Portrait of Jimenez Julien, the author and publisher of FertilityWindow

Published and maintained by Jimenez Julien. Questions about this page can go straight to jimenezjulien42@gmail.com.