1000x an idea

To: Lena Brandt, Aisha From: PM, Pantry Re: Shared lists: the 1000x version, and what we build first

Recommendation Build Aisha's proposal, scoped to fix duplicate purchases. The evidence already supports it, and it is the first step toward something much larger.

The 1000x version: Pantry is where a household runs its food Sharing with one partner is the smallest unit of a bigger idea: the household is the customer, not the individual.

• Households of any shape: partners, families, roommates, with roles and attribution ("Sam added oat milk").
• Live coordination: claim items ("I've got this"), see ticks in real time, and use an "I'm at the store, need anything?" ping.
• Shared memory: one household's staples, habits, and pantry stock, which no single-user list can build.
• Household intelligence: this is where AI belongs. Once two people's behavior feeds one list, we can predict restocks, merge "milk" and "whole milk," and suggest the weekly shop.
• Household plan and commerce: Plus priced per household, with one-tap handoff to delivery or pickup.
• Growth loop: every invite brings a new user, so acquisition becomes a product feature.

What's real today - 11% of lists are already edited from two or more devices, and people share logins to do it. They are working around us. - On those lists, 38% of items come from the second device, so the second person is a real contributor. - "We both bought the milk" produced 1,900 tickets last quarter, our top support request. - Retention is 71% at month 3 for multi-device lists versus 22% for everyone else. I would not quote this as the effect of sharing. Households that already depend on Pantry are more likely to share, so it may be selection. We should test it (see below).

On AI I wouldn't put AI in the first release. Recipes and meal plans, a feature set that stacked on top of the list, are opened by only 4% of users a month. The lesson is to build where behavior already exists. Sharing has that behavior. AI becomes useful in a second phase, once shared data exists to learn from, and I'd earn it there rather than lead with it.

What we build first (one quarter, four engineers and a designer) 1. Invite one partner by link. The partner gets their own account, not a shared login. We need separate identities for anything later, including location consent. 2. Real-time sync with both people adding and ticking items, plus attribution of who added what. 3. Duplicate-purchase protection: a push notification when the other person ticks something off ("Sam got milk"), and a clear in-store "already bought" state. 4. Login-sharer migration: detect lists used from multiple devices and prompt an invite.

Deliberately out of scope - Multi-person households, claiming, roles, AI, and the paywall. Keep sharing free in v1 so the invite loop isn't throttled. - Location. Legal requires opt-in from each person, and the other person's opt-in before we show a location. If we pursue "I'm at the store" later, a manual "I'm shopping now" toggle gives most of the value with no location tracking.

How we'll know it's working Ship the invite prompt to a randomized subset of eligible users and hold out the rest. This tests the retention claim directly.

Watch Plus conversion as a secondary signal, not a target. A guardrail is list-sync errors and conflicting edits, since a shared list that loses items would hurt trust.

Decision points - End of quarter: if the holdout shows no retention lift but tickets fall, we have a support win and a weaker growth story. We would reconsider the household vision before investing further. - If retention lifts: next quarter, extend to multi-person households and test a household Plus tier. AI-based staples prediction comes after that.

Open questions for you both - Do we have the data to separate new-to-Pantry invitees from existing users? - Are we comfortable launching the free tier with no paywall for a quarter?

To: Lena Brandt and Aisha Subject: From shared lists to the coordination layer for household shopping

The 1000× version

Aisha’s proposal is not just multiplayer checkboxes. It could be the first step toward Pantry becoming the place a household coordinates everything it needs to buy.

Today, each person remembers needs, sends messages, shops, and discovers what someone else already bought. At full ambition, Pantry turns that fragmented process into one shared system: what we need, what we already have, who is handling it, and what remains undone.

An item might begin as a voice note, a pasted message, or a recurring household need. Pantry organizes it, flags likely duplicates, and—with permission—learns when to suggest replenishment. Households could eventually include roommates, caregivers, and extended family. Later, Pantry could connect that shared intent to retailer carts, substitutions, and delivery, while leaving purchasing decisions with users.

The business could expand from a personal utility into household subscriptions and, eventually, commerce revenue. But those opportunities depend on earning trust in coordination first. This is a direction, not a forecast of 1,000× revenue.

Why this wedge—not another content feature

We already see people working around the product by sharing credentials. Eleven percent of lists are edited across devices with different phone numbers; second devices contribute 38% of items on those lists. This looks like substantive participation, not occasional viewing.

Multi-device users’ month-three retention is 71%, versus 22% for others. That is evidence of opportunity, not proof that sharing causes retention: more committed households may already be selecting into this behavior. Likewise, 11% of lists does not mean 11% of users.

The clearest unmet need is concrete: 1,900 duplicate-purchase tickets last quarter. Meanwhile, recipes and meal plans reach only 4% of users monthly. We should deepen Pantry’s existing shopping workflow rather than build another destination users must remember to visit.

What we should build next quarter

With four engineers and one designer, ship one list, two separate accounts, reliable coordination:

• Invite one partner through a secure link; accept, leave, and revoke access.
• Both people can add and check off items, with clear attribution.
• Fast synchronization, offline recovery, and predictable handling of simultaneous edits.
• A lightweight “I’m buying this” claim, visible to both people, with easy release. Checking an item off means purchased; claiming it means someone is handling it.
• Help existing credential-sharing households move to separate accounts.

Make basic sharing free: charging before establishing the collaboration habit would constrain adoption. Defer larger groups, inventory, retailer integrations, and monetization experiments.

AI belongs in service of the job, not in the launch headline. Test a small, optional assistant that converts pasted household messages into proposed list items and flags likely duplicates. Users confirm every change. Ship it only if it saves effort without introducing meaningful mistakes; it must not delay the coordination core.

No location tracking is needed. “I’m buying this” is an explicit action, not an inferred whereabouts signal. Any future location feature must require the explicit opt-ins Legal specifies, including both people’s consent before sharing location.

How we’ll know it works

Instrument household participation, claims, purchases, synchronization failures, and reported duplicates. Do not treat invitation volume as success.

Run a randomized rollout, keeping collaborating accounts in the same experiment group. Analyze by assignment, not only among people who accept invitations.

Proposed decision gates, to validate against baseline and statistical power:

• At least a 10% relative improvement in day-30 retention versus control.
• At least half of activated pairs still have both people contributing in week four.
• At least a 25% reduction in self-reported duplicate purchases among activated pairs.
• No material deterioration in list reliability, privacy incidents, or support burden.

Report month-three retention when cohorts mature; a quarter-end readout cannot establish it for late adopters. Scale only if Pantry makes two people’s shopping measurably easier—not merely more shareable.