1000x an idea

To: Lena Brandt, Aisha Subject: From a shared list to the system that runs household replenishment

Recommendation

Commit next quarter to testing household coordination, not merely adding a second editor. Aisha’s proposal is the smallest entry point into a much larger opportunity: Pantry becomes the trusted system that ensures a household has what it needs, without anyone having to manage every purchase.

The 1000x version

Today, Pantry remembers what someone typed. At its most ambitious, Pantry coordinates the entire replenishment cycle: noticing needs, resolving preferences, assigning responsibility, finding the right purchase, and confirming arrival.

Imagine: “Keep our household stocked within $150 a week.” Pantry learns recurring needs from explicitly connected purchase history and household corrections, drafts a replenishment plan, reconciles conflicting requests, and coordinates whoever—or whichever service—will fulfill it. Eventually, users could authorize bounded automatic purchases, with spending limits, explanations, and easy overrides.

The expansion is from one person’s checklist to a household’s purchasing agent, then a demand network connecting households to retailers and delivery providers. Core sharing could remain free; trusted automation could support Plus, with optional transaction revenue later. Recommendations must serve household preferences, not whichever retailer pays most.

AI belongs in interpreting messy requests, recognizing equivalent items, and proposing replenishment—not in deciding whether two phones agree. Synchronization must be reliable software. This is an ambition, not a forecast or next-quarter roadmap.

Why this is the right starting point

Users are already working around our product: 11% of lists are edited from multiple devices with different phone numbers. Second devices contribute 38% of items on those lists. This looks like genuine joint work, not occasional viewing.

Those users retain at month three at 71%, versus 22% for others. That is compelling but not causal: committed households may naturally retain better, and devices are not verified partners.

The clearest unmet need is operational: 1,900 duplicate-purchase tickets last quarter. Meanwhile, only 4% opened recipes or meal plans last month. We should earn the right to expand by preventing “we both bought the milk,” not by launching another planning destination.

What we build first

With four engineers and one designer, ship a narrow, free, two-person shared-list pilot:

• Separate accounts; a simple invitation, acceptance, and removal flow.
• Fast shared additions and check-offs, with clear sync status and safe recovery after disconnection.
• An explicit, visible “I’m buying this” claim, followed by “bought,” so coordination happens before checkout. Surface conflicting claims; never imply an offline claim is confirmed.
• Clear attribution and controls to leave sharing without exposing other private lists.

Test with existing login-sharing households first. Do not require location: voluntary item claims solve the immediate problem with less risk. Any future location feature requires explicit opt-in from both the person being tracked and the intended recipient, plus revocation controls.

For Lena’s AI question: time-box a prototype that flags likely duplicate entries such as “milk” and “whole milk.” Test precision with users; never silently merge. It ships only if useful and does not delay the coordination foundation. No ordering, retailer integrations, inventory prediction, or meal-planning expansion this quarter.

How we know it works

Instrument the funnel from invitation through acceptance to both people contributing and completing a shopping cycle. Weekly active collaborating households is our adoption metric—not invitations sent.

Randomize eligible initiating accounts to invitation access or control, keeping linked partners in the same experiment. Compare outcomes by assignment, not just among successful sharers.

Before launch, power the test around these proposed decision thresholds:

• At least a 20% relative reduction in self-reported duplicate purchases per shopping trip.
• A five-percentage-point improvement in day-28 retention, followed by month-three measurement.

Track sync failures, lost edits, accidental sharing, notification complaints, and Plus cancellations as guardrails. Support tickets are corroborating evidence, not the sole outcome.

Expand only if households repeatedly coordinate and randomized outcomes improve without material trust failures. If invitations succeed but duplicate buying persists, fix coordination before broadening the vision.

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?