Tiffin services · CRM
Keep every customer, payment and leave day in one place instead of a notebook.
A CRM for a tiffin service is a customer record that holds the address, plan, payments, leave days and renewal date for each person. GullySales sets up a simple sheet or tool and a routine to keep it current, sized to a kitchen run by one or two people.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Last updated 14 Nov 2026.
For tiffin services
Where it usually goes wrong, and what we would do.
“The notebook breaks when the list grows”
A notebook works for fifteen customers and fails for forty. Payments are missed, leave days forgotten, a cancelled customer is still cooked for. The loss is small each time and adds up to a real amount.
“Renewal date is the most important field”
A tiffin plan ends on a date, and that date is the moment to ask for renewal. A kitchen that writes the date down can message before the plan ends. A kitchen that does not finds out when the customer is gone.
“Leave and diet notes change the cooking”
If a customer is away for a few days, no food should be packed. If another does not eat onion, the note must be in front of the cook. A record that reaches the kitchen each morning prevents waste and complaints.
“A heavy tool will not get used”
A cook with wet hands will not fill in a long form. The record has to be small enough to update from the phone in a moment. A simple sheet kept up to date beats a complicated system left empty.
What we do
What we deliver for tiffin services.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A customer sheet
Columns for name, address, phone, plan, start date, payment, diet notes, leave and end date.
Result: One sheet that shows every customer at a glance.
A morning cooking list
A view of the day's boxes, with the delivery order and the diet notes next to each name.
Result: A list you can print or read on the phone.
Payment reminder routine
A saved message and a list of who is due, sent from the same sheet.
Result: A list of customers whose payment is due.
Waiting list tab
Names of people waiting for a place, with the area and the date they asked.
Result: A queue you can work through when a place opens.
Customer-end note
Why each customer left, in their words, written when a plan ends.
Result: A column of reasons you can read together.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
The fields a tiffin kitchen needs to cook the right meals and renew the right plans.
- Name, number and delivery landmark
- Filled by the cook at the first message. It lets the delivery person find the door and the owner send a renewal.
- Plan, meals and days
- Lunch, dinner or both, and which days. It drives the cooking list for the next day, so it is the field the stove depends on.
- Diet rule or allergy
- Written in the customer's words. It is read before cooking, and must be changed when the customer tells you something new.
- Plan start, renewal date and amount paid
- Filled when payment arrives. It shows who is due to renew, and replaces the notebook where a missed date costs a month's money.
- Leave days
- Entered when a customer says they will be away. It stops cooking a meal no one will eat and gives the credit the customer expects.
- Reason for leaving
- Moved city, price, taste, delay or other. It is the only field that tells the owner what to fix.
Who it is for
This is written for these tiffin services.
- Home kitchens run by women for PG residents and students
- Tiffin services supplying working professionals in IT parks
- Regional tiffins, such as Gujarati, Marwari, Bengali, Kerala or Andhra meals
- Jain and sattvic tiffin services
- Diet and low-oil tiffins
- Tiffins for senior citizens living alone
- Hostel and mess tiffin suppliers
- Lunch-box suppliers delivering to offices and factories
- Dabba services that collect and return carriers
Before you decide
When this may not be the right fit.
- You have a handful of customers and remember each, so a sheet would add typing without telling you anything new
- The cook will not open a sheet during the cooking hours, and a record filled once a month is wrong by then
- You are not yet taking advance payments by a traceable method, so the record would hold amounts you cannot check
Before you decide
Agree the work. Know how to judge it.
CRM for tiffin services: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from tiffin services. Anything missing is noted in the written scope, with who will supply it.
- Your present notebook or contact list
- We need to read what you have, whether a notebook, a phone list or messages. Photographs of pages are fine. Without it, the sheet begins empty and fills as customers pay.
- A list of the plans you offer
- The sheet needs plan names, what each includes and the rules on leave. A page of notes is enough. Without it, the plan field stays free text, and renewal reminders cannot be matched to the plan.
- A phone or laptop that opens the sheet
- The record is only useful if you can open it with wet hands in the kitchen. A phone with the sheet saved is enough. Without that, the record is updated at night from memory.
- A rule for storing food needs
- Decide what you write about allergies and diets, and who sees it. A line in the sheet is enough. Without a rule, such notes are scattered across chats and a mistake in the kitchen follows.
- A backup person who can read the sheet
- If you are unwell or away, someone must be able to find the cooking list and the addresses. Name one person you trust. Without this, a day off stops the kitchen.
How it works
How the CRM work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Look at how the notebook works today
We sit with the notebook, the phone contacts and the payment messages you use now, and follow one customer through joining, payment, leave and renewal. You show us where you look things up and where you lose track. The record is designed around those exact lookups.
- 2
Choose between a sheet and a simple tool
For one or two people in a kitchen, a shared sheet serves better than software. We show you what a sheet holds and what a light tool adds, and you decide, with the cost of upkeep in view. A heavy tool that is not opened is worse than none.
- 3
Set the fields for each customer
Each customer gets address, plan, start date, renewal date, payment status, leave days and food notes. You decide which are compulsory. Food allergies and diet needs are recorded as notes for cooking, with a rule on who can see them.
- 4
Build the cooking list for the morning
From the record we draw a one-page view of who is eating today, any leave, any change of address and any diet note. You test it on a normal morning. If the list does not match what you cook, the fields are changed.
- 5
Set the payment and renewal reminder
A reminder routine lists those whose plan ends soon and those who have not paid. You decide the wording of each message. Cash payments get a step: note it at once, with a mark that it was cash.
- 6
Run notebook and sheet side by side
For a short period you write in both while we watch what goes missing. On a day you choose, the notebook stops. We then compare the record with the count of customers and renewals noted before, and fix any gaps.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Do I need paid software?
Is customer information safe in a sheet?
Can I store customers' food allergies in the sheet?
What if a customer pays in cash and I forget to note it?
Where should a customer's allergy note sit in the record?
How do I record a cash payment so it is not missed?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for tiffin services
Related work to consider.
Closest to this: leads and follow-up
Also for tiffin services
Or start from the overview: sales and marketing for tiffin services.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.