How AI took an hour off my grocery shopping every week
My partner and I eat on a rotation. Four different food lists on a four-week cycle, designed so we’re not cooking the same things back to back. Every Saturday we pick meals for the coming week, and on Sunday we shop.
This system works for us. But the tooling is a separate problem.
I kept a backlog of recipes in one place. The weekly list lived somewhere on my phone. The shopping list got rebuilt from scratch every time, and I’d manually flatten ingredient overlaps across two or three recipes in my head. “We’re both using onions so that’s four total, not two plus two.” Existing apps that claim to handle this are cumbersome, or come with vendor lock-in.
I described the problem to Friday in a single message.
The conversation
I want you to make me a workspace to help me manage my recipes, meal planning, and grocery list. I’ve attached a food chart. We rotate through each column of foods weekly, on a 4-week cycle. Generally on Saturdays we pick a meal plan for the coming week, then Sunday we shop. I want help tracking recipes, compiling the grocery list and sending it to me.
Friday asked seven questions to make sure it got the details right.
Where do you want the grocery list delivered? I’ve already got your email connected — we could use that.
Great.
How do you want to add random mid-week items?
I’ll just shoot you a message here.
How precise do you want ingredient quantities in recipes?
Best effort , I’ll give you what I have, fill in reasonable quantities for the rest.
How do you want to track which week of the rotation you’re in?
We’re in the first week’s rotation now. Just take it from here.
What happens to the shopping list and meal plan at the end of the week?
Archive the meal plans, clear the shopping list when the email gets sent. You can consider finishing the week’s list by sending the email.
That was my idea and Friday ran with it.
After the seven questions, Friday reflected the whole thing back:
The workspace tracks your 4-week food rotation, advances automatically every Sunday, and holds your recipe backlog as a living recipe book. You drive planning on Saturdays — name what you want to make, Friday builds the plan and loads ingredients onto the list. When you say “send the list,” it compiles everything, emails it, clears the list, and archives the meal plan. Ad-hoc items — just drop them in chat during the week.
Then Friday just built it.
What the workspace has
Four memory stores:
recipes — permanent backlog, quantities best-effort, week tags
meal-plans — archived forever, indexed by rotation week and date
shopping-list — active and ephemeral, clears on send
rotation-tracker — current week, auto-advances Sundays
Two jobs:
Send the list: compile, email, clear list, archive meal plan
Sunday cron: advance rotation tracker
Planning: just chat. No job, no form. I talk to it and it knows the context.
Using it
A few days after setup, I opened the workspace and dropped this:
Heya, I need a quart of milk and 2 half-gallon things of Oatly this week, add it to my list
Done. Three seconds.
Then I pointed it at a couple of recipes: one by URL, one from my old recipe manager. I told it to save them and add them to the grocery list for the week, and mentioned I had some of the basic ingredients on hand. Friday extracted the recipes, saved them to my recipe book, and added only what I didn’t have.
Then:
Good deal, enough for now. Can you email it to me?
Email sent, list cleared.
What’s different about doing this in Friday
I’ve used plenty of other tools for recipes. For example, Paprika is good at storing and scaling them. But it doesn’t know where I am in the rotation, doesn’t track the list, and doesn’t flatten ingredient overlaps across recipes and email me a grouped list on request.
The flattening is the thing I kept doing manually. Fajitas and a stir-fry in the same week both need bell peppers. I used to count that in my head.
The workspace is real. Memory stores, jobs, a cron schedule that fires every Sunday at 6am Mountain. Not a description of what a workspace would look like. The actual thing.
Context persists. When I say “I’ve already got avocado oil,” that shapes what goes on the list. When I ask about past meal plans, Friday pulls them. Nothing drops between sessions.
The interface is conversation. I don’t fill out a recipe form. I give Friday a URL or a photo from a cookbook. Friday extracts what it needs. I don’t click “generate grocery list.” I say “send it” and it sends.
What’s next
Saturday planning is the part I’m most curious about. Friday knows which food list is active and can pull relevant recipes from the backlog before I ask. It already knows I make pumpkin chili once a month.
You can build the same thing on Friday Studio. Free to start. You describe what you need, Friday asks the right questions, and the workspace exists.
 | A guest post by
|