Skip to content
GullySales

Food trucks · CRM

One sheet that remembers every organiser, date and plate count.

A CRM for a food truck is a simple record of the people who enquire, the events they plan and where each booking stands. GullySales works on setting up a tool light enough to use between orders, rather than software that stays closed.

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

Realistic editorial illustration of restaurants at work in India

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 food trucks

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

  • “The calendar and the enquiries live in different places”

    A date on a phone calendar, a message in Instagram and a quote in a note app. When the question is whether the truck is free on a Saturday, nobody can answer without searching three places.

  • “A repeat organiser is worth remembering”

    The brewery that booked in the rains, the school that hired for its fair and the planner who sent two weddings are your easiest next bookings. If their details are lost, you start again with a stranger.

  • “A heavy tool will not be opened”

    A truck owner at the fryer does not log in to an enterprise system. Whatever you use must work on a phone, take a minute to update and look obvious. If it does not, the old habits return.

  • “Quotes without a record cause arguments”

    When an organiser says they were promised a rate or a menu and nothing was written, the owner has no answer. A note of what was offered, when and to whom settles it.

What we do

What we deliver for food trucks.

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

  1. A simple enquiry record

    Name, organisation, date, venue, crowd size, source, quote sent and status, held in one sheet or light tool.

    Result: Every enquiry has a row and a status.

  2. A free-or-booked calendar linked to the record

    Confirmed dates, held dates and blocked days shown in one view.

    Result: You answer availability without searching messages.

  3. A list of past organisers with notes

    Who booked, what was served, how it went and whether to approach again.

    Result: Your warmest contacts are always at hand.

  4. Stages for each enquiry

    A short set of steps from first message to quote to confirmed to served, so nothing sits unlabelled.

    Result: You see which enquiries need a nudge.

  5. A regular-customer list kept with consent

    Numbers collected at the window with permission, stored apart from event contacts.

    Result: You know who has agreed to hear from the truck.

  6. A short guide for whoever updates it

    One page on how to add and change a row, so a helper at the hatch can do it.

    Result: The record does not depend on one person.

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

A truck needs a short record, not a sales database.

Event date and hold status
Filled by whoever takes the enquiry. It shows at a glance which dates are held, booked or released.
Venue and stand-spot notes
Filled after the site visit or call. It records the gate, power point and parking approval for the next booking at the same place.
Plates and menu quoted
Filled when the quote goes out. It settles any argument later about what was agreed and at what rate.
Approver name and role
Filled from the first conversation. It tells you whom to chase when the writer is not the one who decides.
Regular's consent to messages
Filled at the window by the helper. It shows which numbers may be sent tomorrow's location and which may not.

Who it is for

This is written for these food trucks.

  • Burger, roll and sandwich trucks at office gates
  • Biryani and rice-bowl trucks serving events
  • Coffee, tea and cold-drink trucks
  • Dessert, waffle and ice cream trucks
  • South Indian tiffin and filter coffee trucks
  • Dosa, chaat and street-food trucks
  • Pizza and wood-fired oven trucks
  • Trucks parked at breweries, malls and weekend markets
  • Trucks hired for weddings, school fairs and corporate days

Before you decide

When this may not be the right fit.

  • Nobody will open the record after a service, and a sheet that is never filled gives a false picture of the calendar.
  • You take only walk-up sales and no event bookings, so a plain notebook covers what you need to remember.

Before you decide

Agree the work. Know how to judge it.

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

The phone calendar and booking chats
The record starts from what you already track. Show the calendar and the chats where bookings were made. If dates sit only in memory, the first load is incomplete, and clashes surface later.
A decision on how long a date is held
Organisers ask you to hold a date while the committee decides. Settle how long you will hold and what makes it firm, such as an advance. Without a rule, calendars show dates held for nobody.
A list of past organisers with a note each
A line on each organiser, such as what they booked and whether they paid on time, is enough. Without it the repeat organiser has to be rediscovered from old chats.
A list of regulars who agreed to messages
Only customers who agreed to hear from you go on the list. A name and number with a note of how they agreed is enough. Without consent, the regular list stays empty.
A person who updates it after service
Name who writes the day's enquiries into the record, and when. If nobody is named, the record is filled in bursts and the calendar cannot be trusted.

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

    Follow one event from message to payment

    We trace a real booking with you: the first message, the menu sent, the date held, the advance received, the event day, the thank-you. You show where details are kept now, in a chat, a notebook or a phone calendar. This gives us the stages that the record must follow.

  2. 2

    Choose the fields for an enquiry

    We settle a short list: organiser, contact, date asked, headcount, venue, menu chosen, rate quoted, stage. You strike out anything you will not fill between orders. A long form stays closed during service, so we keep the list small.

  3. 3

    Put the calendar and the record together

    We link the free-or-booked calendar to the enquiry record, so that a date held shows up in both. We test with three imaginary enquiries for the same weekend. You decide how long a date is held for an organiser who has not paid. The rule is written next to the calendar, along with what the helper says to a second organiser who asks for a date that is already held, so that nobody invents an answer at the window.

  4. 4

    Bring in past organisers and regulars

    We enter past organisers with notes on what they booked and what they liked, and add regular customers only where they have agreed to hear from you. You check the entries. Anyone who asked you to stop messaging is marked, and not contacted. Organisers who paid late or changed the headcount at the last minute get a note, since that detail changes how you quote them next time.

  5. 5

    Use it for a real fortnight of enquiries

    You or your helper use the record on live enquiries while we watch what is slow. We adjust fields that get skipped. You decide whether the tool is light enough to keep open. If it is not, we reduce it again.

  6. 6

    Hand over a one-page guide and name the owner

    We write a short guide for whoever updates the record, and you name who owns the data and who may export it. We then read the record against the figures from before: enquiries logged, dates held and bookings confirmed. We also look at how many enquiries had a headcount and a venue written down, because a record with gaps in those two fields cannot support a quote.

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.

Do we need paid CRM software?
Not at the start. A well-built sheet or a free tool is enough while enquiries are few. Move to a proper CRM when the sheet is hard to manage, not before.
Who should update the record?
Whoever answers the message, at the moment they answer it. If that is the owner at the hatch, the update must take under a minute on a phone or it will be skipped.
Can we store customer numbers freely?
Keep only what people agreed to share, store it safely and do not pass it to others. Data protection rules apply to personal information, so check with your adviser on what you may collect and how.
What do we record about a customer who asks us to stop messaging?
Mark the number as opted out and never message it again. A visible stop flag protects the customer and the truck, because a loyal regular who feels pestered leaves. Keep the flag in the same sheet as the number, so no helper can miss it.
Can the record live in a spreadsheet?
Yes, and for a single truck a well-kept shared sheet can be the right size. We design the columns, the stages and the calendar link so that it works as a record and not as a pile of notes. If bookings grow beyond what a sheet can handle, we help you move to a light tool. The deciding point is whether the person at the truck will open it between orders, and we choose the tool that passes that test.
What do we do with a customer who asks to be removed?
Remove the number from every list the same day and mark the record so nobody adds it again. Do not send a last message to confirm. We add a field called do not contact, and the follow-up rules read it. If the customer is also an organiser with a booking, handle the event messages needed for the booking and nothing else. Keep a note of the date of the request in case it is ever questioned.
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 long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
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.

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.