PortfolioTier 3 · Operations Engine
Case Study 03

Zidy. A meal subscription, run like a kitchen should be.

A Lilongwe meal subscription serving two very different customers: office workers who want lunch sorted, and parents who want their children fed properly at school. We built one system that onboards both, plans their week, and tells the kitchen exactly what to cook and where every plate is going.

Personalised OnboardingSubscription & Billing EngineWeekly Meal PlannerKitchen & Delivery Operations
2
customer types, one system
16
step guided onboarding
6
live meal statuses
7
location types managed
11
admin operations views
0
spreadsheets needed
The Brief

A meal subscription lives or dies on what happens at 6am in the kitchen.

Selling a lunch plan is the easy part. The hard part is knowing, every single morning, how many plates of which meal to cook, which school or office each one goes to, who has skipped today, and which child cannot eat nuts. Zidy needed a customer experience simple enough for a busy parent and an operations engine strong enough to run a kitchen without a spreadsheet.

What existed before

A strong idea with no system behind it. Orders, dietary needs, delivery points and payments would all have lived in WhatsApp chats and memory, which breaks the moment you pass a few dozen customers.

What we were asked to build

A customer app that learns each person's routine and tastes, then plans their week for them, and an admin console that turns every active subscription into a daily production list grouped by meal, delivery cluster and location.

The Approach

Two systems, built to work as one.

PART ONE

Onboarding & Personalisation

A guided signup that splits into two paths, captures what each customer actually eats, and recommends the right plan before asking for payment.

PART TWO

Weekly Planner + Kitchen Operations

The customer's week on one side, and on the other, a production board that tells the kitchen what to make, how many and where it is going.

Part One

Two customers, two paths, one signup.

An office worker ordering for themselves and a parent ordering for a child need completely different questions. The onboarding asks who you are ordering for first, then only asks what matters for that person.

Guided Onboarding

The first question decides every question after it.

Choose yourself and the flow asks about your workday, where you will be at lunch and how much control you want over the menu. Choose a child and it asks for their name, school and what they will and will not eat. Nobody answers a question that does not apply to them.

  • Separate flows for workers, students and parents
  • Allergies, dislikes, protein, starch and spice level captured once
  • Progress bar and back button on every step, so nobody feels lost
Onboarding: who are you ordering for
Onboarding, two paths for workers and parents
Onboarding: food preferences step
Food preferences, captured once
Plan Recommendation

The system recommends the plan, the customer just agrees.

Once the profile is saved, every active plan is ranked against the customer's goals, routine and budget, and the best fit is shown first with the reason it was chosen. Checkout opens straight from that screen, so the decision and the payment happen in the same moment.

Onboarding: ranked plan recommendation
Plans ranked against the customer's profile
Part Two

The customer sees their week. The kitchen sees its morning.

Every subscription becomes a week of scheduled meals. Customers can change any day, and every change flows straight into what the kitchen sees for that date.

Customer Home

Open the app and today's meal is already there.

The home screen greets the customer by name and shows today's meal, where it is being delivered and its live status. Parents see the same thing for whichever child they have selected, with copy written for them rather than for an office worker.

Customer home: today's snapshot
Home, today's meal at a glance
Your Week

Every meal tracked from the kitchen to the desk.

Each day moves through scheduled, preparing, packed, on the way and delivered, so a parent knows lunch reached school without having to call anyone. Tapping a day lets the customer swap the meal, skip the day or lock it in, and the next week is one tap away.

  • Live status for every meal of the week
  • Swap, skip or confirm any day before the kitchen cut-off
  • Holidays and non-service days never count as missed meals
Your Week: daily meals and status
Your Week, every day tracked from kitchen to desk
Meal detail: swap, skip or confirm
Swap, skip or confirm any day
Parents & Subscriptions

One parent, several children, no confusion.

A parent can run separate plans for each child from one account and switch between them at the top of any screen. Subscriptions can be paused for a trip or a school break with paid meals preserved, then resumed whenever they are ready.

Parent view: switching between children
One account, several children
Subscription: pause and resume
Pause without losing paid meals
The Production Board

What to cook, how many, and where it is going.

Pick a date and the admin sees the exact number of meals to produce, broken down by dish, delivery cluster, city, school or office, and customer type. A whole day or a single dish can be moved to preparing, packed or dispatched in one action, and customers see that update on their phones.

  • Daily totals grouped by meal and delivery cluster
  • Exceptions flagged before they become missed lunches
  • One status change updates every affected customer
Admin: production board
Production, what to cook and where it goes
Locations & Service Calendar

Schools, campuses and offices, organised by delivery route.

Every delivery point belongs to a city and a delivery cluster, so routes are planned around real geography. Parents can request a school that is not on the list yet, and public holidays are set once as non-service days for a whole city or cluster.

Admin: locations and delivery clusters
Cities, clusters, schools and offices
Plans, Meals & Subscriptions

The whole catalogue and every customer, managed in one place.

Meal plans, the dish catalogue and every subscription live in the same console. Each subscription shows whether it is pending payment, active, paused or needs attention, and supports weekly, monthly or employer-sponsored billing.

Admin: subscriptions list
Every subscription and its status
Admin: meal catalogue
Meal catalogue
The Result

A subscription business that can grow past the founder's memory.

Every meal, customer, child, school and payment is a tracked record, so the operation scales by adding customers rather than adding chaos.

2
Customer journeys
6
Meal statuses, live
7
Location types
11
Admin views
Tier 3 · Operations Engine

This is what we build when the business runs every single day.

Zidy did not need a menu page. It needed a system where a parent signs up once and never worries about lunch again, and a kitchen that knows its morning before the first pot goes on. That is the same Tier 3 thinking we would bring to your business.

NewGen Marketing · Case Study 03