Testing meal planning with our own kitchens first
The NestBoard team · 2026-07-13
Tuesday: the recipe import worked too well
We started the week confident. Everyone on the team added three recipes to their meal plan using the URL import tool. By Tuesday evening, two of us had the same problem: we'd imported a recipe for "quick weeknight pasta," opened the ingredients list on our kitchen tablets, and realized it called for preserved lemon and homemade ricotta.
The import worked perfectly. It pulled every ingredient, every instruction. But "quick" meant different things to different recipe bloggers, and we had no way to flag that a thirty-minute recipe might actually take an hour if you're new to it.
We added a notes field to each meal card that night. Nothing fancy—just a place to write "needs advance prep" or "actually takes 90 min" before the week starts. It shows up when you tap into the day view, right above the ingredient list.
Friday: nobody wanted to decide
By Friday we had a different problem. Four meals were planned. Three nights were blank. We'd all done the same thing: filled in Monday through Thursday with good intentions, then stopped.
The empty boxes weren't a bug. They were a decision we'd been avoiding all week. We already knew importing recipes from any cooking site was smooth, but choosing which recipes—and when—felt like homework.
One of us admitted she'd been planning to "just order pizza" for the blank nights but felt guilty leaving them empty in the app. That's when we realized the meal planner was accidentally creating pressure instead of reducing it.
We added a "TBD / flexible" option. Now you can mark a night as "planned to wing it" and it stops feeling like a gap. It sounds small, but three of us used it the following week.
What surprised us: the pantry integration actually mattered
We built the meal planner knowing it would connect to the pantry feature, but we didn't expect to rely on it. Turns out, when you're looking at Thursday's dinner plan on Monday morning, seeing that you already have canned tomatoes and dried pasta in the pantry changes whether you'll actually cook that meal.
Two team members said they picked different recipes mid-week specifically because the pantry showed they had the base ingredients already. One person avoided a recipe because the pantry flagged that her chicken stock expired three days ago.
The integration wasn't flashy. It just surfaced the right information at the decision point.
The change we didn't make
We talked about adding a "generate a week of meals" button. Robin could look at your pantry, your past favorites, your household size, and build a plan automatically.
We didn't do it. Not because it's technically hard, but because the act of choosing—even if you only choose three nights and leave two flexible—is part of how you stay connected to what your household actually wants to eat this week.
The meal planner isn't supposed to remove you from the process. It's supposed to make the process less scattered. Recipes in one place, ingredients linked to your pantry, notes visible when you're standing in the kitchen.
We shipped it the following Monday.