It's Sunday, and most of the week is already written. Two practices. One late meeting. A birthday party you said yes to back in March.
What isn't written is dinner. Not one dinner. Seven.
So you open the fridge and take inventory. You think about who's even home Tuesday. There's chicken in the freezer, half a bag of spinach with about two days left in it, and a jar of something you bought for a recipe you never made. You scroll a recipe site for four minutes and close it. You write "tacos?" on the list, then cross it out, because you made tacos Thursday.
Look at what that hour actually is.
None of it is cooking. Cooking happens later, you're good at it, and it takes the time it takes. What Sunday takes is the deciding: what, for whom, on which night, with what's already in the house, around a schedule that keeps moving.
Deciding is the job. Cooking is what's left after the job is done.
Count it out.
If dinner happens at your house most nights, you're making that decision somewhere around 300 times a year. Not 300 meals. Three hundred decisions, each one with groceries attached, each one attached to a specific night, and each one made again from close to zero seven days later.
Matthew Dicks wrote a book about time called Someday Is Today, and his argument is that we don't lose life in big pieces. We lose it in small ones. A day is 1,440 minutes. "Minutes matter," he writes, which sounds obvious right up until you total the minutes you spend every week re-answering a question you already answered last week.
So this is a time problem, not a food problem.
You don't have a recipe shortage. Nobody has a recipe shortage. What you have is a decision that reloads every seven days and never stays solved.
Go through the week and give every night a type. Four types cover most households.
Cook night. Somebody's home, the stove gets used, and the recipe can have more than five ingredients.
Fifteen-minute night. Practice starts at 5:30, dinner has to happen between two departures, and whatever you make has to survive being eaten in shifts.
Leftover night. You're eating Tuesday again, on purpose, and you planned it that way from the start.
Fallback night. Nobody's cooking. Step 4 is entirely about this one.
Do this first, because the week is the only fixed thing you've got. Recipes bend. A 6:15 pickup does not. Most meal plans fail because somebody built a list of meals and then handed it to a week that couldn't take it.
Stop trying to pick the best dinner. Pick twelve dinners your household will actually eat, and eat those.
It feels wrong the first week. It works anyway, because twelve is enough that nothing repeats inside close to three weeks, and small enough that you know the ingredients by heart and can shop for them without a recipe open in front of you.
Write the twelve down somewhere permanent. That list is your menu now, and you're allowed to stop auditioning new ones every Sunday.
Tim Ferriss makes this argument in The 4-Hour Workweek about business decisions, and it transfers to a kitchen without much translation. The expensive part isn't making a decision. It's deliberating over it. Every extra option costs you attention before it ever costs you groceries. Cutting the options is what buys the time back.
Some people read that and want to build their own twelve. Others read it and think, I don't want to build a rotation, I want to be handed one that already fits my week. If that's you, that's the exact job I do inside The Meal Plan Concierge.
Daniel Markovitz wrote a book called A Factory of One, about running your own work the way a good factory runs a line. One line of it has stuck with me for years: waste is anything you do that doesn't move the work forward, and re-doing something you already did is the most expensive kind there is.
Rebuilding your grocery list from memory every week is rework.
You already know what goes into those twelve meals. Write each meal's ingredients out once, on the same page as the meal. After that, the weekly list stops being a writing job and turns into an assembly job: pick the meals for the nights you typed in step 1, pull their ingredient lists, cross off what's already in the pantry. None of it is remembering.
Every week has a night that comes apart. The mistake is treating it like a surprise.
Pick the bail-out now, while nothing's on fire. The frozen pizza you keep on hand. The place that delivers. Eggs and toast, which nobody in the history of your house has ever complained about. Write it on the plan as a real line, on a real night.
A pre-decided fallback costs you nothing, and it kills the worst decision of the week: the one you make at 6:40 with your keys still in your hand.
Type the nights. Pick from the twelve. Pull the ingredient lists. Add the fallback. About twenty minutes, in one pass, instead of seven small passes scattered through the week while you're doing something else.
Markovitz on task switching and Ferriss on batching arrive at the same place: you pay a setup cost every single time you start, so start fewer times.
That's the method, and it's yours to run. If you'd rather not run it, you can skip ahead to the week where it's already built for you.
This method breaks. I'd rather you hear that from me than find out on a Wednesday.
It breaks around week three, and not because you ran it wrong. It breaks because the week changed. Practice moved to Thursday. Your daughter is done with the chicken thing she asked for in June. Your husband gets a work dinner on the one night you'd planned the long recipe. Somebody catches a stomach bug, and Tuesday's meal is still sitting in the fridge on Friday.
None of that is a planning failure. That's a household, moving.
The plan was never the burden. Building the plan takes twenty minutes.
The burden is the re-syncing. It's holding the schedule, the preferences, the pantry, the leftovers and the twelve meals in your head at the same time, and re-fitting them to each other every seven days, forever. That's the work nobody assigned to you and nobody else is doing.
A printable can't do it. An app can't do it either, because the app doesn't know Thursday got crazy. It's a coordination job, and coordination is the part that has always stayed yours.
Which is why the useful version of this isn't a better template. It's somebody building the whole thing around your household and handing it back to you finished. Here's what that actually involves.
One more idea from Dicks, because it's the reason I built this in the first place.
He calls it the One-Hundred-Year-Old Plan. When he has a decision to make, he doesn't ask the version of himself sitting there in the moment. He asks the hundred-year-old version, the one standing at the end of it all, and lets that person decide.
Try it on this one. Ask the version of you at the end of your life what she'd want back from your Sundays.
She isn't going to ask for a better rotation. She won't remember the week you got the grocery order exactly right. What she'll remember is specific: a Tuesday with everybody at the table and nobody rushing out the door, the walk after dinner you keep not taking, half an hour on the couch with your husband and both phones face down in the other room.
Time spent re-deciding dinner is time. It isn't overhead, it isn't admin, and it isn't free. It comes out of the same account as everything else you'd rather be doing.
I'm doing this for three households, and it genuinely isn't for everyone. If you want the recurring work taken off your plate instead of another list to maintain, read the details and see whether it fits your household.
Do this tonight, in one sitting, whether or not you ever buy a thing from me.
Write down twelve dinners your household actually eats. Not aspirational ones. The twelve that get eaten without a negotiation.
Then put one number beside each: how many nights of leftovers it produces. Zero, one, or two.
That's the whole exercise. You now have the two pieces every weekly plan needs, and you'll never have to pull them out of memory again. Next Sunday, type your nights, pick from the twelve, add your fallback, and you're running a real system that cost you one sitting and a piece of paper.
And if what you really want is for this to stop being your job at all, that's the version I'm building for three households at $299.
One conversation, and this part of your week stops being yours to carry.
You buy. You book a private 60-minute Household Planning Session with me. We spend that hour on how your household actually runs: your week, your calendar, who eats what, who won't eat what, what's already working and should be left alone, and what you keep rebuilding from scratch.
Within three business days after that session, I deliver a meal-and-grocery planning system built around your household. Your schedule, your preferences, your constraints, your routines. Not a template with your name typed at the top.
It's not a printable. It's not a recipe bundle. It's not a coupon plan or a grocery-savings program. It's not a course, and it isn't software you'd have to set up, fill in, and maintain.
There's nothing here for you to learn, and that's the point. You already know how your household works. The hour is you telling me. The rest is my job.
I'm not a meal-planning guru. I'm not a nutritionist. And I'm not going to pretend I understand your household before we've talked, because I don't.
What I do is build practical systems that take repeating work off a person's plate. That's the whole skill on offer here. You bring the household. I sit down and build the plan properly, once, so it stops getting rebuilt every week.
The rest of my work runs under Show Her Off, where we help couples make more room for connection. This pilot exists because one of the things that quietly eats that room is the planning nobody ever hands off.
Three households. I mean three, not three as a figure of speech.
At three, I can be far more hands-on than would ever hold up later. Your session and your build come from me. In exchange, I learn what this service should actually be by building it with the three of you first. That's the trade, and it's why you're getting this much attention at this price.
$299. One payment. Three founding households, and when the third one is taken I stop the ads and go build.
The guarantee: if it doesn't hand you real time back, tell me and I'll refund you in full. You don't have to build a case for it, and there's no awkward conversation waiting on the other end of that email.
You'll book your 60-minute session right after checkout.What if I have picky eaters? Then they're part of what we map. Picky eating isn't a problem to fix in the session, it's a constraint to build around: who won't eat what, what's non-negotiable, and which meals still work when one person opts out. The system gets built with those people in it, because they're the ones eating.
What exactly do I get? Honest answer: I don't know yet, and I won't until we talk. Here's what's fixed. A meal-and-grocery planning system built around your household's schedule, preferences, constraints and routines, delivered within three business days of the session. What it looks like gets decided in the session itself, based on how you actually run your week. I'd rather tell you that than promise you a format that turns out to be wrong for your house.
When is the session? After you buy. You book it yourself, at a time that works for you. It's 60 minutes, it's private, it's with me, and it's required. Nothing gets built until we've had it.
What if it doesn't help? Full refund. If it doesn't hand you real time back, email me and I'll return the $299. No justification required, no awkward conversation.
Why only three spots? Because three is what I can do at this level of attention. This is a founding pilot, not a launch. When the three households are filled, the ads go off and I go build.