‹ All Plenty pages
Plenty · working notes

Design, distribution, and the hard parts

An IVF logistics app has one job: make sure you never run out of medication in the middle of a cycle. Everything here is built to protect that one promise.

Goes with the clickable prototypeFor figuring out what to buildStatus: concept

The short version

01 Design decisions

Designing for someone who's stressed, tired, and paying close attention

The person using this is in the middle of treatment. Often short on sleep, often scared, and spending a lot of money. Every screen has to earn its place by making one anxious question easier to answer.

The name, and why it isn't pink

Plenty: the promise, as a word. IVF is scarcity anxiety all the way down: eggs, vials, days, money. This app exists to make sure one of those things is never scarce, and the name says so without a metaphor to decode. On purpose, it's not a pink, cursive, baby-themed brand. A common complaint from people doing IVF is that fertility products treat them like they're fragile right when they feel least in control of their own bodies. So the look is calm and medical but warm: a steady teal, warm off-white instead of cold hospital grey, big readable text, and color used only to show status (on track / order soon / running out). Runner-up: Ample, the same meaning in a quieter voice and a less crowded trademark space. An earlier working name, Trellis, was dropped because it needed explaining. Neither finalist has been trademark-cleared yet; the attitude is settled even if the paperwork isn't.

◆ A small design rule

Color only ever means something here. Red means you're going to run out, amber means order soon, green means you're covered. Because everything else is calm, a single red dot on the lock-screen widget actually tells you something.

The reorder math is the whole point, and it's on every screen

Most fertility apps that exist are reminders: take this shot now. The thing that's actually hard to copy, the thing your notes describe as "obsessively checking the fridge and the calendar", is working out when you have to reorder. It pulls together four things almost no app tracks at once:

The result isn't a fuzzy "low" badge. It's a real deadline: "Order Menopur by Thursday 2 PM, or the next delivery is Tuesday, one day after you run out." That one sentence is basically the whole product, and it shows up on the home screen, the meds screen, and the lock-screen widget.

Other apps tell you what to take today. Plenty tells you the last day you can safely reorder before the pharmacy's schedule leaves you stranded.

The trigger shot gets its own treatment

The trigger shot is the one moment in a cycle you can't get wrong: an exact-time injection about 36 hours before egg retrieval. Getting the timing wrong can compromise or cancel the cycle, and a cycle runs $20,000 or more all-in, with $3,000 to $7,000 of that in medication. So it gets its own alarm, separate from ordinary dose reminders, that asks you to confirm twice, and the countdown shows a date range until the clinic locks it in.

The four situations, and what each screen has to do

SituationWhat the person needsWhat the screen shows
First time / setupGet from "the nurse handed me a sheet" to a working schedule in under two minutes.Pick how to bring the protocol in (portal / photo / email / typing) → read it → confirm anything unclear → set times.
Partly set upThe protocol's in, but the cycle hasn't started and there's nothing in the fridge yet, so the reorder math has nothing to work with.A short checklist, not a wall of information; reminders set but quiet until Day 1.
Deep in a cycleAnswer "what do I take, and am I about to run out?" without digging through menus.Trigger countdown with a range, tonight's dose, the reorder deadline, next monitoring visit.
Protocol changedThe clinic changed the plan; quietly overwriting the wrong thing could hurt someone.A clear list of what changed (higher dose, new med, trigger moved) → you approve → it recalculates → new reorder.

The empty, half-set-up, fully-loaded, and "something's uncertain" states are all handled properly, not treated as afterthoughts. During setup, anything the scan wasn't sure about gets flagged for you to confirm instead of being quietly accepted.

▲ Where we draw the line

Plenty never changes a dose on its own, and it never pretends to be the doctor. When the clinic changes something, you see exactly what changed and approve it. It also never places orders for you: it preps the order (what, how much, the deadline, your benefit info) and you place it with the pharmacy by phone or portal. It's a tracker and an assistant, not a medical device and not a pharmacy. That keeps it useful and on the safe side of the rules.

The widget is the part people will actually live in

Your note about a Spotify-player-style thing that stays on the screen is exactly right, and it might matter more than the app itself. During the injection weeks, having to open an app just to check "what's next" is friction and a little bit of dread. So the lock-screen Live Activity and Dynamic Island on iPhone, plus the equivalent always-there notification on Android, home-screen widgets, and an Apple Watch face, keep two facts in front of you at all times: how long until the next shot, and whether you're about to run out. Tap to log it or reorder. Everything else is one layer down.

iPhone first, Android close behind

The prototype puts iPhone first (the text renders as the real iOS font, and Live Activities and the Dynamic Island are the best version of the widget idea) while keeping Android in mind: the right font, an always-there notification with buttons, and Android-style navigation. People doing IVF in the US skew toward higher-income iPhone users, which points the same way. But Android is a quick follow, not a someday.


02 Distribution

Three steps to get in front of the right people

