Solo Cooking: Meal Planning When It's Just You

You're in the produce section, holding a bunch of cilantro. You need about a tablespoon for tonight's recipe. Maybe two if you're generous. The rest of it, the other 95%, will sit in your crisper drawer until Thursday, when it turns to green slime and you throw it away. You know this. You've done it before. You buy the cilantro anyway, because they don't sell it by the tablespoon.

This is cooking for one.

The invisible audience

Meal planning advice is written for households. "Plan your family's meals for the week!" "Get the kids involved in choosing recipes!" "Make enough for leftovers so everyone has lunch tomorrow!" The Pinterest boards and the TikTok meal preps and the Sunday planning sessions all assume more than one mouth at the table.

Recipe sites default to four servings. Grocery stores sell cauliflower by the head and chicken in packs of six thighs. Costco exists for families of four, not studios with a mini-fridge.

If you're a young professional in your first apartment, or an empty nester adjusting to a quieter kitchen, the entire food infrastructure sends a subtle message: this wasn't built for you. And it wasn't.

The advice doesn't fit. "Batch cook on Sundays!" Okay, but eating the same chili for five consecutive nights is its own form of despair. "Shop the sales and stock up!" Sure, if you have somewhere to put 48 rolls of paper towels and can eat six pounds of ground beef before it expires.

Nobody says the quiet part out loud: cooking for one requires a different approach entirely. Scaling down a family plan doesn't cut it.

The rotation trap

So you adapt. You find three or four meals that work at your scale. Chicken breast and rice. Pasta with jarred sauce. Eggs and toast. Maybe a stir-fry if you're feeling ambitious.

These meals survive because they're portion-appropriate and predictable. You know exactly what to buy. Nothing goes to waste. The grocery bill is reasonable. It works.

The rotation works. But week six of chicken-rice-broccoli, you start eating out just to taste something different.

It works until it doesn't. Until you realize you've eaten the same four dinners for two months straight and you're ordering takeout because you're bored, not tired. The rotation is a defense mechanism against waste. You'd cook more variety if it didn't mean buying ingredients you can't finish.

That guilt sits in the background. "I should eat more vegetables." You'd love to. But a whole head of cauliflower is a commitment for one person, and the half you don't use tonight has about three days before it belongs in the compost.

The math that doesn't work

Recipe scaling sounds simple in theory. Divide everything by four. But cooking doesn't work in clean fractions.

What's half of one egg? A third of a 14-ounce can of coconut milk? You can't buy a quarter of an onion. The recipe calls for a cup of broth and the carton holds four cups, so you're either making this same recipe three more times this week or watching three cups of broth expire in your fridge.

Baking is worse. Half a recipe of cookies still requires you to buy a whole bag of chocolate chips and a whole stick of butter and a whole container of baking soda. The economics of cooking for one are different than most food advice accounts for. Bulk buying saves money per unit but costs more in waste. The "price per serving" math that works for families breaks down when half the ingredients go bad before you can use them.

This isn't a discipline problem. It's a logistics problem that nobody acknowledges because the food world wasn't designed for a party of one.

What context changes

The problems above aren't about a lack of recipes or motivation. They're about a lack of connection between meals. Tonight's cilantro has no relationship to tomorrow's dinner. That half-can of coconut milk exists in isolation. Each meal is a standalone event, and the waste accumulates in the gaps between them.

When your AI knows you're cooking for one, those connections become visible.

You bought a bunch of cilantro for tonight's tacos. The AI sees cilantro in your pantry and knows you're cooking solo. Tomorrow's suggestion uses the remaining cilantro in a rice bowl. The day after, the last of it goes into a quick salsa verde with a chicken thigh. Three meals, one bunch of cilantro, no green slime in the crisper drawer.

That head of broccoli you've been avoiding? When the system knows your household size and your pantry, it plans around it. Roasted broccoli as a side tonight. The rest goes into a frittata tomorrow. Two meals, zero waste, and you didn't have to figure out the connection yourself.

That response doesn't suggest a recipe in isolation. It links two meals together so the ingredients carry across both. Individual meals become a connected sequence, and the waste problem shrinks because nothing exists as a standalone purchase anymore.

Your pantry tracks what's expiring, so the broccoli that's been sitting for three days gets prioritized over the canned beans that have months. Your receipt scan logs what you bought and when, so the system knows the tofu is fresh and the spinach is on borrowed time.

Why planning matters more, not less

There's a common assumption that meal planning is for busy families juggling multiple schedules and dietary needs. And if it's just you, you can wing it.

The opposite is true. When you're cooking for one, there's no margin. A family of four can absorb a head of broccoli across multiple plates in one sitting. You can't. A family forgets about leftovers and someone eventually eats them. You forget about leftovers and they become a science project.

Every ingredient you buy needs a plan, or it becomes waste. No one else is going to bail you out by finishing the leftover soup or eating the bananas before they go brown.

The 5pm decision fatigue that hits families hits solo cooks just as hard, with the added layer of "it's just me, so I'll just have cereal." Which is fine sometimes. But not every night.

Meal planning for one isn't excessive. It's practical. A fifteen-minute Sunday look at what's in your fridge and what you might eat this week means less money in the trash and fewer evenings staring into the refrigerator hoping for inspiration.

Cooking for one is real cooking

Somewhere along the way, solo meals got framed as lesser. "Sad desk lunch." "Bachelor cooking." Entire marketing campaigns built around the idea that cooking for one is a temporary state you'll eventually graduate from.

It's not. Millions of people cook for one, permanently, by choice or by circumstance. A recent grad in a studio apartment. An empty nester whose kids moved out. Someone who lives alone and is fine with it. None of them need to be told to "treat yourself to a nice dinner." They need tools that understand the difference between cooking for one and cooking for four.

The mental load of meal planning doesn't disappear because there's only one person at the table. If anything, you feel it more, because there's nobody to share the decisions with.

Start with your fridge

You don't need to overhaul anything. Open your AI and tell it what you have. That half block of tofu, the broccoli, the two chicken thighs, the rice that's been in the pantry since you moved in. Let it figure out what links those together into actual meals for this week.

The cilantro doesn't have to end up as slime. The cauliflower doesn't have to be a commitment you regret. When your AI knows how your kitchen works over time, every ingredient gets a purpose, and cooking for one stops being a series of isolated meals and starts being something that actually flows.

Start with what's in your fridge tonight