Maryland reactivation needs savings discovery without language that suggests a personal food price.
The next send protects returning-household conversion, while the reviewed message pattern must protect against a pricing claim that cannot be substantiated.
Who you’d be doing this for
“It said this was my best price, so I thought the deal was based on me.”
Tereza Djordjevic · Household grocery shopper
She lives in Maryland and reopens the app when weekly grocery costs rise.
What is at stake
Seventeen conversation summaries contain personal-price language that cannot yet be verified against source interactions. You have to weigh reactivation continuity against a reviewed experience that makes savings claims defensible.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- reactivation continuity vs pricing-claim defensibility
- useful savings discovery vs strict review
- 72-hour send deadline vs verified evidence
- shared journey coherence vs surface-specific containment
Why Instacart
Lifecycle experiences and conversational shopping both shape how Maryland households interpret savings while returning to grocery delivery.
Written with these in mind
Not your kind of problem? 41 more at Instacart, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.