To the household, Trepo is the operating system for the kitchen — cook what you have, know what you have. To the market, that same product is the first live read on what people actually eat.
One is how we win users. The other is how we win the decade.
Delivery in an hour. Ten thousand SKUs in an aisle. Groceries on four apps. Access to food is at an all-time high — and there is still no system for the part that comes after it arrives. You are the system. You stand in the aisle and try to remember what's in your own fridge.
The list is written from whatever you happen to recall standing in the kitchen. It is wrong before you leave the house.
The third jar of cumin isn't a discipline problem. It's a visibility problem. Nobody can see their own pantry from the store.
What you forgot you owned goes off behind what you bought instead. The waste is the receipt for the memory failure.
There is an enormous industry built around getting food into the home. There is almost nothing built for the six days it sits there.
Purchase is instrumented to the cent. Consumption is not instrumented at all.
Which means the single most decision-relevant fact in the household — what you have and how fast you're going through it — is the one fact nobody records.
Retail media is the fastest-growing ad channel in the world, and it is targeted almost entirely off purchase history — a lagging, fragmented, per-retailer guess at what a household wants. It can tell you someone bought a thing once. It cannot tell you whether they ate it, liked it, ran out of it, or replaced it.
One retailer's loyalty data sees one basket. The same household shops four other banners that retailer will never see.
Panel and scan data arrives aggregated and weeks late, with the household stripped out of it.
Everything downstream of the till is a model. Nobody is measuring the actual event — the food being used.
Both pains are the same missing dataset. The household can't see its own kitchen, and neither can anyone selling into it.
Purchase data is a lagging guess. Everyone measures the checkout. Nobody measures the pantry.
A purchase tells you a unit left a shelf. Consumption tells you it was wanted, used, and is about to be needed again. Only one of those predicts the next purchase.
You cannot buy this data. It only exists if a household voluntarily tells you what it has, every week, for free — which requires giving them something worth doing it for.
Agentic shopping is coming fast, and it will not work on fragmented purchase history. Whoever owns the consumption layer owns the agent's inputs.
Trepo is the operating system for the kitchen. It tracks what a household has, tells them what they can cook with it right now, and turns what's running out into the shopping list — on an app, with a countertop device for the households that want zero friction.

The habit is the product. Every job a household comes to Trepo for happens to be a job that writes to the graph — which is why the dataset grows without us ever asking anyone to "track" anything.




Retail media is the fastest-growing ad channel in the world and it is still being targeted off receipts.
A live consumption layer doesn't improve that market. It reprices it.
We beat our own forecast by 2.5x, a month ahead of schedule, with no paid acquisition engine behind it. Peak day: 3,033 active households against a pre-launch baseline of roughly 35.
And they use it. Signups are cheap — logged food isn't. Every number below is a household choosing to do work for us.
We don't think the size of the grocery industry tells you anything about us. The question that matters is whether one household is worth enough, and whether there are enough of them.
So: bottom-up, from a single kitchen. A household's annual grocery spend, the share of it that moves online where an agent can transact, and a 3% affiliate take on what we replenish.
Per-household spend, online share and household count below are structural placeholders. I'll pin each to a citable source (BLS food-at-home, Brick Meets Click eGrocery) before this leaves the building — the arithmetic is right, the inputs aren't signed off.
And that's the affiliate line alone — before the CPG data and retail-media revenue that arrives years earlier.
Name the real incumbent honestly: it isn't another app, it's the note on your phone and your own memory. Everything funded in this space clusters on one side of a single line.
Their data is a by-product of a transaction they own. Nobody logs their pantry into a checkout.
A daily reason to tell us what's in the house. That habit is the moat — it took a product, not a partnership.
Every log makes the next recommendation better, which makes the next log more likely. The graph is the flywheel.
Brands pay for what no panel can give them: household-level consumption on their category, across every banner their buyer shops. Already in market — our first partner one-pager went out on real portfolio data.
Once the graph knows the cadence, the list becomes an order. We take a share of a basket the household was always going to buy — with better timing than anyone else can offer.
Data revenue funds the household growth; household growth makes the data more valuable and the replenishment volume bigger. Neither line caps the other.
The device is not the business. It is the highest-fidelity acquisition and logging surface for households that want zero friction — and it pays for itself at point of sale.
Builds the thing. Hardware and software both — the Halo device, the firmware, the OTA pipeline, the ingestion backend and the Kitchen Graph itself are his. Previously Neuro and Tesla.
Need Matt's exact titles, dates and the two or three shipped accomplishments he wants named at Neuro and Tesla. I'm not inventing a bio for a diligence document.
Owns revenue, and has stood on both sides of the trade we're building. Retail media and advertising at Buyen; CPG sales and marketing leadership at USCAPE — the buyer of this data and the seller of the products it measures.
Need Zach's exact titles, dates and the accomplishments to name. The framing above is the argument; the credentials need to be his words.
The pairing is the point: this company needs someone who can ship a consumer hardware-and-AI product, and someone who already knows what a CPG brand will pay for the data it produces.
Growth is the line that's real today: 287 to 12,924 households, 2.5x past our own forecast, a month early. Revenue starts on the data side, where a partner conversation is already live, and the replenishment line turns on once the graph is dense enough to predict cadence.
A 24-month projection needs monthly burn and cash on hand, and I have neither. Give me both and the model gets built as a supporting document — which is where Icehouse says it belongs anyway, alongside the cap table, the hiring plan and a written investor FAQ. The deck slide stays this thin on purpose.
Data revenue booked to date, pipeline value, and the assumed month the replenishment take-rate switches on.
We're raising $X.XM on a $XXM cap SAFE to turn a working consumer product into the consumption layer that agentic shopping will have to run on.
Take the graph from thousands of kitchens to the density where cadence becomes predictable per category.
Ship the leg that turns a list into an order — the product step that unlocks the take-rate business.
Convert live CPG interest into contracted data revenue, so the second raise is priced off revenue, not story.