Designed for Trial Angle light + dark mode
Keepchin: turning everyday food behaviour into a connected product system.
This lesson breaks down how Keepchin works, why it exists, and how its individual components connect into one coherent platform. The central lesson is not simply about building a food website. It is about learning how a builder can begin with an ordinary human problem, structure it into useful behaviours, and then create an ecosystem around those behaviours.
Keepchin is not trying to solve “food” as one giant problem.
The platform starts from a more practical observation: modern life has made food decisions fragmented. People buy food in one place, track fitness somewhere else, learn recipes elsewhere, forget what is in the fridge, overspend on groceries, order convenience food impulsively and often have no single place that helps them connect all of those decisions.
Doom scrolling and the attention economy can make eating more reactive. Remote work can remove the natural movement and meal rhythms that came with commuting. Exercise goals can exist independently from what someone actually eats. Household budgeting can be separated from grocery prices. People may want to cook but not have the time to shop. Others can shop but need someone to prepare a meal. A business may need food for staff. A family may need an event cook. A person may simply need to know what to make with the ingredients already sitting at home.
A strong product does not begin with features. It begins by identifying a repeated human friction that can be organised better.
Eating, shopping, budgeting, cooking, learning and fitness are often handled separately.
People often do not know what they have, what they are spending or what is running low.
When attention is stretched, the easiest available food decision tends to win.
Sellers, cooks, shoppers, restaurants and couriers exist, but the user’s need is rarely coordinated end-to-end.
Separate the problem from the solution.
- Write down one repeated behaviour your audience struggles to organise.
- List the tools or people they currently use to solve fragments of it.
- Ask what becomes possible if those fragments are connected.
The purpose is to help people build a better relationship with food.
Keepchin’s main product is the personal food-life experience. Commerce exists to support that experience, not to replace it.
A member should gradually be able to answer five practical questions from one place: What am I trying to achieve? What do I have? What have I eaten? What do I need? Who or what can help me next?
This positioning changes the product from a conventional food marketplace into something closer to a food-life operating system. The user’s goals and daily reality become the organising layer; recipes, groceries, restaurants, cooks and services become actions that can be recommended when relevant.
Four connected systems make the platform understandable.
| System | Function | Why it matters |
|---|---|---|
| My Keepchin / Food Avatar | Goals, routines, food habits, kitchen, meals, progress and personal intelligence. | This is the centre of the product and the main reason for repeat use. |
| Keepchin Market | Ingredients, prepared food, restaurant ordering and grocery price comparison. | Turns insight into purchase action. |
| Keepchin Learn | Recipes, cooking knowledge and healthy-living education. | Improves capability instead of making the user permanently dependent on ordering. |
| Keepchin Services | Shop For Me, cooks, event cooking, corporate cooking, shoppers and couriers. | Solves the execution gap when the user cannot or does not want to do everything personally. |
When a product has many features, organise them into a small number of mental models. Users should understand the system before they understand every feature.
The Avatar converts a generic website into a personal system.
The Avatar is not intended to be a cartoon profile. It is a structured representation of the member’s food goals, preferences, routines and context.
What the Avatar can know
Eat better, stay fit, support athletic activity, manage weight, improve cooking, spend less or organise meals.
Preferred cuisines, foods enjoyed, foods avoided, cooking ability and household size.
Typical breakfast, lunch, dinner and workout times.
Usual location and personal weekly food budget.
Once these parameters exist, Keepchin can stop showing the same homepage to everyone. The platform can prioritise different information depending on the member’s context.
The kitchen inventory turns food already owned into usable information.
Members can record items in their fridge, freezer and pantry, including quantity and expiry information. This sounds simple, but it creates one of Keepchin’s most powerful bridges: inventory → meal idea → missing ingredients → purchase or service.
Example behaviour
If a member has rice, tomatoes, onions and eggs, Keepchin can recognise recipes that use those ingredients, rank meals that require fewer missing items and highlight food that should be used soon. A low-stock item can be moved to the grocery list. Missing ingredients can lead to grocery-price comparison. If the member does not want to cook, the same intent can lead to a restaurant or Cook.
The same data can create several forms of value. “Tomatoes are running low” is simultaneously a household insight, a shopping trigger, a budgeting event and a marketplace opportunity.
Planning converts intention into a repeatable routine.
Goals are weak when they remain abstract. Keepchin gives them operational form through meal planning, food logging, budget tracking, activity logs, reminders and progress signals.
Plan breakfast, lunch, dinner and snacks across a week, using recipes or custom meals.
Record what was actually eaten and distinguish between intention and behaviour.
Compare weekly spending with the member’s chosen budget and track major food-spend categories.
Show consistency in logging, planned meals, home cooking and activity without pretending to provide a medical health score.
The key product decision here is that Keepchin should encourage awareness and consistency, not create a misleading numerical judgement about whether a person is “healthy.” The system can organise behaviour while keeping clinical or highly individualised medical advice outside the product’s automatic claims.
Commerce appears when the user’s next action requires it.
Keepchin supports ingredient sellers, prepared-food sellers and restaurants, but the marketplace is strongest when it connects naturally to a user’s food-life context.
This creates a more credible marketplace proposition: Keepchin does not have to manufacture demand. The personal product can reveal demand that already exists.
Keepchin coordinates people, not only products.
Some food problems cannot be solved with a product catalogue. They require a person to perform work. Keepchin therefore supports provider roles within one account.
| Role | What they do | Typical user need |
|---|---|---|
| Seller | Sells ingredients or prepared food. | “I need to buy this.” |
| Cook | Personal cooking, event cooking, corporate cooking, classes or meal preparation. | “I need someone to prepare this.” |
| Shopper | Buys items from the member’s grocery list on their behalf. | “I want to cook, but I cannot shop.” |
| Courier | Moves completed shopping or orders to the member. | “I need the goods delivered.” |
| Restaurant | Publishes menus and accepts orders. | “I want a ready meal.” |
One person can operate as a Buyer, Seller, Cook, Shopper or Courier without needing separate accounts. This matters in markets where economic roles are fluid and people can participate in more than one side of a marketplace.
A workflow becomes a business when value can move through it.
Keepchin’s transactional layer connects quotations, deposits, balances, restaurant ordering, delivery fees, shopper proofs, ratings and notifications.
Example: event cooking
A similar logic applies to Shop For Me: request → Shopper assignment → purchase → proof/receipt → courier → delivery → review. The product is valuable because the workflow remains visible from beginning to end.
Intelligence should connect context to the next useful action.
The Food Avatar engine is useful when it reduces decision friction. It does not need to “think” magically. It needs to combine signals in a disciplined way.
Prioritise meals that use ingredients already at home.
Move recipes forward when they use food that should be consumed soon.
Consider estimated meal cost against the member’s chosen weekly budget.
Exclude explicitly avoided ingredients and prioritise relevant cuisines or goals.
Surface nearby or relevant sellers, restaurants and approved providers.
Use plans, logs and completed actions to make the daily interface more relevant.
This is a lesson in business creativity, not only product development.
Within 500 STEAM, Keepchin can be used to demonstrate how a builder turns imagination into a structured offering. The idea begins broad—food, wellbeing, shopping, cooking, budgeting, providers—and becomes credible only when each part is given a role inside a coherent system.
| Builder question | Keepchin answer | Why it matters |
|---|---|---|
| What problem is worth organising? | Fragmented food decisions and routines. | Creates a human reason for the product to exist. |
| What is the centre? | The member’s Food Avatar and daily food life. | Prevents the marketplace from becoming the whole identity. |
| How does value compound? | Kitchen data informs meals; meals inform groceries; groceries inform commerce and services. | One action strengthens several parts of the system. |
| How can supply join? | Sellers, Cooks, Shoppers, Couriers and Restaurants. | Creates an ecosystem instead of a single-purpose tool. |
| How can it make money? | Transactions, commissions, bookings, delivery, subscriptions or business services can eventually sit on top of demonstrated utility. | Monetisation follows useful behaviour. |
| How does it remain credible? | Moderated providers, transaction-gated reviews, clear boundaries around health claims and visible workflows. | Trust is designed into the product. |
Business creativity is the act of combining imagination, human behaviour, technology, operations and commercial logic into an offering people can understand and use.
What another African builder should learn from this prototype.
Map your own “Keepchin moment.”
- Name one ordinary activity your audience repeats every week.
- Identify the information they need before making a decision.
- Identify the people, products or services required after that decision.
- Design one dashboard that connects the “before” information to the “after” action.
- Ask which part should remain free utility and which part could become a credible commercial transaction.
The real product lesson
Keepchin is valuable as a 500 STEAM case study because it shows that a builder does not need to begin with perfect technology. The first responsibility is to make sense of the problem, define the human outcome, arrange the parts into a credible system and keep improving the prototype until the offering becomes viable, useful and commercially understandable.
Review the lesson ↑