1000x an idea

To: Lena Brandt, Aisha From: Product Re: Shared lists, from one partner to the whole household

The bet

Pantry becomes the place a household runs its groceries, not a list one person keeps.

The 1000x version

People already share logins to get this today. The need is real, and the login is a workaround. At full ambition, the household is the unit. Any number of members share lists, a pantry view, and a live "what's running low" view. Members claim items ("I'm getting the milk") so nobody buys it twice. The app learns the household's routines, drafts the next list, and tracks what's in the house from what members tick off. Once Pantry holds a household's shopping state, it becomes the natural front end for delivery and reordering, and the household becomes the Plus tier.

Location is where this gets tempting: "your partner is two aisles away," or "you're near the store and the list just changed." Legal allows this only with opt-in from the person being located and from the person viewing. If we ever go there, we design that consent in from the start. It is not part of this quarter.

What the data says

• The behavior already exists without us. 11% of lists are edited from two or more devices.
• Those users are still active at month 3: 71%, against 22% for everyone else. This is correlation. Heavy households may both use the app more and share more. We need an experiment before we claim the feature drives retention.
• On those lists, 38% of items are added from the second device. Sharing is doing real work.
• Last quarter, 1,900 support tickets were about duplicate purchases. That pain is specific and measurable.
• Recipes and meal plans get 4% monthly opens. Our record on features people don't reach for is weak, so I'd treat "it needs AI" with caution.

On AI: the shared-list problem is mostly coordination. Who has claimed what, and whether "milk" and "whole milk 2L" are the same item. Rules and simple matching can handle much of that. We add a model where matching visibly fails, and only after we've seen where.

What we build this quarter

Two-person shared lists, aimed at duplicate purchases:

1. Invite one partner by link. Both accounts edit in real time.
2. Claim an item. Claimed items show who has them.
3. Duplicate warning when an item is already on the list or was ticked off in the last few days.
4. Activity feed so each person sees what changed.

Both members use it free. Putting the core behind Plus would cut off the free users who look most like our retained group, and it would test pricing rather than the product. We can test Plus separately later.

Not this quarter: location, groups larger than two, AI, delivery integration.

Team: two engineers on sync and invites, one on matching and duplicate detection, one on claims and activity, and the designer on the flow across both accounts.

How we'll know it's working

Randomize. Among eligible users on multi-device lists, half see the invite prompt and half don't. Without a holdout, we can't separate the feature's effect from the users who would have stayed anyway.

Leading indicators (weeks 2 to 6): - Both-active rate: share of invited lists where both members add or tick items within 14 days. Proposed target: 30%. - Share of items added by the second member on invited lists, compared with the 38% baseline.

Outcomes (month 3 of the cohort): - Retention lift for invited lists over the holdout. Proposed target: at least 5 points. This number is a guess until we have a holdout baseline, so we'll set it properly in week 1. - Duplicate-purchase tickets down 30% from the 1,900-per-quarter run rate.

Guardrails: - No drop in list completion or ticking for solo users. - No rise in unsubscribes or privacy complaints. - Invitee Plus conversion tracked, not targeted.

Decision rules: - If the both-active rate is under 15% after six weeks, the invite is the wrong shape. We revisit before building more. - If retention lifts but tickets don't fall, the next investment goes to matching and claims, not to new sharing features.

Recommendation

Approve the two-person build with the holdout. Keep the household vision as the direction we're testing toward, and let the week-6 numbers decide whether we earn the next step.

MEMO

TO: Lena Brandt (CEO), Aisha (PM) FROM: Product Team DATE: October 24, 2023 SUBJECT: The 1000x Vision for Shared Lists (and What We Build in Q1)

---

The Insight: Shared Lists Are Our Growth Engine

We thought Pantry was a personal productivity tool. Our data tells a different story: Pantry is a household coordination network.

Today, 11% of lists hack multi-device access using shared logins. When they do, Month 3 retention leaps from 22% to 71%, and partners contribute 38% of additions. But the experience is broken: 1,900 users wrote in last quarter because "we both bought the milk."

Solving this is not just a defensive UX fix—it is our path to category dominance.

---

The 1000x Vision: The Autonomous Household Operating System

Today, Pantry is a static scratchpad. At 1000x, Pantry is the ambient operating system for household commerce.

A household of two (and later, families or roommates) spends zero cognitive effort managing supplies: 1. Zero-Friction Ingestion: AI parses receipts, listens to ambient kitchen prompts, and tracks shared purchase cadences to predict depletion without manual entry. 2. Invisible Coordination: The app dynamically routes runs: "Alex is walking by Trader Joe's; Chris needs oat milk." Zero double-purchases, zero forgotten items. 3. From List to Fulfillment: When lists hit a threshold, Pantry either routes the physical trip via synchronized in-store navigation or dispatches the order through 1-click merchant APIs.

Instead of fighting for 4% engagement on recipes, we own the point of intent for household spending. That transforms Pantry from a $4.99/mo utility into the primary interface for a $1.5T grocery market.

---

Lena’s AI Mandate: Intelligence, Not Gimmicks

Recipes failed because users don’t want Pantry to tell them how to cook. They want Pantry to tell them what they forgot.

We will apply AI directly to the shared workflow: * The "Shared Brain" Depletion Model: An on-device ML model that maps co-purchasing cycles across the pair. When Partner A adds coffee, AI prompts Partner B: "You usually run out of oat milk two days after coffee. Add it?" * Smart De-duplication & Categorization: Auto-clustering shared chaotic inputs into store-aisle taxonomies in real time.

---

What We Build in Q1 (4 Engineers, 1 Designer)

We must earn the right to the 1000x vision by nailing real-time two-player shopping and eliminating the "both bought the milk" problem.

Scope: 1. Native Partner Pairing: Clean invite flow via magic link. Each partner gets an independent profile tied to one shared list. 2. Live Store Mode & Collision Avoidance: * When Partner A starts checking items off, Partner B gets a push notification: "Alex is shopping right now." * When an item is claimed or checked off, it updates via WebSockets in sub-second real time with an avatar badge ("Alex just grabbed the milk"), killing duplicate purchases. * Compliance note: Zero background GPS tracking required. State is triggered purely by app activity (tapping "Start Shopping" or checking off the first item). 3. Pantry AI Assistant (v1): Predictive prompt when opening the app: "Partner added 4 items. Based on your household history, did you also need eggs?" 4. Monetization Wedge: 1 shared list is free. Unlimited lists and AI Household Predictions roll into Pantry Duo ($7.99/mo) or the existing Plus plan.

---

How We’ll Know It’s Working

We will measure success over the first 60 days across three key metrics:

Shared shopping turns single-player churn into multi-player network effects. Let’s build it.