Why you save 200 recipes and cook none of them

Open Instagram. Go to your saved folder. Scroll.

Somewhere in there is a pasta dish you were genuinely excited about in March. You have not made it. You will probably never make it. And it is not because you are disorganised or lazy — it is because saving and cooking are separated by four small, boring problems, and nobody has fixed all four in one place.

They are worth naming, because once you can see them you stop blaming yourself.

1. The recipe isn't really in the post

You saved a video. Where is the recipe?

Maybe in the caption. Maybe on screen for two seconds at 0:14. Maybe in a pinned comment. Maybe in the creator's link-in-bio, behind an ad wall, on a page that takes nine seconds to load and moves as it does.

So "get the recipe" is not one action. It is a small research project of three to five steps, and its length is unpredictable before you start. Not hard — just uncertain, and just long enough that you do it on a Sunday when you are relaxed and never at six o'clock on a Wednesday when you actually need dinner.

The gap is not between wanting to cook and cooking. It is between wanting to cook and knowing how long it will take to find out how.

2. Saved isn't a list, it's a pile

A saved folder has no structure worth the name. No times. No ingredient index. No filter for "things I can make in 25 minutes with what is in the fridge". No way to ask the only question you ever actually ask, which is what can I cook tonight.

So it degrades with use. Every save makes the pile slightly less useful than it was, because it is one more thing between you and the one you meant. At forty saves, finding the right recipe is genuinely harder than opening a delivery app — and the delivery app is right there, and it is very good at being easy.

This is the exact opposite of how a collection is supposed to work. A good collection gets more valuable as it grows.

3. Planning is a chore that starts empty

Nearly every meal-planning app hands you a blank calendar and asks you to drag recipes onto it, twenty-one times, once a week, forever.

That is not a feature. That is homework with a nice typeface.

The apps are not wrong that a plan helps — a planned week demonstrably produces more home-cooked dinners and a smaller shop. They are wrong about who should do the work. You already told the app what you like. You told it forty times, by saving forty videos. Turning that into a week is exactly the kind of dull, constrained, repetitive task software is good at and a tired person on a Thursday is not.

We think this is the single largest unclaimed opportunity in the category, and it has a post of its own.

4. The shopping list is wrong, so you stop trusting it

This is the one that actually kills the habit.

Read the public reviews of any recipe app with a grocery feature and you will find the same four complaints, over and over, across every app in the category:

• "garlic" and "2 cloves garlic" listed as two separate items
• fresh herbs filed under frozen, so you walk the shop twice
• a list that goes stale the moment you change one meal
• ticked items that reappear after a refresh, so you buy pasta twice

Here is why that is fatal rather than annoying. A shopping list you have to double-check is worse than no list at all, because now you are doing the work and auditing it. The whole value of a list is that you can switch your brain off in the shop, and a list with one wrong line in it is a list you can never switch off for again.

So after a fortnight you go back to typing things into your notes app, and the meal planning quietly stops. Not with a decision — nobody ever decides to stop meal planning. It just erodes.

A list you can't trust costs more than no list at all.

Why fixing one of these doesn't work

Each of the four is individually small, and that is exactly why the problem has survived. Every app in this space has fixed one or two of them well.

But the frictions multiply rather than add. An app that extracts recipes beautifully and then hands you an empty calendar has fixed step one and left you stuck at step three. An app with a lovely planner that draws from a stock recipe database has solved planning for recipes you never chose, which is not the problem you had. And any of them can be undone by a shopping list with garlic on it three times, because that is the step where trust is actually won or lost.

You need all four, in one place, or the chain breaks at the weakest link and you are back in the saved folder scrolling past a pasta dish from March.

What we're building

FasterChef is the four fixes, in order:

1. Share a reel, get a real recipe. Ingredients, quantities, numbered steps

— with the creator credited and linked on every single one.

1. A library that is actually searchable. By time, by cuisine, by what you

have cooked before, and forgiving of a typo.

1. A week that plans itself from what you have already saved, respecting

what you do not eat and how long you really have on a weeknight. It takes under 200 milliseconds and makes no model call, so it cannot hand you a recipe you never saved.

1. A shopping list that is correct. Merged against a dictionary of 412

canonical ingredients, converted, sorted by aisle, and still correct — with your ticks intact — after you change the plan.

None of those four is a new idea. Doing all four properly, in one app, is the part nobody has done.

We're building it now. If you want in early, the waitlist is below.