It's 7:30 pm. Nobody's said it out loud yet, but the question is already in the room: do we cook, or do we just order something? You drift toward the fridge, then toward your phone, then back, and twenty minutes later you've neither started dinner nor ordered it. The cook-or-order standoff is its own small genre of tired-evening paralysis.
Here's the thing almost everyone gets wrong about it: "cook or order?" feels like a question about effort, but it stalls for the same reason "what should we eat?" stalls. You haven't decided what you actually want yet.
Why "cook or order" is so hard to answer
By evening you're low on the fuel good decisions run on. It's decision fatigue: a day of choices has worn down your capacity to make one more, and now you're being asked to weigh effort, cost, time, cravings and cleanup all at once, at your worst hour for exactly that kind of thinking.
So the brain does what a depleted brain does – it avoids the hard part. Opening a delivery app feels like progress, but it hands you three hundred restaurants and lets you keep scrolling, which is just the original indecision with a delivery fee attached. You didn't decide. You outsourced the stalling.
The real question underneath
"Cook or order" is two decisions pretending to be one:
- What do I actually want to eat tonight?
- How much effort do I have for it?
The second question is easy – you already know if you have twenty minutes and a little willingness, or nothing left at all. It's the first one that's genuinely hard, and it's the one both cooking and ordering depend on. Answer it, and "cook or order" mostly answers itself.
That's why the fastest people at this don't debate the method. They lock the dish, then the method is obvious.
A 10-second way to decide
Try it in this order:
- Pick the craving, not the recipe. Something warm or something fresh? Comfort or light? You're choosing a direction, not committing to a specific dish yet – that's a decision a tired brain can finish.
- Land on one dish. Narrow the direction to a single thing you'd actually be happy eating. If nothing surfaces, spin a random dinner and react to what comes up – a concrete option is far easier to accept or reject than an open menu.
- Let tonight's energy pick the door. Have twenty minutes? Cook it. Running on empty? Order that same dish. The decision was never really "cook or order" – it was "what," and you just made it.
The whole point is to spend your last scrap of decision-making on the dish, not on the delivery app's carousel.
When to cook, when to order – honestly
Cooking wins more nights than the takeout habit admits. It's cheaper once fees and a tip land, and a twenty-minute skillet dinner often beats waiting forty minutes for a driver. But ordering is a legitimate move, not a failure – on the truly-done nights it buys you time and zero cleanup, and choosing it on purpose feels completely different from defaulting to it because deciding was too much.
The failure mode isn't ordering. It's the twenty-minute scroll that ends in ordering anyway, resentful and later than if you'd just chosen.
Where SomeYum fits
This is the exact loop SomeYum is built for. You swipe through dish cards one at a time, yes or no, and the app learns your taste as you go – so instead of an open "what do I want?", you get a short string of easy reactions that end in a decision. A few swipes and dinner's decided.
Then it gives you both doors on the dish you picked: cook it with the full recipe included, or order it – one tap finds that exact dish at places near you. Same decision, either method, no second stall. It's the dish-first idea applied to the cook-or-order night specifically: decide what, and the how stops being a fight.
The craving is more decisive than the method. Settle it first, and 7:30 pm stops eating your evening.
Frequently asked questions
Should I cook or order takeout tonight?
Decide the dish before you decide the method. 'Cook or order?' is an effort question wearing a food question's clothes, and it stalls because you haven't picked what you actually want yet. Once you know it's, say, garlic butter shrimp pasta, the choice is easy: cook it if you have twenty minutes, or order that same dish if you don't.
How do I decide between cooking and ordering?
Pick the craving first, then let tonight's energy pick the method. If you have the time and even a little willingness, cooking is cheaper and usually faster than delivery once you count the wait. If you're running on empty, order the exact thing you settled on instead of scrolling a delivery app for another twenty minutes.
Is it cheaper to cook or order in?
Cooking is almost always cheaper once delivery fees, service charges and a tip are added on, and for simple dinners it's often faster than waiting for a driver. Ordering buys you time and zero cleanup on the nights you have nothing left. The trick is choosing on purpose rather than defaulting to delivery because deciding felt like too much.
Why do I always end up ordering takeout?
Usually because the delivery app is the path of least resistance when you're too tired to decide. It opens with hundreds of options and lets you keep scrolling, so it absorbs the indecision instead of ending it. Deciding the dish first – in seconds, not minutes – removes the reason you reached for it.