Now taking the first pilot kitchens in the Greater Toronto Area
Run your tiffin kitchen from one screen.
Tifflo turns your subscriber list into tonight's cook list, tomorrow's packing list, and a prepaid meal balance that can't drift. Your customers keep messaging you on WhatsApp — nothing changes for them.
- Tonight's cook list, dish by dish
- Tomorrow's packing list, name by name
- Meals left, not a dollar balance
Free during the pilot · No card · We set your kitchen up with you, by hand.
Built for owner-operated tiffin kitchens · 20–100 standing subscribers · Greater Toronto Area
Everything you need to know before you start cooking.
Who's subscribed, how many meals go out today, what came in this month, and who's about to run out — on one screen, in your kitchen's own timezone.
Real layout. Sample kitchen. Made-up numbers.
Right now the answer lives in three places.
The WhatsApp thread
Who asked to skip Thursday, who switched to veg, who said they'd pay Friday. It's all there — somewhere above three hundred other messages.
The notebook
Names, plans, what's paid. Accurate, and readable by exactly one person. If you're ill on Wednesday, the kitchen stops.
The arithmetic
How many plates of fish curry tomorrow. Who's nearly out of meals. Whether this month is better than last. Redone by hand, every week.
None of it is wrong. It's just that only you can read it — and it has to be redone tomorrow.
Generate. Cook. Pack. Done by nine.
One button in the evening, two printed lists in the morning. The same loop every day, whether you have twenty subscribers or a hundred.
Press generate, get a cook list
Tifflo reads every active subscription against your menu rotation and works out what tomorrow actually needs — not plates, portions. Twelve fish curry, nine chana masala. Safe to run more than once, and it never generates a meal the customer's balance can't pay for.
Pack against a list with names on it
In the morning it's one card per customer: the address, the plan, how many meals they have left, and the exact dishes going in that bag. Tap deliver as each one goes out — or mark the whole day at once. A skip costs the customer nothing.
Add a customer mid-week without doing maths
Someone starts on a Wednesday. Tifflo quotes the part-week before you commit — six of ten meals, starting Wed 13 August — and creates the subscription, the wallet and the first credits in one go. Terms line up on a calendar boundary, so the whole kitchen renews together.
New subscription
Part week — 6 of 10 meals
$30.00 today, then the full week from Mon 18 Aug.
The wallet counts meals, not money.
A tiffin service sells coupon books, not a dollar balance. So Tifflo stores what the customer actually bought — ten meals, twenty meals — and spends exactly one when you deliver one.
A skip costs nothing
The credit doesn't burn, it just waits. Nobody argues about a Thursday they didn't eat.
A pause loses nothing
Someone travels for three weeks and comes back with exactly the meals they paid for.
No rounding drift
Every meal costs exactly one credit. No per-meal rate, no fractions of a dollar going missing over a month.
It can't go negative
Orders are never generated for meals a wallet can't fund, so unpaid food never hides inside your numbers.
Every payment, delivery, skip, refund and correction writes a permanent, dated row with a reason on it. The balance can never disagree with its own history.
Everything else the kitchen needs.
The morning glance
Active subscribers, meals today, cash collected this month against the same point last month, and who's running low.
Rotating menu cycles
Build a four- or five-week rotation once. Loop it forever from an anchor date, or date it and swap the menu monthly.
Plans and pro-rating
Pricing tiers, delivery days, meals per day. Start someone mid-week and the quote pro-rates itself before you commit.
Dishes your way
A reusable dish catalogue with dietary tags, optional swap pricing, and macros for the plans that track them.
Your kitchen's clock
Your timezone, how many days ahead you cook, what time prep starts, and your own meal periods — not Lunch and Dinner if you don't use them.
Printable lists
The cook list and the packing list print clean, so the person at the stove doesn't need a login or a phone.
We started with the hardest part.
Most tools in this space began on the road — routes, drivers, tracking — and added meal subscriptions on top. Tifflo began at the other end, with the menu rotation and a wallet that counts meals instead of money. That's the part you can't retrofit later, and everything else is being built on top of it.
Live today, in real kitchens
- Subscriber and subscription management, with pause, resume and cancel
- Rotating menu cycles — a four- or five-week loop, or a dated monthly menu
- Daily cook lists with per-dish portion counts, ready to print
- Packing lists with each customer's address and exact dishes
- A prepaid meal-credit wallet with a permanent, dated ledger
- Pro-rated mid-week starts, quoted before you commit
What's coming next
In build order: driver logins and a driver view, WhatsApp notifications, scheduled order generation, and then route planning.
Tifflo is on its way to covering the whole tiffin operation, not just the kitchen end of it.
Pilot kitchens set the order. If routing is what would change your week most, say so when you apply — that's how this list gets sequenced.
Free during the pilot.
Pilot kitchens use Tifflo free while it's built around how they actually work — every feature, no tier gating, for as long as the pilot runs. When there is a price, you'll hear it from me before anyone else, and you'll agree to it before anything changes.
- Every feature on this page, with no tier gating
- Your kitchen set up by hand, with your real plans and balances
- A direct line to the person building it
- A say in what gets built next
What happens after you apply.
- 1
You send the form
Six fields, about sixty seconds. Your name, your kitchen, where you deliver and roughly how many subscribers you have.
- 2
We talk for twenty minutes
Your plans, your menu rotation, and how you track who's paid today. I'll show you exactly how your kitchen would run on it, and answer anything about what's live now versus what's coming.
- 3
I set your kitchen up and switch it on
Usually within one to two business days. Your dishes, plans, cycle and every subscriber's meal balance go in with me — at a cycle boundary, not mid-cycle, so nobody's count is ambiguous on day one.
Questions worth asking.
How is this different from the delivery apps?
Most tools in this space started with the road — routes, drivers, tracking, labels — and added meal subscriptions on top. Tifflo started at the other end, with the part that's hardest to retrofit: the menu rotation and a wallet that counts meals rather than money. That's why the cook list knows it needs twelve fish curry, and why a skip costs your customer nothing. The delivery side is being built on top of that foundation.
Do you do routes, a driver app, or WhatsApp notifications?
Not yet — they're what's being built next, in that rough order: driver logins and a driver view, then WhatsApp notifications, then scheduled order generation, then route planning. Today deliveries are marked by whoever has the packing list, and you message customers yourself. Pilot kitchens have a real say in the order, so if routing is what would change your week most, say so when you apply.
What does it cost?
Nothing during the pilot. There's no price yet because there's no billing yet — pilot kitchens use Tifflo free while it's shaped around how they actually work. When there is a price, you'll hear it from me before anyone else, and you won't be moved onto it without agreeing to it.
Do my customers have to install anything?
No. Your subscribers never touch Tifflo and never see it. They keep messaging you however they do now — WhatsApp, text, a phone call. Tifflo is the record you keep, not the channel they use.
How does the meal balance work?
The wallet counts meals, not money. Someone buys ten meals; every meal you deliver spends exactly one credit. A skip costs nothing — the credit simply stays. A pause costs nothing. The balance can't go negative, and orders are never generated for meals a wallet can't fund.
What if I'm not in the GTA?
Write anyway and say where you are. The software is timezone-generic and works anywhere, but the first pilot kitchens are in the Greater Toronto Area because I want to be able to sit in the kitchen while we set it up. If you're further out, I'll be honest about what I can and can't do for you.
How do I get my existing customers in?
I do it with you, by hand, before you switch over. Your dishes, plans, menu cycle and every subscriber's current meal balance go in together — at a cycle boundary rather than mid-cycle, so nobody's count is ambiguous on day one.
What happens after I apply?
I email you within one to two business days and we find twenty minutes to talk about your plans, your menu rotation and how you track balances today. Then I set your kitchen up and switch it on. Every pilot kitchen is configured by hand rather than through a signup form — deliberately, because it means your real plans and balances are in place before you run a single day on it.
Is my data mine?
Yes. It's your kitchen's data, kept separate from every other kitchen on the platform, and you can ask for a copy or ask me to delete it at any point.
Take on the first pilot cohort.
I'm taking on a small number of tiffin kitchens in the Greater Toronto Area — enough to build this properly around real kitchens, few enough that I can set each one up myself.
- Free during the pilot — no card, no trial clock
- Set up by hand, with your real plans and balances
- Your kitchen's data is yours, and you can take it out
This goes straight to my inbox — I read every one myself, and I'll show you exactly how Tifflo would run a kitchen like yours, including what's live now and what's coming next.
Shaheem · building Tifflo in Toronto