Meal-first recognition
Explore the food itself instead of relying only on a branded product lookup. Estimates should remain transparent about uncertainty.
Core ideaThe story
A real-life frustration became a food-intelligence idea.
Nutri Eat-IQ began with a simple observation: food tracking can be awkward when the food you actually eat is not listed by its exact name. The ambition is to make understanding food feel more accessible, flexible, and useful.
Where it began
The problem was personal
While using a food tracker, the founder ran into missing entries for foods such as homemade coconut chutney made by a grandmother and customized dishes such as cheese Maggi. The issue was not that these foods were unusual — it was that a database-first workflow could struggle to represent them.
The everyday moment
“I ate it. Why can’t I log it?”
Family recipes, regional foods, toppings, and customized meals are part of normal life. Searching for an exact pre-listed entry can create friction or lead to a poor match.
The design question
What if we started with the meal?
That question inspired the Chat / Scan My Meal concept: start with the food itself, estimate with context, and offer similar-food matching when the exact item is not available.
The build journey
From calorie logging to food intelligence
The project has grown beyond the initial frustration into a broader platform concept.
Ingredient understanding
Help users understand labels, additives, allergens, and marketing language rather than just recording a number.
EducationAlternatives and comparisons
When an exact match is missing, use a close food match or compare options with relevant context.
Practical supportProgress and insights
Make reflection easier through weekly views, personal goals, and pattern awareness.
Habit supportChallenges and community
Use badges, missions, and shared learning to make food education more engaging.
EngagementHealth and wellbeing
Align the project with the broader ambition of supporting health literacy and informed everyday decisions.
PurposeWhat the project stands for
Build for the way people actually eat
Nutri Eat-IQ is being developed around three principles: be useful in everyday situations, explain information in plain language, and be honest about what an estimate can and cannot tell you.
01Start with real needs
02Make data understandable
03Keep the user in control
04Improve through iteration
Made in India
Created with local food realities in mind
India’s food culture includes family recipes, regional dishes, street food, home cooking, and countless variations. A useful food-intelligence experience should respect that variety while being clear that no system can infer every ingredient or quantity from a name or image alone.
Intelligence for Every Bite.
The goal is not to tell people what they are allowed to eat. It is to help them understand more about their options, ask better questions, and make choices that fit their own context.
Meet the founder
Paarth Gupta
Founder & builder of Nutri Eat-IQ
Nutri Eat-IQ grew from a real everyday frustration: when I tried to log homemade coconut chutney or customized cheese Maggi in a food tracker, the exact item was not always available. That experience pushed me to explore a more flexible, meal-first approach to food intelligence.
My goal is to make food information easier to explore — from estimated nutrition and ingredient explanations to similar-food matches and practical learning resources — while being transparent that estimates are not the same as laboratory measurements.
What I want Nutri Eat-IQ to solve
Make food information easier to access even when a meal is homemade, customized, or missing from a conventional food database.
How the idea keeps evolving
From meal identification to ingredient education, similar-food matching, weekly reflection, and interactive learning — the aim is to make food knowledge more usable, not overwhelming.
What matters when building it
Clarity over jargon, honest estimates over false precision, and tools that support user choice rather than shame or prescribe.