When cheaper isn't the win
Okay. We've talked chicken, we've talked bulk buys, we've talked produce. Now let's talk about the thing that trips people up more than any of that: the idea that the cheapest option is always the right one.
It's not. Not always. And this took me a while to actually believe.
The seven-dinner disaster
First week I ever tried meal planning, I did it the "right" way. I sat down, found a bunch of recipes that looked healthy and impressive, priced them out, and they were cheap. Beans, big bags of spinach, from-scratch everything. I bought ingredients for seven dinners.
I cooked two of them.
Nobody in my house wanted the other five. Calvin wouldn't touch most of it, Jaden was polite about it but I could tell, and I ended up standing over the sink dumping a whole bag of slimy spinach into the garbage on Saturday. That spinach was the "cheap" choice. It cost me money and I never even ate it.
That's the week I learned to plan for the family I actually have, not the family on Pinterest. 🥲
Cheap isn't the same as cost-effective
Here's my actual opinion on this, and I know it goes against a lot of budgeting advice: sometimes cheaper isn't the win. Sometimes the win is dinner happening at all.
The rotisserie chicken is the easy example, we've covered that. But it shows up everywhere:
- The dried beans are cheaper than canned, but if you never actually soak them and end up ordering pizza instead, the canned beans were the cheaper choice, once you count the pizza.
- The bulk bag of a vegetable nobody in your house likes isn't a deal. It's slime in eight days.
- The recipe that takes 90 minutes might have cheap ingredients, but if it means you're serving dinner at 7:30 to kids who started melting down at 5:30, that's a cost too. Just not one that shows up on the receipt.
I run this stuff like I run everything else, looking for where the actual failure is. And the failure is almost never "I spent too much on chicken." It's "I bought food nobody ate" or "I planned something so complicated I gave up."
How to actually check yourself on this
Before you put something on your plan because it's the budget option, ask two questions:
Will my people actually eat it? Not "should" eat it. Will. If you have a picky eater, or a partner who's polite about food he doesn't love, or a kid who only wants rice right now (mine did, for a solid week, and honestly rice is just on my template permanently now, I stopped fighting it) — plan around the real answer, not the aspirational one.
Can I actually pull it off on a weeknight? If the cheap recipe needs 45 minutes of active cooking after work, and your actual weeknight has 20 minutes before someone's crying about homework, it doesn't matter what it costs at the store. You won't make it. You'll order out, and now it cost more than the "expensive" option would have.
A quick gut check for your own list
Look at your plan from the last couple lessons. For each dinner, ask yourself honestly: is this cheap on paper, or cheap in real life?
If you've got something on there that you added because it was frugal, not because you knew your family would eat it, flag it now. Swap it for something boring that you know works. Boring and eaten beats impressive and thrown out, every time. I'd rather you serve tacos for the fourth time this month than watch another bag of spinach go bad.
This isn't about spending more. It's about spending on the things that actually turn into dinner, instead of the things that turn into garbage.
Before next time: Look back at your week's plan and circle anything you added because it was cheap rather than because you know it'll get eaten. We'll use that next lesson.