The essential thesis: why we're starting with food.
The categories that shape our days — food, time, money, waste — are still served by software that treats each one as separate. We think they're one system. Here's the thinking behind Everything Essential.
If you ask a household to describe the operations they run every week, most people pause. They don't think of themselves as running operations. But they are — quietly, constantly, and almost entirely in their heads.
What's in the fridge. What's expiring soon. What's on sale this week. What we ate last Tuesday. What the kids will actually eat. What's left in the grocery budget. What we need to reorder. What got thrown away. All of it, tracked across a dozen mental spreadsheets and a few sticky notes on the fridge door.
The categories that touch every day
Everything Essential exists because, in our view, the categories that most people think about every day — food, time, money, waste — are still served by software that treats each one as a separate problem. Different apps. Different data. Different mental models. Different teams.
But in real life, they're one system. The shopping list is downstream of the recipe. The recipe is downstream of the inventory. The inventory is downstream of last week's grocery run. The grocery run is downstream of the budget. The budget is downstream of how much got wasted. Everything is connected — except, somehow, the software.
The shopping list doesn't know what's in the fridge. The recipe app doesn't know what's about to expire. The budget app doesn't see what got thrown away.
A system company, not an app company
We're not building a recipe app, or a fridge tracker, or a grocery list. We're building a system that holds those things together, and earns the right to make calmer, smarter defaults on top of them. The product is in the connections.
This is why we describe Everything Essential as a system company. Our work is intentionally less visible than a typical consumer app — fewer notifications, fewer animations, fewer screens. The wins are quieter: a list that's already right when you open it, an expiry warning that arrives one day before you'd have noticed.
Why food first
Of all the essential categories we could have started with, we chose food. Three reasons:
- Density of decisions. Few things in daily life produce as many small decisions as feeding a household. Most of them are repetitive. All of them benefit from memory.
- Sharpness of the waste problem. Households waste roughly a third of the food they buy — a number that's stable, well-documented, and almost entirely fixable with better information.
- A clean loop. Grocery → inventory → recipes → reorder is a loop we can actually close. Closing it makes every other step better.
That product is called Friddy. It's the first place we've put the Everything Essential thesis into practice. It won't be the last.
What we're not going to do
We're not going to gamify the kitchen. We're not going to send streak notifications or guilt people about their groceries. We're not going to optimize for engagement. The product is good if you forget you're using it — and remember you saved $80 at the end of the month.
What's next
Over the coming months we'll write more about the design philosophy, the data model, the food research, and the small group of people we're building this with. If any of this sounds interesting, the best way to follow along is the newsletter — or, if you'd like to partner with us, the contact page.
Thanks for reading. We've been thinking about this for a long time, and we're glad to finally be building it.