Vegan Cook - Straightforward Vegan Recipes
The problem
Cooking plant-based with an allergy takes more effort than it should. Many vegan recipe sites label recipes as gluten-free, nut-free, or soy-free, but those labels only cover part of the allergy or dietary restriction spectrum. Peanuts and tree nuts are usually grouped together, sulphites are not usually tracked, and some general recipe sites mix vegan and non-vegan recipes. So a reader still has to check every dish to make sure the dish adheres to their dietary needs. Time is the other constraint, since most people cooking on a weeknight want something they can make within 30 minutes.
User persona
Vegan Cook is built for home cooks around the world who cook plant-based and are short on time. My goal is for recipes to be completed within 30 minutes.
The site serves three groups in particular:
-
People with an allergy, who need to know exactly what is in a dish before they cook it
-
People who have chosen a vegan diet for ethical, environmental, or health reasons
-
People cooking for someone they love who is vegan, and who may not know vegan cooking well themselves
Why build Vegan Cook
I am vegan with a dairy allergy, so I read every label before I cook. I wanted a recipe site that was clean and fast, needed no login, no distracting ads, and treated allergen information as seriously as the recipe itself.
Standing out in a crowded market
When I looked closely at the market, I found that my original assumption did not hold. I had expected established vegan recipe sites to handle allergens poorly, but several of them already label their recipes. Vegan Richa marks recipes as gluten-free, nut-free, or soy-free, Minimalist Baker groups its recipes into gluten-free and soy-free collections, and Forks Meal Planner, a paid service, adjusts its meal plans for nuts, gluten, and soy.
Explaining Indian ingredients for a global audience is also something other sites already do. Labelling alone would not be enough to stand out. The gap that remains is narrower. Competitors group peanuts and tree nuts together, none of the sites I reviewed track sulphites, and a label only tells a reader what to avoid. It does not help them cook a dish safely if it contains something they cannot eat.
Based on this, I am making two bets.
-
The first is to go deeper on allergies than a label. Readers will be able to combine exclusions, such as no peanut and no soy in under 30 minutes. Each recipe will carry substitution notes for the allergens it contains and clear warnings where cross-contamination is a risk.
-
The second, for India, is to build recipes around quick-commerce delivery apps. A recipe that uses only ingredients available on an app such as First Club, and that can be cooked in 30 minutes, makes a simple promise: order the ingredients and have dinner on the table within the hour. None of the competitors I found are built around this, and it ties directly into the growth plan.
Scoping the MVP
My first version of the idea included a login with two-factor authentication, sign-in with Google and Apple, favourite recipes, a reward system with points and a leaderboard for submitting recipes, and a map of vegan places nearby. As I built it, I narrowed the scope to what mattered most for the persona: reliable recipes with clear allergen information. Everything else either moved to the roadmap or was dropped, and readers do not need an account to use the site.
MVP feature set
-
Allergen labelling on every recipe: Each recipe declares which of five tracked allergens it contains: sulphite, peanut, soy, gluten, and tree nuts. A notes field covers cases that need a word of caution, such as shared equipment or an ingredient outside the five. This feature is the foundation for the deeper allergy support on the roadmap.
-
Filters: Users can narrow the collection by allergen, skill level, cuisine, meal type, and spice level, so they only see what is safe and suitable for them. This feature is critical for a simple user experience.
-
Recipe of the day: The home page features a rotating recipe drawn from the full collection. Having this feature helps create stickiness in users and compels them to come back.
-
Journal: Longer posts on plant-based cooking, such as which cooking oil suits which dish, which rice suits which dish, and dairy alternatives. Having a journal was important for me to document my journey and I debated a lot on whether this truly is an MVP. However, since I had the content already, I decided to add it as part of the MVP.
-
Recipe submissions: Readers can submit their own recipes. Every submission is checked for animal-derived ingredients in the browser and again on the server, and then reviewed by hand before it is published. The effort to have the feature is worth it since it can help grow the content library. There are guardrails to ensure the quality of submission is up to the mark and the site content is not diluted.
-
Weekly newsletter: Subscribers receive a weekly issue of recipes through an automated email pipeline. This is an MVP feature since this helps create the pipeline of early adopters or users.
-
No login and no ads for readers: Readers can browse the site without distracting ads or the need to log in or sign up. Due to the privacy focus and need to stand out amongst competition, this feature is essential.
Although I wanted photos to be part of the MVP, I launched without photos so I could focus on recipe quality and allergen accuracy, and I plan on adding my own photography in the future.
Content decisions
A recipe site is only as good as its recipes, so I spent as much time on content as on the product. I reviewed every published recipe and removed one restaurant-level dish that did not suit a home cook. Since many of the recipes are Indian, I added short explanations for ingredients and techniques that readers outside India may not know, such as jeera (cumin seeds) and tempering spices in hot oil. I also standardised the site to British English, with American terms in brackets, such as aubergine (eggplant) and coriander (cilantro).
Security and privacy
I ran a full security review of the site. Admin access is restricted by role and enforced on the server, database access is controlled through row-level security, and the secret database key never leaves the server. Recipe submissions and newsletter sign-ups are rate limited to prevent abuse. Before making the code repository public, I confirmed that no subscriber data was stored anywhere in the code.
Launch
Vegan Cook is live at vegancook.live, with 52 recipes across 11 cuisines and six journal posts. I built the site with Lovable, and handled the security review, content review, and newsletter testing myself.
Roadmap
-
Grow the collection to at least 200 recipes, with at least 30 each for breakfast, lunch, and dinner
-
Keep new recipes within 30 minutes, and bring existing recipes within that limit where the dish allows it
-
Add filters that combine allergen exclusions with cooking time
-
Add substitution notes for each allergen a recipe contains, along with cross-contamination warnings
-
Build recipe collections around ingredients available on quick-commerce apps in India
-
Add my own photography to the recipes
-
Grow the audience through the growth plan below
-
Set up email domain authentication so the newsletter reliably reaches inboxes
-
Add collection pages for lunch, dinner, and snacks, to match the existing breakfast page
Growth plan
The site has a solid base of content, so the next step is to grow its audience. The audience is worldwide, but I am starting in India, where I have a network and where quick-commerce apps make the ingredient partnerships possible.
I plan to grow in three stages -
-
Influencers in India: I will partner with food influencers in India, who will cook recipes from Vegan Cook live and share them on Instagram. This brings the recipes to people who already follow vegan and healthy cooking.
-
Health-conscious delivery apps: I will partner with delivery apps that focus on healthy food, such as First Club, to send joint newsletters as special editions. Each edition will use only ingredients available on that app, so readers can order everything they need for the recipe in one place.
-
Food brands: I will partner with food brands to show how their ingredients fit into a healthy diet, using recipes from Vegan Cook. Partner content will always be clearly labelled, and every recipe will carry the same allergen labelling as the rest of the site.
Metrics
-
Page views
-
Newsletter subscribers
-
Returning visitors