Skip to content
GullySales

Corporate catering companies · CRM

Keep each office's contract date, headcount and decision-maker where a new manager can find them.

A CRM for a corporate catering company is the record of every office you serve or have quoted: who orders, who approves, how many eat, when the contract ends and what was said at the last tasting. GullySales sets up that record so a renewal date or a lapsed event client becomes a task with a name against it, not a memory.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Catering staff check prepared meals in an institutional kitchen

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 corporate catering companies

Where it usually goes wrong, and what we would do.

  • “The renewal date lives in the owner's head”

    A cafeteria contract ends on a set date. If only the owner knows it, the first sign of trouble is a notice that another vendor has been appointed.

  • “What the panel said at the tasting is in one person's notebook”

    Somebody said no onion on Thursdays and somebody else wanted a south Indian counter. When the salesperson leaves, so do the notes, and the next tasting starts from nothing.

  • “Event and contract clients share one sheet”

    A seminar lunch and a daily cafeteria need different fields and different follow-up. In one long sheet, a lapsed event client is never noticed.

What we do

What we deliver for corporate catering companies.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. An account record for every office

    Company, building, the person who orders, the one who approves, the accounts contact, headcount range, meal types and contract end date.

    Result: A new salesperson can take over an account on the first day.

  2. Separate pipelines for events and for contracts

    Event enquiries tracked from date and headcount to quote and booking, and contract enquiries from tasting to agreement, with their own stages.

    Result: Each kind of enquiry is followed up the way it is bought.

  3. A contract calendar with end and notice dates

    Every daily-meal agreement with its end date and the last date for renewal talks, read from the signed paper, with a reminder set ahead of each.

    Result: The renewal call is a task, not a worry.

  4. Tasting and visit notes

    Who attended, what was praised, what they asked to change and the date decided, entered straight after the tasting.

    Result: The next tasting for the same panel begins with what they said.

  5. A complaint and correction log

    Each complaint with the meal, the cause, the fix and whether the client was told it was fixed.

    Result: A pattern shows in the log before it shows in a lost contract.

  6. Enquiry and pipeline report

    Enquiries by source, tastings, contracts won and renewals due, against the baseline recorded before work started.

    Result: The owner sees where each account stands without asking around.

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.

What to record, and when

What a corporate caterer should record about each office, and whether it needs software yet.

Who orders, who approves, who pays
Record three names per company: the admin or facilities person who orders, the head who approves and the accounts contact who pays. Most lost accounts changed the second name.
Meal type, headcount range and service times
Write what you serve, such as lunch, tea or night meals, the usual headcount and the hours. When the headcount drifts you notice before the client raises it.
Contract start, end and notice date
Enter the end date and the last date for renewal talks as read from the signed agreement. Set a reminder well before it, in your own diary or system.
Tasting and visit notes
After each tasting, record who came, what was praised and what they asked to change. The next one for the same panel then starts from what they said.
Complaints and what changed
Log the meal, the complaint, the cause and the fix. A pattern such as cold rice on Mondays appears in the log long before it appears in a renewal.
Do you need software yet?
A sheet with one row per office works for a few contracts if one person owns it. Move to a CRM when sales, kitchen and accounts all need the same history, or when a salesperson's phone holds half the record.

Who it is for

This is written for these corporate catering companies.

  • Cafeteria and canteen operators for offices
  • Daily lunch-box and tiffin suppliers to companies
  • Conference, seminar and offsite caterers
  • Boxed-meal caterers for training programmes and client visits
  • Night-shift and late-working meal suppliers
  • Caterers to co-working spaces and managed offices
  • Pantry, tea, coffee and snack suppliers for offices

Before you decide

When this may not be the right fit.

  • You serve a handful of offices and one person remembers every contract date, so a CRM would add typing and nothing more.
  • Nobody will log a tasting or a complaint after the visit, and the record would be wrong from the start.

Before you decide

Agree the work. Know how to judge it.

CRM for corporate catering companies: 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 corporate catering companies. Anything missing is noted in the written scope, with who will supply it.

