1000x an idea

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.

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?