From Scratch Updates

What We’re Learning From Early Testing

Closed beta is underway, and the first lesson came quickly.

You can prepare as much as you want internally—and still miss things that matter in the real world.

One of the first issues we ran into wasn’t deep inside the app.

It was access.

Some users had trouble getting in.

It wasn’t a major system failure.

It was something simpler—something we had overlooked while focusing too much on the internal side of the app.

And that’s exactly the point.

What seems obvious during development doesn’t always hold up when real people try to use it.

That’s the value of this phase.

We were able to catch it early, make the adjustments, and move forward.

Because this isn’t about getting everything right the first time.

It’s about finding what breaks—and fixing it quickly.

And that’s exactly what this stage is for.

Closed Beta Begins

By March, we had taken the app as far as we could on our own.

We had built it.
Tested it.
Refined it.

But there’s a limit to what you can learn without real users.

At some point, you have to let go of control and see what actually happens.

That’s where closed beta begins.

This isn’t about everything being perfect.

It’s about seeing how the app holds up in real life.

Where people get stuck.
What they ignore.
What they come back to.
And what actually helps.

Because once people start using it on their own, assumptions don’t matter anymore.

Only behavior does.

So this is the point where From Scratch moves out of development—and into the real world.

We’ll see what holds up.

Why Community Became the Center of From Scratch

As we kept building, we ran into a question we couldn’t ignore.

You can find recipes anywhere.
Meal planning tools already exist.
Grocery lists can be generated automatically.
And more of that process is becoming easier to automate.

So we had to ask:

What would actually make this stand out?

If all of that can be done—and will continue to improve as AI becomes part of everything—what’s missing?

What’s the one thing that can’t just be generated or automated?

That answer changed the direction of the app.

It wasn’t more features.

It was people.

From Scratch wasn’t meant to be something you use alone.

It was meant to bring people into the same space around cooking.

To share what they’re making.
To learn from each other.
To see what actually works in real life.

A parent figuring out what their kids will eat.
Someone learning to cook for the first time.
Families managing busy nights and limited time.

That kind of experience doesn’t come from content.

It comes from other people.

That’s when community stopped being an idea—and became the center of what we’re building.

Because in the end, what makes cooking meaningful isn’t just the food.

It’s the people around it.

Why We Shifted Toward a Better Path for Building the App

By this point, we had learned a lot.

We knew what didn’t hold up.
We knew where things got too complicated.
And we had a clearer picture of what actually mattered.

But there was still a problem.

We weren’t building in a focused way yet.

There were still too many directions.
Too many ideas competing for attention.
Too many things that could be built.

We were spending more time thinking about what to build than actually building it.

That made progress slower than it should have been.

It also made decisions harder than they needed to be.

That’s when we made a shift.

We stopped thinking about everything the app could be.

We started focusing on what it needed to be.

That meant simplifying decisions.

Fewer features at a time.
Clearer priorities.
And building in a way that actually moved things forward.

Not just adding more.

That shift changed how we approached the entire app.

It brought more structure to the process.
More clarity to what we were building.
And more consistency in how decisions were made.

Because at some point, progress doesn’t come from more ideas.

It comes from choosing a direction—and sticking to it.

Why Teaching People to Cook Had to Be Part of From Scratch

At a certain point, we realized something we couldn’t ignore.

Recipes and meal planning weren’t enough.

You can give someone a recipe.
You can help them plan their week.
You can even make shopping easier.

But if they don’t feel confident in the kitchen, none of that goes very far.

That shows up in small moments.

Not knowing if the heat is too high.
Not understanding what a step really means.
Second-guessing whether something looks right.
Or getting halfway through and feeling stuck.

That’s where people drop off.

And it’s not because they don’t care.

It’s because they don’t feel confident.

That changed how we looked at the app.

From Scratch couldn’t just tell you what to cook.

It had to help you understand what you’re doing while you’re cooking.

That’s where things like clearer instructions and in-the-moment guidance started to matter more.

Not just telling you what to do—but helping you understand the small things along the way.

What something should look like.
What a term actually means.
What to adjust when something feels off.

Because those are the moments where people either keep going—or give up.

And if the app doesn’t help there, it doesn’t really help.

Because the goal isn’t just to give people meals.

It’s to help them feel like they can cook.

What We Learned From Ideas That Didn’t Hold Up

As From Scratch started taking shape, we had a lot of ideas that sounded good on paper.

Some were detailed.
Some were clever.
Some felt like they covered every angle.

But that didn’t automatically make them useful.

One of the biggest lessons we learned was that it’s possible to design something that looks complete from a systems point of view and still misses real life completely.

A feature can be polished.
It can be thorough.
It can account for edge cases and hypotheticals.

And still not make the app better for the person using it.

That forced us to get more honest about the difference between interesting ideas and useful ones.

Some features added complexity without adding enough value.
Some solved problems users weren’t really worried about.
And some created more work than they removed.

Badges were one example.

At first, they sounded fun. Earn progress. Unlock milestones. Add a little momentum.

But the deeper we got into it, the more it felt like extra weight instead of something people would genuinely care about.

That was a turning point.

We stopped asking whether an idea could be built well.

We started asking whether it should exist at all.

That shift made From Scratch better.

Because a product doesn’t improve by doing more.

It improves by focusing on what actually helps.

Why We Chose Simplicity Over Trying to Track Every Ingredient at Home

One of the first ideas we explored was a “smart pantry.”

The goal was simple on paper: track everything you have at home so the app always knows what you can cook.

It sounds like a perfect feature.

In reality, it breaks almost immediately.

Food disappears without being logged. Kids grab snacks. Ingredients get used for things you didn’t plan. Quantities are rarely exact. And no one wants to stop and update an app every time they use half an onion.

We realized quickly that the system only works if the data is perfect — and in a real kitchen, it never is.

That leads to a worse experience, not a better one.

Instead of helping, the app starts making bad assumptions:

• suggesting meals you can’t actually make
• missing ingredients you thought you had
• creating more friction than it removes

At that point, the feature becomes something you have to manage — not something that helps you.

So we made a decision:

We’re not building a full pantry tracking system.

Instead, we’re focusing on what actually works in real life:

• helping you decide what to cook
• helping you plan meals and shop efficiently
• giving you simple tips so you can learn as you cook

Not trying to perfectly track everything inside your kitchen.

Because in the end, simplicity isn’t about doing less.

It’s about removing the parts that don’t hold up in the real world.

From Scratch — Where It Started

From Scratch didn’t start as an app.

It started as a problem.

Meal planning sounds simple until you actually try to do it. You open the fridge, you check what you have, you think about what you want to make, and then you realize you’re missing half the ingredients. So you pivot. Or you give up. Or you order something instead.

That cycle repeats more than people like to admit.

Back in November 2024, I sat down and wrote out what problems I could actually solve:

• Planning meals without overthinking every decision
• Figuring out what to do when you don’t have, or don’t like, an ingredient
• Helping people feel more confident in the kitchen, not lost in it
• Bringing back the idea that cooking is about more than food — it’s about sharing something with other people

Most recipe apps don’t solve this. They give you content, not solutions.

From Scratch is being built to close that gap.

The goal isn’t to have the most recipes. The goal is to make cooking at home easier, faster, and more realistic for everyday life.

This is where it started. Everything being built now traces back to that moment.