Signed contracts with end and notice dates
The contract calendar is only useful if its dates are right. Bring the signed contracts or letters of award, with the term and the notice period. If one is an email exchange, forward it. Dates we cannot confirm are marked as unconfirmed so nobody relies on them at renewal.
Notebooks and sheets with tasting notes
Panel comments, objections and promises made at tastings carry great value in the system. Bring the notebooks, sheets or phone notes where they sit, even if untidy. Without them the records begin with names and dates but no memory of what each office was told.
Who pays and who signs
For each office, write who approves the invoice and who signs the contract, which may be different people from the facilities contact. A rough list is enough. When this is missing, a renewal letter goes to the person who eats the lunch and not to the person who decides.
A complaint and correction history
Gather what you recall of the complaints in the last year and how each was fixed, from supervisors' messages or the account person's notes. They go into the log linked to each office. If none was recorded, we begin the log now and mark earlier months as unknown.

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. 1

    Collect each office from the owner's memory

    The details of the accounts live in your head, a notebook and an old spreadsheet, so we sit with you and write each office down: the decision-maker, the facilities contact, the headcount, the start date and the date the contract ends. We mark the gaps. The result is a first list that you correct, and it is the base for the system.

  2. 2

    Split event and contract pipelines

    An event client and a contract client move through different stages, so we draw two pipelines with you. Events run from enquiry to quote, tasting, booking and after-event note. Contracts run from enquiry to panel tasting, trial, signing and renewal. Each stage is named in your words, and any stage no one uses is removed.

  3. 3

    Set the fields a new manager needs

    A new account manager should find the headcount history, the dishes the panel liked, the person who pays, the notice period and open complaints on one screen. We build the record with those fields and no others. You test it by asking a supervisor to find the contract date for a named office.

  4. 4

    Enter the tasting and visit notes

    We go through the notes from tastings and kitchen visits that sit in notebooks and phones, and enter them against the right office with your team. You supply what the panel said, who objected and what was promised. The notes are kept on the account, so a change of salesperson does not remove them.

  5. 5

    Compare the pipeline with your last contracts

    We check the pipeline against the enquiry and contract count recorded before the work began, to see whether every live enquiry has an owner and a next date, and whether the contract calendar matches the signed papers. You decide which fields to drop and which view you will open each morning.

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.

  1. 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.

  2. Step 2

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. 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.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Is a spreadsheet enough for a small list of offices?
Yes, if one person owns it and every account has the same columns. Move when two or three people need the same history at once, or when you cannot find last year's notes at renewal time without asking someone.
Our supervisor will not update the record. What then?
Attach the update to something the supervisor already does, such as the headcount confirmation or the end-of-service call, and keep the fields few. Have the owner open the record whenever an account comes up; a record nobody reads is not kept.
Client conversations are on WhatsApp. Do we copy them over?
Copy only what changes the account: a headcount change, a complaint, a decision. Note the date and the outcome, not the chat. Keep the conversation on the company number so the history stays with the business.
Whose record is it when a salesperson resigns?
The company does, so contacts and notes belong in the company's own system, not a personal phone. Keep logins in the company's name and remove access on the last day. Client staff's details are personal data, so keep only what you need.
Do our kitchen supervisors need to use the CRM?
Only for a few things, such as logging a complaint or a headcount change on an account, and we make that a short form on a phone. Supervisors should not need to learn a full system. The account manager and the owner use the pipeline and the contract calendar. If supervisors find even the short form heavy, we let them send a message to a coordinator, who enters it on their behalf.
Can we keep event clients and contract clients in the same list?
They can share one list of offices, but they must not share a pipeline. An event client who attended a seminar lunch is a possible contract client, and the record should show that, but the stages, follow-ups and reports are different. We tag each account as event, contract or both, and keep the two pipelines apart so that a contract renewal is not buried under a pile of one-day quotes.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.
What do you need from us?
Your brief, and a conversation. After that, access to whatever this work touches, such as your website, your accounts or your enquiry record, and time with the people who handle your enquiries.

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.