This is the response from Claude. This is a fun architecture problem because the "age" dimension has to drive three separate systems (email content, box contents, and eligibility), and they age at different rates. Here's how I'd build it. 1. Get the data model right first Everything downstream depends on a few clean profile properties: - baby_birthdate (date type — must be a true date property, not text) - due_date (date) for pre-birth profiles - parent_stage (string: expecting / parent) — your master routing switch - baby_age_months (number) — optional but very worth it, see below - birthdate_confidence (string: confirmed / estimated) — matters a lot for the expecting-parent handoff - baby_name, and a child_2_birthdate if you want to handle siblings Collect these at the earliest possible touchpoint: a two-question quiz on the popup ("Is baby here yet?" → date picker), a post-purchase survey, and an always-available "update baby's info" link in your email footer. Whatever percentage of profiles lack a birthdate is the percentage of your list that can't be personalized, so this capture rate is the real ceiling on the whole system. 2. The routing problem, and why a linear flow won't work A single flow with Delay 30 days → Email 1 → Delay 30 days → Email 2 fails exactly as you suspected: everyone starts at Email 1. Your 7-month customer would get newborn cord-care content for the next six months. There are two viable patterns. Pattern A — Segment-triggered milestone flows (recommended). Build one segment per age bucket, defined off the date property: baby_birthdate is at least 210 days ago AND baby_birthdate is less than 240 days ago → "Baby Age – 7 Months" Then each segment triggers its own small flow (1–3 emails) via the Added to Segment trigger. Your 1-month customer lands in "Baby Age – 1 Month," gets that content, and next month Klaviyo drops them from that segment and adds them to "2 Months," which triggers the next flow. Your 7-month customer enters at "7 Months" and continues from there. Nobody gets stale content, nobody gets a six-email catch-up dump, and the system self-corrects if someone updates their birthdate later.