Devpost Shipyard Creator Contest - Haus Chef Written Proposal

Problem

Home cooks juggle recipes and planning across too many places: social media posts, web pages, notes apps, and shared documents. That fragmentation creates repeated work and inconsistent results:

Recipes are hard to capture and standardize.
Meal planning happens in a separate tool, so it never stays in sync.
Grocery lists are rebuilt manually every week.

This wastes time and makes cooking feel harder than it should.

Target Audience

Primary users are busy home cooks and households who want a simple, unified flow from “I found a recipe” to “I have a plan and a list.”

Key profiles:

Individuals saving recipes from TikTok, YouTube, and blogs.
Families coordinating meal plans and groceries.
People who want repeatable weekly planning without extra admin.

Solution Overview

Huas Chef unifies the core workflow into a single app:

Import a recipe from any URL.
Convert it into structured data.
Plan meals for the week.
Generate a grocery list automatically.

The recipe becomes the source of truth. Planning and grocery lists are derived from it, so the data stays consistent without extra steps.

Product Flow

Capture: Paste a URL or add manually.
Structure: Ingredients and steps are extracted and cleaned.
Plan: Add recipes to a weekly meal plan.
Shop: Generate a list based on the plan, deduplicated and organized.

This replaces three separate tools with one continuous flow.

Monetization Strategy

The cost driver is recipe importing, which requires scraping and compute. That makes it the most logical paid feature.

Model:

Free tier: manual entry + limited imports.
Pro tier: higher import limits + advanced tools.

RevenueCat powers subscriptions so monetization can scale without rewriting core logic.