"Put it in the App Store" is a footnote. People doing IVF are reached through channels that run on trust and gatekeepers. The plan is three steps, where each one earns the credibility you need for the next.

Step 1 · now

People who've been through it

Where the most desperate users already are, and it costs almost nothing.

Step 2 · months

The nurses

Fertility nurses handle the medication chaos. Win a few and they'll recommend you.

Step 3 · the business

Pharmacies and benefits companies

Where the money and the scale are. They already have the patient.

Step 1: Go where people are already stuck

People doing IVF form unusually active, tight-knit online groups, mostly because the medical system leaves them on their own for exactly the logistics this app handles.

✓ Your real edge

You lived this. In these communities, "I built the thing I wish I'd had during my own cycle" isn't a marketing line. It's the most believable thing you can say, and no funded competitor can fake it.

Step 2: Win the nurses, then the clinics

Fertility nurses field a huge number of medication and reorder questions; it's one of the most time-consuming parts of their day. An app that cuts down "where's my med / I ran out" calls is a gift to them. Get a few nurses on your side, let them recommend it to patients, then go to the clinic with real usage numbers and an option to co-brand it. Clinics move slowly and worry about compliance, so lead with "this saves your nurses time and prevents cancelled cycles," not with the tech.

Step 3: The actual business: pharmacies, benefits, employers

One correction from checking what the named buyers already do: Progyny is closer to a competitor than a customer. Progyny Rx is an integrated pharmacy benefit with partner pharmacies, delivery tracking in their member app, and a clinician call with every delivery. The pitch "sponsor our app, it's cheap insurance" asks them to pay for something they already built. The real openings are the benefits companies without integrated pharmacy programs, and the much larger group Progyny never touches: people paying cash or on ordinary insurance, whose logistics nobody coordinates at all.

The market is also small enough that this matters. The CDC counts roughly 435,000 fertility treatment cycles a year in the US, across about 252,000 patients. Narrow that to people on specialty pharmacies with delivery constraints and an iPhone, for a few intense weeks each, and the consumer numbers alone can't carry a company. That's not a reason to quit; it's the reason the money has to come from businesses that lose thousands per cancelled cycle.

PartnerWhat they getWhat you tell them
Benefits companies without an integrated pharmacy
Carrot, Maven, Stork Club, and employer plans
Fewer cancelled cycles, people sticking to the plan, happier members.A missed trigger or a run-out can waste a $20k+ cycle you're paying for. Sponsor the app for your members; it's cheap insurance.
Independent fertility pharmacies first
SMP, MDR, VFP, Schraft's; CVS Specialty stays the user-side default but has its own app and won't meet a solo startup
Fewer panicked phone calls, fewer emergency rush shipments, less expensive medication thrown away.We turn "I'm out!" calls into planned reorders that fit your delivery schedule.
Employers (directly)A visible, humane fertility perk.Add the logistics piece to the fertility benefit you already offer.
Clinic software / portals
eIVF, IDEAS, Artisan, BabySentry
Something useful for patients they didn't have to build.We turn the protocol into a live schedule: the auto-sync you want, as a partnership.

Order matters: the community proves people want it and gives you people willing to say so. But raw downloads won't impress a benefits company; they buy outcomes. So the app should count the moments that matter from day one: every time someone reorders days before they would have run out, that is a prevented emergency, and the tally of those is the sales deck for step 3. Build that counting in now; it can't be reconstructed later.


03 The hard parts

Where this gets hard, and what to do about it

People clearly want this, and the pain is real. The risks are almost all about the business model and getting the data, not about whether anyone will use it. Here's the straight version.

The risks, worst first

● Risk 1: People leave, and that's the design

A cycle is a few intense weeks, and the best outcome, a pregnancy, means the person stops using the app. You won't make much per user, and the people you help most disappear the fastest. What to do: don't build a $9-a-month consumer app. Make your money during the weeks people need you most, through sponsorship (pharmacies, benefits companies), and cover more of the process: egg-freezing, frozen-embryo transfers, the shot-heavy early-pregnancy weeks, repeat cycles. Then someone has more than one reason to stay.

● Risk 2: "It syncs from the clinic automatically" is the hardest promise

eIVF and similar clinic software usually don't offer a way for outside apps to pull your data, and clinics won't hook up an unproven startup quickly. What to do: treat automatic sync as a goal and a Step-3 partnership. Make photo, email, and typing-it-in genuinely good, with a person always confirming, so the app is fully useful even if no clinic lifts a finger. The prototype is built that way on purpose.

● Risk 3: Liability and privacy

Telling someone when to inject or reorder means a wrong answer can hurt them, and holding fertility data is sensitive, especially after Dobbs. What to do: clear lines (the clinic is always right, you confirm everything, no dosing advice), collect as little data as possible, encrypt it, promise never to sell it, and make deleting it easy. Make privacy something you advertise, not fine print. Stay clearly on the "tracker, not medical device" side, and get a lawyer before that line gets fuzzy. The app stores have their own rules here too: Apple bars health data from ads and analytics, and Google treats reproductive data as high-sensitivity, so compliance with both is a launch requirement, not a nice-to-have.

