Hello Chef

What the company appears to be: Hello Chef is a mobile cooking app built around an AI assistant named Chefie, designed to help users plan meals, find recipes, and cook with conversational interaction. The app allows users to speak naturally to Chefie, who can suggest recipes, adjust ingredients, create meal plans, and guide users through cooking steps.

What changed: This is a self-reported project from a single developer (Justin Solitro) that has evolved from an idea sparked by ChatGPT into a functional prototype. The author states it was built over several years of ideation and development, with recent work involving AI tooling and structured implementation.

The single most important open question: Is there evidence of actual user adoption or traction beyond the developer's personal use? The description contains no data on users, revenue, customers, or market validation — only self-reported claims about functionality and experience.

Note: This analysis is based entirely on the author's own description. No external verification, historical data, or third-party sources are available. All findings reflect what the author states, not necessarily what is true.

The description states that Hello Chef is a mobile cooking app built around an AI sous chef named Chefie. Users interact with Chefie via voice or text to get recipe suggestions, adjust ingredients, create meal plans, and follow guided cooking steps.

• The app supports three ways to add recipes: conversational interaction with Chefie, structured prompts, or manual entry.
• It includes features like pantry management, meal planning, shopping list generation, and cookbook organization.
• Recipes can be saved, shared, favorited, and organized into cookbooks.
• There is a social component including chef profiles, attribution of adaptations, follows, and public/private cookbooks.

Inference: The app appears to be a hybrid between AI-powered recipe assistant and community-driven cooking platform. However, the description does not confirm if these features are fully implemented or tested with users beyond the developer.

The author positions Hello Chef as an "AI sous chef" that helps users navigate the kitchen from idea to execution — including meal planning, substitutions, and guided cooking.

• The tagline “Your AI sous chef!” reinforces this positioning.
• The app is described as a companion for home cooks who want to learn new techniques or simplify their cooking process.
• It emphasizes conversational interaction and integration with real-world tasks like pantry updates and shopping lists.

Claim: The author claims the app was built using AI tools such as ChatGPT and Codex, and that it integrates OpenAI's API for structured tool calls.

Inference: The positioning evolved from a personal experiment to a functional prototype aimed at improving everyday cooking experiences.

The description does not explicitly define target customers or ideal customer profiles (ICP).

• The author describes the app as useful for home cooks who want to learn and simplify their cooking.
• It targets people interested in meal planning, recipe discovery, and guided cooking.
• There is no mention of specific demographics, usage frequency, or behavioral segmentation.

Not evidenced: No clear indication of who uses or would use this product beyond the author’s personal experience.

There is no evidence provided about a business model or pricing strategy.

• The description does not mention monetization methods, subscriptions, freemium tiers, or any commercial structure.
• Features like meal planning, recipe creation, and social sharing are described but without financial implications.

Not evidenced: No information on how the product will generate revenue or be sold.

The app is built using modern web and mobile technologies:

• Mobile frontend: React Native with Expo
• Backend: Next.js + TypeScript
• Database: PostgreSQL via Prisma ORM
• AI integration: OpenAI API with typed tools for recipe search, creation, and editing
• Streaming responses: WebSockets for real-time updates during recipe generation
• Image handling: Inngest job queue for background image generation

Claim: The author built the app manually in Nest.js before switching to a more structured approach using AI tools like Codex.

Inference: Technical architecture suggests a scalable, modern stack suitable for mobile and backend services.

There is no evidence of traction or user adoption beyond the developer’s personal use.

• The author mentions building it over several years and testing it during Build Week.
• It has been submitted to an OpenAI hackathon (Devpost).
• There are no references to users, downloads, retention metrics, or revenue.

Not evidenced: No data on actual usage, customer base, or performance indicators.

The description does not reference competitors or market positioning relative to existing cooking apps or AI assistants.

• The author notes that traditional recipe sites don’t offer the same level of interaction or substitution learning.
• It is implied that the app offers a conversational interface and AI-driven personalization not found in typical apps.

Not evidenced: No competitive landscape analysis, pricing comparison, or differentiation from existing solutions.

Several risks are implied by the self-reported nature of the project:

• Lack of validation: The app exists only as a developer prototype; no evidence of real-world usage or feedback.
• Single-person development: With only one team member, scalability and long-term maintenance may be concerns.
• Unverified AI integration: While tools like OpenAI are mentioned, there is no clarity on how they are implemented or whether they function reliably in production.
• Social features risk: The social elements (profiles, attribution, sharing) could introduce complexity without clear user incentives.

Inference: Without external validation, the product may not meet market needs or be viable at scale.

1. What specific problems do users face that Hello Chef solves?
2. How many people are currently using the app beyond yourself?
3. Have you conducted any user testing or gathered feedback from actual home cooks?
4. What is your plan for monetization and scaling beyond a single developer?
5. Can you demonstrate how Chefie handles edge cases like conflicting dietary restrictions or recipe conflicts?
6. Are there plans to integrate with grocery delivery services or smart kitchen devices?