02 · 2025 · Product & automation
autoPlan
An automated meal-planning loop: it drafts the week, the household votes on Telegram, and the grocery carts build themselves.
Live — in production
Solo build
Runs every Thursday
Overview
Pick, vet, cook, repeat — with the household involved, but without a weekly meeting about it.
A Thursday-night job drafts a balanced week and posts it to Telegram. Everyone votes with one tap — accept, swap, or veto — the plan locks in, and a bot builds the multi-store grocery cart. The only human input is a thumb.
01 — The problem
The weekly dinner question.
Every household deals with it: what to eat next week, who's shopping, what's already in the fridge. It's usually an hour of back-and-forth that rarely produces a plan lasting past Monday — low stakes, high friction, and a good fit for automation.
02 — The approach
One tap instead of a meeting.
Instead of asking the household to plan, autoPlan asks them to react. The system drafts a balanced, preference-aware week and drops it into the group chat everyone already uses. Accept keeps it, swap rerolls one night, veto removes a dish for good. The plan settles in a few taps.
03 — The build
Built from cheap, boring parts.
Python on GitHub Actions drafts the week on a schedule. A Cloudflare Worker holds the live vote state in D1. Supabase stores the recipes and preferences. Once the plan locks, a Playwright bot logs in and builds multi-store Instacart carts. There are no servers to maintain, and every piece runs on a free or near-free tier.
04 — The outcome
It runs on its own now.
The loop runs unattended every week. The recipe library, preferences, and cook history are its memory, so the drafts get better and the vetoes get rarer. The negotiation didn't get faster — it went away.
~60 min
of weekly planning, gone
1 tap
from draft to a filled grocery cart
Want more detail? Get in touch →