▲ Risk 4: You're not the only one doing reminders

IVF apps with medication reminders exist, but the consumer-direct field is thinner than it looks. Embie now goes through clinics: if yours doesn't offer it, you can't use it. The apps a patient actually already has are the incumbents to watch: Progyny's member app and CVS Specialty's app both track deliveries. What none of them do, as far as checking could find, is compute the reorder deadline. What to do: don't compete on reminders; nearly everyone has those. Compete on the reorder math and on knowing the details: each pharmacy's delivery days and cutoffs, and each insurer's fill limits and quirks. Two honest caveats. That knowledge decays: pharmacy schedules and owners change (Alto changed hands twice in 2025), so the knowledge base needs a named way to stay true, with verification dates the user can see. And keeping it true is ongoing work that should be budgeted like any other cost.

● Risk 5: The deadline we compute is wrong

The product asks people to trust one number. If the pharmacy calendar is stale, a holiday intervenes, or a dose change never got entered, that number is wrong, and someone who trusted it runs out. A wrong deadline is worse than no deadline. What to do: this is why the design already leans on showing its work: deadlines display when their inputs were last verified, counts get audited when they go stale, and the connection banner freezes trust to a timestamp when sync breaks. Default buffers stay conservative, and when confidence is low the app says so and suggests calling the pharmacy.

▲ Risk 6: The "a person checks everything" promise is labor

Version one leans on human confirmation: scanned protocols, packing lists, and audit prompts all end with a person approving. For the user that's the right call. For the company it's work that grows with every signup, and some of it looks a lot like clinical review. What to do: name who does this checking and at what volume it breaks, and bring on two advisors before anyone outside the household uses it: an REI nurse and a fertility pharmacist.

Ideas worth trying next


04 What to build first

What to build first, and what I'd ask you

A suggested line for the first version, and the calls I couldn't make for you.

A suggested first version

Since this was written, the product grew a five-level map (see the Level explorations page): L1 medication execution, L2 inventory and reorders, L3 protocol and results, L4 calendar and to-dos, L5 the whole path from first evaluation. In those terms, version one is Levels 1 and 2, built well. Everything below still holds; it describes the inside of those two levels.

Build now

The core

  • Photo, email, and manual entry, with a person confirming
  • Schedule and dose reminders
  • Inventory and the reorder-deadline math
  • The trigger alarm
  • The iPhone lock-screen widget
Fake it for now

Keep the rules narrow

  • Hand-pick 2–3 pharmacies (CVS Specialty first)
  • 3 payment paths: Progyny, Aetna, out of pocket
  • Reorder = a prep sheet plus a call or portal handoff; the user places it
Skip for now

Not yet

  • Automatic clinic sync
  • Ordering straight from a pharmacy
  • Android (quick follow)
  • Benefits-company integrations
◆ If you only build one thing

Build the reorder-deadline calculator for someone on CVS Specialty with a Progyny benefit, and put its answer on the lock-screen widget. If that one sentence, "order by Thursday 2 PM or you run out Tuesday", makes people on r/IVF say "I needed this," the rest of the plan is worth it.

Questions I'd want you to answer

  1. Whose product is this, really? Mostly answered now: consumer-first, but counting prevented emergencies from day one so there's evidence to sell to benefits companies later. The unanswered part: who plausibly writes the first business check, and for what?
  2. Is this a company or a feature? If the concept works, Progyny or CVS could add a reorder deadline to their apps in a quarter. The defense is the parts they won't do: the cross-pharmacy, cross-insurer knowledge base and the privacy-first, patient-side stance. Whether that's enough is a real question to sit with.
  3. How much beyond the injection weeks do you want to cover? Egg-freezing and frozen-embryo transfers work almost the same way and would fix the "people leave" problem, but they're more to build. In or out for version one?
  4. How much of the legal and privacy work do you want to take on early? Handling health data, agreements with any clinic or pharmacy partner, and the politics around fertility data are real work. Take it on now, or stay deliberately light at first (a personal tracker, no sharing of partner data)?
  5. Settled: Plenty never places the order. You decided this: the app reminds and preps, the user transacts with the pharmacy. The remaining question is how far assistance can go without crossing that line. Tracking numbers the user pastes in? Reading the pharmacy's confirmation email? Checking benefit balances? Each is useful and each inches closer to being a party to the transaction.

This goes with the clickable Plenty prototype, the Level explorations, and the Feature concepts pages. All of them are early concept pieces meant for figuring things out: not medical advice, not a finished product, and not connected to any clinic, pharmacy, insurer, or the eIVF portal. The medication names, pharmacy rules, insurance details, and dates are made up as examples, and would need to be checked against real clinical and insurance sources before anything ships.