Twelve years at Caterpillar designing earthmoving equipment. Years running operational systems for commercial real estate. Pre-flight checklists every single time I get in a plane. Then I looked at my own kitchen and realized we were running it by memory and stress.
Every other system in my life had structure. Aviation has checklists for a reason — not because pilots are forgetful, but because a good system removes the chance to fail under pressure. Engineering is the same: you design the process so the right outcome is the default, not the lucky one.
But dinner? Dinner was improvised at 5pm with a tired brain and whatever was in the fridge. We bought food we never used, threw out leftovers we swore we'd eat, and somehow still ended up ordering takeout because nobody wanted to decide. It wasn't a willpower problem. It was a systems problem.
So I did the thing engineers do: I treated the week like a plan to be computed, not a series of decisions to be survived. Cook once, use it intentionally across a few days, let one prep session quietly carry the next three meals. Buy exactly what the week needs. The "magic" everyone talks about with meal planning isn't recipes — it's the routing. The way Sunday's cook becomes Monday's lunch and Tuesday's something-else.
That's what VectorMeals is. Not another wall of recipes. A planning engine that looks at your whole week and makes the meals work together — so you cook less, waste less, spend less, and still eat real food. The same pre-flight discipline, pointed at the one place in my life that never had it.
I'm building it solo and bootstrapped — no VC, no growth team, no ad agency. That's why the pricing is fair, the roadmap is honest, and I read every support email myself. It'll be rough around the edges sometimes. I'll fix things as I find them, and I'll tell you when I have.
If any of this sounds like your kitchen — welcome aboard.