02 — The Portfolio Architecture
Four brands, two user types, one intended flow.
In Tandem's four brands serve overlapping use cases but different user motivations. Understanding the intended flow between them — who enters where, and where they're meant to go next — is the foundation of any portfolio lifecycle strategy.
Cozi
Free + Premium
Family calendar and planning for intact families. Scheduling-first, deliberately simple.
OFW
Paid primary
Court-ordered co-parenting compliance: messaging, expense tracking, legal documentation.
FamilyWall
Free + Premium
Fuller family hub — overlaps Cozi, adds location tracking, messenger, and budgets.
Custody Nav
Specialized
Custody-schedule planning for separated families — and a legal-guidance funnel into OFW.
Differentiated
Cozi vs. FamilyWall: overlap at acquisition, divergence in depth
Both have shared calendars, shopping lists, to-do lists, and meal planning. The meaningful difference: FamilyWall adds real-time location tracking with safe-zone alerts, a family messenger (text, voice, photo, video), photo sharing, and budget tracking. Cozi is scheduling-first and simpler. FamilyWall is a fuller family hub — likely skewing toward households that need location visibility or multi-generational coordination. Cannibalization risk is real at acquisition; once in, the feature sets diverge enough to serve different power users.
Confirmed funnel
Custody Navigator → OFW: not a competitor, a top-of-funnel feeder
Custody Navigator's footer reads "Made with OurFamilyWizard" — a small forensic detail that confirms the portfolio design. CN captures parents at the moment of separation: pick a custody schedule template (2-2-5-5, 2-2-3), customize for holidays, calculate overnight percentages, export a calendar. That's the planning phase. OFW is where they live that schedule — messaging, expense tracking, legal documentation.
The funnel is: separation → Custody Navigator (plan it) → OFW (execute it). The lifecycle question is how well In Tandem is converting CN users into OFW subscribers — by design, or by accident.
Data needed
Cross-brand migration: the portfolio's core unmeasured metric
What percentage of CN users convert to OFW — and how quickly? Is there an in-product CTA from CN to OFW, or does conversion rely on organic discovery? Do Cozi users cross to OFW or FamilyWall during a separation? These migration rates are the core metric for whether the portfolio is working as designed.
Portfolio logic
The architecture is sound — the lifecycle question is conversion rate
Cozi and FamilyWall serve married or partnered households at different feature depths. OFW and Custody Navigator form a confirmed acquisition funnel for co-parenting families — CN captures the planning moment, OFW owns the ongoing execution. The portfolio design is coherent. The open question isn't whether it makes sense — it's whether lifecycle programs are actively driving users through the intended paths, or whether those transitions are happening by accident.
03 — The Cohort Divide
Court-ordered vs. voluntary: two users, opposite motivations.
OFW serves two radically different user types — one compelled by a judge, one persuaded by convenience — yet both likely receive identical lifecycle treatment. This is where the biggest ARPU and retention opportunity in the portfolio lives.
| Dimension |
Court-Ordered User |
Voluntary User |
| Motivation |
Compliance — legally required |
Convenience — chose to use |
| Churn Risk |
Near-zero |
High |
| Feature Priority |
Legal compliance: visit tracking, recording, court-ready exports |
Ease of use: integrations, automation, convenience features |
| Onboarding Urgency |
Urgent — court mandates ASAP |
Gradual — explores at own pace |
| Upgrade Motivation |
Legal features: evidence, court-ready documents, professional access |
Convenience: integrations, smart alerts, cross-product access |
| Engagement Trigger |
Legal necessity — external mandate |
Daily utility — internal motivation required |
Critical gap
The tagging problem: invisible cohorts
Running segment-specific lifecycle programs requires knowing which users are court-ordered and which are voluntary at signup. There's no evidence this tagging happens. Both cohorts likely receive the same email sequences, notifications, and upsell messaging — even though their needs, price sensitivity, feature priorities, and churn dynamics are fundamentally different.
A standard "How did you hear about us?" question at onboarding — with "court order or legal requirement" as one option alongside attorney recommendation, online search, and friend or family — would capture the segmentation signal without feeling interrogative. One low-friction question, two entirely different lifecycle programs downstream.
Biggest Opportunity
One signup question unlocks two separate lifecycle programs — and a material ARPU lift.
Court-ordered users are near-zero churn and largely price-insensitive — the ideal premium upsell target for evidence and legal-compliance features. Voluntary users are high-churn and convenience-driven — they need a freemium model, better onboarding, and features that prove daily utility fast. Treating them as one segment means neither gets a lifecycle program that actually fits.
04 — Where the Experience Breaks
Four lifecycle gaps, one journey audit, and the data foundation to fix them.
User reviews and forum discussions surface friction points across OFW's lifecycle — most visible in voluntary users, where there's no legal mandate absorbing the frustration.
High · Conversion blocker
No free trial for voluntary users
Court-ordered users don't need a trial — they're required to pay. But voluntary users, price-sensitive and shopping alternatives, hit a hard paywall before experiencing core value. Without a free tier or trial, the freemium conversion funnel doesn't exist for the cohort that needs it most. Competitors with free tiers capture these users first.
High · Activation failure
Setup complexity at activation
Users consistently report OFW as "confusing to set up." Creating accounts for both parents, syncing family structure, and configuring access permissions requires coordination that many users haven't completed. For court-ordered users, urgency pushes through the friction. For voluntary users, there's no external pressure — and they drop.
- Two-parent account creation requires coordination before the product provides value
- Family-structure complexity (custody schedules, children, professional access) hits new users all at once
- Unknown: is there in-app guidance? Progressive disclosure? Or full setup at first login?
High · Retention risk
Unsegmented notifications
Notifications are reported as "annoying" — suggesting a one-size-fits-all cadence applied to two very different user types. Court-ordered users may be getting notifications that feel unnecessary (their motivation is external). Voluntary users may not be getting the engagement nudges they need to build the habit that keeps them subscribed.
Medium · Ceiling effect
No integration layer for power users
Voluntary users cite lack of integrations as a churn driver. Power users who want to connect OFW to their calendars, email, or other tools hit a ceiling and leave for alternatives. Court-ordered users tolerate this — they can't leave. Voluntary users don't have to.
The journey audit: a voluntary user's inferred lifecycle
Stage by stage, here's where the voluntary cohort meets friction the court-ordered cohort never feels.
Acquisition
App-store search, lawyer referral, or family-law Google
Likely minimal paid-marketing visibility. The question: what share of users arrive voluntarily vs. court-ordered — and do both land on the same onboarding?
Unknown split
Activation
Confusing setup, two-parent coordination required
No value delivered until both parents create accounts. No evidence of progressive disclosure or a guided setup flow. Voluntary users stall here; court-ordered users push through out of necessity.
High friction
Engagement
One notification cadence for everyone
No evidence of activity-based triggers or cohort-specific nudges. Court-ordered users engage by necessity; voluntary users need habit-building support the current system doesn't provide.
Unsegmented
Conversion
Hard paywall before value
No free trial. Voluntary users make a blind purchase decision without experiencing the product's core differentiators. What does the free tier show — enough value to justify premium, or a crippled experience that frustrates?
Paywall too early
Retention
Structural for one cohort, earned for the other
Unknown: voluntary six-month retention, top churn reason per cohort, and whether any win-back or pause programs exist. Court-ordered retention is structural; voluntary retention requires product-led engagement.
Data needed
Upgrade
One upsell message serving two motivations
Premium upsell triggers and messaging are unknown. Legal features upsell to court-ordered; convenience features upsell to voluntary. If both cohorts see the same prompt, it serves neither well.
Untailored
The data foundation: five layers to segment-specific programs
Building segment-specific programs across four brands requires a unified customer view — and the data infrastructure to act on it. Here's the architecture, bottom layer first.
1
Event capture layer
Capture signup source, court-ordered tag at signup, first feature used, email opens, push clicks, and feature-adoption frequency. The court-ordered tag is the most critical — everything downstream segments on it.
Must buildFoundation
2
CDP unification (Segment)
Unify the user profile across OFW, Cozi, FamilyWall, and Custody Navigator. Attributes: cohort (court-ordered/voluntary), acquisition source, feature adoption, LTV. Without this, cross-brand lifecycle is impossible — you're flying blind on portfolio migration behavior.
SegmentCross-brand view
3
Segmentation engine (Databricks)
Define frequency tiers per cohort: casual (1–2×/month) → core (weekly) → power (3+×/week). Define a north-star event per cohort — for court-ordered users it's "visit logged" or "court date tracked"; for voluntary, "message sent" or "shared calendar used."
DatabricksTier definition
4
Lifecycle programs (Iterable)
Segment-specific email, push, and in-app sequences. Goal: move users casual → core → power, then upsell at the right moment with the right message. Court-ordered: premium evidence features. Voluntary: convenience integrations and habit-building nudges.
IterableProgram execution
5
Feedback loop & experimentation
A/B test messaging per segment. Measure activation rate by cohort, upgrade rate, six-month retention, and ARPU uplift. Structured experimentation frameworks — not one-off tests — that prove lifecycle impact on growth and inform the product roadmap.
OngoingCompound ROI
| Dimension |
Court-Ordered |
Voluntary |
| North Star Event |
Visit logged / court date tracked |
Message sent / shared calendar used |
| Frequency Tiers |
Casual (1–2×/wk) · Core (3–4×/wk) · Power (daily) |
Casual (1–2×/mo) · Core (1–2×/wk) · Power (3–4×/wk) |
| Premium Lever |
Evidence features: recording, court-ready exports, professional access |
Convenience features: integrations, automation, cross-product access |
| Retention Strategy |
Retention is given — upsell and ARPU are the lever |
Retention must be earned — engagement programs, save flows, product habit |
05 — How I'd Start
The first four weeks of investigation.
If I were running lifecycle across this portfolio, I wouldn't launch a single program in month one. Foundational questions about data, product, and segmentation need answers first — these are the eight investigations that unlock everything else.
| Investigation |
What it answers |
When |
| Product tagging at signup |
Does OFW ask "How did you hear about us?" with "court order or legal requirement" as an option? If not, can Product add it — and how do we backfill existing users: survey, behavioral signal, or NPS prompt? |
First |
| Portfolio migration flow |
What share of Cozi users upgrade to OFW or FamilyWall? Do FamilyWall users cross to OFW during a separation? Can we measure this today in Segment or Iterable? |
First |
| Freemium model definition |
What's free vs. paid across each product? Is there a trial? Is the paywall around compliance features or convenience features — and does it differ by cohort? |
Week 1 |
| Activation barrier diagnosis |
Why do users say "confusing to set up"? Two-parent account creation? Family-structure complexity? Lack of in-app guidance? Session recordings or support-ticket analysis will answer this quickly. |
Week 1 |
| Notification strategy audit |
What's the current cadence? Do court-ordered users receive different sequences from voluntary? Is there segmentation by activity level or feature adoption — or one sequence for all? |
Week 2 |
| Data maturity assessment |
What's available in Segment and Iterable today? Can we segment by signup source, feature adoption, or frequency — or are we starting from scratch with basic email sequences? |
Week 2 |
| ARPU by cohort |
What's the LTV difference between court-ordered and voluntary users today? Where is premium conversion happening — and is it from the right cohort with the right message? |
Week 2 |
| Competitive positioning |
Are other court-ordered co-parenting tools gaining ground? What do family lawyers recommend today? Is OFW's moat as structural as it appears — or eroding at the voluntary layer? |
Weeks 3–4 |
From investigation to first pilot
Three phases, four weeks, ending with the first proof point: a split welcome sequence.
1
Weeks 1–2: Stakeholder interviews
Product (what data exists?), Data (Segment maturity?), Legal (what do courts require, and how does that shape the product contract?), Finance (current ARPU by cohort — does the data even exist today?).
Low effortContext-building
2
Weeks 2–3: Data audit & baseline
Map the current funnel per cohort. Identify data gaps — missing tags, untracked events, unsegmented sequences. Establish baselines for activation, conversion, and retention across court-ordered vs. voluntary users, even if the split has to be inferred at first.
Med effortMeasurement foundation
3
Weeks 3–4: First pilot — the split welcome sequence
One version for court-ordered users (urgency, compliance features, legal admissibility), one for voluntary users (setup simplicity, daily utility, habit formation). Measure open rate, activation, and first feature adoption by cohort. Use the results to validate the segmentation logic and shape the six-month roadmap.
Low effortFirst proof points
Strategic Framing
The company that segments court-ordered from voluntary will have a moat competitors can't replicate.
In Tandem's portfolio is uniquely positioned — a mix of mandatory and voluntary users, free and premium products, overlapping use cases across four brands. Most operators would treat lifecycle here as "same messaging, more channels." The real opportunity is data infrastructure that distinguishes the two cohorts from day one, then optimizes each independently. Court-ordered users stay longer when compliance features are best-in-class. Voluntary users stay longer when convenience features prove daily utility fast enough to build the habit before churn. That's the difference between lifecycle as an email channel and lifecycle as a growth system.