About
Echelon Foundry, applied to foodservice.
Culinary is a practice within Echelon Foundry: the same systems thinking, software depth, and demand for evidence—brought to the workflows and decisions that shape foodservice.
Founder & principal consultant
Kevin Miller
Founder & Principal Consultant, Echelon Foundry
AI · Software Engineering · Foodservice Technology
A technologist with deep culinary grounding—and a practice built to connect operating reality to technical decisions.
Kevin brings more than 25 years of software engineering and technical leadership experience across architecture, modernization, AI systems, delivery, and decision frameworks.
His culinary grounding comes from more than 40 years of cooking, Indiana State Fair culinary competition in categories including dips and brownies, catering experience, chocolatier work, and extensive informal study. That study has included Culinary Institute of America educational material and instruction from chefs trained at Le Cordon Bleu, in France, and in professional catering environments.
A precise claim
Culinary fluency is not restaurant-operator theater.
Kevin does not claim restaurant employment or operator experience. His role is to bring unusual technical depth to foodservice while understanding enough of the environment to ask better questions, observe the work carefully, and avoid designing from abstraction alone.
Architecture, modernization, software development, AI systems, integrations, technical assessment, reliability, and state-system research.
Four decades of practice, competition, catering, chocolatier work, and continuing informal culinary education.
The broader Echelon team adds restaurant, culinary demonstration, accessibility, and James Beard scholarship experience.
The combination
Domain fluency. Decision discipline. Engineering capability.
Culinary grounding
Enough fluency to recognize that service pressure, physical work, timing, accessibility, and exceptions change what a good system looks like.
Clarity
A disciplined way to separate the problem from the proposed solution and choose a proportionate next move.
Engineering depth
The ability to assess, advise, architect, modernize, integrate, and build when implementation is the evidence-backed answer.
Working principles
What guides the practice.
- Diagnosis before prescription.
- Do not choose a tool before locating the mechanism that produces the problem.
- Operational fit over feature count.
- A system is useful only when it works for the people, timing, constraints, and exceptions around it.
- Evidence before momentum.
- Make value, risk, uncertainty, and stopping conditions visible before scaling.
- Build only when building is earned.
- Custom software is a capability, not a predetermined recommendation.
Bring us a problem
You do not need to know whether the answer is AI.
The first job is to understand the operating problem well enough to choose a proportionate next move.
Discuss a foodservice problem