Why it’s here
A small business has the same problem my kitchen does: information arrives in email and paper, and a person retypes it. The approve-first inbox is the pattern I’d use for vendor emails, invoices and orders. The machine reads and drafts. A person decides.
Why I built it
With kids in school, a lot of information comes into our house. Flyers, school emails, grocery lists, reminders. Most of it needs someone to read it and type it somewhere. I wanted that to stop.
What it does
- Every household gets an email address. Forward a school email to it, or upload a flyer or a PDF. Claude reads it and suggests what to add.
- Nothing lands without approval. Suggestions wait in an inbox. A person says yes before anything goes on the board.
- Groceries go to Kroger. Product search and the cart are wired to the Kroger API.
- A daily briefing. What’s on today, what’s overdue and what’s coming this week, by email, by push notification, or both.
- Caregivers see what they need. A sitter or grandparent can join the household without seeing the subscriptions or cards.
- Claude has a budget. Each household gets a daily limit on reads, and the same email arriving twice is read once.
How it’s built
Next.js on Vercel, with Convex for data, sync and scheduled jobs. Resend handles sign-in email, the briefing and the incoming mail. The Claude API reads flyers, PDFs and emails.
How it came together, day by day, is in the build log.