One person, one kitchen, one very patient AI.
ChefVault has no co-founder. There is no seed round. There is no
"team of fifteen across three time zones." There is one
multi-hyphenate, one Apple Silicon laptop, and a Claude window
that has been open for the better part of a year. That is the
entire roster.
The stack is React Native and Expo for the apps, WatermelonDB
for the offline-first sync layer, a Node/Postgres backbone, and
roughly eleven thousand lines of TypeScript that David wrote
himself — sometimes between sets, sometimes during a quick break
in the wings, mostly at the kitchen island after the shows when
the rest of the country was asleep. The first working build of
the dual-measurement engine was finished on a red-eye out of
McCarran. The hydration calculator was finished on a kitchen
counter in a Hampton Inn at 4 a.m. The recipe scraper was
finished, fittingly, in a hotel buffet.
People ask, sometimes a little suspiciously, "how is one person
building this?" The honest answer is the AI. Not the AI doing
the engineering — the engineering is the founder's, the
decisions are the founder's, the taste is the founder's — but
the AI as a tireless pair, the AI as the rubber duck that
answers back, the AI as the patient junior who never sighs when
you ask it to refactor the unit-conversion table for the eighth
time. That is the unfair advantage of building in 2024. One
person with taste, an AI with stamina, and a problem worth
solving can ship the thing.
The thing they shipped is ChefVault. It runs on iOS, Android,
and the web. It stores ingredients as both grams and volume.
It calculates baker's hydration the second you add water. It
scales recipes in fractions. It imports from any URL on the
open web. It works on a plane with no signal. It costs less
than the price of a single bag of bread flour per month, and
the founder writes every release note himself in a hotel
somewhere — usually after the show, usually with a sourdough
on the second bulk, usually still in the suit.