I built a meal planning app to solve my own problem. Here's what actually happened.
My wife and I were spending real time every week sitting down and figuring out what we were going to eat. Not a few minutes. Actual time. We had a collection of Hello Fresh recipes we'd liked and things we'd found online over the years, and the process every month was: dig through the pile, pick some meals, write a list. Same thing, every time.
The first version of what became Ladle was embarrassingly simple. It was basically a randomizer. Give it a list of recipe titles, it picks some for the week. That's it.
It worked for that one planning session at the start of the month. But every 3 to 5 days we'd run out of planned meals and have to start over. Look at what we picked, figure out what ingredients we needed, check what we had, build a shopping list. That part hadn't gotten any easier.
That's when I built the shopping list.
The ingredient combining problem nobody warns you about
Building a shopping list sounds straightforward until you try to do it across multiple recipes at once.
Recipes are inconsistent. One calls for 'kosher salt.' Another calls for 'salt.' Another calls for 'sea salt, to taste.' They're all salt. But a naive system lists them as three separate line items. We'd end up with 15 lines for salt and pepper alone.
So a meaningful chunk of the work went into normalization: teaching the system that these things are the same thing, combining quantities intelligently, and producing a shopping list that actually reflects what you need to buy rather than a raw dump of every ingredient from every recipe.
That problem is still evolving. Instacart integration is built and pending activation, which will let the list go from organized to actually shoppable in one tap. But the normalization work was the foundation that made everything else worth building.
Why it's called Ladle
The recipe collection was always the part that felt most personal. Over the years you accumulate recipes from everywhere: websites, cookbooks, handwritten cards from family members, photos you took of a magazine page in a waiting room. They live in different places and formats and there's no good way to bring them together.
The URL and photo import features came from that. You can paste a recipe link from any website, snap a photo of a cookbook page, or photograph a handwritten card and Ladle pulls out the real ingredients and adds it to your library.
The name came from that idea. A ladle scoops up whatever is in front of you. That's what the app does with recipes: it gathers them from wherever life left them and brings them into one place where they can actually be used.
What's in it
The app is live at useladle.com. Here's what it does:
200+ curated recipes across cuisines and skill levels, handpicked not generated
URL and photo import: paste a link or scan any recipe and it lands in your library
Auto-plan: generates a full week of meals across 4 modes with dietary exclusions and frequency limits
Consolidated shopping list: ingredients combined across all planned meals, pantry staples filtered out, organized by store section
Cookbook PDF export: every recipe you save exports as a formatted PDF
How I thought about pricing
I’ve run multiple rounds of competitive analysis, mapping Ladle's feature set against Mealime, Plan to Eat, Paprika, Samsung Food, Mela, and AnyList. The goal was to find gaps worth filling and understand what a complete system actually needed. Samsung Food is a useful benchmark in that group because it has real resources behind it. By the time that process ran its course, Ladle had features none of the others had: full AI photo import from cookbooks, handwritten cards, and screenshots; cookbook PDF export; and a smart auto-plan with 4 modes, dietary rules, and history-weighting that has no real equivalent in the field.
That created an interesting problem. An advisor pointed out that when you offer more features than competitors at a lower price, you don't look like a bargain. You look like something is wrong with it. So I priced accordingly.
The model is a 14-day free trial with full access and no credit card required, then Pro at $4.99/month or $41.99/year.
Where it stands
It's early. The app is live, it's being used by us, and the foundation is solid. The mobile path is next (Capacitor build is ready, working through App Store enrollment). Instacart integration is built and waiting on partner activation. The recipe library just hit 200.
The goal has always been the same: remove as much admin time from the planning and shopping phases of cooking as possible so the part that's actually enjoyable, the cooking itself, gets more room.
If you're curious, the full blog post on the shopping list problem is here, and the app is at useladle.com with a free trial.
