Cloud kitchens · CRM
A customer list is the asset a delivery app never gives the kitchen.
A CRM for a cloud kitchen is a simple system that records who ordered, what they ordered, how they came to the kitchen and whether they agreed to be contacted. GullySales sets one up around your direct orders, corporate accounts and tray enquiries, using a tool your team will actually open.
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 cloud kitchens
Where it usually goes wrong, and what we would do.
“The settlement sheet is not a customer record”
The aggregator's sheet shows orders and money. It does not show a customer's preferences, birthday, office or the complaint last month. Without a record of its own, the kitchen treats every returning buyer as new.
“Corporate accounts live in a manager's phone”
An office lunch account starts as a chat with one admin. If the manager leaves or changes numbers, the account's menu, price and timing details go with them. A shared record keeps the account with the kitchen.
“Too many fields kill the habit”
A form with twenty boxes is abandoned on a busy evening. A kitchen that records name, number, source, last order and consent, and nothing else, will keep the list current.
“Consent has to be recorded, not remembered”
When a customer says yes to messages at the bag card, that yes needs a date and a source beside it. Without it, the kitchen cannot show later that it had permission.
What we do
What we deliver for cloud kitchens.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A CRM set-up
A simple tool, such as a spreadsheet or an ordinary CRM, configured with the fields a kitchen needs and nothing more.
Result: Open it on a phone and add a contact in a few taps.
A customer and account structure
Separate views for direct customers, corporate accounts and tray enquiries, each with its own status steps.
Result: Each type of buyer has its own list.
A consent field and rule
A recorded opt-in with date and source, and a rule that only opted-in contacts receive offers.
Result: Filter the list by consent and see only people who agreed.
A data entry routine
Who adds a new contact, when and from which source, written so it fits the packing shift.
Result: A one-line instruction taped beside the counter.
A tidy-up pass
A review of duplicates, wrong numbers and old records, with a rule for removing anyone who asks to leave.
Result: A clean list and a note of what was removed.
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 cloud kitchen's record needs for consumers and office accounts.
- Brand ordered from
- Filled automatically or by the packer. Lets the kitchen see which brand a customer prefers and avoids sending the wrong brand's offer.
- Order source
- Filled by the person who logs the order. Marks the app, a call, a chat or a bag insert, so direct orders can be counted.
- Consent to be messaged
- Filled at the point the number is taken. Records the day, the channel and what was agreed, so a message can be sent without doubt.
- Office account and floor
- Filled by sales. Holds the company, the contact, the delivery floor and the headcount, which the kitchen needs for a standing order.
- Diet and allergy notes
- Filled when the customer says so. Lets the packer and the kitchen avoid a dish the customer cannot eat.
- Complaint and what was done
- Filled by whoever handled it. Gives the next person the history before they reply to a repeat customer.
Who it is for
This is written for these cloud kitchens.
- Multi-brand cloud kitchens
- Single-brand delivery-only restaurants
- Biryani, North Indian and South Indian delivery brands
- Dessert and bakery cloud kitchens
- Healthy meal and diet food kitchens
- Corporate lunch box kitchens
- Shared kitchen operators renting space to brands
- Cloud kitchen franchises
Before you decide
When this may not be the right fit.
- Orders come only through an aggregator, and you hold no customer details you have permission to keep.
- Nobody will update a record after a delivery, so the list would be out of date after a few orders.
Before you decide
Agree the work. Know how to judge it.
CRM for cloud kitchens: 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 cloud kitchens. Anything missing is noted in the written scope, with who will supply it.
- Every list of customers you keep
- Bring the phone contacts, sheets, notebooks and exports. Do not tidy them first. Whatever is left out of the import stays outside the system, and the team will keep two records.
- A way to show where each number came from
- For each list, tell us how the numbers were collected: ordered directly, left on a card, given by an office, or shown on an app. Numbers with no known origin are held aside. Without this, the consent field starts blank and nothing can be used. If origins are mixed within one list, tell us which part came from which route, and we split it.
- The names of office accounts and their terms
- List the offices and hosts you serve on agreed terms, with the contact, the usual order and how they pay. A page from a notebook is enough. Without it the corporate accounts begin empty, and the manager's phone remains the only record.
- One person who will make the entries
- Name who records each order or enquiry. It can be the cashier or the manager. Without a named person the CRM is built and not used, because during a busy evening everyone assumes someone else will do it. A shift pattern for the cashier or manager, with someone named for each shift, completes the picture.
- Your view on what the CRM must never hold
- Decide whether payment details, addresses of private homes or health information are kept out, and say where any necessary detail lives instead. We write it into the setup. Without a rule, someone will paste sensitive details into a note.
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
Gather the lists you keep in different places
We ask where customer names and numbers are today: the phone book, a notebook, a cashier's sheet, the app exports and the manager's contacts. You open each for us. We list what each holds and how reliable it is, which tells us what can move into one record. We also note which list was last updated, so that the newest numbers win when two lists disagree about the same person.
- 2
Choose a tool the team will really open
We compare a simple CRM and a shared sheet against the habits of your staff, and recommend the one they will use during a busy evening. You decide, and you make sure the subscription, if any, is in the kitchen's name. The tool should fit the phone.
- 3
Decide what each record must hold
With the manager we list the few facts worth keeping for a customer or an office: name, number, brand, how they joined, consent, last order and next step. You cut every field that nobody would fill in. A long form kills the habit.
- 4
Set up accounts for offices and party hosts
For corporate and bulk buyers we set up an account holding the office, the person who decides, the person who orders and the terms agreed. You supply the details. The account stays in the CRM when the manager who knew the buyer leaves. The structure also records who in the office is allowed to change an order, so a late amendment does not come from a stranger.
- 5
Record consent and import the clean contacts
We add a consent field with the date and how it was given, then import only the contacts with a clear permission. Others are held aside. You approve the import. The old lists are marked as closed once the import is checked against a sample.
- 6
Train the team on the three entries that matter
We show the staff the three entries to make after an order or an enquiry, using real examples from your kitchen, and watch them do it. You check the first few records. We then fix the form wherever someone got stuck.
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 we need paid CRM software?
Can the CRM pull orders from Zomato or Swiggy?
Who owns the customer data?
Can we keep the phone numbers that an aggregator gives us?
Is a sheet enough for a small kitchen?
How do we keep staff from skipping entries?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for cloud kitchens
Related work to consider.
Closest to this: leads and follow-up
Also for cloud kitchens
Or start from the overview: sales and marketing for cloud kitchens.
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.