The short version
Why I built Weeknight

Most weeks, dinner isn't one decision. It's five: what's actually in the kitchen, what the people you're feeding will eat, what you already bought last week, what you're low on, and whether there's time to cook any of it. Solving that from scratch every single night is real work, and nobody hands out credit for it.
So I built Weeknight to answer those questions once, at the start of the week, instead of five times before six o'clock. You tell it who you're feeding and what's on your shelves. It plans dinners around that, keeps track of what you've used, and puts together a shopping list with only what you're actually out of.
Recipes are the easy part. The hard part is remembering what you cooked last Tuesday, which chicken your household will actually finish, and that there's already a jar of sauce in the back of the pantry. Weeknight is built for the hard part — it isn't a recipe site with a calendar bolted on.
Everything here is aimed at one outcome: dinner, handled. So the evening can just be the evening.
Questions or ideas? hello@weeknight.co
