My PM Interview® - Preparation for Success

My PM Interview® - Preparation for Success

Design a wedding registry.

How to unify physical wishlists and cash funds into one registry couples and guests actually want to use.

My PM Interview's avatar
My PM Interview
Sep 09, 2026
∙ Paid

This post is for our Paid Subscribers. If you haven’t subscribed yet,

Claim Exclusive Discount & Unlock Access

Design a wedding registry.

Check more Answers on Prepterview.in

Clarifying Questions

Before diving in, I would want to align on scope, because “design a wedding registry” could mean anything from a standalone consumer product to a feature bolt-on inside an existing wedding planning platform like The Knot or Zola.

  • Are we building a standalone registry product or a feature within an existing wedding platform? This determines how much we rely on organic couple discovery versus cross-sell from a planning tool that already has the couple’s trust and wedding date.

  • What specific frustration are we prioritising? Existing item-only registries (Crate and Barrel, Williams Sonoma) work reasonably well for physical gifts, while cash-fund platforms (Honeyfund, founded 2006) handle digital contributions but not physical items. The documented gap is fragmentation across both, not any single registry type in isolation.

  • What is the intended monetisation model? A 2.5 to 3 percent cash-processing fee on contributions is the dominant model today. Knowing whether we are fee-based, subscription, or retailer-commission-based shapes every prioritisation decision downstream.

  • What is the geographic scope? The U.S. wedding industry generates roughly $70 billion in annual spend, and average wedding gift spend per guest sits around $160. International scope would add payment-rail complexity and currency handling on day one.

  • Are there regulatory or financial-services constraints we need to design around? Collecting and disbursing cash funds could trigger money-transmission licensing requirements in certain U.S. states, which would affect our engineering timeline and legal review process significantly.

For this answer I will assume we are building a new, standalone wedding registry product targeting U.S. couples, monetised through a 2.5 percent cash-contribution processing fee, and that the core design challenge is registry fragmentation. Specifically, the well-documented problem is that couples wanting physical gifts, a honeymoon cash fund, and a charitable donation option today must juggle three or four separate links across disconnected platforms, which creates genuine confusion for guests about where and how to give. The product I will design is a single unified registry that surfaces all three contribution types under one shareable link.

Product Description

The U.S. wedding registry market is part of the broader $70 billion wedding industry and directly influences roughly $19 billion in annual gift spend. Approximately 2.5 million weddings take place in the U.S. each year, and the average guest list runs between 100 and 150 people, each spending roughly $100 to $200 on a gift. The dominant legacy players (Bed Bath and Beyond before its 2023 closure, Williams Sonoma, Crate and Barrel) built item-only registries that work well for traditional household gifts but have no native cash-fund capability. Zola, founded in 2013, was the first platform to combine item listings and a cash fund in one place, and it now claims more than 700,000 couples per year. Honeyfund, founded in 2006, pioneered the dedicated honeymoon cash fund and has processed more than $600 million in contributions, but it handles only cash, not physical items. The result is a fragmented landscape where roughly 58 percent of couples today use more than one registry platform simultaneously, according to The Knot’s 2023 Real Weddings Study.

The business model for the product I am designing centres on a 2.5 percent cash-processing fee, slightly below PayPal’s Honeyfund fee of 2.8 percent and competitive with Zola’s 2.5 percent. At an average cash-fund contribution of $3,000 per couple and 500,000 couples on the platform within three years, that represents roughly $37.5 million in annual processing-fee revenue, before any retailer affiliate commission on physical items (typically 3 to 8 percent of item sale price). The key strategic differentiation is genuine unification: not a cash-fund platform with a token item list bolted on, and not an item registry with a tepid cash-fund add-on, but a product designed from the couple’s actual desired outcome, which is one link, one experience, and no guest confusion.

Define Goal

The core problem is that couples’ actual gift preferences have diversified far beyond what any single-purpose registry platform accommodates, and the fragmentation that results from using multiple platforms simultaneously creates real friction for both couples managing multiple links and guests uncertain how or where to contribute.

The goal I want to focus on is increasing the share of total wedding gift spend that flows through a single unified registry, by making it meaningfully easier for couples to express varied gift preferences and for guests to act on them in one place.

The north star metric I would use is total contribution value processed per couple registry within 30 days of the wedding date. I prefer this over simple registry setup rate because setup completion is a leading indicator of intent, not outcome. It is also more meaningful than guest visit count, because a guest who visits and leaves without contributing represents a failure of the core value proposition. Contribution value per registry captures both breadth (did enough guests find and use the registry) and depth (did guests feel confident contributing meaningful amounts), and it ties directly to our processing-fee revenue model.

Share

User Segmentation

Couples

  • Mixed-preference couples (ages 28 to 38, primary segment): They already own many household basics from cohabiting before the wedding, want a handful of physical upgrades (nice cookware, bedding), a honeymoon fund, and possibly a charitable option. They feel genuine frustration juggling Zola for items, Honeyfund for cash, and a separate charity link, and they worry guests are confused about which to use. This is the segment that most directly validates the product’s core hypothesis.

  • Cash-first couples (ages 30 to 42): They have lived together for several years, own nearly everything they need, and primarily want cash contributions toward a home down payment or travel. They are under-served by item-heavy registries and slightly over-served by cash-only platforms that still lack integration with any physical gift option. Their average honeymoon fund target is approximately $5,000 to $8,000, making them high-value from a processing-fee standpoint.

  • Traditional couples (ages 24 to 32): They are getting married earlier, may not have cohabited, and still want a substantial physical item list. Cash funds feel impersonal to them or to their older relatives. They are reasonably served by existing item registries but would benefit from a cleaner, more modern setup experience and better thank-you tracking.

Guests

  • Local guests (ages 30 to 65, primary gift-givers): Comfortable buying physical items or contributing cash online. Their main pain point is finding multiple registry links and not knowing which one the couple prefers or whether their chosen contribution type is even supported on the platform they land on.

  • Remote and international guests: Shipping a physical gift across the country or internationally is logistically difficult. Cash or digital contributions are strongly preferred, but they need payment methods that work across borders, including international card support and potentially local payment methods.

I will focus the rest of this answer on mixed-preference couples because they represent the largest underserved segment, their pain point maps most directly to the product’s core hypothesis, and capturing them validates the unified registry model in a way that either cash-first or traditional couples alone would not.

Pain Points

User's avatar

Continue reading this post for free, courtesy of My PM Interview.

Or purchase a paid subscription.
© 2026 PREPTERVIEW EDU SOLUTIONS PRIVATE LIMITED · Publisher Privacy ∙ Publisher Terms
Substack · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture